Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 137,704 of 138,051    |
|    Don Spam's Reckless Son to Andrew    |
|    Re: Why does boot block for "Purge old k    |
|    18 Mar 23 08:35:16    |
      From: hyperspace.flyover@vogon.gov.invalid              Andrew wrote:       > Tristan Miller wrote:       >> Greetings.       >>       >> Occasionally when I boot my machine, the system pauses for a minute       >> or two with the message, "A start job is running for Purge old       >> kernels".       >>       >> If I understand correctly, purging old kernels simply means       >> uninstalling them. If this is the case, why is this something that       >> boot has to block for? I mean, once the system is up an running,       >> I can always use zypper or rpm to manually remove old kernels. So       >> it's obviously something that *can* be done without interfering       >> with my use of the machine. I get why the bootup script might want       >> to clean up old kernels every once in a while, but why can't it       >> just launch a process that does this unobtrusively in the       >> background?       >>       >> Regards, Tristan       >>       >       > Having just updated a kernel on a Leap 15.4 machine, the system still       > waits for the purge to complete.       >       > The purge of the old kernels runs in parallel to the setup of my       > "wicked managed network interfaces". On a system with SSD discs the       > purge takes only slightly longer than the wicked setup. On my older       > system the purge takes well over a minute, I'd guess at 80 seconds.       >       > The older system has another problem anyway, my /boot partition is       > over 500MB and has around 50% free with the current kernel and the -1       > kernel. This is insufficient when it comes to installing a new kernel       > and I'm going to have to start getting rid of the -1 kernel before       > installing the new one. The beast is dual-boot with Windows 10 and I       > am not prepared to risk moving the main Windows partion which is just       > behind /boot.              An update has come out which fixes the problem.       purge-kernels-service-0-150200.8.6.1.noarch              It turns out the behaviour was deliberate, YaST -> Software Management       -> [search for "purge"], and then look at "Change Log". The entry for       06 May 2021.              --- 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