Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Each new user of a new system uncovers a new class of bugs. -- Kernighan


computers / alt.os.linux.suse / Re: Why does boot block for "Purge old kernels"?

SubjectAuthor
* Why does boot block for "Purge old kernels"?Tristan Miller
+- Re: Why does boot block for "Purge old kernels"?Andrew
+* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
|`* Re: Why does boot block for "Purge old kernels"?Andrew
| `* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
|  +- Re: Why does boot block for "Purge old kernels"?Bit Twister
|  `* Re: Why does boot block for "Purge old kernels"?Tristan Miller
|   +- Re: Why does boot block for "Purge old kernels"?Andrew
|   `- Re: Why does boot block for "Purge old kernels"?Carlos E.R.
+- Re: Why does boot block for "Purge old kernels"?Andrew
`* Re: Why does boot block for "Purge old kernels"?Andrew
 +* Re: Why does boot block for "Purge old kernels"?Uwe Bonnes
 |`- Re: Why does boot block for "Purge old kernels"?Carlos E.R.
 +* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
 |`* Re: Why does boot block for "Purge old kernels"?Andrew
 | `* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
 |  `* Re: Why does boot block for "Purge old kernels"?Andrew
 |   `* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
 |    `* Re: Why does boot block for "Purge old kernels"?Andrew
 |     `* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
 |      `* Re: Why does boot block for "Purge old kernels"?Andrew
 |       `- Re: Why does boot block for "Purge old kernels"?Aragorn
 `* Re: Why does boot block for "Purge old kernels"?Don Spam's Reckless Son
  `* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
   `* Re: Why does boot block for "Purge old kernels"?Don Spam's Reckless Son
    `* Re: Why does boot block for "Purge old kernels"?Carlos E.R.
     `* Re: Why does boot block for "Purge old kernels"?Don Spam's Reckless Son
      `- Re: Why does boot block for "Purge old kernels"?Carlos E.R.

Pages:12
Why does boot block for "Purge old kernels"?

<t38vgs$v6d$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=494&group=alt.os.linux.suse#494

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: psychon...@nothingisreal.com (Tristan Miller)
Newsgroups: alt.os.linux.suse
Subject: Why does boot block for "Purge old kernels"?
Date: Thu, 14 Apr 2022 13:11:24 +0200
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <t38vgs$v6d$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 14 Apr 2022 11:11:24 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="28dc1ebf9014a5287453d49eba5a56f6";
logging-data="31949"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/0a/5jr7Ot4bHDW8NGtF99H5yNkL5U3GE="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.8.0
Cancel-Lock: sha1:pY37Um1xLN1I2xof5+MZ80eu36A=
Content-Language: en-CA
 by: Tristan Miller - Thu, 14 Apr 2022 11:11 UTC

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

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: Why does boot block for "Purge old kernels"?

<t39ev0$1t1l$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=495&group=alt.os.linux.suse#495

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!iNGj/luDezKLilfl3oxwcA.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Thu, 14 Apr 2022 17:34:56 +0200
Organization: Aioe.org NNTP Server
Message-ID: <t39ev0$1t1l$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="62517"; posting-host="iNGj/luDezKLilfl3oxwcA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.11.1
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Thu, 14 Apr 2022 15:34 UTC

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
>

I think you'll find that the function runs the next time you boot after
a kernel update, but I was wondering exactly the same thing yesterday
evening. A new kernel was installed, I rebooted and then watched the
system taking a timeout while removing the (-2) kernel.

--
This mail has been tested by https://RKIvirus.com/ and has been found to
contain Covid-19. Disinfect after reading.

Re: Why does boot block for "Purge old kernels"?

<2aurii-08o.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=496&group=alt.os.linux.suse#496

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!weretis.net!feeder8.news.weretis.net!news.mixmin.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 17 Apr 2022 00:58:42 +0200
Lines: 31
Message-ID: <2aurii-08o.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net JY+EWgpwB89OTDUF56G8SwONr32+BoEWtepLJvJ9qS86QzaZ/B
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:TsFbmg+4c4AzU6tNL7QLIgl5xgE=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.8.0
Content-Language: en-CA
In-Reply-To: <t38vgs$v6d$1@dont-email.me>
 by: Carlos E.R. - Sat, 16 Apr 2022 22:58 UTC

On 2022-04-14 13:11, 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?

AFAIK, it doesn't block here, other things continue running, even the
boot sequence. I can not check this instant, but I think I can login
while the job is running. I should be able to verify this tomorrow.

You do not say what release you are using.

The job simply calls on zypper to delete the oldest kernel after an update.

You can verify what it does by running:

systemctl cat purge-kernels.service

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<t3gesa$nal$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=500&group=alt.os.linux.suse#500

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!iNGj/luDezKLilfl3oxwcA.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 17 Apr 2022 09:16:26 +0200
Organization: Aioe.org NNTP Server
Message-ID: <t3gesa$nal$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me> <2aurii-08o.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="23893"; posting-host="iNGj/luDezKLilfl3oxwcA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.11.1
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Sun, 17 Apr 2022 07:16 UTC

Carlos E.R. wrote:
> On 2022-04-14 13:11, 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?
>
> AFAIK, it doesn't block here, other things continue running, even the
> boot sequence. I can not check this instant, but I think I can login
> while the job is running. I should be able to verify this tomorrow.
>
> You do not say what release you are using.
>
>
> The job simply calls on zypper to delete the oldest kernel after an update.
>
> You can verify what it does by running:
>
> systemctl cat purge-kernels.service
>
>
I have Leap 15.3 with the splash screen turned off so that I can see
what is going on. The script runs as part of the boot process and
*before* logging in is possible, this is obviously what Tristan sees as
well. In my case - on my old laptop, no ssd - it delays the appearance
of the login screen by just over a minute.
No idea if this is something new, I'll often boot and then get on with
something else for a minute or two. It *is* something I first noticed a
couple of days before Tristan reported it here.

--
This mail has been tested by https://RKIvirus.com/ and has been found to
contain Covid-19. Disinfect after reading.

Re: Why does boot block for "Purge old kernels"?

