3 ms·
The ctl file also lets you control other connection settings, such as keep alive. It would also be unfortunate to run ls in /net/tcp and dump the entire IPv4/6
by ddevault 4y ago
The ctl file also lets you control other connection settings, such as keep alive. It would also be unfortunate to run ls in /net/tcp and dump the entire IPv4/6 space into your terminal.
- jagged-chisel 4y agoNot sure I buy that last sentence. Why would the system populate these directories with anything other than a) what’s configured to be assigned to the system, and b) what the caller requests to be created by simply opening a specific path? Sure, you could script opening each address of the entire address space and have an unfortunate situation, but you don’t get that by default when you simply query what exists. That said, it’s been a veeeery long time since I tried out Plan9 and Inferno.
- ddevault 4y agoYeah, you could do that, but it's a bit magic innit?
- jagged-chisel 4y agoEverything is a file. Dumping magic strings in these “files” causes stuff to happen … Magic indeed.
- boris 4y ago> The ctl file also lets you control other connection settings, such as keep alive. Yes, though this could have been achieved with a bunch of sysfs-like entries under /net/tcp/127.0.0.1/80/<port>/ with the added benefit of being easily discoverable. > It would also be unfortunate to run ls in /net/tcp and dump the entire IPv4/6 space into your terminal. A reasonable semantics here would be to only list hosts to which there are active connections.