You are not logged in.
Hi
I want to have two arch linux installation on my PC (like "production" and "testing"), they would use the same filesystems - except for root partition of course, and I need to keep them from overwriting the files in common boot partition:
/boot/kernel26.img
/boot/kernel26-fallback.img
- these two are allright, i will edit /etc/mkinitcpio.d/kernel26.preset to save newly generated images under different names.
BUT there are also vmlinuz26, initrd26 and System.map26 files. Do I need to care about them? How can I have them generated and saved under different names?
I have to add, that both installations might use different versions of kernel, so this might be a problem....
Offline
How about a second boot partition with a separate copy of GRUB. Have the primary boot partition chainload the second boot partition?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
I have no experiences with this.... Does it mean, that i will see grub menu twice during the boot?
I would prefer cleaner (simplier solution) if possible...
Offline
Don't share the /boot partition.
On one of them, mount /boot as /realboot (or whatever you want) (ill assume you doing this with "testing"), and edit you menu.lst with these changes:
title Arch Linux Testing
root (hd0,n) # This should be whatever it is seen on linux as -1 (sda5 -> (hd0,4) )
kernel /boot/vmlinuz26 root=/dev/sdxY ro
initrd /boot/kernel26.img
Last edited by some-guy94 (2010-01-06 23:25:17)
Offline
Sharing the boot partition will cause some hassles, I think. One idea is to have a pacman wrapper maintain each kernel in its own subdirectory, and have that alias'd to 'pacman' on each system.
An untested (and incomplete) script to show the concept:
pacman $@
if [ <simple test to identify system> ]; then
bootdir='/boot/arch1'
else
bootdir='/boot/arch2'
fi
find /boot -maxdepth 1 -type f -exec mv '{}' "${bootdir}" \;
Offline
It will be second boot partition and chainloaded grub... It seems to be simpliest solution. Thanks all
Offline