<6j6tii-7un.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=501&group=alt.os.linux.suse#501

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.mixmin.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 17 Apr 2022 12:26:14 +0200
Lines: 64
Message-ID: <6j6tii-7un.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <2aurii-08o.ln1@Telcontar.valinor>
<t3gesa$nal$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net Cfxozh0A+cyptrAUjkqf/woFf/Ei9Mdnm2wv5NRbmXoBOcusJC
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:NXw/4Yu6DdiKkrhVcnj6oCebrYY=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.8.0
Content-Language: en-CA
In-Reply-To: <t3gesa$nal$1@gioia.aioe.org>
 by: Carlos E.R. - Sun, 17 Apr 2022 10:26 UTC

On 2022-04-17 09:16, Andrew wrote:
> Carlos E.R. wrote:
>> On 2022-04-14 13:11, 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?
>>
>> AFAIK, it doesn't block here, other things continue running, even the
>> boot sequence. I can not check this instant, but I think I can login
>> while the job is running. I should be able to verify this tomorrow.
>>
>> You do not say what release you are using.
>>
>>
>> The job simply calls on zypper to delete the oldest kernel after an
>> update.
>>
>> You can verify what it does by running:
>>
>> systemctl cat purge-kernels.service
>>
>>
> I have Leap 15.3 with the splash screen turned off so that I can see
> what is going on.  The script runs as part of the boot process and
> *before* logging in is possible, this is obviously what Tristan sees as
> well.  In my case - on my old laptop, no ssd - it delays the appearance
> of the login screen by just over a minute.
> No idea if this is something new, I'll often boot and then get on with
> something else for a minute or two.  It *is* something I first noticed a
> couple of days before Tristan reported it here.
>

I booted this Leap 15.3 today after a kernel update. I did:

systemd-analyze plot >bootup.svg
eog bootup.svg

And I clearly see that the boot process continues running while
purge-kernels is running (for 41 seconds in my case).

It is the service "display-manager" which waits, apparently.

You can run "systemd-analyze critical-chain", but in my case
"purge-kernels" is not listed, which I think it means it does not delay
others.

I suggest you ask in the support mail list.

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<slrnt5o6l6.jfqo.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=502&group=alt.os.linux.suse#502

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 17 Apr 2022 08:48:20 -0500
Organization: A noiseless patient Spider
Lines: 63
Message-ID: <slrnt5o6l6.jfqo.BitTwister@wb.home.test>
References: <t38vgs$v6d$1@dont-email.me> <2aurii-08o.ln1@Telcontar.valinor>
<t3gesa$nal$1@gioia.aioe.org> <6j6tii-7un.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="e709a7f18b087c4a372c865880d06380";
logging-data="4509"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18oE/T/CkQA6xdo98IoX/rd23HiMQ69azc="
User-Agent: slrn/pre1.0.4-6 (Linux)
Cancel-Lock: sha1:fu+6jUtHxGGP3W13Gz4X7m2GdYs=
 by: Bit Twister - Sun, 17 Apr 2022 13:48 UTC

On Sun, 17 Apr 2022 12:26:14 +0200, Carlos E.R. wrote:
> On 2022-04-17 09:16, Andrew wrote:
>> Carlos E.R. wrote:
>>> On 2022-04-14 13:11, 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?
>>>
>>> AFAIK, it doesn't block here, other things continue running, even the
>>> boot sequence. I can not check this instant, but I think I can login
>>> while the job is running. I should be able to verify this tomorrow.
>>>
>>> You do not say what release you are using.
>>>
>>>
>>> The job simply calls on zypper to delete the oldest kernel after an
>>> update.
>>>
>>> You can verify what it does by running:
>>>
>>> systemctl cat purge-kernels.service
>>>
>>>
>> I have Leap 15.3 with the splash screen turned off so that I can see
>> what is going on.  The script runs as part of the boot process and
>> *before* logging in is possible, this is obviously what Tristan sees as
>> well.  In my case - on my old laptop, no ssd - it delays the appearance
>> of the login screen by just over a minute.
>> No idea if this is something new, I'll often boot and then get on with
>> something else for a minute or two.  It *is* something I first noticed a
>> couple of days before Tristan reported it here.
>>
>
> I booted this Leap 15.3 today after a kernel update. I did:
>
> systemd-analyze plot >bootup.svg
> eog bootup.svg
>
>
> And I clearly see that the boot process continues running while
> purge-kernels is running (for 41 seconds in my case).
>
> It is the service "display-manager" which waits, apparently.
>
>
> You can run "systemd-analyze critical-chain", but in my case
> "purge-kernels" is not listed, which I think it means it does not delay
> others.

You can have a large delay if anything runs update-grub.
The large delay is caused by umount of each partition update-grub opened/mounted.

Re: Why does boot block for "Purge old kernels"?

<t3m8ho$v79$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=506&group=alt.os.linux.suse#506

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: psychon...@nothingisreal.com (Tristan Miller)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Tue, 19 Apr 2022 14:05:12 +0200
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <t3m8ho$v79$1@dont-email.me>
References: <t38vgs$v6d$1@dont-email.me> <2aurii-08o.ln1@Telcontar.valinor>
<t3gesa$nal$1@gioia.aioe.org> <6j6tii-7un.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 19 Apr 2022 12:05:12 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="faee35124b77778fdca6837bf64d9bae";
logging-data="31977"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/MCVfRMr1n2yL7dGBv5tOtGlpGpC0yQEI="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.8.0
Cancel-Lock: sha1:8eEGTq0v0YzSYAS2vWDZ1jEA+y4=
In-Reply-To: <6j6tii-7un.ln1@Telcontar.valinor>
Content-Language: en-CA
 by: Tristan Miller - Tue, 19 Apr 2022 12:05 UTC

Dear Carlos,

On 17/04/2022 12.26, Carlos E.R. wrote:
> I booted this Leap 15.3 today after a kernel update. I did:
>
> systemd-analyze plot >bootup.svg
> eog bootup.svg
>
>
> And I clearly see that the boot process continues running while
> purge-kernels is running (for 41 seconds in my case).

I'm also running Leap 15.3. I produced an SVG plot as you suggested and
I see that you're right that the boot process continues while the
kernels are purged. However, it seems that multi-user.target and
graphical.target aren't reached until the purge is complete. So
contrary to what you recalled in your previous message, I can't actually
log in until the purge is complete.

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: Why does boot block for "Purge old kernels"?

