111–120 of 204 posts
Earlier quoted context omitted.
> And let me ask a question, if systemd is crap, why does every major distro use it? If Big Mac is a crappy food, why billions are served with it?
Or maybe you should questions yourself as to why you are so angry about what others like
Earlier quoted context omitted.
Cron has all these features: - single place control: crontab -e - additional constraints: systemctl status && scirpt.sh - randomize startup times: sleep ${RANDOM:0:MAX} && script.sh The nice thing is that it integrates with the existing infrastructure (shell scripts). This means you don't have to add code to cron to add features. I agree with the 10s of files in /etc/cron.daily, etc. But those are there for convenien…
There are some cool features in systemd that are not easy to do in cron. Example: I use restic backup. One timer runs every 24h or on the next boot if there where more than 24h since the last backup as this is a laptop. Also it waits some random amount so that not all script run at the same time after boot. If a backup fails (eg remote server down) it retires every 15min, but no more than one hour before I get an Mai…
sleep $random
for i in 1 2 3 4; do
backup && exit 0
sleep 15m
done
logger "backup failed"
exit 1
Yes systemd might be slightly easier, but that's because they put a lot of money into systemd, not because systemd is a better architecture. It's nice that they open sourced it (although it does give them a competitive edge), but we can't act like what used to be there isn't as good.
Someone could have packaged utility wrapper scripts in much less time than it did to add those features to systemd, and these wrapper script would be more widely usable (by init scripts, cronjobs, etc)
Earlier quoted context omitted.
There is so much truth to what you say. I used Linux exclusively from January 2000 until April 2012. A lot has changed in that time, but out of all the changes the three I'm most thankful for are: (1) Xorg replacing XFree86 and making video "just work" (2) Pulse Audio replacing OSS and making audio "just work" (3) systemd replacing the dog's breakfast of scripting madness each distro built from scratch instead of col…
I don't know about (2). Alsa "just worked" when pulse audio was released and PA did not "just work" for like 8 years after the first release. Seems like software history revisionism to me.
Earlier quoted context omitted.
What is it intended for? Certainly not large scale user groups backed by an LDAP server, as those would have consistent uid/gid so setting everything to be owned by nobody wouldn't make sense technically... What is the use case?
Portable home directories. Think pen drives.
Earlier quoted context omitted.
As someone who has learned Linux/Unix just the past few months using a systemd based distro, I find it a breeze to use. Great documentation, FOSS, and really easy to pick up. I just don’t understand why there is so much dislike thrown around when that energy can be focused elsewhere on truly bad behavior/software. And from my understanding, there are distros out there that don’t use systemd for those who dislike it t…
Systemd by itself is alright, the problem for me is the larger movement from "Linux is about choice" to tightly integrated, opinionated tools. Examples: - Gnome started to depend on systemd features. Now non-systemd systems become second class citizens. - You used to be able to freely swap out window managers, taskbars, and so on, because everything was working with common standards. In the modern world, everything i…
My Linux workstation and servers are not something I want to tinker with, I want solidity and stability and a fragmented user space ecosystem is not the solution.
Earlier quoted context omitted.
There is so much truth to what you say. I used Linux exclusively from January 2000 until April 2012. A lot has changed in that time, but out of all the changes the three I'm most thankful for are: (1) Xorg replacing XFree86 and making video "just work" (2) Pulse Audio replacing OSS and making audio "just work" (3) systemd replacing the dog's breakfast of scripting madness each distro built from scratch instead of col…
I don't know about (2). Alsa "just worked" when pulse audio was released and PA did not "just work" for like 8 years after the first release. Seems like software history revisionism to me.
PulseAudio let us have a common stack instead. There were bugs (PulseAudio was probably a bit buggy at first, and also hit audio driver bugs because of the new ways of using them). The transition was rough and PulseAudio is not perfect too but is it there for reasons and solves many issues.
Now it is being replaced by PipeWire, probably for the best (more efficient, can replace JACK too, making sound management much easier on Linux), but PipeWire leverages experience from PulseAudio.
I lived the transition to PulseAudio and it went well for me and probably a lot (the majority?) of people. Some things could probably have been handled better, especially the (too early?) transition. I think PulseAudio still is/was a good thing.
Work hard and solve a big, complex set of problems. Solve them well. Offer the solution as free open source. Work some more to offer extra functionality and fix the bugs. Become the internet's villain. Come up with a commercial solution to a simple problem. Ex: file sharing or password management. Make it slow, insecure, privacy violating, lose people's data. Make millions, become a hero.
There is so much truth to what you say. I used Linux exclusively from January 2000 until April 2012. A lot has changed in that time, but out of all the changes the three I'm most thankful for are: (1) Xorg replacing XFree86 and making video "just work" (2) Pulse Audio replacing OSS and making audio "just work" (3) systemd replacing the dog's breakfast of scripting madness each distro built from scratch instead of col…
While I get that some people are uncomfortable with breaking with traditions, I absolutely do not get all the hostility directed towards this craftsman programmer.
Earlier quoted context omitted.
Since all software has bugs, that doesn't make it a new problem now does it?
systemd had way more bugs and crinkles for an init system when it first started, and an init system is critical software .
Linux itself was mostly unusable when it first started. And a kernel is even more important.
Earlier quoted context omitted.
There is so much truth to what you say. I used Linux exclusively from January 2000 until April 2012. A lot has changed in that time, but out of all the changes the three I'm most thankful for are: (1) Xorg replacing XFree86 and making video "just work" (2) Pulse Audio replacing OSS and making audio "just work" (3) systemd replacing the dog's breakfast of scripting madness each distro built from scratch instead of col…
I don't know about (2). Alsa "just worked" when pulse audio was released and PA did not "just work" for like 8 years after the first release. Seems like software history revisionism to me.
The reason so many people had issues with PA was not PA but the brokenness of the underlying system that PA exposed for the first time when trying to use all these drivers in a systematic way and build functionality on top of it. It took years of fixing all the drivers and PA - unfortunately - got a lot of undeserved flak.
PA is the reason that Linux has a halfway decent audio subsystem, being able to deal with all the modern devices; thank you, PA devs.
I find it hilarious that people are festive about PA being replaced by Pipewire - if PA hadn't paved the way, the Linux driver landscape would not be in such a good shape today and Pipewire would 'fail' in exactly the same way that PA 'failed.