I wonder if something is broken here. A few days ago I compiled 2.2.14 with make-kpkg and installed it. When I rebooted, 2.2.13 came up. As I recall, the symlink looked correct, however.
After I ran lilo 2.2.14 would boot. Previously, this was done as part of the .deb installation. Bob On Sat, Jan 08, 2000 at 02:04:10PM -0600, matt garman wrote: > > I was getting a bit of a headache trying to get my new kernel to work, > until I realized the following: I had "image=/vmlinuz" on one line of > my /etc/lilo.conf, but /vmlinuz is a symlink into /boot, which hadn't > been updated to point to the new kernel. > > I thought when I built a kernel with make-kpkg and installed the > resulting .deb with dpkg, that either /etc/lilo.conf was updated to see > the new kernel, or the /vmlinuz symlink was updated. Or am I mistaken? > > Thanks, > MG > > -- > Matt Garman, [EMAIL PROTECTED] > "And through the window in the wall > Come streaming in on sunlight wings > A million bright ambassadors of morning." > --Pink Floyd, "Echoes" > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- Bob Nielsen, N7XY (ex-W6SWE) (RN2) [EMAIL PROTECTED] Tucson, AZ DM42nh QRP-L #1985 http://www.primenet.com/~nielsen