<t3mmuf$qgq$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=507&group=alt.os.linux.suse#507

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!iNGj/luDezKLilfl3oxwcA.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Tue, 19 Apr 2022 18:10:55 +0200
Organization: Aioe.org NNTP Server
Message-ID: <t3mmuf$qgq$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me> <2aurii-08o.ln1@Telcontar.valinor>
<t3gesa$nal$1@gioia.aioe.org> <6j6tii-7un.ln1@Telcontar.valinor>
<t3m8ho$v79$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="27162"; posting-host="iNGj/luDezKLilfl3oxwcA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.11.1
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Tue, 19 Apr 2022 16:10 UTC

Tristan Miller wrote:
> Dear Carlos,
>
> On 17/04/2022 12.26, Carlos E.R. wrote:
>> I booted this Leap 15.3 today after a kernel update. I did:
>>
>> systemd-analyze plot >bootup.svg
>> eog bootup.svg
>>
>>
>> And I clearly see that the boot process continues running while
>> purge-kernels is running (for 41 seconds in my case).
>
>
> I'm also running Leap 15.3.  I produced an SVG plot as you suggested and
> I see that you're right that the boot process continues while the
> kernels are purged. However, it seems that multi-user.target and
> graphical.target aren't reached until the purge is complete.  So
> contrary to what you recalled in your previous message, I can't actually
> log in until the purge is complete.
>
> Regards,
> Tristan
>

Carlos also says
> It is the service "display-manager" which waits, apparently.

which is - functionally - what we are both saying, the system is not
actually useable until the kernels have been purged. The two of us see
the boot-process as being over when we can log in.

--
This mail has been tested by https://RKIvirus.com/ and has been found to
contain Covid-19. Disinfect after reading.

Re: Why does boot block for "Purge old kernels"?

<nlm3ji-dsq.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=508&group=alt.os.linux.suse#508

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!paganini.bofh.team!weretis.net!feeder8.news.weretis.net!3.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Tue, 19 Apr 2022 23:37:27 +0200
Lines: 30
Message-ID: <nlm3ji-dsq.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <2aurii-08o.ln1@Telcontar.valinor>
<t3gesa$nal$1@gioia.aioe.org> <6j6tii-7un.ln1@Telcontar.valinor>
<t3m8ho$v79$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net nuio76T86UHzOR7nIFt0Kgv3ANpc+WudqdOV64XByNyNM6oK/x
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:x7+5dSMkd1XBhQxqHlTXN6dVAvc=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.8.0
Content-Language: en-CA
In-Reply-To: <t3m8ho$v79$1@dont-email.me>
 by: Carlos E.R. - Tue, 19 Apr 2022 21:37 UTC

On 2022-04-19 14:05, Tristan Miller wrote:
> Dear Carlos,
>
> On 17/04/2022 12.26, Carlos E.R. wrote:
>> I booted this Leap 15.3 today after a kernel update. I did:
>>
>> systemd-analyze plot >bootup.svg
>> eog bootup.svg
>>
>>
>> And I clearly see that the boot process continues running while
>> purge-kernels is running (for 41 seconds in my case).
>
>
> I'm also running Leap 15.3.  I produced an SVG plot as you suggested and
> I see that you're right that the boot process continues while the
> kernels are purged. However, it seems that multi-user.target and
> graphical.target aren't reached until the purge is complete.  So
> contrary to what you recalled in your previous message, I can't actually
> log in until the purge is complete.

Well, I did say in my second post that "display-manager" did not start
till "purge-kernels" finished.

So, again, I suggest you bring up the issue in the mail list, because I
do not know why "display-manager" waits.

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<t5tkvr$1fpp$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=577&group=alt.os.linux.suse#577

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!iNGj/luDezKLilfl3oxwcA.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Mon, 16 May 2022 15:52:59 +0200
Organization: Aioe.org NNTP Server
Message-ID: <t5tkvr$1fpp$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="48953"; posting-host="iNGj/luDezKLilfl3oxwcA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.11.1
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Mon, 16 May 2022 13:52 UTC

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
>

I have just updated a kernel on my test machine, if you submitted a bug
report it has not been acted upon (yet).

--
This mail has been tested by https://RKIvirus.com/ and has been found to
contain Covid-19. Disinfect after reading.

Re: Why does boot block for "Purge old kernels"?

<td64kf$nc9$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=642&group=alt.os.linux.suse#642

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!5o/dDybsjSwKCUt9oFhEPg.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Fri, 12 Aug 2022 20:02:55 +0200
Organization: Aioe.org NNTP Server
Message-ID: <td64kf$nc9$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="23945"; posting-host="5o/dDybsjSwKCUt9oFhEPg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.10.2
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Fri, 12 Aug 2022 18:02 UTC

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.

Re: Why does boot block for "Purge old kernels"?

<jlt346FlqicU1@mid.individual.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=643&group=alt.os.linux.suse#643

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!lilly.ping.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: bon...@hertz.ikp.physik.tu-darmstadt.de (Uwe Bonnes)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: 14 Aug 2022 20:09:42 GMT
Lines: 42
Message-ID: <jlt346FlqicU1@mid.individual.net>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 0cQG7VMVcJhyRvD5Ol1g4AnVxZrYPlLBA9Tjc54thc99YthY35
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:wsBEhdin5qtiQk1DSTZvtGpX4aU=
User-Agent: tin/2.4.2-20171224 ("Lochhead") (UNIX) (Linux/5.3.18-150300.59.87-preempt (x86_64))
 by: Uwe Bonnes - Sun, 14 Aug 2022 20:09 UTC

Andrew <Doug@hyperspace.vogon.gov> 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.

I also have the impression that the update jobs, e.g. for the locate
database run blocking at that point. Opensuse 15.3.
--
Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

Re: Why does boot block for "Purge old kernels"?

<t097ti-qqt.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=644&group=alt.os.linux.suse#644

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!lilly.ping.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 20 Aug 2022 16:51:41 +0200
Lines: 11
Message-ID: <t097ti-qqt.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<jlt346FlqicU1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net vNerevqkGGtY2vhGTSjbLAieWLVinw0+34bVDcwblVIjkoBdaC
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:CqFiCaR8+5lAhneQX3kuIpWi1MM=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.12.0
Content-Language: en-CA
In-Reply-To: <jlt346FlqicU1@mid.individual.net>
 by: Carlos E.R. - Sat, 20 Aug 2022 14:51 UTC

