Mailinglist Archive: opensuse-security (257 mails)

[Philippe Vogel <filiaap@xxxxxxxxxx>]

Philippe Vogel wrote:

> suse@xxxxxx wrote:
>
> > Quoting Mathias Homann <admin@xxxxxxxxxx>:
> >
> > > Am Mittwoch, 25. August 2004 17:39 schrieb Mike Rose:
> > >
> > > > When using:
> > > > rpm -ivh kernel-whatever.rpm
> > >
> > >
> > > but obviously thats not the way YOU installs a kernel update.
> >
> >
> > I believe the difference lies in:
> >
> > rpm -ivh kernel-foo.i586.rpm
> >
> > and
> >
> > rpm -Uvh kernel-foo.i586.rpm
> >
> > YaST/YOU/fou4s all use the "upgrade" path.  The "install" path moves 
> > the old
> > kernel to "previous", unless I'm mistaken.
> >
> > Perhaps this is a perfect thing for the SuSE guys to change in 
> > YaST/YOU: Make
> > kernel upgrade use the "install" type path, or perhaps find some way 
> > to give
> > the option?  Maybe just make a note about it in the install patch 
> > messages to
> > give the user an informed option to quit out of YOU and type it in 
> > manually?
> >
> > The "install" path is great for the vast majority of systems today, 
> > but can
> > cause problems on smaller systems, as our wonderful linux kernel 
> > weighs in at
> > nearly 65 megabytes, and the corresponding sources at 243mb.  My laptop
> > wouldn't like to keep too many copies of that size lying about...
>
>
> I had same things as well. Even once I had to rebuild rpm database 
> because of a corrupted rpm-database file during a broken update via YOU.
>
> Since I don't read any mails from Roman Drathmüller there lays the 
> problem. While he mentained the list there where some smaller problems 
> but not this dau looking updatepolicy since the last months.
>
> If you not try to fix this I will swith to some better mentained 
> distributions (gentoo or debian which have longer uptimes than SuSE ever 
> had). Afaik a lot more investigation is needed before giving an update 
> to the public that doesn't seem work at all.
>
> What I don't do the last times is to use automated YOU instead I chose 
> the updates I want to install - especially on kernel and other important 
> updates.
>
> With this policy you make yourself a bad name in the community and don't 
> lose it until you think over to change this bad policy. Even for novell 
> it can't be a good thing to lose customers (even if they think only 
> corporate customers are the right customers, but with linux you can't 
> think like this because it is a community driven OS!).
>
> Best reguards
>
> Philippe

P.S.: Until this issues aren't fixed I a) don't use You or b) use 
different self compiled software which in fact works better and more 
reliable (look at gentoo!).