<quote who="Daniel"> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> /etc/fstab is set up properly with /dev/hda3 being mounted to /. I >> believe >> that this is too early in the boot process for fstab to be even >> accessed. > > fstab is accessed soon after the execution of /sbin/rc > >> If I am not mistaken, at the point that this is happening, it is only >> responding to the kernel options passed from grub. > >>I would assume that it >> is assigning the /dev/ROOT to whatever is passed as the root= in the >> commandline from grub. > > both entries under most conditions need to be consistant. There is no > automatic detection from the grub kernel args.
Okay. My bad on this count. > >>I may be wrong here, but, whatever the case, the >> entries in /etc/fstab are not the issue here. > > Just for example my /etc/fstab (using devfs - replace with > /dev/hd[a-z][1-8] > as desired). > > Mine reads: /dev/hda1 /boot ext2 noauto,noatime 1 1 /dev/hda2 none swap noatime 0 0 /dev/hda3 / ext3 noatime 0 0 There is also the tmp section as well, but this should be the offending party, however, it looks right to me. According to fdisk, this is how I have the disk partitioned. It is also how I had the filesystem mounted to do the install. I am pretty sure that fstab is not the issue, though I do not have any better idea. Not really sure what is up, but, as background, this was happening to me before whenever I tried to build any software. This is the reason that I tried to rebuild the entire system. It was a 1.2 to 1.4 upgrade that had never quite taken to the change. It was a bit buggy, and this was the last straw. Anyway, I am trying to build it on another hard drive at the moment, just in case it is some weird hard drive glitch. Thanks for the ideas. -- Ian Truelsen Email: [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