On 2022-08-14 22:09, Uwe Bonnes wrote:
> Andrew <Doug@hyperspace.vogon.gov> wrote:

> I also have the impression that the update jobs, e.g. for the locate
> database run blocking at that point. Opensuse 15.3.

Not during boot.

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<n697ti-7ou.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=645&group=alt.os.linux.suse#645

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!hirsch.in-berlin.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 20 Aug 2022 16:54:47 +0200
Lines: 24
Message-ID: <n697ti-7ou.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net zWb1AM3Azgfmw0YTbtu8bw7yMZ2F6EQeVdaQbNFYSVGgGw5CNI
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:5gMjoa6fth0YTV7cTucUk6RozDk=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.12.0
Content-Language: en-CA
In-Reply-To: <td64kf$nc9$1@gioia.aioe.org>
 by: Carlos E.R. - Sat, 20 Aug 2022 14:54 UTC

On 2022-08-12 20:02, Andrew wrote:
> 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.

Try instead uninstalling "plymouth" (and then run mkinitrd).

This package does the graphic display during boot, and it makes the
kernel image much larger.

500 M should be enough.

Telcontar:~ # df -h | grep boot
/dev/nvme0n1p4 1011M 98M 862M 11% /boot
/dev/nvme0n1p1 500M 19M 482M 4% /boot/efi
Telcontar:~ #

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<tdra7e$11ui$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=646&group=alt.os.linux.suse#646

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!5o/dDybsjSwKCUt9oFhEPg.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 20 Aug 2022 20:47:09 +0200
Organization: Aioe.org NNTP Server
Message-ID: <tdra7e$11ui$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="34770"; posting-host="5o/dDybsjSwKCUt9oFhEPg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.13
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Sat, 20 Aug 2022 18:47 UTC

Carlos E.R. wrote:
> On 2022-08-12 20:02, Andrew wrote:
>> 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.
>
> Try instead uninstalling "plymouth" (and then run mkinitrd).
>
> This package does the graphic display during boot, and it makes the
> kernel image much larger.
>
> 500 M should be enough.
>
> Telcontar:~ # df -h | grep boot
> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
> Telcontar:~ #
>
>

Thanks, that particular machine is a test system so I tried it. It
still boots with no problems but I won't see if it really helped until
the next kernel comes along.
It's my only pre-UEFI system and has been running since 2010, which is
why the /boot is sized the way it is.

Re: Why does boot block for "Purge old kernels"?

<9vu9ti-o9a.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=647&group=alt.os.linux.suse#647

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!lilly.ping.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 21 Aug 2022 17:18:32 +0200
Lines: 48
Message-ID: <9vu9ti-o9a.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor> <tdra7e$11ui$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 0b0i2niZlFaDTUKQt+G+Fgtafxm2JmeQ0eZBKzxgF0imEzgzln
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:hO1udH5G33kCvkbKvPqCxKgrM6w=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.12.0
Content-Language: en-CA
In-Reply-To: <tdra7e$11ui$1@gioia.aioe.org>
 by: Carlos E.R. - Sun, 21 Aug 2022 15:18 UTC

On 2022-08-20 20:47, Andrew wrote:
> Carlos E.R. wrote:
>> On 2022-08-12 20:02, Andrew wrote:
>>> 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.
>>
>> Try instead uninstalling "plymouth" (and then run mkinitrd).
>>
>> This package does the graphic display during boot, and it makes the
>> kernel image much larger.
>>
>> 500 M should be enough.
>>
>> Telcontar:~ # df -h | grep boot
>> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
>> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
>> Telcontar:~ #
>>
>>
>
> Thanks, that particular machine is a test system so I tried it.  It
> still boots with no problems but I won't see if it really helped until
> the next kernel comes along.
> It's my only pre-UEFI system and has been running since 2010, which is
> why the /boot is sized the way it is.

You can simply do:

df -h /boot

before and after removing the package, to see the effect it has.

This is the file that changes:

cer@Telcontar:~> ls -lh /boot/initrd*

.... 13M Aug 8 14:45 /boot/initrd-5.3.18-150300.59.63-default
.... 13M Aug 8 14:45 /boot/initrd-5.3.18-150300.59.87-default

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<tdu3hl$1shi$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=648&group=alt.os.linux.suse#648

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!5o/dDybsjSwKCUt9oFhEPg.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 21 Aug 2022 22:11:33 +0200
Organization: Aioe.org NNTP Server
Message-ID: <tdu3hl$1shi$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor> <tdra7e$11ui$1@gioia.aioe.org>
<9vu9ti-o9a.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="62002"; posting-host="5o/dDybsjSwKCUt9oFhEPg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.13
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Sun, 21 Aug 2022 20:11 UTC

Carlos E.R. wrote:
> On 2022-08-20 20:47, Andrew wrote:
>> Carlos E.R. wrote:
>>> On 2022-08-12 20:02, Andrew wrote:
>>>> 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.
>>>
>>> Try instead uninstalling "plymouth" (and then run mkinitrd).
>>>
>>> This package does the graphic display during boot, and it makes the
>>> kernel image much larger.
>>>
>>> 500 M should be enough.
>>>
>>> Telcontar:~ # df -h | grep boot
>>> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
>>> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
>>> Telcontar:~ #
>>>
>>>
>>
>> Thanks, that particular machine is a test system so I tried it.  It
>> still boots with no problems but I won't see if it really helped until
>> the next kernel comes along.
>> It's my only pre-UEFI system and has been running since 2010, which is
>> why the /boot is sized the way it is.
>
>
> You can simply do:
>
> df -h /boot
>
> before and after removing the package, to see the effect it has.
>
> This is the file that changes:
>
> cer@Telcontar:~> ls -lh /boot/initrd*
>
> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.63-default
> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.87-default
>
>

Oh, I did that immediately. The file was slightly smaller and the
partition dropped to 48% used.
Given that the previous 50% was with two kernels, an additional one
should still only be 75% before reverting to 50% once the oldest one had
been removed, I don't see any alternative to waiting for a new kernel
update.
The -1 kernel still has the Plymouth stuff in there so the next update
may fail until I remove it, and the following one could then still be
ok. Calculations will not help.

