You are sure that we are talking SPECIFICALLY about SuSE Professional 8.0?
Kernel
ftp://ftp.suse.com/pub/suse/i386/update/8.0/kernel/2.4.18-20030324/k_deflt-2
.4.18-261.i386.rpm ?!??!
If you are positive about the above 2 points, then the bet is off, indeed...
P.S. I've never said that I will quit SuSE from now on... I stick with'em
since version 5.3 ...and right now I'm installing a 8.1 route server...
so... ;)
Have a lot of fun...
Radu
----- Original Message -----
From: "Bjorn Tore Sund"
50 klients of five major hardware groups, with variations within each. 10 servers, all different, with very different hardware and configurations. Problems one the one machine where I have a new Nvidia card, problems on the two servers where I have LVM setups. No problem which took more than 15 minutes to resolve.
Radu, you loose your bet. That's 47 kernel upgrades that went without problems. I for my part am still happy with SuSE, and my pre-order for 8.2 is now in. :)
Bjørn
On 3 Apr 2003, Ken Schneider wrote:
Compaq lt1720US laptop, no problems with kernel update. You need to make sure that your /etc/sysconfig/kernel file is correct regarding the bootup modules installed (for mk_initrd) and run mk_initrd && lilo.
Ken
On Thu, 2003-04-03 at 03:45, Radu Voicu wrote:
Hi, Bob!
I am sure that your intentions are good, but I can bet that NOBODY
the SuSE 8.0 default kernel k_deflt 2.4.18 without any problem...
I've tried on several machines, one was a Compaq Deskpro and other was IBM NetVista... do you think that those machines are supported by SuSE??!?
I don't want to start any flames on the list, but I'm pretty pissed off because all those machines was in production and remotely administered... and I've trusted SuSE like always... and they dissapointed me big time on this one...
Regards, Radu
----- Original Message ----- From: "Bob Vickers"
To: "Eduard Avetisyan" Cc: ; Sent: Thursday, April 03, 2003 11:32 AM Subject: Re: [suse-security] Linux-Server is frozen after security update of kernel On Wed, 2 Apr 2003, Eduard Avetisyan wrote:
I'm afraid it's time to ask - on what type of machine and what configuration has SuSE tested the new kernel ;-) Maybe all switch to exactly that type of hardware in the future?
It's also fair to ask the people having problems whether their hardware is on SuSE's supported hardware list. People can run SuSE Linux on any hardware they like, and they can ask for advice on appropriate mailing lists. But they shouldn't start whinging to SuSE unless they have checked the hardware is supported (maybe it is, maybe it isn't, I don't know).
We should also remember that the traffic on this list is heavily biased towards people having problems. I imagine the upgrade worked flawlessly on most systems.
And one more thing: in the days before the update was released the messages on this list were along the lines of "Why haven't you released it yet, it can't take that long to build a kernel?". Obviously if they could have a few weeks for testing they could eliminate a lot of these
upgraded problems.
But they have to strike a balance.
Bob ============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
-- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk@mi.uib.no Email: bjornts@mi.uib.no http://www.mi.uib.no/
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here