On Thu, 26 Aug 2004 07:21:34 -0500, Jeff Vian <jvian10@xxxxxxxxxxx> wrote: > On Thu, 2004-08-26 at 05:32, Philipp Ott wrote: > > Hi Bob! > > > > > What have I done wrong? Any suggestions appreciated. > > > > Can you show us the output of mount? And which harddrives and partitions > > do you have? > > > > What is the hda2 and hda3 in your fstab? Do you see a boot folder with a > > newer kernel there? > > > > I think the Label assignments in fstab and maybe /boot/grub/menu.lst > > confuses the installation process. > > > > You can safely replace Label assignments in fstab with the real > > partition. So > > > > LABEL=/1 / ext3 defaults 1 1 > > LABEL=/boot1 /boot ext3 defaults 1 2 > > > > becomes for example > > > > /dev/hda2 / ext3 defaults 1 1 > > /dev/hda1 /boot ext3 defaults 1 2 > > > > Afterwards you can use rpm -Uhv > ^^^^^ > > I take exception to giving anyone this instruction. You should use -ivh > instead. > If something happens during the update you are left with a non-working > system. If you do the install you then have 2 kernels installed and if > the new one does not work you can easily go back to the old one. > > Yum does not do an update on a kernel. It defaults to doing an install > for just this reason. Although I do not use up2date AFAIK it also > handles the kernel packages this way. > > > > > > /mnt/cdrom/Fedora/RPMS/kernel-2.6.5-1.358.i586.rpm to install the kernel > > again from the 1st Fedora CD. > > > > Regards > > Philipp Ott > > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list > If it tells you that /dev/cdrom isn't a valid block device, I would look to see what it is linked to. # cd /dev # ls -l cdrom that will show you the link to the actual device it is using. reply with that and I can better help.
