Earlier quoted context omitted.
How dare he ask other people to use the software he wrote.
I think "ask" here is the wrong word, and you know it.
Systemd redux: The end of Linux
431–440 of 464 posts
Re: Systemd redux: The end of Linux
#432Earlier quoted context omitted.
When have you ever seen syslog go belly up?
You are clearly too young to remember. But don't worry journal will get there
Re: Systemd redux: The end of Linux
#433Earlier quoted context omitted.
> They are already dumping Solaris/AIX/HP-UX as much as they can so environments are a bit more homogeneous (and easier to support). Whoever is pushing for this is an idiot then. Verisign, for example, has had 100% DNS uptime for the .net, .org, and .com root servers for ~15 years because of their mixed environments. In every one of their POPs they tend to have at least two racks of equipment with: * 2 different bran…
Yet Google and Facebook keep using Linux for all their servers.
Re: Systemd redux: The end of Linux
#434Earlier quoted context omitted.
Simple one PID files. Assume server with lots of processes. Service A starts writes PID to disk, lets say 123. lots of processes start and stop as it goes along and does its work. Service A crashes/stops working PID 123 gets reused by a new process SysAdmin comes and hits /etc/init.d/ServiceA restart shell script calls kill 123 which was a totally different process now not at all related to ServiceA. etc... Clean unm…
I still think 64 bit non reused pids are the best long term solution. There are other pid race conditions. (Not having pid files deleted on reboot is a different issue of course). Although the Capsicum model (in FreeBSD, slowly getting into Linux) where you can have file descriptors for processes is another different model.
Re: Systemd redux: The end of Linux
#435Earlier quoted context omitted.
You know this is funny, I remember reading comments EXACTLY like this about 3-4 years ago but with pulseaudio in place of systemd. Pulseaudio was Lennart's previous project. It broke everything in linux sound for a while, everybody moaned and hated it and said it was the worst thing since the crucifixion of Christ. Yet, name one problem you had with sound on linux in the past year? There are very few. Pulseaudio now…
You're entirely right and I've upvoted you. However, with one small caveat: servers don't generally have sound cards so the impact of this was relatively low. There aren't that many desktop Linux users out there. I mean I'm a Unix guy at heart and I'm typing this on a Windows laptop. I've never used Linux on the desktop and probably never will. Now servers do have init processes and we don't really want to spend the…
Then you're not really a Unix guy at heart.
At home, all I run is Linux, including the laptop my non-geeky wife uses.
For me it was a hard choice. I knew she would object because it would be "different" and she's not really interested in learning a gazillion different computing-systems, but on the flip side it meant it was simpler, quicker and less work for me to maintain the computers at home.
Once setup things just work, and ensuring everything (including flash and other vulnerability vectors) is up to date is one apt-get upgrade away.
Re: Systemd redux: The end of Linux
#436I'm quite happy to be a part of the development team for GNU Guix, a distro that is not using systemd. I'm not a systemd hater, but it's definitely not for me and I'm not thrilled with the direction that development is going. It's a shame that sysvinit and friends are so bad that using systemd is the best option we have right now. Maybe GNU dmd will be able to stand up to it someday.
Thank you for doing this. That being said, it's a little too esoteric for my tastes (among other things: "if you are looking for a stable production system that respects your freedom as a computer user, a good solution at this point is to consider one of more established GNU/Linux distributions."). Do you know of any Linux distros that a) don't use systemd, b) are vaguely active / supported, and c) run on UEFI? (My c…
Not addressing any other of your points, doesn't most laptops/computers which ships with UEFI allow you to set it to boot in "legacy-BIOS" mode?
Even if you're currently UEFI-booting, I would be seriously surprised if UEFI-support was a requirement for every OS your machine can boot.
Re: Systemd redux: The end of Linux
#437Earlier quoted context omitted.
Strange I don't see the issues you're talking about I use Ubuntu Desktop on a variety of desktops and laptops. I'd say PA was stable by Ubuntu 12.04. I do Skype and Google Talkplugin (now Hangouts).
Try using it with JACK and setting up a DAW.. then you'll see the pain.
In particular for problems of getting Youtube (or any browser audio) to work while other apps use JACK directly.
Although on a recent new install it seemed to work without them as well.
One problem is I need to start/stop the qJackCtl thing every time my laptop comes back from sleep, to get sound working again. There must be a way to automate (or, preferably, fix) this, right? Anyone know?
Re: Systemd redux: The end of Linux
#438Going against the "divide et impera" principle, "do just one thing, and do it well", "everything is a text file" (configurations and logs) and "pipes" which are very natural idiom, in a UNIX-like system which has been built upon these principles , is just bad engineering, shallow understanding and, perhaps, too high ambitions of knowing better how to fix what isn't broken. The question why do we have this project and…
Mac OS X has launchd for 10 years now.
Solaris 10 replaced sysvinit with SMF.
Don't have any experience with AIX but the documentation says it has a "System Resource Controller" with a "srcmstr" daemon to manage services; though it looks like it runs on top of something sysvinit-like:
http://www-01.ibm.com/support/knowledgecenter/ssw_aix_61/com...
BSDs have generally never used sysvinit, although they do have shell-based service management.
So actually none of the particular examples you cite use purely sysvinit to manage services.
And it's also quite obvious that there are use-cases where reliable and fast service management are very important on servers.
One is containers, where you may run 10000 of them on a single host, and you have to reboot the host some time too, so you don't want to delay the start up of all those containers by loads of slow and racy shell scripts. Or even better, you want to have socket activated containers that don't actually start until they are needed.
https://www.getpantheon.com/blog/pantheon-running-over-50000...
Another is hyperscale servers: There are now really small ARM and x86 based servers and you can put 4-500 of those in a single rack. That means a lot more individual servers to admin, and failure modes that are relatively rare in current server rooms will become an order of magnitude less rare, so more robust OS level service management is helpful.
Re: Systemd redux: The end of Linux
#439Earlier quoted context omitted.
With the irony that Poettering was the guy to pull the plug on the alternative. And alternative that could live on top of any init out there.
Lennart's view is that he did all he could to avoid breaking using GNOME with ConsoleKit: http://lwn.net/Articles/621182/
http://erickoegel.wordpress.com/2014/10/20/consolekit2/comme...
Re: Systemd redux: The end of Linux
#440Earlier quoted context omitted.
With the irony that Poettering was the guy to pull the plug on the alternative. And alternative that could live on top of any init out there.
Lennart's view is that he did all he could to avoid breaking using GNOME with ConsoleKit: http://lwn.net/Articles/621182/
http://erickoegel.wordpress.com/2014/10/20/consolekit2/comme...