Re: Why does boot block for "Purge old kernels"?

<mpbcti-loi.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=649&group=alt.os.linux.suse#649

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Mon, 22 Aug 2022 15:09:42 +0200
Lines: 70
Message-ID: <mpbcti-loi.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor> <tdra7e$11ui$1@gioia.aioe.org>
<9vu9ti-o9a.ln1@Telcontar.valinor> <tdu3hl$1shi$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net UGUAAgF8A+fWOg3wkZWbGwmL8hbXw9/KYYFdc7sywDhRdLHZRz
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:k6BU2ypeeKlD+ZHUMLiWDBmEMt8=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.12.0
Content-Language: en-CA
In-Reply-To: <tdu3hl$1shi$1@gioia.aioe.org>
 by: Carlos E.R. - Mon, 22 Aug 2022 13:09 UTC

On 2022-08-21 22:11, Andrew wrote:
> Carlos E.R. wrote:
>> On 2022-08-20 20:47, Andrew wrote:
>>> Carlos E.R. wrote:
>>>> On 2022-08-12 20:02, Andrew wrote:
>>>>> 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.
>>>>
>>>> Try instead uninstalling "plymouth" (and then run mkinitrd).
>>>>
>>>> This package does the graphic display during boot, and it makes the
>>>> kernel image much larger.
>>>>
>>>> 500 M should be enough.
>>>>
>>>> Telcontar:~ # df -h | grep boot
>>>> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
>>>> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
>>>> Telcontar:~ #
>>>>
>>>>
>>>
>>> Thanks, that particular machine is a test system so I tried it.  It
>>> still boots with no problems but I won't see if it really helped
>>> until the next kernel comes along.
>>> It's my only pre-UEFI system and has been running since 2010, which
>>> is why the /boot is sized the way it is.
>>
>>
>> You can simply do:
>>
>> df -h /boot
>>
>> before and after removing the package, to see the effect it has.
>>
>> This is the file that changes:
>>
>> cer@Telcontar:~> ls -lh /boot/initrd*
>>
>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.63-default
>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.87-default
>>
>>
>
> Oh, I did that immediately.  The file was slightly smaller and the
> partition dropped to 48% used.

Oh. I expected a significant difference. When I tested this was long
ago, though, so I suppose that now they are including so many things in
the initrd that it no longer makes an impact.

> Given that the previous 50% was with two kernels, an additional one
> should still only be 75% before reverting to 50% once the oldest one had
> been removed, I don't see any alternative to waiting for a new kernel
> update.
> The -1 kernel still has the Plymouth stuff in there so the next update
> may fail until I remove it, and the following one could then still be
> ok.  Calculations will not help.

Er... no, when you remove the package all the initrds are remade without
it. All kernels. Look at the dates of the files (see mine above, same
timestamp).

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<tg2nm2$bvu$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=674&group=alt.os.linux.suse#674

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!5o/dDybsjSwKCUt9oFhEPg.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Fri, 16 Sep 2022 22:52:18 +0200
Organization: Aioe.org NNTP Server
Message-ID: <tg2nm2$bvu$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor> <tdra7e$11ui$1@gioia.aioe.org>
<9vu9ti-o9a.ln1@Telcontar.valinor> <tdu3hl$1shi$1@gioia.aioe.org>
<mpbcti-loi.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="12286"; posting-host="5o/dDybsjSwKCUt9oFhEPg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.13
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Fri, 16 Sep 2022 20:52 UTC

Carlos E.R. wrote:
> On 2022-08-21 22:11, Andrew wrote:
>> Carlos E.R. wrote:
>>> On 2022-08-20 20:47, Andrew wrote:
>>>> Carlos E.R. wrote:
>>>>> On 2022-08-12 20:02, Andrew wrote:
>>>>>> 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.
>>>>>
>>>>> Try instead uninstalling "plymouth" (and then run mkinitrd).
>>>>>
>>>>> This package does the graphic display during boot, and it makes the
>>>>> kernel image much larger.
>>>>>
>>>>> 500 M should be enough.
>>>>>
>>>>> Telcontar:~ # df -h | grep boot
>>>>> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
>>>>> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
>>>>> Telcontar:~ #
>>>>>
>>>>>
>>>>
>>>> Thanks, that particular machine is a test system so I tried it.  It
>>>> still boots with no problems but I won't see if it really helped
>>>> until the next kernel comes along.
>>>> It's my only pre-UEFI system and has been running since 2010, which
>>>> is why the /boot is sized the way it is.
>>>
>>>
>>> You can simply do:
>>>
>>> df -h /boot
>>>
>>> before and after removing the package, to see the effect it has.
>>>
>>> This is the file that changes:
>>>
>>> cer@Telcontar:~> ls -lh /boot/initrd*
>>>
>>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.63-default
>>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.87-default
>>>
>>>
>>
>> Oh, I did that immediately.  The file was slightly smaller and the
>> partition dropped to 48% used.
>
> Oh. I expected a significant difference. When I tested this was long
> ago, though, so I suppose that now they are including so many things in
> the initrd that it no longer makes an impact.
>
>> Given that the previous 50% was with two kernels, an additional one
>> should still only be 75% before reverting to 50% once the oldest one
>> had been removed, I don't see any alternative to waiting for a new
>> kernel update.
>> The -1 kernel still has the Plymouth stuff in there so the next update
>> may fail until I remove it, and the following one could then still be
>> ok.  Calculations will not help.
>
> Er... no, when you remove the package all the initrds are remade without
> it. All kernels. Look at the dates of the files (see mine above, same
> timestamp).
>

I suppose I could have said "you are right" (with the reduced size) but
I was waiting for a new kernel to come along. It has.

240 MB - Total size of /boot
107 MB - Used (with two kernels)
117 MB - Free
This means 48% of /boot is in use.
zypper still said it needed another 10 MB to install the new kernel.
Abort, retry, ignore? [a/r/i] (a):

