The Office Space riff is just so much cadmium cojones: https://www.youtube.com/watch?v=FECIYlo3KRY
Landmines kill little kids without asking. Do we want more things killing automatically?
Thank you. It's very tempting to circlejerk about this. People on Slashdot are supposed to have a few more critical thinking abilities. Doesn't always work out that way.
There are still questions about Windows 10 data transfers, but misinformation and sloppy research as found in the original Forbes article, does not help in any way.
If it were truly a better system I wouldn't have to switch endlessly between ribbon tabs while performing simple formatting tasks. Once configured (even minimally), the toolbar stayed *put*, allowing muscle memory to speed operation.
The ribbon is great for discovery and people who never get past "ransom letter" documents. It sucks ass for experienced users.
I'm glad that the tasks you do are so constrained that they fit into a single toolbar. As an experienced user I use many different features and being able to switch context to have a much wider selection then would fit into one toolbar is beneficial. This is even more true in Excel then Word.
Swore at it for a month when I first started using it because I needed to unlearn some habits, now find it much easier.
I miss the simplicity of the bsd-like init config scripts sitting on top of SysV in Arch, before they adopted systemd. So much could be configured from rc.conf, the daemon commands were simple, and I never had problems booting. gah
Yielding the power of UNIX has always laid in creating your systems inittab file, I thought everyone did that. I used to look upon rc scripts as an unnecessary complication of the system and wondered why they were there. If a service needs to be up, init makes sure it's up. If you want to take the service down, tell init to take it down. vim
Network services, is good example, a shell script handled by rc, is a prime candidate for an init controlled service. Getting init to kick of printer services after a short delay so that CPU time is focus on providing a GUI to a user could be another. Messaging system is a perfect example.
What about using runlevel 4 for your customised system state, 3 for shell level maintenance, 5 for GUI level maintenance? How about an ondemand runlevel?
Just learn how to use init *actions*, which is a lot simpler than systemd. Simple, scarily powerful and totally under utilised in Linux.
After spending some time with systemd writing unit files and playing around with jounalctl my sense is that this entire situation would be resolved with a set of small tools that manipulate inittab files properly that could support a GUI based inittab editor, thus complementing/completing the original design philosophy with a small maintainable set of tools that rpm, yast, apt-get could utilize. I wonder if people would be interested in such a thing? Perhaps it's time to contact the Devuan people.
I can agree with systemd supporters that the rc system is crap, however that still isn't init and systemd is as monolithic as the rc system, except it's compiled. I think the main objection to the idea of systemd is init is a core idea of the UNIX Operating System that is powerful. I've never seen a Linux distribution that uses init properly and essentially the argument is to replace a core idea of a stable operating system platform because people just don't understand how to use UNIX's most powerful concept one step removed from the kernel. Fast and lean!
The funny thing is, after all these years, I still haven't got everything I can get out of init. Do you understand what you are destroying systemd guys?
Has anyone got a use case yet?
SysV and the flusterfuck dyslexic script hackery behind SysV was a constant nightmare with a mountain hardware complaints leading back to it.
Even so the clusterfuck of rc scripts in most redhat derivatives was Red-Hat's creation. People aren't using init, via inittab, properly and now the reason cited to replace init is because the rc system, and the script hackery behind it created by red-hat is disliked. Keh?
Wouldn't a better rc system work better?
Here is a thought, why not learn how to use the shell properly so that shell hackery is not required. Or another idea, learn how to implement design patterns in bash/sh/ksh/zsh. Init is a simple elegant idea, people are arguing for it's removal because they aren't skilled enough writing *shell scripts*. It seems a bit silly to me that people who can't write something so simple have any business modifying the way the OS initializes.
It would be great to get Ken Thopson's opinion on the situation.
However, since we have the attention of many systemd advocates, can someone please throw a use case at me that init doesn't satisfy that systemd does? I'm really trying to understand why it is supposed to be better than something that is as tested as init. I don't mind using it, but why it is supposed to be so compelling?
Old programmers never die, they just hit account block limit.