Imagine if all the people who prefer systemd would write posts like this as often as the opposition. Just use what you like, there are plenty of distros to choose from.
Imagine if all the people who prefer systemd would write posts like this as often as the opposition. Just use what you like, there are plenty of distros to choose from.
Wireguard runs over UDP, the port is undistinguishable from closed ports for most common port scanning bots. Changing the port will obfuscate the traffic a bit. Even if someone manages to guess the port, they’ll still need to use the right key, otherwise the response is like from a wrong port - no response. Your ISP can still see that it’s Wireguard traffic if they happen to be looking, but can’t decipher the contents.
I would drop containers from the equation and just run Wireguard on the host. When issues arise, you’ll have a hard time identifying the problem when container networking is in the mix.
You install the Google services and Play store from the gOS Apps application, then use them like normal.
Behind the scenes they run in the sandboxed environment, but to the user it makes no difference.
resolvectl flush-caches
just in caseLook at resolvectl dns
to check there’s no DHCP-acquired DNS servers set anymore
If you use a VPN, those often set their own DNS servers too, remember to check it as well.
Protonmail, but not really because of encryption. I just liked their Android client and webmail the most. I’ve had sensitive backups on Proton Drive for a long time, so that also played a role in the choice.
I hosted my own server for quite a few years, but the SMTP clients (Thunderbird, Evolution, K9 mail) all doing things slightly differently made me give up. Biggest push was that K9 mail didn’t really move deleted mail to trash. These were probably dovecot configuration issues, but I got tired of searching for solutions. Never had any deliverability issues.
Perhaps I misunderstand the words “overlapping” and “hot-swappable” in this case, I’m not a native english speaker. To my knowledge they’re not the same thing.
In my opinion wanting to run an extra service as root to be able to e.g. serve a webapp on an unprivileged port is just strange. But I’ve been using Podman for quite some time. Using Docker after Podman is a real pain, I’ll give you that.
on surface they may look like they are overlapping solutions to the untrained eye.
You’ll need to elaborate on this, since AFAIK Podman is literally meant as a replacement for Docker. My untrained eye can’t see what your trained eye can see under the surface.
In my limited experience, when Podman seems more complicated than Docker, it’s because the Docker daemon runs as root and can by default do stuff Podman can’t without explicitly giving it permission to do so.
99% of the stuff self-hosters run on regular rootful Docker can run with no issues using rootless Podman.
Rootless Docker is an option, but my understanding is most people don’t bother with it. Whereas with Podman it’s the default.
Docker is good, Podman is good. It’s like comparing distros, different tools for roughly the same job.
Pods are a really powerful feature though.
This is true, with a couple gigs of RAM and SATA storage Nextcloud is not at all bad. Assuming an instance with not that much simultaneous users.
It feels like slow sometimes, then after an hour with M365 at work it doesn’t feel slow at all.
There’s a base image of ublue, which is Silverblue without a DE. I’d suppose you can mostly just layer e.g. Sway or i3 on top.
Traditional package model will still have it’s usage, of course, I agree. But if Silverblue works for a developer like me, I’d say a for more “regular” users immutable distros seem like a very viable option.
I recently put the nvidia variant of ublue-os on my work laptop, which has Optimus graphics. Couldn’t be happier.
It’s great to see these variants popping up! I really think ostree may be the future for desktop Linux, and not even very far away.
Rsyslog to collect logs to a single server, then lnav for viewing them on that server is a good combo. Oldschool but very effective for self-host scale.
Glad the tip was useful!
For a bit enhanced log file viewing, you could use something like lnav, I think it’s packaged for most distributions.
Cockpit can be useful for journald, but personally I think GUI stuff is a bit clunky for logs.
Grep, awk and sed are powerful tools, even with only basic knowledge of them. Vim in readonly mode is actually quite effective for single files too.
For aggregating multiple servers’ logs good ol’ rsyslog is good, but not simple to set up. There are tutorials online.
Oh the times when getting GTA from a friend required 30+ 3½" floppy disks IIRC. That plus making 5 or 6 round trips to friend’s house, because one of them almost always got corrupted during the zip process.
And since no one had the disk space or knowhow to store the zip packets on HDD for the inevitable re-copying, had to redo the whole pack from scratch each time.
Edit: disk->HDD
Devuan is more stable
So Devuan has even older versions of packages than Debian? Stability in the distro context means that features, APIs, UIs don’t change. Please don’t mix software bugs with stability.
It may be I’ve entirely misunderstood how systemd works, but I think your description of it is off by a mile too.
but a different init starts a new process ID for each separate program
Of course there are PIDs with systemd too! First of all, systemd itself has a PID (1).
For systemd, which runs system wide to handle everything, if one program locks, systemd has to make adjusts for the whole system to fix the problem.
This is just wrong… Sure, if the service in question is dependent on a lot of other services, or vice versa. If your programs tend to lock, that’s the application’s fault and should be handled at the application level.
I found Artix to run smoother or lighter than Arch.
This is most definetly a difference in what else is running on the system. Systemd doesn’t really use that much resources. Unless you are measuring RAM usage in the megabytes. Which is of course valid on constrained systems, but on a regular desktop one browser tab will need orders of magnitude more resources than any init system.
I want Firefox running an isolated process from the one that Plasama desktop is running
This just shows you have absolutely no clue on Linux processes, I really really doubt anyone is running Firefox under systemd. And neither have you.
There are valid reasons for choosing a different init system, but you have not provided a single one that is really true. It seems like you are only repeating things heard from some one else.
The difference is systemd is one thing to handle everything
This is true, but it refers to systemd handling a lot more than process management. Systemd has the problem that nowadays it does log management, memory management, login management, user management etc. This goes against the UNIX philosophy of one tool for one job, and THAT is why people frown on systemd.
I’d second this. Fedora is great, don’t get me wrong, but it’s not rolling or stable.
I think stable was referring to not crashing here.
Most Debian based distros, actually.
There’s occasionally something buggy, but the last time I ran Windows there were a lot of bugs too. They’re just abstracted away, which Linux DEs don’t do at all.
For me, it’s about choosing the bugs that bug me less. If Windows is working better for you, just run Windows. Internet points are not worth much.