Messages in this thread | | | Subject | Re: wpa supplicant/ipw3945, ESSID last char missing | From | Dan Williams <> | Date | Tue, 03 Oct 2006 13:40:33 -0400 |
| |
On Tue, 2006-10-03 at 10:23 -0700, Jean Tourrilhes wrote: > On Tue, Oct 03, 2006 at 09:38:45AM -0400, Theodore Tso wrote: > > > > There is a fundamental question hiding here, which is whether or not > > it is acceptable to break users who are running some large set of > > mainline distro's, such as RHEL 4, SLES/SLED 10, Ubuntu Dapper, > > et. al, but who want to upgrade to a newer 2.6 kernel? > > > > Many users have moved to Ubuntu Dapper, or RHEL 4, or SLES/SLED 10 > > because they don't want to deal with a constantly changing/breaking > > GNOME/X world, where packages are constantly being updated and > > possibly breaking their desktop. > > In the past, I personally tried to upgrade Red-Hat Workstation > 4 with a pristine 2.6 kernel. This was far from trivial, as Red-Hat > did compile their kernel with some weird options/patches, and > userspace (libc) were expecting those. > On the other hand, I've been personally running the latest > 2.6.X kernels on Debian stable for as long as 2.6.X was > available. And, things *do* break, in the past I had trouble with > module tools, I can't run devfs or udev, Pcmcia is on the verge of > breaking, etc... > > In other words, running a bleeding edge kernel with a > super-stable distro has never been for the casual user. And, I wonder > what's the wisdom of it for the casual user, has he certainly can't > use the advanced features of the new kernel unless he updates his > userspace. > My main box is Debian stable with a 2.4.X kernel. For that > box, I don't see the point of going to the latest 2.6.X kernel, it > would give me more trouble than benefits. > > Just for kicks. Today, a new Slackware was released. And guess > what, it has Wireless Tools 28 ;-)
I'm going to push wireless-tools-28 final for FC5-updates this week too.
Dan
> > Jean
- 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/
| |