Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.slackware    |    I think its the one without Selinux crap    |    87,272 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 86,522 of 87,272    |
|    Henrik Carlqvist to root    |
|    Re: Updating to current    |
|    10 Dec 23 10:39:44    |
      From: Henrik.Carlqvist@deadspam.com              On Sat, 09 Dec 2023 12:45:08 +0000, root wrote:       > In that case, I suppose that slackpkg upgrade will also create a new       > initrd, and all I will have to do it re-run lilo before booting into       > the new system?              I haven't used slackpkg myself (I have my own scripts and Makefile to       download and install security patches) and I don't have any initrd       installed as I use huge kernels. However, from what I have seen in       threads about broken installations after kernel upgrades and read in the       changelog I think that you will manually have to create a new initrd if       you are using a generic kernel.              Again what Petri wrote:              On Thu, 07 Dec 2023 06:21:33 +0000, Petri Kaukasoina wrote:       > "Be sure to upgrade your initrd after upgrading the kernel packages.       > If you use lilo to boot your machine, be sure lilo.conf points to the       > correct kernel and initrd and run lilo as root to update the       > bootloader.       > If you use elilo to boot your machine, you should run eliloconfig to       > copy the kernel and initrd to the EFI System Partition."              regards Henrik              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca