Mailinglist Archive: opensuse-security (257 mails)
| < Previous | Next > |
Re: [suse-security] Bad quality of updates from SuSE ftp server
- From: maarten van den Berg <maarten@xxxxxxxxxxxx>
- Date: Wed, 25 Aug 2004 23:05:13 +0200
- Message-id: <200408252305.13858.maarten@xxxxxxxxxxxx>
On Wednesday 25 August 2004 17:28, Ralf Ronneburger wrote:
> Hi,
>
> to add my 2 cents to the discussion about bad update-quality - I'm also
> not satisfied the way it works in the last months. And as it is a fact,
> that there where many problems especially with kernel-updates in the
> last time it'd be a good idea for suse to not uninstall the old kernel
> and delete it's config but to add the new kernel as default and leave
> the old one as fallback on the system. It's not that we can't help
> ourselfs if spamassasin or tripwire are broken, but updating a kernel on
> a remote SuSE-system these days requires some delight in risk.
Ralf ! Thank you !!!!!
This has been on my "wanted" list too but I never did speak up about it.
I've had so many occasions where I (or hardware, or SuSE...) fscked up and
left me with an unbootable, headless, CDrom & floppyless machine. :-(
I try to take due diligence myself by manually installing kernels with rpm -i
instead of rpm -U but even if I don't forget that, one has to adjust a lot of
things in /boot/ and lilo.conf to get a real working fallback kernel.
The last case I remember was a kernel upgrade that swapped my onboard SATA and
ATA drive order, so it couldn't boot anymore. Little things, lotta hassles...
Maarten
> Greetings,
>
> Ralf
--
When I answered where I wanted to go today, they just hung up -- Unknown
> Hi,
>
> to add my 2 cents to the discussion about bad update-quality - I'm also
> not satisfied the way it works in the last months. And as it is a fact,
> that there where many problems especially with kernel-updates in the
> last time it'd be a good idea for suse to not uninstall the old kernel
> and delete it's config but to add the new kernel as default and leave
> the old one as fallback on the system. It's not that we can't help
> ourselfs if spamassasin or tripwire are broken, but updating a kernel on
> a remote SuSE-system these days requires some delight in risk.
Ralf ! Thank you !!!!!
This has been on my "wanted" list too but I never did speak up about it.
I've had so many occasions where I (or hardware, or SuSE...) fscked up and
left me with an unbootable, headless, CDrom & floppyless machine. :-(
I try to take due diligence myself by manually installing kernels with rpm -i
instead of rpm -U but even if I don't forget that, one has to adjust a lot of
things in /boot/ and lilo.conf to get a real working fallback kernel.
The last case I remember was a kernel upgrade that swapped my onboard SATA and
ATA drive order, so it couldn't boot anymore. Little things, lotta hassles...
Maarten
> Greetings,
>
> Ralf
--
When I answered where I wanted to go today, they just hung up -- Unknown
| < Previous | Next > |