On 4/23/19 3:28 PM, Stasiek Michalski wrote:

GRUB is mostly pointless in scenarios where OS boots fine and only one OS is installed in graphical session. It would be nice to hide it.

Why? If you have just one operating system installed, you can just hibernate your machine anyway and don't have to reboot the machine at all.

Fedora has 4 patches for this purpose [1,2,3,4], the only thing we would need to add to this would be YaST handling of setting variable automatically for graphical target.

FWIW, Fedora also has almost 300 patches on top of GRUB 2.02:

https://src.fedoraproject.org/rpms/grub2/tree/master

I think that's just way too much. They will have a lot of fun with the upcoming version 2.04 when they have to rebase everything.

I know that snapper is an useful tool for openSUSE, and GRUB is very much required for this to work, but snapper is almost always used when user isn't able to boot into the system.

But what about just switching to systemd-boot then? Adrian

On wto, Apr 23, 2019 at 3:38 PM, John Paul Adrian Glaubitz wrote:

On 4/23/19 3:28 PM, Stasiek Michalski wrote:

...

GRUB is mostly pointless in scenarios where OS boots fine and only one OS is installed in graphical session. It would be nice to hide it.

Why? If you have just one operating system installed, you can just hibernate your machine anyway and don't have to reboot the machine at all.

You need to reboot for updates/upgrades (which in case of Tumbleweed are just like updates ;) ) If I didn't restart as much as I do, I wouldn't be suggesting this change :P

...

Fedora has 4 patches for this purpose [1,2,3,4], the only thing we would need to add to this would be YaST handling of setting variable automatically for graphical target.

FWIW, Fedora also has almost 300 patches on top of GRUB 2.02:

...

https://src.fedoraproject.org/rpms/grub2/tree/master

I think that's just way too much. They will have a lot of fun with the upcoming version 2.04 when they have to rebase everything.

I mean, openSUSE has 150, it's still not going to be fun.

...

I know that snapper is an useful tool for openSUSE, and GRUB is very much required for this to work, but snapper is almost always used when user isn't able to boot into the system.

But what about just switching to systemd-boot then?

We cannot do this, systemd-boot doesn't support booting from different partition than the one mounted for loader entries. Our default partition is /boot/efi (kernel+initrd however in /boot), and YaST will complain about different setup than this. This is done because of snapper, which backs up /boot for the sake of keeping the same kernel and initrd for snapshots. GRUB2 with BLS will work with such setup though.

Adrian ��Nry隊Z)z{.r+맲rz^ˬzN(֜^ ޭ隊Z)z{.r+0Ǩ LCP [Stasiek] https://lcp.world

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On wto, Apr 23, 2019 at 4:36 PM, Daniel Morris wrote:

On Tue, Apr 23, 2019 at 03:56:50PM +0200, Stasiek Michalski wrote:

...

On wto, Apr 23, 2019 at 3:38 PM, John Paul Adrian Glaubitz wrote:

...

On 4/23/19 3:28 PM, Stasiek Michalski wrote:

...

GRUB is mostly pointless in scenarios where OS boots fine and only one OS is installed in graphical session. It would be nice to hide it.

Why? If you have just one operating system installed, you can just hibernate your machine anyway and don't have to reboot the machine at all.

You need to reboot for updates/upgrades (which in case of Tumbleweed are just like updates ;) ) If I didn't restart as much as I do, I wouldn't be suggesting this change :P

Why don't you just hide GRUB and/or set the timeout to 0? Zero patches, zero wait.

You will have to remember the sequence to interrupt it for those odd times you want to pass flags to the kernel, rollback etc. - and be quick-on-the-draw :)

I've found a 1 second timeout is a happy medium, and doesn't detract from the normal/fast boot sequence for family I've transitioned.

Eh, I guess I should have better explained it, GRUB requires graphical mode to be loaded before Linux is initialized, which causes needless flickering and such. Not loading GRUB at all for users and usecases where they don't need it would be a great solution in that case. LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 23/04/2019 17.00, Stasiek Michalski wrote:

On wto, Apr 23, 2019 at 4:36 PM, Daniel Morris <> wrote:

...

I've found a 1 second timeout is a happy medium, and doesn't detract from the normal/fast boot sequence for family I've transitioned.

Eh, I guess I should have better explained it, GRUB requires graphical mode to be loaded before Linux is initialized, which causes needless flickering and such. Not loading GRUB at all for users and usecases where they don't need it would be a great solution in that case.

Uninstall plymouth. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 25/04/2019 19.29, Stasiek Michalski wrote:

On czw, Apr 25, 2019 at 2:34 PM, "Carlos E. R." wrote:

...

On 23/04/2019 17.00, Stasiek Michalski wrote:

...

 On wto, Apr 23, 2019 at 4:36 PM, Daniel Morris <>  wrote:

...

...

 I've found a 1 second timeout is a happy medium, and doesn't detract  from the normal/fast boot sequence for family I've transitioned.

 Eh, I guess I should have better explained it, GRUB requires graphical  mode to be loaded before Linux is initialized, which causes needless  flickering and such. Not loading GRUB at all for users and usecases  where they don't need it would be a great solution in that case.

Uninstall plymouth.

That's unrelated, besides, we ship plymouth to make the distribution look halfway decent. You are free to uninstall it yourself though, plymouth is here to stay as the default as SUSE has decided to not develop kernel backed bootsplash.

Sorry. I always remove it on all my installs as unnecessary bloat. When I decided to do so, it accounted for half the size of the initrd image, besides causing issues. Me, I consider the flow of kernel text messages as it boots beautiful - but hey, that's me :-) I have no issues with it being the default. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org