Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 9026 - grub configuration as listed is incorrect in code listing 16.14
Summary: grub configuration as listed is incorrect in code listing 16.14
Status: RESOLVED INVALID
Alias: None
Product: Websites
Classification: Unclassified
Component: [OLD] Documentation (show other bugs)
Hardware: x86 All
: Lowest trivial (vote)
Assignee: Sherman Boyd (meekrob) (RETIRED)
URL: http://www.gentoo.org/doc/build.html
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-11 21:31 UTC by Jeff Lanthripp
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Lanthripp 2002-10-11 21:31:53 UTC
The following two lines are incorrect in code listing 16.14:

splashimage=(hd0,0)/boot/grub/splash.xpm.gz
kernel /boot/bzImage root=/dev/hda3

With the example setup given in the rest of the document, the correct lines 
would be:

splashimage=(hd0,0)/grub/splash.xpm.gz
kernel /bzImage root=/dev/hda3 

This is because the boot partition is separate from the root partition in the 
setup example given.  If the boot partition wasn't separate, the lines of code 
in code listing 16.14 would be correct.  Since the boot partition is separate, 
the leading /boot leads to a system that cannot be booted from hard disk.  The 
situation is easily remedied by booting to a livecd, mounting the boot 
partition (/dev/hda1 in the example), and editing menu.lst to fix the 2 
erroneous lines.
Comment 1 Jeff Lanthripp 2002-10-11 22:14:41 UTC
I just was informed that there should have been a symlink, /boot/boot, pointing 
to /boot

This symlink wasn't there because emerge system had failed on grub due to the 
fact that /boot couldn't be remounted in rw mode because it was mounted as vfat 
(perhaps because win2k had previously been installed on that hard drive?).  I 
therefore had to manually unmount /dev/hda1 and remount it with the "-t ext3" 
switch.  This apparently caused the symlink to either disappear or to not be 
created in the first place.