
On 04/07/2018 06:04 AM, André Verwijs wrote:
Leap 15 191.1 fix boot-loader first..!!! else there's no point for testing...
I have done several installs of Leap 15. The boot loader has been fine. I just did a test install today, with legacy booting (not UEFI). And it was fine.
for "bios_boot" partition create a subvolume to make leap bootable...
This does not make any sense. There needs to be a bios_boot partition. A bios_boot subvolume is not the same thing, and would not work. The default install proposal created a bios_boot partition. I'm not seeing any problem there. Yes, if you skip the proposed partitioning and use the expert partitioner, then you will need to manually create a bios_boot partition. If you use the expert partitioner, you are supposed to be expert enough to know that. I've been reading your posts to this list. But when I look into testing the problems you describe, I find that you have not given enough detail on what the problems are. You have not said what you tried to do. You have not said what file system you use. As far as I know, if you use "btrfs", then you need to boot from the MBR unless you have a separate "/boot". And a separate "/boot" is a bad idea with "btrfs", because booting a snapshot won't work. If you boot from the MBR, then it is not necessary that a partition be flagged as active. But you will need a "bios_boot" partition for installing grub to the MBR with a "btrfs" root partition. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org