2012/6/3 Colin Guthrie <mag...@colin.guthr.ie>: > 'Twas brillig, and Wolfgang Bornath at 03/06/12 17:12 did gyre and gimble: >> 2012/6/3 Colin Guthrie <mag...@colin.guthr.ie>: >>> 'Twas brillig, and Richard Couture at 03/06/12 12:27 did gyre and gimble: >>>> I notice that when, at the end of the installation of MGA2, I select the >>>> level of security as HIGH, that I am permitted entry into the system in >>>> Linux Single mode without a challenge password, which is a new, and IMHO >>>> undesirable, behavior from previous versions. >>>> >>>> Is this a new feature, or have I stumbled upon a bug? >>>> >>>> The /etc/inittab does have ~~:S:wait:/sbin/sulogin in it but I can get >>>> in without a password... Must be something new in system D >>> >>> /etc/inittab is no longer used or read. >>> >>> For single user mode now-a-days we boot to rescue.target (this is done >>> automatically if you just put a 1 at the end of the kernel command line >>> to support "runlevel 1"). >> >> Ok, convinced. >> But if /etc/inittab is not used any more, where do I change initial >> runlevel not for one boot but for a while? With inittab it was easy to >> change the default runlevel. > > The tools in drak* still let you configure this, so that's the "easy" way. > > For real men (and women), we just change the > /etc/systemd/system/default.target symlink to point at whatever target > we want to use by default. > > For ad-hoc changes you can pass systemd.unit=foo.target on the kernel > command line or just append a runlevel number or the words "single" or > "failsafe" as before.
I knew there will be regressions in usage. No more easy change with sed! :) Or: I feel educated to use the GUIs! Thx -- wobo