On Sat, 11 May 2019 22:39:46 +0200 Knurpht-openSUSE <knurpht@opensuse.org> wrote:
Op zaterdag 11 mei 2019 22:21:32 CEST schreef Carlos E. R.:
On 11/05/2019 20.27, Knurpht-openSUSE wrote:
Op zaterdag 11 mei 2019 20:11:25 CEST schreef Carlos E. R.:
On 11/05/2019 19.58, Stephen Berman wrote:
You can not share the /boot partition.
O? I have: But you are an expert. You don't count :-p
knurpht@Knurpht-HP:~> cat /leaproot/etc/fstab | grep boot/efi UUID=AC45-5602 /boot/efi vfat defaults 0 0 knurpht@Knurpht-HP:~> cat /etc/fstab | grep boot/efi UUID=AC45-5602 /boot/efi vfat defaults 0 0 knurpht@Knurpht-HP:~>
where the top one is Leap 15.0's, the bottom one is Tumbleweed's.
As I wrote, I also have /boot/efi mounted in Leap 15.0. Does that mean Leap is using UEFI to boot? If so, how can I get Tumbleweed to use it as well? As I also wrote in my followup to Carlos E.R., I was unable to do this during the Tumbleweed installation. Should it be possible and if so, how? A possibly relevant datapoint: When I compare the /boot directories in my Leap and Tumbleweed installations, in addition to /boot in Tumbleweed lacking the efi subdirectory, I see that, while in both installations the grub2 subdirectory contains the subdirectory x86_64-efi, in Leap it is filled with 267 *.mod files, while in Tumbleweed it is empty (both installations also contain the directory i386-pc under grub2; in Leap it contains 277 *.mod files, in Tumbleweed 278). Is this another indication that the bootloader (in Leap) is using UEFI?
But that's the EFI partition, it is designed to be shared. I was talking about the /boot partition. Ah, OK, you're right. Don't know why one could not share a parition mounted on /boot ....
Can you elaborate? What about the vmlinuz and initrd symlinks? Are they not necessary? Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org