The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
DavidS877 said:
European typing detected.
Click to expand...
>implying he didn't knew already
DavidS877 said:
GPS isn't that hard
Click to expand...
>starts to list an entire electronic project just to get local NTP running
See, that's what I meant. With Pi-Hole it's a matter of maybe less than half an hour of command line fuckery in a new Proxmox container to have a local recursive DNS server with filtering running. No need to come up with a hardware add-in to get it working, which is why having Pi-Hole is trivial and everyone should have it, while local NTP is much higher on the autism spectrum.
 
Ferryman said:
Alright guys, I need some input: FreeBSD or OpenBSD? Gut says OpenBSD cause no CoC cancer and much higher focus on cleanliness & security, but then FreeBSD is bigger, has more packages, and is allegedly easier to configure and troubleshoot. I have never used a BSD system before, so thoughts & advice are appreciated. The host machine will be an X230, which I'm pretty sure should have good hardware support for both.
Click to expand...
OpenBSD is more focused on security, so you're gonna have to do things like enable simultaneous multi-threading (off by default) to get a reasonable desktop experience. All BSDs have good documentation though so it'll probably just be a matter of Reading The Friendly Manual.

As others have said, FreeBSD is closer to Linux. Unsure about the performance of Wi-Fi (cards?) on a X230, but using it on a semi-recent laptop resulted in very slow internet speeds.

The init system on both is just scripts, so they're a bit slow when it comes to booting. No complaints otherwise.
 
Slav Power said:
No need to come up with a hardware add-in to get it working, which is why having Pi-Hole is trivial and everyone should have it, while local NTP is much higher on the autism spectrum.
Click to expand...
I can't see why you'd need your own atomic clock for it, though. Why not just use WWVB as the source for the NTP server? (It also has its own NTP server but if you're doing it locally presumably you have some specific reason for not wanting to use that.)
 
i440BX said:
But Wayland is removing the freedom of customizability and things a program can do
Click to expand...
I wouldn't say that would be one of my criticisms of wayland. You can do as much customization as you could on x11. My criticism would be it doesn't have the ecosystem x11 does still. Not really too surprising since its only now that people are actually starting to move over. And because it doesn't have the ecosystem still, you end up running into things you can't do with it people were able to with x11.

For myself. I actually don't have any problems running pure wayland, no xwayland. For me nothing I use is actually broken on wayland. And the x11 specific things I used I was able to replace with wayland native versions. Like all my dmenu scripts, things along those lines. I'm able to just move back and forth between x11 and wayland. Without any real issue, now that I've found everything I needed on the wayland side.

Ferryman said:
Alright guys, I need some input: FreeBSD or OpenBSD? Gut says OpenBSD cause no CoC cancer and much higher focus on cleanliness & security, but then FreeBSD is bigger, has more packages, and is allegedly easier to configure and troubleshoot. I have never used a BSD system before, so thoughts & advice are appreciated. The host machine will be an X230, which I'm pretty sure should have good hardware support for both.
Click to expand...
If your hardware works with openbsd. Probably pick openbsd.
 
Hypothetical: if you were to unhook all of the systemd components except the init system, put them in a separate core package outside of the init process, and then move Poettering away from both, would it be accepted? PID 0 no longer runs absolutely everything, but absolutely everything is still standardized in one conglomerated package, which is pretty much the only reason systemd has became a thing.
 
Betonhaus said:
can i rsync /home to a different drive and rsync -avP
Click to expand...
This is potentially a big footgun depending on whether your packages can handle back-and-forward compatibility of config data. Watch the versions closely.

Slav Power said:
if you were to unhook all of the systemd components except the init system
Click to expand...
Most reasonable post-systemd inits do this. S6 and runit do, at least. The problem is the entrenchment of systemd, that it's designed by idiots who are hostile to multiple use cases. It's better to dogfood the alternatives. I love systemd-nspawn though. It could be an isolated program, no need for pid 1 stuff.
 
analrapist said:
This is potentially a big footgun depending on whether your packages can handle back-and-forward compatibility of config data. Watch the versions closely
Click to expand...
I was able to shrink my / partition to 50gb, create a new partition and rsync /home to it and add it to Linux Mint's fstab and everything works, I'll try and see if it still works after installing Solus tonight
 
Slav Power said:
Hypothetical: if you were to unhook all of the systemd components except the init system, put them in a separate core package outside of the init process, and then move Poettering away from both, would it be accepted? PID 0 no longer runs absolutely everything, but absolutely everything is still standardized in one conglomerated package, which is pretty much the only reason systemd has became a thing.
Click to expand...
I don't know much about SystemD, but the complaint that I've heard from people was that it doesn't adhere to the Unix philosophy, so if it was just an init system without a bunch of other unrelated stuff (including a sudo equivalent that nobody uses despite it being on most systems) I think few people would be bothered by it.
 
volatile puar said:
I don't know much about SystemD, but the complaint that I've heard from people was that it doesn't adhere to the Unix philosophy, so if it was just an init system without a bunch of other unrelated stuff (including a sudo equivalent that nobody uses despite it being on most systems) I think few people would be bothered by it.
Click to expand...
I wouldn't say that's as true as people make it sound. It still is technically a modular set of programs that each do one thing. The only way it doesn't adhere to the unix philosophy is it's not portable outside of Linux. But you absolutely can still swap in other things instead of using the systemd programs with it. I would say it does about as much as things like the coreutils. Where it's one thing but a bunch of smaller programs that each do their own thing, that can be swapped out.

As far as functionality. I actually think systemd works well. My problems with it have nothing to do with how it works, and it not sticking to the unix philosophy.

Some good gnome hate fuel.
 
You must log in or register to reply here.
Back
Top Bottom