I’m still trying various things to speed up boot, and am unsure if pressing F5 to boot 12.1 will start systemv while using grub2. I also seen instructions to add a line to grub to automatically start it, but that only applies to grub 1
How can I start systemv using grub2?
So, normally to get to use any of the openSUSE grub legacy settings to work, it suggested that you load grub into the root openSUSE partition and chain load it as if it where Windows. Then, the old grub will load and the old options will be there. This only works if grub legacy was installed with openSUSE 12.1. When running, openSUSE, you could install grub then, being careful not to upset your grub2 install. If openSUSE is not in partitions 1, 2, 3 or 4, I am not sure you can chain load it then.
Thank You,
walter joseph wrote:
> How can I start systemv using grub2?
Edit /etc/default/grub
It is self documented – read the first line
Just add init=/sbin/sysvinit to the GRUB_CMDLINE_LINUX_DEFAULT
list.
Remember this is running Systemd in SysV init mode. To actually use the
traditional init you need to intall sysvinit and sysvinit-init packages.
On 2012-01-15 21:16, jdmcdaniel3 wrote:
> If openSUSE
> is not in partitions 1, 2, 3 or 4, I am not sure you can chain load it
> then.
Yes, you can, I do it. With grub legacy, I have no idea about grub 2.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Did you load grub into a logical partition Carlos? I ask because if my base system is using grub2, you need to load grub legacy from somewhere. Can it be loaded from a logical partition using a chainload?
Thank You,
You can chainload everything from everywhere and in both directions … except that openSUSE Grub2 doesn’t seem to be able to chainload Legacy Grub when it is installed in the extended partition … which doesn’t surprise me that much - athough I guess I did that with Ubuntu’s Grub2 already, but it was installed in the MBR. Grub is always a little bit more clever when it sits at mile zero.
I guess then that is a Yes to “Can openSUSE be chain loaded from a logical partition from grub2 when grub legacy is ONLY installed in the same logical partition”. A booting situation that would normally not work when not chain loading from grub2. Thanks for the info please_try_again.
Thank You,
You can chainload everything from everywhere and in both directions … except that openSUSE Grub2 doesn’t seem to be able to chainload Legacy Grub when it is installed in the extended partition … which doesn’t surprise me that much - athough I guess I did that with Ubuntu’s Grub2 already, but it was installed in the MBR. Grub is always a little bit more clever when it sits at mile zero.
I don’t know for sure, but perhaps a robot has taken over please_try_again causing the same response to be posed twice, but I am not for sure about that. lol!
Thank You,
Well… Wait a minute. On a Legacy BIOS system, the booloaders have to be installed in different partitions (primary or logical don’t matter). The rest can be installed - and will be if you have only one installation in the same partition under /boot/grub and /boot/grub2. Thus you can have Grub2 in MBR and Legacy Grub in the root partition (but not in the extended one - at least not if you want to chainload it*). I have an updated version of findgrub that I haven’t posted yet, which can now identify openSUSE’s Grub2. The latest available version already recognizes new Fedora’s Grub2.
It’s the forum that doesn’t work and tries to reconnect for ever.
It’s the forum that doesn’t work and tries to reconnect for ever.
I’m experiencing the same phenomena from time to time.
Yes I see the same issue from time to time, but I just hit my computer and it starts working again. Or well, maybe I just feel better after I do that. Or well, perhaps I just hope I feel better and by the time I get to the end of it all, its working again. Humm…
Thank You,
On 2012-01-16 03:26, jdmcdaniel3 wrote:
> Did you load grub into a logical partition Carlos? I ask because if my
> base system is using grub2, you need to load grub legacy from somewhere.
> Can it be loaded from a logical partition using a chainload?
Yes, I did it. I don’t remember which of my installs does it, but I have
used that setup. It is one main grub in the MBR, and this one can load
another grub anywhere, primary or logical.
What needs primary partitions is generic boot code and marking partitions
as bootable.
But as I said, I have not tried grub2, only legacy.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-01-16 04:36, jdmcdaniel3 wrote:
> I guess then that is a Yes to “Can openSUSE be chain loaded from a
> logical partition from grub2 when grub legacy is ONLY installed in the
> same logical partition”. A booting situation that would normally not
> work when not chain loading from grub2. Thanks for the info
> please_try_again.
I remember now where I did it, my laptop.
MBR: generic boot code.
GRUB 1: Extended partition, #4
Linux Boot code in logical partition 5, root in 6.
Plus Windows and another Linux.
GRUB 1: Logical partition 9 (secondary test system)
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Wow is this complicated. You’d think this would be a good setting in yast instead of all this rigermarole. Might be easier to convince canonical to give up their fast boot secrets.
This is absolutely not complicated, and the question was already answered it post #3 - actually half ways, because @eng-int didn’t say that you had to refresh the menu after modifying /etc/default/grub. You can achieve that with updategrub -2 (or updategrub --grub2) if you happened to install this package. Otherwise you would use the following command:
grub2-mkconfig -o /boot/grub2/grub.cfg
And the system will now boot in system V if this is what you want.
But nothing prevents you from booting systemv by appending init=/sbin/sysvinit to the line booting the kernel (line starting with “linux”) in Grub2 menu. You just have to press “e” to edit the boot entry, add the option, than boot with CTRL-x or F10.
Btw, Ubuntu doesn’t use systemd, but upstart.
walter joseph wrote:
>
> Wow is this complicated. You’d think this would be a good setting in
> yast instead of all this rigermarole. Might be easier to convince
> canonical to give up their fast boot secrets.
>
The answer to the subject question is not complicated. It was given in post
#3. all the rest is a side discussion about using both GRUB1 one and GRUB2.
OpenSuSE uses GRUB1, so that is what is easily configured via YaST. You have
chosen to use GRUB2, which is not normal for openSuSE.
I do not know why you think that using either systemd-sysvinit or
sysvinit-init will shorten the boot time. If anything I would expect
them to lengthen it, unless you are using something unusual, such as
software RAID or mounting network filesystems before logon.
The first line is an instruction to grub2-mkconfig …
"But nothing prevents you from booting systemv by appending init=/sbin/sysvinit to the line booting the kernel (line starting with “linux”) in Grub2 menu. You just have to press “e” to edit the boot entry, add the option, than boot with CTRL-x or F10.
Btw, Ubuntu doesn’t use systemd, but upstart.[/QUOTE]
Ok I got it. Thanks all. (no change to boot though).