On 8/5/19 5:58 AM, L A Walsh wrote:
On 2019/08/04 09:13, Stasiek Michalski wrote:
Besides, some of the limitations that come with the spec (although aren't present in grub implementation in Fedora/RHEL)
Why not? Should we be using that version?
are the lack of subdirectories for boot entries as well as the lack of ability of booting linuz/initrd from non-boot partitions. openSUSE by default has boot partition set to /boot/efi, and keeps the kernel and initrd in /boot, which prevents bls compatible software
"bls-compatible?"
(namely systemd-boot) from working. This happens due to systemd-boot not mounting anything but the boot partition, while GRUB just mounts everything as it exists, slowing down the boot process, but allowing booting from each and every one of the devices present in the system.
For speed, would it be impossible to only load the kernel you want to boot from using lilo? I use lilo and go from boot to multi-user prompt in about 20-25s. I'm not using an SSD, but a 3-disk RAID 5 for boot (HW RAID).
Why does openSUSE have boot partition mounted to /boot/efi? Snapshots. We can't have kernel and initrd in snapshots if the boot partition is FAT-like, so the /boot is mounted as a btrfs submodule, while /boot/efi is a FAT-like partition which can be used by EFI.
--- Nothing supports snapshot except btrfs? FWIW, I can probably backup and restore my boot partition in less time than it would take someone to restore a snapshot (boot is only 206M used), root 3.2G and /usr 12G), though I certainly don't have snapshot granularity.
I somewhat doubt that, given restoring a snapshot is as simple as selecting an item in grub, booting running a single command then rebooting for good measure. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org