Re: Upgrade to 9.04?



On Thu, Oct 8, 2009 at 11:43 PM, Willis Taylor <th1bill@xxxxxxxxxxxxx> wrote:

I am two full days getting to this point and I have backed up my Home
Directory to DVD.  Would I be better off t cease trying to grow sme hair

Sometimes, yes. It might be better to do a clean install, provided how
much stuff you've already put on that system that won't be on the CD.
It's a tossup. I came from a Debian system where you basically kept on
the same platform (testing) and rode that, and never installed a new
release from point zero. But that's just me.

More to the point, I think NoOp is on the right track with the RT
kernel you're using. "rt" means "real time" and if there's no
compelling reason to use that flavor of the kernel, you should stick
to more "generic" kernels. But the root of your problem is a
sependency issue because some of the packages depend on other packages
that can't be installed or because they're not configurable, which
goes basically into a circular loop.

Backing out of that problem might be difficult, since the main
component that's at issue is a kernel. We certainly don't want you to
end up with an unbootable system (even so, you could temporarily
select one of the other installed kernels listed in grub).

Here's what aptitude shows (this is Jaunty, but only the version
numbers have been changed to protect the innocent) for linux kernels

p linux-image - Generic Linux kernel image.
v linux-image-2.6 -
i A linux-image-2.6.27-11-generic - Linux kernel image for
version 2.6.27 on x86/
c linux-image-2.6.27-7-generic - Linux kernel image for
version 2.6.27 on x86/
c linux-image-2.6.27-9-generic - Linux kernel image for
version 2.6.27 on x86/
i A linux-image-2.6.28-10-generic - Linux kernel image for
version 2.6.28 on x86/
i A linux-image-2.6.28-11-generic - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-11-server - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-11-virtual - Linux kernel image for
version 2.6.28 on x86/
i A linux-image-2.6.28-13-generic - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-13-server - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-13-virtual - Linux kernel image for
version 2.6.28 on x86/
i A linux-image-2.6.28-14-generic - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-14-server - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-14-virtual - Linux kernel image for
version 2.6.28 on x86/
i A linux-image-2.6.28-15-generic - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-15-server - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-15-virtual - Linux kernel image for
version 2.6.28 on x86/
p linux-image-2.6.28-3-rt - Linux kernel image for
version 2.6.28 on Ingo
i linux-image-2.6.28-8-generic - Linux kernel image for
version 2.6.28 on x86/
i A linux-image-2.6.28-9-generic - Linux kernel image for
version 2.6.28 on x86/
i linux-image-generic - Generic Linux kernel image
p linux-image-rt - Rt Linux kernel image
p linux-image-server - Linux kernel image on Server Equipment.
p linux-image-virtual - Linux kernel image for virtual machines


Key :

i means installed
i A means automatically installed
p means it's a package and not installed
v is a "virtual" package

There are basically several components to the kernel - here, you see
"linux-image-generic" which is actuallly a small package which is a
"meta" package that always installs he most up to date kernel
available for the platform (2.6.28-15 for Jaunty ATM). Same with
"linux-image-rt". But for most use, linux-image-generic is what you
should use.

There should be a way to safely back out of your situation if you
remove the linux-image-rt stuff you already have and do a manual
install with aptitute of linux-image-generic, but realistically this
is something that the update manager should have been able to handle.

Hope you can solve your problem.
--
thanks for letting me change the magnetic patterns on your hard disk.

--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



Relevant Pages

  • Re: Upgrading from old Sarge (Testing) to Unstable
    ... > The package I'm most concerned about upgrading is the kernel. ... If you installed it via the debian tools, ie. via a .deb package it will be found in the 'Obsolete and locally created packages' section in aptitude. ... You can later install a new kernel or compile a new kernel, but as said in the release info, I strongly recommend to do this in a separate step: use your existing kernel to see if everything works fine; ... 50% Building Dependency Tree Reading extended state information... ...
    (Debian-User)
  • SUSE Security Announcement: several kernel security problems (SUSE-SA:2005:044)
    ... please install the update packages. ... Use the following command to determine which kind of kernel is ... Download the kernel RPM package for your distribution with the ... Starting from SUSE LINUX 9.2, ...
    (Bugtraq)
  • Re: Using yum to update livna nvidia packages?
    ... >> Yum by default does an install on new kernels and modules. ... >> package and since that comes from livna the issue at that point would ... 6629 drive installed for the existing kernel 2.6.10-1.770. ...
    (Fedora)
  • Re: I get it now! (smbfs support)
    ... > under dselect and no dependency warnings being issued. ... The smbfs package only gives you the programs to mount the shares. ... dependency system cannot see if your kernel has smbfs support. ... be annoying if you had to install another kernel only to get the smbfs ...
    (comp.os.linux.setup)
  • input method on fc3?
    ... FC3 and soundcard ... >> without problems and sound works fine. ... What modules were loaded with kernel ... I can install and configure samba on Linux as easily as I can install ...
    (Fedora)