On 10/28/2014 01:22 AM, Linda Walsh wrote:
Will specifying '3' on the kernel command line (in boot console (lilo or grubX)...still boot you into multi-user+ VT-tty console?
it works for me with 13.1. it worked for me on 12.3 :-0
I.e. when I boot,
I don't know, Linda. I've modified what happens when you boot in a number of ways by editing the command line, as I've described here. I boot using initrd. I recall you don't. That may make a difference.
if I have a problem in the early boot, I use "KNAME S". If it is after early boot but during service bring-up, I use "KNAME 1". (where KNAME = the kernel you want to boot).
So if KNAME selects the kernel, which in grub2 is done with the menu, then that has noting to do with the runlevel. What does KNAME 1,2,3,4,5,6,7,8,9 do? Is this an index into some name table of kernels? Where is that table? I realise you have modified your boot process but this seems very strange.
Do those same hooks stop systemd at the proper location(s)?
I don't know what you mean by "stop". And I don't know what you mean by 'hooks' The docco says the kernel parses the command line and hands such parameters as it doesn't process itself to the init process, so If I, as I described in earlier email, put a "3" in the command line in grub2/editmode then "init 3" gets run. Systemd is smart enough to recognise that and make use of the "runlevel3.target". I think I described to Ruben that path. So I don't know what you mean by "stops". if you mean "stops before bringing up X" then that's the wrong question. That's not how systemd works. X isn't in the target list for a simple multi-user boot. All this is clear in the docco. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org