The adventurous solution would have been to have tried "i" as in "do it
anyway". I copped out, removed the older kernel with Yast -> Software
Management (at which point 50-60 MB was in use) and then installed the
new one using zypper. The 240 / 107 / 117 / 48% figures still hold true.
I'm assuming zypper's calculation of how much it needs is at fault, the
additional kernel should have meant 160 MB was in use. zypper's
guesstimate of 127 MB for a new kernel seems ridiculous, unless there is
some compression going on there during the update process.
There are vmlinux-whatever.gz files in there which take 17-18 MB each,
if one takes 80 MB before compression that would explain a lot.

Re: Why does boot block for "Purge old kernels"?

<m0tgvi-reb.ln1@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=675&group=alt.os.linux.suse#675

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!news.neodome.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 17 Sep 2022 15:00:38 +0200
Lines: 101
Message-ID: <m0tgvi-reb.ln1@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor> <tdra7e$11ui$1@gioia.aioe.org>
<9vu9ti-o9a.ln1@Telcontar.valinor> <tdu3hl$1shi$1@gioia.aioe.org>
<mpbcti-loi.ln1@Telcontar.valinor> <tg2nm2$bvu$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net Wh0CvHoeT5y3qUVwfNhX+QoGTnQ6LZuVhRU6d/Tw2uXUTVX2YN
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:ncAqRWthXr5CMBX+LcY0XQvAXUQ=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.2.2
Content-Language: es-ES, en-CA
In-Reply-To: <tg2nm2$bvu$1@gioia.aioe.org>
 by: Carlos E.R. - Sat, 17 Sep 2022 13:00 UTC

On 2022-09-16 22:52, Andrew wrote:
> Carlos E.R. wrote:
>> On 2022-08-21 22:11, Andrew wrote:
>>> Carlos E.R. wrote:
>>>> On 2022-08-20 20:47, Andrew wrote:
>>>>> Carlos E.R. wrote:
>>>>>> On 2022-08-12 20:02, Andrew wrote:
>>>>>>> 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.
>>>>>>
>>>>>> Try instead uninstalling "plymouth" (and then run mkinitrd).
>>>>>>
>>>>>> This package does the graphic display during boot, and it makes
>>>>>> the kernel image much larger.
>>>>>>
>>>>>> 500 M should be enough.
>>>>>>
>>>>>> Telcontar:~ # df -h | grep boot
>>>>>> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
>>>>>> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
>>>>>> Telcontar:~ #
>>>>>>
>>>>>>
>>>>>
>>>>> Thanks, that particular machine is a test system so I tried it.  It
>>>>> still boots with no problems but I won't see if it really helped
>>>>> until the next kernel comes along.
>>>>> It's my only pre-UEFI system and has been running since 2010, which
>>>>> is why the /boot is sized the way it is.
>>>>
>>>>
>>>> You can simply do:
>>>>
>>>> df -h /boot
>>>>
>>>> before and after removing the package, to see the effect it has.
>>>>
>>>> This is the file that changes:
>>>>
>>>> cer@Telcontar:~> ls -lh /boot/initrd*
>>>>
>>>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.63-default
>>>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.87-default
>>>>
>>>>
>>>
>>> Oh, I did that immediately.  The file was slightly smaller and the
>>> partition dropped to 48% used.
>>
>> Oh. I expected a significant difference. When I tested this was long
>> ago, though, so I suppose that now they are including so many things
>> in the initrd that it no longer makes an impact.
>>
>>> Given that the previous 50% was with two kernels, an additional one
>>> should still only be 75% before reverting to 50% once the oldest one
>>> had been removed, I don't see any alternative to waiting for a new
>>> kernel update.
>>> The -1 kernel still has the Plymouth stuff in there so the next
>>> update may fail until I remove it, and the following one could then
>>> still be ok.  Calculations will not help.
>>
>> Er... no, when you remove the package all the initrds are remade
>> without it. All kernels. Look at the dates of the files (see mine
>> above, same timestamp).
>>
>
> I suppose I could have said "you are right" (with the reduced size) but
> I was waiting for a new kernel to come along.  It has.
>
> 240 MB - Total size of /boot
> 107 MB - Used (with two kernels)
> 117 MB - Free
> This means 48% of /boot is in use.
> zypper still said it needed another 10 MB to install the new kernel.
> Abort, retry, ignore? [a/r/i] (a):
>
> The adventurous solution would have been to have tried "i" as in "do it
> anyway".  I copped out, removed the older kernel with Yast -> Software
> Management (at which point 50-60 MB was in use) and then installed the
> new one using zypper.  The 240 / 107 / 117 / 48% figures still hold true.
> I'm assuming zypper's calculation of how much it needs is at fault, the
> additional kernel should have meant 160 MB was in use.  zypper's
> guesstimate of 127 MB for a new kernel seems ridiculous, unless there is
> some compression going on there during the update process.
> There are vmlinux-whatever.gz files in there which take 17-18 MB each,
> if one takes 80 MB before compression that would explain a lot.

When this happened to me I tried to find 10 meg I could move temporarily
to another partition. 240 megs is now too small. Mine is a gigabyte
(103M in use), of course after I changed the disk and reformatted.

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<tg6ajg$1tfd$1@gioia.aioe.org>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=676&group=alt.os.linux.suse#676

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!aioe.org!5o/dDybsjSwKCUt9oFhEPg.user.46.165.242.75.POSTED!not-for-mail
From: Dou...@hyperspace.vogon.gov (Andrew)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 18 Sep 2022 07:33:36 +0200
Organization: Aioe.org NNTP Server
Message-ID: <tg6ajg$1tfd$1@gioia.aioe.org>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor> <tdra7e$11ui$1@gioia.aioe.org>
<9vu9ti-o9a.ln1@Telcontar.valinor> <tdu3hl$1shi$1@gioia.aioe.org>
<mpbcti-loi.ln1@Telcontar.valinor> <tg2nm2$bvu$1@gioia.aioe.org>
<m0tgvi-reb.ln1@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="62957"; posting-host="5o/dDybsjSwKCUt9oFhEPg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.13
X-Notice: Filtered by postfilter v. 0.9.2
 by: Andrew - Sun, 18 Sep 2022 05:33 UTC

