ok then how do i access [2b00:13c0:47:1422::5]:7236 through a file?
i don't think that's possible
only on plan9
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
ok then how do i access [2b00:13c0:47:1422::5]:7236 through a file?
i don't think that's possible
only on plan9
echo hello > /dev/tcp/2b00:13c0:47:1422::5/7236

Can confirm; user is file too
Source: user
Ok you got me with this one.
Btw the mitochondria are the powerhouse of the cell.
It makes more sense when you realize that it's not that everything is files it's that everything can be treated as a file. There are other APIs to interact with things, but everything can be interacted with as if it was a file. It doesn't seem as bonkers like this.
Everything is computer.
Exactly. A file is really just a way to understand a collection of bits. So saying everything is files is like saying everything in computers can be described as sets of bits, which is not a terrible heuristic.
It's like saying everything is a wave IRL.
Especially the particles
Files don't actually exist once you dig down
Bro stop digging I need those files to keep existing
Yeah, it sort of depends on the definition of the word file. "File" in the sense that it can be interacted with like a file versus "file" in the sense that it's data on a disk. But then, if you're really thinking about it, data on a disk isn't a file, it's data, and we can just interact with it like a file.
Welcome, brother. But remember that they must walk the path themselves or they will never reach true understanding.
π€―
In Windows land, it's HANDLEs...which is typedef void* HANDLE IIRC
Generally speaking, a handle is an opaque reference to an os object; the typedef here makes that clear. Linux uses the same general concept as well, though file objects are typically referenced through file descriptors rather than windows style handles.
Stages of POSIX enlightenment:
Most people stop at stage 2, stage 3 hits when you decide to write a filesystem, stage 4 when you've finished your first filesystem. Stage 5 is when you start working on kernel internals. No one can tell you how to reach stage 6, you must discover it for yourself.
true enlightenment: everything is a string over an IO socket
But are sockets not files?
files are named sockets ποΈ
/dev/null sez nothing is also a file
Asking for a friend.
If you can recognize "nothing" then "nothing" must be something right? So if nothing is a file, because /dev/null says so, then nothing MUST be something to be a file. And therefore /dev/null can't be nothing.
Or do I just need more tea? Or maybe whisk(e)y?
The word "nothing" isn't itself nothing. It is something used to describe nothing.
The word "nothing" is the English word describing the concept of nothing. And I have to use the word to describe the concept. So yes, you are correct the word is itself "something". So that is probably one point for "nothing" to not exist.
I have now consumed 3 cups of tea. And my head now hurts from thinking about nothing. I should never have stepped into this post.
Unfortunately, no one can be told what a file is. You have to see it for yourself.
This is your last chance. After this, there is no turning back. You take the blue pill - the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill - you stay in Wonderland and I show you how deep the file system goes.
I feel like it's more of a "If I tried to tell you what this was, you wouldn't believe me" than a "I am physically incapable of explaining the idea that you're plugged into a computer".
Am I a file?
In the end, we are all files. We have our read()s and write()s, in in our time we play many offsets.
Hope your name isn't Peter
Can you read me?
"How can files be real if the filesystem isn't real?" - Jaden Smith (probably)
You'll know you've reached stage 6 when you seriously start considering running Plan 9 as a daily driver
Yep, takes a moment to wrap your head around but the longer you read linux/unix documentation, the more it makes sense why it is the case.
tldr: it's to have nicer, less complicated I/O operations
it enables just having two API calls: read() and write() to do everything