hey, when i repeat the operation now i get the following:
debian:~# apt-get upgrade linux-image-amd64/etch-backports
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
debian:~# apt-get install linux-image-amd64/etch-backports
Reading package lists... Done
Building dependency tree... Done
Selected version 2.6.21+8~bpo.1 (Backports.org archive:etch-backports) for
linux-image-amd64
linux-image-amd64 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
But when i check /boot all i see is a deb package: initrd.img-2.6.18-4-amd64,
vmlinuz-2.6.18-4-amd64, a text file
config-2.6.18-4-amd64 and System.map-2.6.18-4-amd64. i assume removing
anything would cause a crash right? Can config be edited? uname -r still
gives 2.6.18-4-amd64. Grub just offers a choice of single user mode and
regular login both with the old kernel. Can the kernel be downloaded in an
ordinary manner? Sorry for bugging you all this time. thanks very much for
the help.
Sincerely,
Cavan
On 7/7/07, Cavan Mejias <[EMAIL PROTECTED]> wrote:
Ok im using Grub. Ill give it a try.
Cavan
On 7/7/07, Barak A. Pearlmutter <[EMAIL PROTECTED]> wrote:
>
> > Dear Barak, should uname -r after reboot show: 2.6.18-4-amd64?
> thats
>
> No. You should be running 2.6.21, although 2.6.18 should still be
> available.
>
> Check in the directory /boot to be sure the 2.6.21 kernel is
> installed.
>
> (a) If not, try again using the command line:
>
> apt-get install linux-image-amd64/etch-backports
>
> (b) If it was, then for some reason the system booted into the
> incorrect available kernel. Assuming you are using "grub", which by
> default you will be, when the machine boots up you have a brief window
> to choose which kernel of the available kernels it will use.
>
> --Barak.
>