Carlos E.R. wrote:
> On 2022-09-16 22:52, Andrew wrote:
>> Carlos E.R. wrote:
>>> On 2022-08-21 22:11, Andrew wrote:
>>>> Carlos E.R. wrote:
>>>>> On 2022-08-20 20:47, Andrew wrote:
>>>>>> Carlos E.R. wrote:
>>>>>>> On 2022-08-12 20:02, Andrew wrote:
>>>>>>>> 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.
>>>>>>>
>>>>>>> Try instead uninstalling "plymouth" (and then run mkinitrd).
>>>>>>>
>>>>>>> This package does the graphic display during boot, and it makes
>>>>>>> the kernel image much larger.
>>>>>>>
>>>>>>> 500 M should be enough.
>>>>>>>
>>>>>>> Telcontar:~ # df -h | grep boot
>>>>>>> /dev/nvme0n1p4        1011M   98M  862M  11% /boot
>>>>>>> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi
>>>>>>> Telcontar:~ #
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Thanks, that particular machine is a test system so I tried it.
>>>>>> It still boots with no problems but I won't see if it really
>>>>>> helped until the next kernel comes along.
>>>>>> It's my only pre-UEFI system and has been running since 2010,
>>>>>> which is why the /boot is sized the way it is.
>>>>>
>>>>>
>>>>> You can simply do:
>>>>>
>>>>> df -h /boot
>>>>>
>>>>> before and after removing the package, to see the effect it has.
>>>>>
>>>>> This is the file that changes:
>>>>>
>>>>> cer@Telcontar:~> ls -lh /boot/initrd*
>>>>>
>>>>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.63-default
>>>>> ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.87-default
>>>>>
>>>>>
>>>>
>>>> Oh, I did that immediately.  The file was slightly smaller and the
>>>> partition dropped to 48% used.
>>>
>>> Oh. I expected a significant difference. When I tested this was long
>>> ago, though, so I suppose that now they are including so many things
>>> in the initrd that it no longer makes an impact.
>>>
>>>> Given that the previous 50% was with two kernels, an additional one
>>>> should still only be 75% before reverting to 50% once the oldest one
>>>> had been removed, I don't see any alternative to waiting for a new
>>>> kernel update.
>>>> The -1 kernel still has the Plymouth stuff in there so the next
>>>> update may fail until I remove it, and the following one could then
>>>> still be ok.  Calculations will not help.
>>>
>>> Er... no, when you remove the package all the initrds are remade
>>> without it. All kernels. Look at the dates of the files (see mine
>>> above, same timestamp).
>>>
>>
>> I suppose I could have said "you are right" (with the reduced size)
>> but I was waiting for a new kernel to come along.  It has.
>>
>> 240 MB - Total size of /boot
>> 107 MB - Used (with two kernels)
>> 117 MB - Free
>> This means 48% of /boot is in use.
>> zypper still said it needed another 10 MB to install the new kernel.
>> Abort, retry, ignore? [a/r/i] (a):
>>
>> The adventurous solution would have been to have tried "i" as in "do
>> it anyway".  I copped out, removed the older kernel with Yast ->
>> Software Management (at which point 50-60 MB was in use) and then
>> installed the new one using zypper.  The 240 / 107 / 117 / 48% figures
>> still hold true.
>> I'm assuming zypper's calculation of how much it needs is at fault,
>> the additional kernel should have meant 160 MB was in use.  zypper's
>> guesstimate of 127 MB for a new kernel seems ridiculous, unless there
>> is some compression going on there during the update process.
>> There are vmlinux-whatever.gz files in there which take 17-18 MB each,
>> if one takes 80 MB before compression that would explain a lot.
>
>
> When this happened to me I tried to find 10 meg I could move temporarily
> to another partition. 240 megs is now too small. Mine is a gigabyte
> (103M in use), of course after I changed the disk and reformatted.
>

This machine is ancient and is dual boot with Windows 10 (originally
Windows 7), I'll have to live with the pain.

Re: Why does boot block for "Purge old kernels"?

<20220918080028.364a9be0@nx-74205>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=677&group=alt.os.linux.suse#677

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: telcon...@duck.com (Aragorn)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sun, 18 Sep 2022 08:00:28 +0200
Organization: A noiseless patient Strider
Lines: 19
Message-ID: <20220918080028.364a9be0@nx-74205>
References: <t38vgs$v6d$1@dont-email.me>
<td64kf$nc9$1@gioia.aioe.org>
<n697ti-7ou.ln1@Telcontar.valinor>
<tdra7e$11ui$1@gioia.aioe.org>
<9vu9ti-o9a.ln1@Telcontar.valinor>
<tdu3hl$1shi$1@gioia.aioe.org>
<mpbcti-loi.ln1@Telcontar.valinor>
<tg2nm2$bvu$1@gioia.aioe.org>
<m0tgvi-reb.ln1@Telcontar.valinor>
<tg6ajg$1tfd$1@gioia.aioe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: reader01.eternal-september.org; posting-host="ed5ee6714dceb6c379eb3dc8d20ab7f4";
logging-data="118107"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18JO3oJAP0zrVSU1JUX79E3"
Cancel-Lock: sha1:53AyoFVTcRaSQluNf4XTeHweABA=
X-Newsreader: Claws Mail 4.1.0 (GTK 3.24.34; x86_64-pc-linux-gnu)
 by: Aragorn - Sun, 18 Sep 2022 06:00 UTC

On 18.09.2022 at 07:33, Andrew scribbled:

> Carlos E.R. wrote:
>
> > When this happened to me I tried to find 10 meg I could move
> > temporarily to another partition. 240 megs is now too small. Mine
> > is a gigabyte (103M in use), of course after I changed the disk and
> > reformatted.
>
> This machine is ancient and is dual boot with Windows 10 (originally
> Windows 7), I'll have to live with the pain.

Considering that you're also using Windows on that machine, living
with pain should be second nature to you by now. :p

--
With respect,
= Aragorn =

Re: Why does boot block for "Purge old kernels"?

