Mailinglist Archive: zypp-devel (226 mails)
| < Previous | Next > |
Re: [zypp-devel] keeping old kernel packages
- From: "Dr. Peter Poeml" <poeml@xxxxxxx>
- Date: Mon, 21 Apr 2008 15:00:28 +0200
- Message-id: <20080421130028.GY21995@xxxxxxx>
On Mon, Apr 21, 2008 at 02:50:11PM +0200, Jan Kupec wrote:
yum has a "keepkernels" Feature which lets the user determine the number
in case it is a kernel, but I find that I don't actually use that
feature. I prefer that I do that housekeeping on my own (deinstalling
old kernels).
I think, anyone who desires to keep old kernels installed is absolutely
capable (and willing) to do that. And anyone who isn't is probably not
aware of old installed kernels anyway and doesn't make use of them.
Also in the light of our bootloader scripts not being able to deal with
it properly either.
Also, in real life I may want to keep a particular kernel package which
may be a little older, but I may want to remove the last two kernels
before the current one anyway.
In the end the number of kernels installed in parallel is self-limited
anyway, because rpm/the installer will complain if / fills up with
kernel modules, or /boot fills up with kernels. So it's easy to see for
the admin that some old kernels should be removed to free space.
Just my two cents,
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
Klaus Kaempf wrote:
* Michael Andres <ma@xxxxxxx> [Apr 18. 2008 16:35]:
1st: Who decides which packages are to be installed with -i?
The user!?
Yes.
At least, this is what I remember from previous discussions on this
topic.
A patch, as it contains additional information about an update, should
also be able to request "-i" vs. "-U" for a package.
This helps kernel installs, where "-i" should be the default without
requiring user interaction.
(We still need a way to limit the number of parallel installed kernels)
Would that do more good than harm? Why not leave this to the user?
yum has a "keepkernels" Feature which lets the user determine the number
in case it is a kernel, but I find that I don't actually use that
feature. I prefer that I do that housekeeping on my own (deinstalling
old kernels).
I think, anyone who desires to keep old kernels installed is absolutely
capable (and willing) to do that. And anyone who isn't is probably not
aware of old installed kernels anyway and doesn't make use of them.
Also in the light of our bootloader scripts not being able to deal with
it properly either.
Also, in real life I may want to keep a particular kernel package which
may be a little older, but I may want to remove the last two kernels
before the current one anyway.
In the end the number of kernels installed in parallel is self-limited
anyway, because rpm/the installer will complain if / fills up with
kernel modules, or /boot fills up with kernels. So it's easy to see for
the admin that some old kernels should be removed to free space.
Just my two cents,
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
| < Previous | Next > |