SoylentNews is people
SoylentNews
Frew Schmidt has written seven posts on init systems and supervisors. He covers both basic and advanced supervisors, and what they do including some more unusual options.
This discussion has been archived.
No new comments can be posted.
Seven Part Post on Supervisors and Init Systems
|
Log In/Create an Account
| Top
| 18 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
If life gives you lemons, make lemonade.
(Score: 2, Funny) by Anonymous Coward on Thursday August 10 2017, @12:30AM (9 children)
It's more systemd propaganda. If you read it, you'll go blind!
(Score: 0) by Anonymous Coward on Thursday August 10 2017, @01:04AM
Seriously though
(Score: 1, Interesting) by Anonymous Coward on Thursday August 10 2017, @01:08AM (6 children)
But what if I'm already blind, you insensitive clod!
(Score: 3, Funny) by Anonymous Coward on Thursday August 10 2017, @03:01AM (5 children)
systemd-screenreaderd will be automatically installed, and your old screen reader will be permanently disabled.
(Score: 1) by ThatIrritatingGuy on Thursday August 10 2017, @06:59AM (4 children)
But what if want a screen reader that won't defragment my hard drive ?
(Score: 3, Funny) by ledow on Thursday August 10 2017, @07:43AM (3 children)
Make sure you don't put a number in the username, then it won't run as root so it can't defrag.
Unless, of course, your domain has an underscore in it.
(Score: 4, Insightful) by VLM on Thursday August 10 2017, @12:14PM (2 children)
Because shell scripts were "too complicated" to use and debug, LOL.
Also it doesn't work because its running a windows DLL using the wine emulator, but thats OK, because whats really important is all systems use the same thing even if it doesn't work, and for no apparent reason gnome and kde require it.
I swear the systemd people are being paid by the *BSD people to ruin linux. Either them, or microsoft is bankrolling systemd.
(Score: 5, Informative) by ledow on Thursday August 10 2017, @12:31PM (1 child)
Irony:
All the systemd functionality could be achieved with shellscripts, without even having to change the SysVInit style of things. Everything. From the process control to the cgroups functionality to everything.
But, apparently, it all had to be executables... erm... because.
And now we have init system binaries running their own DNS resolver (badly) because of it.
The thing I love - systemd was supposed to ensure that, when you wanted to use DNS - for, say, mapping a network location to boot from - you could use any resolver and systemd was supposed to make sure that everything it required would be up and ready by the time you needed it. That was kind of the whole point of it. So why systemd required its OWN DNS resolver, rather than make sure the system one was up and ready, I can't really fathom.
(Score: 2) by VLM on Thursday August 10 2017, @06:13PM
They have noobs in charge of systemd, typical inner platform effect. They'll have an entire kernel embedded in there before ya know it. Noobs...
I changed some DNS server ips at home and on some static configured ubuntu images I had a huge battle with resolvconf and/or systemd over resolv.conf and the online advice from years old blogs simply no longer works. What a nightmare. In the old days you'd edit the text file /etc/resolv.conf and it just works every time, but that is complicated into not working now, and reinstalling ubuntu is the simplest way to change a DNS server IP address on a static configured machine. I did work around it eventually without reinstalling, I think I deleted and recreated the file and then chattr'd it immutable or something. What a piece of shit of an operating system that you can't even trust text editor changes to work. "Systemd, now making windows easier to admin than MS windows..."
(Score: 0) by Anonymous Coward on Thursday August 10 2017, @04:15AM
I'm pretty sure that's not true. Clicking the link does give you hairy palms though.