SUCCESS! It Boots! Re: kernel and booting (was Re: Ongoing Woody upgrade
Colin and the List readers.
With fervent thanks to the Almighty, and to Colin, and to the Debian List,
my system is now updated to CURRENT Woody status. Moreover, it rebooted
without significant incident.
I will write down some of the messages and ask about them and some other
issues. But right now I'm thankful and celebrating this small success.
This has been a bit traumatic because the Unix expert who was my usual
Debian helper has departed the sunny South to RI for an undetermined time.
I'm having to learn this in my dotage. When you guys use the word ancient,
look in the dictionary. You see a picture of me there beside the word. ;)
Anyhow, I'll learn this stuff well. I have a system here at the office
devoted solely to installation, and I'll install it, Sarge, Sid and X and
some various window managers until I become proficient.
Perhaps I can return in small measure the help you guys have given me.
David Teague
On Fri, 13 Sep 2002, Colin Watson wrote:
> Date: Fri, 13 Sep 2002 19:21:07 +0100
> From: Colin Watson <cjwatson@debian.org>
> To: David Teague <dbt@cs.wcu.edu>
> Subject: Re: kernel and booting issue (was Re: Ongoing upgrading Woody
>
> On Fri, Sep 13, 2002 at 12:40:59PM -0400, David Teague wrote:
> > Installation is going great guns. Only glitch was in the operator
> > headspace, i.e. my issue of installing the 2.2.20 kernel. It wanted
> > to overwrite my current 2.2.20 modules. That probably was OK but I
> > did NOT want it to mess with the boot process, so I chose to abort
> > the kernel installation at that point.
>
> Ah, that would explain why apt-get was getting a kernel; it was
> upgrading a currently installed package. If you have something like the
> following setup:
>
> /vmlinuz -> /boot/vmlinuz-2.4.18-k6
> /vmlinuz.old -> /boot/vmlinuz-2.2.20
>
> ... then my understanding is that upgrading the 2.2.20 package will not
> mess with /vmlinuz. Barring a crash or power failure, anyway, you'll
> have plenty of opportunity to check those symlinks and your boot loader
> configuration before rebooting.
>
> Hope that starts to help,
>
> --
> Colin Watson [cjwatson@flatline.org.uk]
>
>
Reply to: