On Mon, May 31, 2004 at 09:57:16AM -0600, Gunnar Wolf scribbled: > Lucas Albers dijo [Mon, May 31, 2004 at 01:44:51AM -0600]: > > Eg scenario: > > I'm upgrading my remote server 500 miles away as part of a regular > > maintenance contract. > > I upgrade to sarge, then upgrade my kernel. > > Oops the network stops working, that qualifies as close to the worst item > > that could occur. > > Wait... Are you telling you are running Testing on a mission-critical > server? You know, things like this are not supposed to happen very > often, but unless you are running Stable, you are bound to hit on our > problems and changes. > > (Note, BTW, that I also adhere to the 'we must first sort this out' > point of view... But please, for the love of the most sacred, try > not to run anything too important with Testing. I'm running 70+ machines on testing without any problems (except for an occasional need to recompile a package from unstable so that it works with testing, but that's a rare bird). But I do not _ever_ run _any_ stock kernel on any of the machines. If somebody runs a stock kernel from any distro on their server, they are asking for trouble. I've always considered the stock kernels to be good enough for desktop use (by users who don't want to get involved in kernel compiling) and for the installation process, but not much farther than that. Having said that, removing the driver was a really not the best move, as Ben Collins said. regards, marek
Attachment:
signature.asc
Description: Digital signature