-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Mon, 10 Jun 2013 18:25:18 +0200 "Carlos E. R." <robin.listas@telefonica.net> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-06-10 15:54, Patrick Shanahan wrote:
* Linda Walsh <suse@tlinx.org> [06-10-13 03:01]:
As for debugging the problem... used to be you could boot to single-user and step through your bootup steps to find the problem...
But.. how is that done on systemd?
And you cannot try?
wtf, Linda.
It still works as before, add a 1 or "S" to the init line or go to console and "init S"/"init 1"
She refers to a different feature. It was a setting, activated I think by creating an empty file of a certain name, or by editing 'rc' and defining:
DO_CONFIRM=yes
Then the init process would prompt the admin on every single module whether to run or skip. This, AFAIK, is not available with systemd.
systemd.confirm_spawn= Takes a boolean argument. If true asks for confirmation when spawning processes. Defaults to false. Not that I actually tested it, but it is in documentation. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG2DpwACgkQR6LMutpd94w0gACg0c9U0BiLZhfEGNjZ6KdHTMVt 8LUAoMfTnPAqK/toMWKRM9WU5xz0SxCm =uhJb -----END PGP SIGNATURE-----