Russell Cattelan wrote:
On Tue, 2003-04-15 at 19:02, Stefan Smietanowski wrote:
Hi Mogens.
Hm, there must be a better way of doing this (tm). Remounting
the installation partition?
...
Success! It turned out to be easier than I thought:
I couldn't umount /mnt/sysimage, it was busy because
/mnt/sysimage/proc and /mnt/sysimage/dev/pts were
also mounted.
To umount everything, and mount it again,
one has to add these two lines to
/usr/lib/booty/bootloaderInfo.py in stage2.img,
near line 806, (inbetween the calls
of /sbin/grub-install and /sbin/grub):
fsset.umountFilesystems(instRoot)
fsset.mountFilesystems(instRoot)
- maybe the upgradeGrub function needs to
be changed as well...
It works both if the /boot directory
is a part of the root directory, and if
/boot is on an XFS partition of its own.
Mogens
Excellent work. I'll be testing this and will probably release a new DVD
with this fix tomorrow. Thanx alot.
Sadly enough it didn't help.
I got an exception because the partition is in use...
And yes, I inserted those two lines on line 806.
Yes I discoverd the same thing.
I think the real solutions is to do a readonly
and then a read write mount.
I just don't know if the python code supports a remount.
// Stefan
It doesn't by default but I'm testing a workaround right now.
May I ask why you used the 2.4.20-8XFS kernel and not the 2.4.20-9XFS
kernel that I made? Thought it could be an idea to be up to date on the
files you replace at least?
// Stefan
|