I bought a computer with Leap 15.0 preinstalled on an SSD, and I also wanted to install Tumbleweed on the disk. For reasons detailed below, I did this without installing a bootloader for Tumbleweed, but since Tumbleweed is frequently updated, including grub2, I think it would be better to install the bootloader in Tumbleweed. Due to my lack of knowledge, I would be grateful for advice on how to do that safely. Some specifics follow about the disk and what I did to install Tumbleweed. The SSD had three partitions: /boot, / (root) and swap. I shrank the root partition (formatted as ext4) and added a btrfs partition for Tumbleweed. I first left /boot and swap as is, but the Tumbleweed installer said there was no bootable partition (I don't remember the exact wording, something like no BIOS boot table). I then tried deleting the /boot partition and adding it again, selecting "BIOS Boot" as the partition ID, but the installer still said there was no bootable partition. I also tried different file systems to format /boot -- originally it was FAT and I also tried XFS and ext3 -- but that made no difference. So finally, I left the /boot partition unchanged but unmounted it and proceeded with the installation. At the summary I then changed the boot setup to prevent any boot loader being installed and any changes made to the MBR. The installer said I might end up with an unbootable system, but I went ahead anyway. The installation completed and on rebooting the boot screen showed only Leap 15.0 as before, but after running grub2-mkconfig in Leap, Tumbleweed was found and I could boot it and it seems to be fine. The disk has GPT with protective MBR. As noted the /boot partition is formatted as FAT and also contains a directory efi, which is populated in the running Leap, which mounts /boot/efi, but in the running Tumbleweed, where /boot is not a separate partition, after mounting the partition Leap sees as /boot/efi, the efi directory is empty (in the running Tumbleweed). I do not plan to install any MS-Windows system, but I do plan to install other Linux-based systems besides Tumbleweed, and possibly a *BSD system. How can I install the bootloader in Tumbleweed -- either from the currently installed Tumbleweed or by reinstalling it -- without risking making both Tumbleweed and Leap unbootable? If that requires deleting the existing /boot partition and add it anew, is it necessary, given the systems I plan to install, to have the efi directory, and if so, do I just have to make /boot/efi a mountpoint, and if not, what else to I need to do to make sure it exists and gets populated as required (if it's required)? And if the efi directory is not needed, what would be the recommended file system for the boot partition? I also have a question concerning having a separate /boot partition shared by Leap, Tumbleweed and any other systems I install: in each system the directory /boot contains versioned files of the kernel, config, etc., but there are also symlinks vmlinuz and initrd pointing to the latest version installed in the system; if Leap and Tumbleweed (and other Linux-based systems) populate the same /boot directory, the last one installed would override existing symlinks, so I don't see how this can work. Is it possible for different systems to use the same /boot directory, installed on a separate partition, and if not, where do the files used for booting different systems need to go, when a separate /boot partition is used? Thanks, Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org