{"id":2484,"date":"2005-04-21T01:40:23","date_gmt":"2005-04-21T01:40:23","guid":{"rendered":"http:\/\/www.soulhuntre.com\/items\/date\/2005\/04\/21\/more-on-linux-stability-issues\/"},"modified":"2005-04-21T01:40:23","modified_gmt":"2005-04-21T01:40:23","slug":"more-on-linux-stability-issues","status":"publish","type":"post","link":"http:\/\/legacyiamsenseiken.local\/2005\/04\/21\/more-on-linux-stability-issues\/","title":{"rendered":"More on Linux stability issues…"},"content":{"rendered":"
Remember way back (chuckles) when I mentioned that it looks like Linux is in trouble<\/a>? Well here are two threads on \/. – aside from the recent stupidity with BitKeeper<\/a> – to show you what I mean. Even the zealots see the problem.<\/p>\n Some quotes…<\/p>\n “Instead we have a bunch of fragmented containers (KDE, Gnome, lots of lesser known desktop environments) that are incomplete and immature. Heck, its a pain in the ass sometimes to get simple brain-dead stuff such as printing and mounting a drive working. So you have projects like OpenOffice having to write their own container!!! And Miguel (bless his heart) making a version of Microsoft’s .NET container (Mono) for Linux that is still incomplete and sits with an incomplete container — Gnome, which is sitting on top of an incomplete desktop container — Linux. <\/p>\n I know this is a rant, but my shop recently switched back to Windows from Linux desktops (about 40 people), why? Because the new CEO (and me too), were sick and tired of people trying to get things to work together properly.<\/b> We were sick of not having an Exchange replacement (don’t get me started on the open source ones now “available”). And new hires and our clients were just plain used to using the dominant containers out there (windows\/mac). ” – quote in context<\/a><\/i><\/p>\n “<\/i>I’ll say it: the 2.6 kernel is unstable on x86_64 platforms with USB 2.0 mass storeage devices. There are bug reports everywhere. The response? “It’s fixed.” The reality? The system locks up like Fort Knox whenever it’s booted with a USB 2.0 mass storeage device attached.” – quote in context<\/a><\/font><\/p>\n “<\/i>They’re doing active development on 2.6 and they don’t want to fork 2.7 because apparently they’re making good progress working as they are. They expect the distros to do regression testing — something they are not equipped to do on a sufficiently large scale. Examples of major bugs allowed through are a memory leak when burning CDs (I think that was 2.6.5) and in 2.6.8 I can’t have SATA and ATA devices connected to my motherboard (which supports both, and works under other versions of the Linux kernel and FreeBSD) at the same time. Those are the major ones that have affected me but there’s always something.<\/p>\n\n
\n