Re: Just to increase the state of confusion.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



---- Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: 
> Aaron Konstam wrote:
> > After receiving the definitive note that F8 has reached EOL I received a
> > notice of an update waiting to be installed. Very strange.
> 
> Maybe your mirror was out of sync. Or maybe the update comes from a
> third-party repository.

One of he updates that I got one day after EOL was a kernel update so it's not a third party repository.

Jan 08 17:50:48 Updated: db4-4.6.21-3.fc8.i386
Jan 08 17:50:49 Updated: db4-cxx-4.6.21-3.fc8.i386
Jan 08 17:50:49 Updated: nss_compat_ossl-0.9.4-2.fc8.i386
Jan 08 17:51:22 Installed: kernel-2.6.26.8-57.fc8.i686
Jan 08 17:51:33 Updated: db4-devel-4.6.21-3.fc8.i386
Jan 08 17:51:55 Installed: kernel-devel-2.6.26.8-57.fc8.i686
Jan 08 17:51:55 Updated: bluez-utils-alsa-3.35-5.fc8.i386
Jan 08 17:51:56 Updated: preupgrade-1.0.1-1.fc8.noarch
Jan 08 17:51:59 Updated: kernel-headers-2.6.26.8-57.fc8.i386
Jan 08 17:52:00 Updated: bluez-utils-cups-3.35-5.fc8.i386
Jan 08 17:52:02 Updated: bluez-utils-3.35-5.fc8.i386
Jan 08 17:52:05 Updated: xterm-238-1.fc8.i386
Jan 08 17:52:06 Updated: vpnc-0.5.3-1.1.fc8.i386

And as Murphy would have it, this kernel doesn't boot:
...
Booting the kernel.
Red Hat nash version 6.0.19 starting
Unable to access resume device (UUID=blah blah blah...)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed. No such file or directory.
setuproot: error mounting /proc. No such file or directory.
setuproot: error mounting /sys. No such file or directory.
switchroot: mount failed: No such file or directory.

The 2.6.26.5-28.fc8 boot just fine. The normal procedure would be to file a bug but in this case that's not possible since all F8 bugs have been dropped.

So why don't I just upgrade to F9? Well, I'd like to but as I've previously reported on this list, something modified my /etc/fstab, inserted a bunch of UUIDs and removed the mount point for windows drive (dual boot) and so broke BackupPC. I'm about to start another thread on trying to figure this out and I don't want to upgrrade until I have a good backup.

Steve

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux