On Fri, 2003-10-17 at 10:14, Justin Findlay wrote: > I did that: > > title Red Hat Linux (2.4.22) > root (hd0,0) > kernel /vmlinuz-2.4.22 ro root=/dev/hda3=/ > initrd /initrd-2.4.22.img > > and now it tells me: > > ds: no socket drivers loaded! > Kernel panic: VFS: Unable to mount root fs on 03:00 >
This may be causing the problem. It should be
kernel /vmlinuz-2.4.22 ro root=/dev/hda3
instead of
kernel /vmlinuz-2.4.22 ro root=/dev/hda3=/
> But how can the stock redhat kernels boot with this mysterious LABEL
> variable?
>
The LABEL indicates the volume label. I think RedHat setup will assign
labels to your partitions after partitioning your hard disk. man fstab
says the following about labels:
"Instead of giving the device explicitly, one may indicate the (ext2 or xfs)
filesystem that is to be mounted by its UUID or volume label (cf. e2label(8)
or xfs_admin(8)), writing LABEL=<label> or UUID=<uuid>, e.g., `LABEL=Boot'
or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will make the system
more robust: adding or removing a SCSI disk changes the disk device name
but not the filesystem volume label."
Technically the LABEL technique should work, but only if the volumes
actually have those labels. I think you can view this information in fdisk or
cfdisk.
Casey
signature.asc
Description: This is a digitally signed message part
_______________________________________________ newbies mailing list [EMAIL PROTECTED] http://phantom.byu.edu/cgi-bin/mailman/listinfo/newbies
