LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   A reminder for upgrading - I did it again :( (http://www.linuxquestions.org/questions/slackware-14/a-reminder-for-upgrading-i-did-it-again-4175462993/)

mlangdn 05-22-2013 07:41 AM

A reminder for upgrading - I did it again :(
 
I've been a bit lazy and had been putting off upgrading -current. The last one I had done was back on May 7, there has been a lot of activity since. Time to go to work....

Everything seemed to have went well until the reboot. I had a screen but no way would the input devices work. No keyboard, no mouse. I knew I had made a new initrd, changed lilo.conf, had already uninstalled the Nvidia driver, and it seemed all the rest of the miscellaneous stuff there is to do.

Thankfully, I always have a custom kernel ready to go. I rarely use it, but its there waiting to save my butt.

What dawned on my feeble brain in a flash was I had not ran lilo.

All is well once again.

allend 05-22-2013 09:22 AM

Quote:

What dawned on my feeble brain in a flash was I had not ran lilo.
Literally LOL. Should run a poll on that one. I did it myself (OH NO not again! Will I never learn?) going from kernel 3.8.11 to 3.8.13 recently.
Just because the internet connection is most reliable late at night does not mean that it is the best time to do a kernel upgrade. :-)

mrclisdue 05-22-2013 10:01 AM

Add me to the "forgot to run lilo" heart-stopping kernel panic moment....

The other occasional "gotcha" occurs if I have neglected to change the default download_all=no to yes in slackpkg.conf. Invariably, at some point in the next few months, I'll return to my screen to see the various failure messages from slackpkg, and if it's a good day, I'll immediately recognize the problem. However, on a not-so-good day I may just kick the dog and scream at the kids (my own kids are grown and gone, but there are always a few snotty-nosed ones in the hood that I can scare away....)

cheers,

brianL 05-22-2013 10:07 AM

Me too. Anybody who hasn't?

ruario 05-22-2013 10:12 AM

You could always use extlinux and then as long as you defined /boot/vmlinuz as the kernel in your extlinux.conf and it is a symlink pointing to your kernel you are good to go (though you will need /boot to be ext{2,3,4} or btrfs). There is no extra command to run before rebooting.

mina86 05-22-2013 11:05 AM

I'm using my own installkernel script which can be configured to upgrade lilo automatically. In the past I had it also set up to automatically compile and install new nVidia drivers. But yeah, it sort of implies that you'll compile your own kernel rather than using stock one.

Bindestreck 05-22-2013 11:11 AM

I never forget to run Lilo, never.

mrclisdue 05-22-2013 11:19 AM

Quote:

Originally Posted by eXpander_ (Post 4956599)
I never forget to run Lilo, never.

Quite possible. But are you aware that you're not wearing trousers?

cheers,

dugan 05-22-2013 11:24 AM

I just updated with slackpkg, and it promoted me to run lilo.

EDIT: That prompt is dangerous! It turned out I had to edit my lilo.conf to change the version of vmlinuz being pointed to, and also regenerate my initrd.

zakame 05-22-2013 11:48 AM

I guess that's the reason why the kernel package advice in /etc/slackpkg/blacklist is there.

Didier Spaier 05-22-2013 11:52 AM

I hope we won't forget anymore ;)

onebuck 05-22-2013 12:35 PM

Member Response
 
Hi,
Quote:

Originally Posted by Didier Spaier (Post 4956628)

Cute!

As to forgetting to run lilo, who me? Honestly, only a few times. :doh:

Bindestreck 05-22-2013 12:38 PM

Quote:

Originally Posted by mrclisdue (Post 4956610)
Quite possible. But are you aware that you're not wearing trousers?

cheers,

Am, yes, you ate it, remember?

rkelsen 05-22-2013 07:14 PM

3 cheers for UEFI and eLILO!

Once the new kernel has been added to elilo.conf, there is nothing more to do. :)

ChrisAbela 05-23-2013 02:06 AM

Quote:

I never forget to run Lilo, never.
Isn't that a double negative?


All times are GMT -5. The time now is 11:51 PM.