You are not the only one. Before I found out it was a fluke in the dev
package that screwed up my rebooting, I thought it had something to do with
the kernels due to the error LILO spewed out.
On Wednesday 08 August 2001 10:59 pm, you wrote:
> I have had this problem with every kernel upgrade....
>
> the links to config, system.map and vmlinuz are not
> being linked to the new kernel when installed. I have
> to do this manually. Also initrd.img is not created
> (and therefore also not linked). If there is a lilo
> script that is supposed to run, it obviously fails but
> does not warn the user. This means that any
> unsuspecting user will have their system not boot
> properly after an upgrade!
>
> Am I the only person experiencing this? If so, how can
> I correct this?
>
> =====
> SI Reasoning
> [EMAIL PROTECTED]
> gnupg/pgp key id 035213BC
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
