By mounting the binary over, I mean something like a bind mount. But in your case of a wrapper script, it doesn’t apply indeed. Though in this case I would simply name the script steam-launcher and call it a day 🙂
Having multiple executables with the same name and relying on $PATH and absolute paths feels hackish to me, but that’s only a matter of preference at this point.
I’m not saying we should get rid of $PATH right now. My point is that it was created to solve a problem we don’t have anymore (not enough disk capacity), but we still keep it out of habit.
As a reminder, the discussion is about what should be rewritten from scratch in linux. And IMO, we should get rid of $PATH as there are better options.
Today’s software would probably break, but my point is that $PATH is a relic from ancient times that solved a problem we don’t have anymore.
You missed my point. The reason $PATH exists in the first place is because binaries were too large to fit on a single disk, so they were scattered around multiple partitions (/bin, /sbin, /usr/bin, etc…). Now, all your binaries can easily fit on a single partition (weirdly enough, /usr/bin was chosen as the “best candidate” for it), but we still have all the other locations, symlinked there. It just makes no sense.
As for the override mechanism you mention, there are much better tools nowadays to do that (overlayfs for example).
This is what plan9 does for example. There is no need for $PATH because all binaries are in /bin anyways. And to override a binary, you simply “mount” it over the existing one in place.
$PATH shouldn’t even be a thing, as today disk space is cheap so there is no need to scatter binaries all over the place.
Historically, /usr was created so that you could mount a new disk here and have more binaries installed on your system when the disk with /bin was full.
And there are just so many other stuff like that which doesn’t make sense anymore (/var/tmp comes to mind, /opt, /home which was supposed to be /usr but name was already taken, etc …).
+1 on the Gazzew U4. I just swapped from browns to it and I’m never going back ! They’re more tactile and much more silent.
endlessh was pretty cool and a more modern version is even better ! I’ll give it a shot !
On a side note, I found a way to trap HTTP connections too while working on my cyb.farm project. The go implementation is ridiculously simple: tarpit.go. It works by providing an endless stream of custom headers to the client, which it is supposed to ingest before getting to the content itself.
I find the config syntax cleaner.
Switches indeed ;)
Both voyager and moonlander are prebuilt, right ? I like the voyager, but might like just a few keys under the thumb compared to my current planck layout.
Thanks for the suggestions !
It’s not about the cost, it’s more about my current situation, storage space, and besides this specific use-case, I have no use for it (and I dont like buying stuff I don’t use).
Crux. Simplest package building system out there, and the core is just out of the way completely, giving you the keys to setup your system just the way you want it.
Keeping the source IP intact means you’ll have troubles routing back the traffic through host B.
Basically host A won’t be able to access the internet without going through B, which could not be what you want.
Here’s how it works:
On host A:
On host B:
This should do what you need. However, if I may comment it out, I’d say you should give up on carrying the source IP address down to host A. This setup I described is clunky and can fail in many ways. Also I can see no benefits of doing that besides having “pretty logs” on host A. If you really need good logs, I’d suggest setting up a good reverse proxy on host B and forwarding it’s logs to a collector on host A.
OpenBSD is the most pleasing expérience I’ve had with an OS. It’s fully contained and has all the tools you need without needing to install anything (eg a DNS, HTTP, SMTP servers, a proxy, a good firewall). All config files look alike and use the same keywords for the same things, making it straightforward to configure everything.
And regarding RAID 1, I’ve never done it myself, but it totally works out of the box (as well as full disk encryption).
OpenBSD for all of them.
Void linux.
I used arch for a couple years, then crux for over 10 years, so I though Void would be a great distro when the systemd drama occured. Tried that, and noped the hell out of it…
For style points at the office.
Or xantfarm for the other times of the year !
There are online service that can do it for you. Check “IPv6” in the glossary.
Right now overlays requires elevated privilèges, but ideally it shouldn’t. Rewriting the Linux kernel to implement per user namespaces like plan9 does would allow unprivileged actions from any user (just like if any user was sitting in a container, overlayed from the base system).
I know we’re not there, and that’s not the direction development is going, but this thread is about dreams, right ? 😉
About the XDG specs, they serve a totally different purpose so they’re out of the discussion IMO. I’m not advocating against env variables. Just
$PATHwhich is a workaround as I see it, but your mileage may vary. As for your “issue” with steam, of course this is the best way to solve it. Because of today’s OS limitation. My point is that with a better designed namespacing implementation, there would be more elegant solutions to solve it (and would get rid of the need to useLD_LIBRARY_PATHtoo, or literally any*_PATHenv variable)