Regarding to multiple boot partitions

[Noratio]

Hi,
I've got dualboot with fc3 32bit and 64bit. Both have separate boot partitions all partitions are done manually. 32 was installed first on sda 64 bit on sdb. MBR is on sda for both installations as i did not install it on sdb.

Problem is that when I update kernel for x86_64 on sdb yum writes kernel (vwlinuz,System.map,initrd,config) to boot partition on sda. Now kernel files for both i386 and x86_64 are named exactly the same. How to avoid overwrite? Or am I just wrong and these files are the same?

I've got a workaround cause had proper order for updates, also could have installed grub on sdb mbr and booted from there also to kernel files on sda boot partition. So this interest me for optimal solution for future.

[sideways]

You have separate boot partitions, by this do you mean where the /boot directory is mounted?

Grub is installed in mbr of sda, so I do not see why you have a problem.

/boot for 32bit will be on sd0 (root (sd0,0) probably) and /boot for 64bit will be on sd1, so your kernel, config files and ramdisk images are all separate.

Or am I misunderstanding you.

[Noratio]

If I update kernel for x86:64 on sdb with yum it writes kernel and configuration ... files mentioned to boot partition of fc3 i386 on sda1. I'll switch box and edit partitions here.

# grub MBR @ sda
#===============
# 32bit fc3:
# sda1 boot
# sda2 home
# sda3 swap for both systems
# sda5 root
#================================================= ====
# sdb1 = currently for temporary storage later for tmp or /and swap
#================================================= ====
# 64bit fc3:
# sdb2 boot
# sdb3 root
# sdb5 home

[nick.stumpos]

can you post your fstab here, are you sure your mounting the correct boot partition for each os

[Dies]

can you post your fstab here, are you sure your mounting the correct boot partition for each os

Yes, exactly, it shouldn't be doing that, it should be writing those files to whatever partition is currently mounted as /boot.

[Noratio]

Thanks guys, I just trusted did right during the installation, apparantely not.
both fstabs points:

LABEL=/boot12 /boot ext3 defaults 1 2


So I'll point them straight to devices

/dev/sda1 /boot ext3 defaults 1 2

and

/dev/sdb2 /boot ext3 defaults 1 2


Is there proper explanation of rh label method for fedora? I never got e2label command work.

[Dies]

Works fine for me.
Try man e2label for a full explanation and usage.

[Noratio]

Thanks
/sbin/e2label
just gave up too soon, something you don't do everyday. Always nice to read man pages after asking forums, well sorry about that. How many times could i have used it, oh well...

Definately something I don't still get about yum and multiple boots. I gave up keeping software supported kernel 2.6.9-1.667 on one boot and ran yum update on it. After reboot the thing just stared me from black screen and message "GRUB". Responding nothing.

I remember having this earlier and booting linux resque:


chroot /mnt/sysimage
grub-install /dev/sda

makes it ok again

Maybe I'll go back to labels.

Sometimes things look desperately complicated for no reason at all, just had add tens of lines to fstab but just didn't think about this. Thanks for your time.