I once ran ‘chown -R root:root /’ in a misguided attempt to solve some permissions issues I was having. 0/10, do not recommend. It turns out a lot of system things aren’t root owned…
Running a stupid command and learning from it is part of the learning process.
You got the basic idea from other posters, but there’s also a lot of weird crap in there as well.
Basically you only need multiple IPs when dealing with services that only really operate on “well known ports”. DNS and SMTP being the usual culprits. For most home users there this is no big deal - even if you wanted to host those services it’s unlikely that you would need more than one ip to do so. HTTP solved this in '97 with HTTP/1.1 which allowed for host headers, which let’s a single server host multiple sites.
This isn’t something new that nginx solved. 😂
By “modern” do you mean “the late 90s”? HTTP 1.1 was adopted in '97 and allowed for the host header. NAT and port forwarding have been around since '94 - 2000ish.
Many services worked on any ports at the time as well. SMTP and DNS are probably the only ones that were (and remain) difficult to run on non-standard ports.
I guess that’s “a lot simpler” than 6 lines of config?
Kids seem to think host name based routing is "new’… It worked fine in the 2000s with Apache.
The trackpad is head and shoulders above anything I’ve ever used. For me, that’s worth the price of admission alone.
I always find this argument odd - I absolutely hate Mac touchpads. Maybe I’m just too used to non-apple hardware or something. Not arguing with you, just pointing out that this may not be a “bonus” for everyone.
It scanned a large amount of text and found something.
How hilariously reductionist.
AI did what it’s supposed to do. And it found a difficult to spot security bug.
“No big deal” though.
Jesus Christ, it would be fewer steps to install Debian and then rust + vscodium.
It’s not uncommon to have your Dockerfile curl https://host/file.tar.gz and then tar xvf file.tar.gz into the filesystem somewhere.
You don’t want to use snaps in docker containers. They need systemd and stuff that are going to be a real pain to get working.
Generally speaking I would avoid combining critical networking infrastructure with other services. Just from a reliability standpoint.
Let your router be just a router. Simple = reliable.
“I use Nix, btw”
You say “The Windows Memory Subsystem” not “The Windows Subsystem for Memory”.
Windows Linux Subsystem would likely be most clear.
I build my infrastructure with the terraform, Ansible and helm charts. The code is it’s own documentation as well as comments in that code explaining why I’ve done things if it’s not obvious.
That very much depends on what you want it to do (what is “everything”) and how many users you have.
Maybe a limited number of skips per hour or something.
It’s very annoying that the community hasn’t standardized on an approach for proxy settings.
OP stated that a VM is not feasable because of ressources on the PC.
I very much doubt that is true. Most standard issue system these days should be able to run an emulator well enough to run iTunes.
About $5USD on Amazon.
ctrl+a and ctrl+e are from Emacs.