<tv3pjl$2d7t8$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=781&group=alt.os.linux.suse#781

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: hyperspa...@vogon.gov.invalid (Don Spam's Reckless Son)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 18 Mar 2023 08:35:16 +0100
Organization: A noiseless patient Spider
Lines: 43
Message-ID: <tv3pjl$2d7t8$1@dont-email.me>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 18 Mar 2023 07:35:17 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="bebc977226ba5ae7e8acae1a889e795f";
logging-data="2531240"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18+7E2lq5Lk1LQWrkd+DzhgRyXoI2T1uhw="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.15
Cancel-Lock: sha1:Rlt8vhqA1DgG1dUHjSyRTc5b5Gg=
In-Reply-To: <td64kf$nc9$1@gioia.aioe.org>
 by: Don Spam's Reck - Sat, 18 Mar 2023 07:35 UTC

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.

Re: Why does boot block for "Purge old kernels"?

<ibpgejx9cq.ln2@Telcontar.valinor>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=784&group=alt.os.linux.suse#784

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!lilly.ping.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_li...@es.invalid (Carlos E.R.)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 18 Mar 2023 14:02:10 +0100
Lines: 97
Message-ID: <ibpgejx9cq.ln2@Telcontar.valinor>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<tv3pjl$2d7t8$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net Tle+Y5sVhMbdO8Pe9U2CzweFImz82/1hpfcpfcX6tuiJLF2n5e
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:5rGXnUQeBmp5B3M1HT+ND9NILGQ=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.8.0
Content-Language: es-ES, en-CA
In-Reply-To: <tv3pjl$2d7t8$1@dont-email.me>
 by: Carlos E.R. - Sat, 18 Mar 2023 13:02 UTC

On 2023-03-18 08:35, Don Spam's Reckless Son wrote:
> 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.

Good find.

Telcontar:~ # rpm -q --changelog purge-kernels-service | less

* Thu May 06 2021 ...@suse.de
- Add ZYPP_LOCK_TIMEOUT=-1 to keep waiting for the lock (boo#1184399).

Which is:

https://bugzilla.opensuse.org/show_bug.cgi?id=1184399

Basically, purge-kernels failed because the user was running zypper at
the same time. So they added loop or something waiting for package
management to be finished and then start the actual purge.

But this is about a lock condition inside zypper, not about the service
holding the boot process. Different issue.

The update you mentions says:

openSUSE-SLE-15.4-2023-793 - Recommended update for purge-kernels-service

This update for purge-kernels-service fixes the following issues:
- Change systemd service type to 'exec' (bsc#1198668)

References:
1198668 (bugzilla) : Tumbleweed: Purge old kernels service block during boot

Comment 11 Michal Koutný 2022-05-13 12:57:12 UTC
....
Thirdly, I can see the purge-kernels.service is of Type=oneshot, which
means it'll block subsequent jobs until the ExecStart= command finishes.
Not sure if there's actually necessity to wait after kernel removal is
done, the Type=simple or Type=exec would only wait for the command start
and the removal may run in parallel (even with jobs that specify
After=purge-kernels.service).

Curious. We'll see.

--
Cheers, Carlos.

Re: Why does boot block for "Purge old kernels"?

<tv4fp0$2gs97$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=785&group=alt.os.linux.suse#785

 copy link   Newsgroups: alt.os.linux.suse
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: hyperspa...@vogon.gov.invalid (Don Spam's Reckless Son)
Newsgroups: alt.os.linux.suse
Subject: Re: Why does boot block for "Purge old kernels"?
Date: Sat, 18 Mar 2023 14:53:36 +0100
Organization: A noiseless patient Spider
Lines: 109
Message-ID: <tv4fp0$2gs97$1@dont-email.me>
References: <t38vgs$v6d$1@dont-email.me> <td64kf$nc9$1@gioia.aioe.org>
<tv3pjl$2d7t8$1@dont-email.me> <ibpgejx9cq.ln2@Telcontar.valinor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 18 Mar 2023 13:53:36 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="bebc977226ba5ae7e8acae1a889e795f";
logging-data="2650407"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+kFuB1Vq+W3Jk1i7PKv8yQNyZrIITbYmA="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.15
Cancel-Lock: sha1:CGsA4Aat8gVZgzSHq7TU1knRHYc=
In-Reply-To: <ibpgejx9cq.ln2@Telcontar.valinor>
 by: Don Spam's Reck - Sat, 18 Mar 2023 13:53 UTC

Carlos E.R. wrote:
> On 2023-03-18 08:35, Don Spam's Reckless Son wrote:
>> 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.
>
> Good find.
>
> Telcontar:~ # rpm -q --changelog purge-kernels-service | less
>
> * Thu May 06 2021 ...@suse.de
> - Add ZYPP_LOCK_TIMEOUT=-1 to keep waiting for the lock (boo#1184399).
>
> Which is:
>
> https://bugzilla.opensuse.org/show_bug.cgi?id=1184399
>
> Basically, purge-kernels failed because the user was running zypper at
> the same time. So they added loop or something waiting for package
> management to be finished and then start the actual purge.
>
>
>
> But this is about a lock condition inside zypper, not about the service
> holding the boot process. Different issue.
>
>
>
>
> The update you mentions says:
>
>
> openSUSE-SLE-15.4-2023-793 - Recommended update for purge-kernels-service
>
> This update for purge-kernels-service fixes the following issues:
> - Change systemd service type to 'exec' (bsc#1198668)
>
> References:
> 1198668 (bugzilla) : Tumbleweed: Purge old kernels service block during
> boot
>
>
> Comment 11 Michal Koutný 2022-05-13 12:57:12 UTC
> ...
> Thirdly, I can see the purge-kernels.service is of Type=oneshot, which
> means it'll block subsequent jobs until the ExecStart= command finishes.
> Not sure if there's actually necessity to wait after kernel removal is
> done, the Type=simple or Type=exec would only wait for the command start
> and the removal may run in parallel (even with jobs that specify
> After=purge-kernels.service).
>
>
>
> Curious. We'll see.
>
>

In the interests of full disclosure I have to point out that the date on
the most recent entry in the Change Log (Change service type to exec
(boo#1198668)) is 13 May 2022.
Has it really taken 10 months to release that fix?

I was watching out for things on my 10-year-old Laptop (no SSD of
course) and saw no sign of the extended wait for a purge which I had
seen after previous kernel updates.
The system was running rather slowly after that boot completed, as I
expected if a purge was running in the background.
(this was running with the "-1" kernel because the newest one was
freezing at a very early stage in the boot process, a different problem).

Pages:12
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor