> Okay, so it was 14 that had the file loopback bug, and 12 that had the
> ieee bug.Those bugs shouldnt have been in there in the first place!
> Those are very major potentially show stopping bugs. What If I get up
> one day, and I cant print? Or build isos? That sounds minor to you, but
> thats a big thing if say, the linux box is a network print server, or,
> its the workstation for the guy in the company who builds the iso. And,
> no, "use the previous kernel" isnt a good excuse. Because what if you
> get hit with bugs back to back? You'll have to go back to some kernel
> way way back. Like 2.4.2. The Kernel needs Quality Assurance.
Yes, this is a QA problem. But also .. if you're a smart net/system
admin, you don't go out installing a just released kernel without
letting others bang on it or run it on some test servers. Where I work,
I insist the admins wait at least 1-2 weeks before going to the latest
release unless there's some huge security fix.
--===================================================================== Mohammad A. Haque http://www.haque.net/ mhaque@haque.net
"Alcohol and calculus don't mix. Developer/Project Lead Don't drink and derive." --Unknown http://www.themes.org/ batmanppc@themes.org =====================================================================
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/