On 2013-09-11 19:06 (GMT-0400) Anton Aylward composed:
Felix Miata composed:
On 2013-09-11 13:55 (GMT-0400) Anton Aylward composed:
the concept of runlevels is obsolete.
So, what complicated mechanism will or have the the systemd people come up with to replace the simplicity of S or 1 or 2 or 3 or 5 on cmdline to override the default runl^H^H^H^Htarget? :-p
Well lets see, how simple are S, 1, 2, 3, 4, 5 and 6? They actually hide a whole pile of shell scripting.
Written scripts, mature too. Sunk cost.
You've traded simplicity of expression for (a) obscurity of meaning and (b) the need to be a programmer to make any adjustments
Cmdline has limited room. Brevity there is welcome, while obscurity is readily overcome via chkconfig -l. "Any" is also misplaced. A tiny bit of tweaking to /etc/inittab to make startup output and vtty initialization like it was pre-systemd has been replaced by a need for a less simple script for performing a similar modification of startup behavior: /bin/sh cp -a /usr/lib/systemd/system/getty@.service /usr/lib/systemd/system/getty@tty1.service sed -i 's/TTYVTDisallocate=yes/TTYVTDisallocate=no/' /usr/lib/systemd/system/getty@tty1.service ln -sf /usr/lib/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service systemctl start getty@tty1.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty2.service systemctl start getty@tty2.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty3.service systemctl start getty@tty3.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty4.service systemctl start getty@tty4.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty5.service systemctl start getty@tty5.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty6.service systemctl start getty@tty6.service
What does the systemd approach offer instead?
Well for a start there's clarity of meaning that is absent from the sysvinit method:
We've got
multi-user.target or graphical.target
So? Multi-user and graphical are clear enough, but who came up with target to summarize an operational configuration easily visualized via the simple chkconfig -l matrix? The word's usage is not clear to me, and thus, not easily memorable. It's all moot anyway. Sysvinit is history. Longer, more easily mistyped strings of systemd supplanting short ones of sysvinit are what those not still using Evergreen have now. I expect if such statistics were to be had, 11.4 would be, if it hasn't already become, the most widely used out of official "support" release of openSUSE to date. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org