Press ‘e’ (small e) on menu entry, move to the end of line that starts with “linux …” and add “1” to the end of line. Press F10 or Ctrl-X to boot. Pressing ESC returns you to menu discarding all changes.
Some Emacs-like editing shortcuts are supported (like ^E to move to the end of line).
On 05/12/2013 08:06 PM, bkorb wrote:
>
> The only answer I’ve figured out is to learn to read grub2 hyeroglyphics
> and add another menu item with just the right collection of options.
>
>
> Code:
> --------------------
> menuentry ‘openSUSE 12.3’ --class ‘opensuse-12-3’ --class gnu-linux --class gnu --class os $menuentry_id_option ‘gnulinux-simple-fc6720c3-8404-47a9-b3e7-d310613a11d1’ {
> load_video
> set gfxpayload=keep
> insmod gzio
> insmod part_msdos
> insmod ext2
> set root=‘hd0,msdos1’
> if x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint=‘hd0,msdos1’ e6ad9c57-3ca5-44ff-85a0-df895dd558ac
> else
> search --no-floppy --fs-uuid --set=root e6ad9c57-3ca5-44ff-85a0-df895dd558ac
> fi
> echo ‘Loading Linux 3.7.10-1.4-desktop …’
> linux /vmlinuz-3.7.10-1.4-desktop root=UUID=fc6720c3-8404-47a9-b3e7-d310613a11d1 resume=/dev/disk/by-label/SWAP splash=silent quiet showopts
> echo ‘Loading initial ramdisk …’
> initrd /initrd-3.7.10-1.4-desktop
> }
>
> --------------------
> I am not entusiastic about deciphering that.
For getting to single user mode, all that matters is the line that starts with
“linux”. Position to it and append a space and the numeral 3. Then use F10 to boot.
> For getting to single user mode, all that matters is the line that
> starts with “linux”. Position to it and append a space and the numeral
> 3. Then use F10 to boot.
Wait, 3 is multiuser with network. Single user is 1.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Either way. 1 or 3, just not 5. thank you! I wish I understood why it was made non-obvious. The pressing the “e” key was what I had most hoped for. That edit-the-line possibility used to be much more obvious.
> Either way. 1 or 3, just not 5. thank you! I wish I understood
> why it was made non-obvious. The pressing the “e” key was what I had
> most hoped for. That edit-the-line possibility used to be much more
> obvious.
Welcome to grub2
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 05/13/2013 11:23 AM, Carlos E. R. pecked at the keyboard and wrote:
> On 2013-05-13 17:06, bkorb wrote:
>
>> Either way. 1 or 3, just not 5. thank you! I wish I understood
>> why it was made non-obvious. The pressing the “e” key was what I had
>> most hoped for. That edit-the-line possibility used to be much more
>> obvious.
> Welcome to grub2
>
On 05/13/2013 12:08 PM, Carlos E. R. pecked at the keyboard and wrote:
> On 2013-05-13 17:58, Ken Schneider wrote:
>> On 05/13/2013 11:23 AM, Carlos E. R. pecked at the keyboard and wrote:
>>> Welcome to grub2
>>>
>> No thanks.
> Oh, absolutely, if I have the chance I prefer keep using grub1 for ever.
> But is it an option, and if so, for how long?
>
My guess is that since openSUSE has become a lemming to Fedora,
following it’s every move, that as soon as Fedora drops legacy grub so
shall openSUSE. So follow what Fedora is doing for a hint.
On 05/13/2013 11:51 AM, Ken Schneider wrote:
> On 05/13/2013 12:08 PM, Carlos E. R. pecked at the keyboard and wrote:
>> On 2013-05-13 17:58, Ken Schneider wrote:
>>> On 05/13/2013 11:23 AM, Carlos E. R. pecked at the keyboard and wrote:
>>>> Welcome to grub2
>>>>
>>> No thanks.
>> Oh, absolutely, if I have the chance I prefer keep using grub1 for ever.
>> But is it an option, and if so, for how long?
>>
>
> My guess is that since openSUSE has become a lemming to Fedora, following it’s
> every move, that as soon as Fedora drops legacy grub so shall openSUSE. So
> follow what Fedora is doing for a hint.
I don’t know if I would characterize it as lemming behavior, but openSUSE does
not have the resources to maintain something like GRUB legacy on its own. When
other distros abandon something, oS has little choice but to follow. Of course,
if you volunteer to be a maintainer of some such facility, it improves the
chances of being kept.
On 2013-05-13 19:04, Larry Finger wrote:
> On 05/13/2013 11:51 AM, Ken Schneider wrote:
>> My guess is that since openSUSE has become a lemming to Fedora,
>> following it’s every move, that as soon as Fedora drops legacy grub so shall
>> openSUSE. So follow what Fedora is doing for a hint.
>
> I don’t know if I would characterize it as lemming behavior, but
> openSUSE does not have the resources to maintain something like GRUB
> legacy on its own. When other distros abandon something, oS has little
> choice but to follow. Of course, if you volunteer to be a maintainer of
> some such facility, it improves the chances of being kept.
Yes, that’s true.
openSUSE did maintain grub 1 for some time, adding patches to it,
because the installer system did not support grub 2, and also because
grub 2 was not ready enough, I think they thought. IIRC, hooking yast to
grub2 was very difficult. They did what they had to do meanwhile, no
alternative.
Now grub2 works, YaST supports it, so they no longer need to support
grub1 on their own. They might keep it the same as they keep lilo, low
profile, while it works. But lilo itself is maintained by other people,
they only need to keep the YaST modules for it.
So the question is, when will they finally ditch grub 1?
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Not quite fair. grub2 default boot screen gives help text how to edit menu entry (exactly “press ‘e’ etc …”). Same as grub legacy did BTW. But in openSUSE theme this message is lost.
On 2013-05-14 05:06, arvidjaar wrote:
> robin_listas;2556515 Wrote:
>> Welcome to grub2
>
> Not quite fair. grub2 default boot screen gives help text how to edit
> menu entry (exactly “press ‘e’ etc …”). Same as grub legacy did BTW.
> But in openSUSE theme this message is lost.
Ah, the theme… The same theme, I guess, that limits the line width so
that the entire kernel version is not displayed, but trimmed, and thus
versions are difficult to differentiate.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 5/12/2013 8:06 PM, bkorb wrote:
>
> The only answer I’ve figured out is to learn to read grub2 hyeroglyphics
> and add another menu item with just the right collection of options.
>
>
> Code:
> --------------------
> menuentry ‘openSUSE 12.3’ --class ‘opensuse-12-3’ --class gnu-linux --class gnu --class os $menuentry_id_option ‘gnulinux-simple-fc6720c3-8404-47a9-b3e7-d310613a11d1’ {
> load_video
> set gfxpayload=keep
> insmod gzio
> insmod part_msdos
> insmod ext2
> set root=‘hd0,msdos1’
> if x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint=‘hd0,msdos1’ e6ad9c57-3ca5-44ff-85a0-df895dd558ac
> else
> search --no-floppy --fs-uuid --set=root e6ad9c57-3ca5-44ff-85a0-df895dd558ac
> fi
> echo ‘Loading Linux 3.7.10-1.4-desktop …’
> linux /vmlinuz-3.7.10-1.4-desktop root=UUID=fc6720c3-8404-47a9-b3e7-d310613a11d1 resume=/dev/disk/by-label/SWAP splash=silent quiet showopts
> echo ‘Loading initial ramdisk …’
> initrd /initrd-3.7.10-1.4-desktop
> }
>
> --------------------
> I am not entusiastic about deciphering that.
>
>
The systemd equivalent of setting the inittab id field is to set the default.target in /etc/systemd/system. The default.target is
a link to one of the runlevel targets in /lib/systemd/system.
This is, of course, a semi-permanent change to runlevels. It’s probably not much use for runlevel1.target, but works well for
headless machines that need runlevel3.target.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
On 2013-05-14 07:36, arvidjaar wrote:
>
> robin_listas;2556643 Wrote:
>> The same theme, I guess, that limits the line width so
>> that the entire kernel version is not displayed, but trimmed, and thus
>> versions are difficult to differentiate.
>
> Yes. Did you report it?
Nope. O:-)
Several reasons. One, that due to Bug 818001, I was not getting emails
from Bugzilla, or from SUSE personnel. The SPF record for SUSE et al was
wrong and my ISP rejected their emails - so I was not being told of any
changes to the Bugzillas I reported.
Two, I have reported hundreds of bugzillas, and too many of them are
still “new”, no answers. This has been worsening lately, so there is
little incentive to report Bugzillas if they are never attended, after
the hundreds of hours I invested investigating some of the issues for
reporting them. Often they are simply closed two years later when the
release is EOL.
Actually, for the Bug mentioned above, I had to go public on the project
mail list and insist loudly, then attention was paid and solved promptly.
And three, I remember a thread here somewhere that mentioned the grub
theme issue, and hacked it to correct this particular problem, several
months ago. It is just something else in the TODO list, together with
reading the grub2 chapter at doc.opensuse.org
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
At first my boot lines were truncated. Even tried changing solution in Yast but then one of the last patches seems to have fixed it and now I see the whole line with the higher res I had set in yast actually now it looks good before it was cheap looking
On 2013-05-14 22:56, gogalthorp wrote:
>
> At first my boot lines were truncated. Even tried changing solution in
> Yast but then one of the last patches seems to have fixed it and now I
> see the whole line with the higher res I had set in yast actually now it
> looks good before it was cheap looking
There is not much I can do about image resolution, the machine is “virtual”:
I think I can edit /boot/grub2/grub.cfg, change the tittles there - but
I have the feeling that everything I change will revert with next kernel
update:
> submenu 'Advanced options for openSUSE 12.3' $menuentry_id_option 'gnulinux-advanced-26c4d5b7-aec6-401e-9aa3-c8528acf978c' {
> <------>menuentry 'openSUSE 12.3, with Linux 3.7.10-1.4-desktop' --class 'opensuse-12-3' --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.7
I tried, deleting part of the first string. It works.
Now what I also want is to create a third menu entry… but the file is
complex.
I gotta read more… and 36 hours a day.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Either way. 1 or 3, just not 5. thank you! I wish I understood why it was made non-obvious. The pressing the “e” key was what I had most hoped for. That edit-the-line possibility used to be much more obvious.
Either way. 1 or 3, just not 5. thank you! I wish I understood