Yes indeed. Tha's what it did. hmm..
Could rootdir=/ be the default and the section:
# Get the root drive.
# For now, this uses the program `df' to get the device name, but is
# this really portable?
root_device=`df ${rootdir} | grep /dev/ | sed
's%.*\(/dev/[a-z0-9]*\).*%\1%'`
root_drive=`convert $root_device`
if test "x$root_drive" = x; then
exit 1
fi
just be changed to use $grubdir then? This will exist at this point as
it would have either been a mount point or been created by:
# Create the GRUB directory if it is not present.
test -d $bootdir || mkdir $bootdir
test -d $grubdir || mkdir $grubdir
earlier? It will also include any rootdir specified by the user.
OKUJI Yoshinori wrote:
>
> From: Tim Riker <[EMAIL PROTECTED]>
> Subject: Re: [grub] bug report
> Date: Fri, 14 Apr 2000 19:13:19 -0600
>
> > I noticed this too and worked around it by setting:
> >
> > rootdir=/boot/grub
> >
> > which is where we have grub installed by default. This way if /boot is a
> > separate partition (possible) grub still seems to do the right thing.
>
> No. See grub-install.in carefully. If you set ROOTDIR to /boot/grub,
> then the script will copy GRUB images to /boot/grub/boot/grub. That's
> not what you want to do. The problem here is that GRUB doesn't know
> how to ``mount'' partitions. I don't think there is any general way to
> solve the "separate partition" problem automatically, so the user
> should specify the root directory explicitly.
>
> Okuji
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
