Correct way of using the orinoco_cs driver
mike at pineview.net
Tue Jan 22 19:29:09 EST 2002
Thanks for you comments, it would seem that I had a misunderstanding of the
----- Original Message -----
From: "Steven Hanley" <sjh at wibble.net>
To: <wireless at lists.samba.org>
Sent: Tuesday, January 22, 2002 11:31 AM
Subject: Re: Correct way of using the orinoco_cs driver
> On Mon, Jan 21, 2002 at 12:42:20AM +1000, Mike O'Connor wrote:
> > I linked the include/asm and include/linux because thats what supposed
> > happen. Must current Disto do not and this causes problem, at least
thats what I
> > have seen from my reading of the linux kernel mail list.
> well lets see, Linus has often said, do not ship distributions with direct
> links to some specific kernel source headers, ship it with a snapshot that
> thew glibc people have created of the headers.
> The kernel (even a stable series) according to Linus has the right to
> the way the headers would work, which can cause glibc and other parts of
> systemn to be come severely messed up.
> No distributions do it anymore as Linus told them not to on pain of shit
> hitting the fan in a big way.
> If you do use whatever headers came with the latest kernel, go ahead but
> is no guarantee things will work.
> /usr/include stuff should all come from glibc. If something needs the
> current kernel headers (say some kernel modules you compile outside the
> tree) or similar (user sace stuff should not be dependant on the current
> kernel headers, they should be dependant on the headers shipped with
> Linus has stated this many times over the years.
> So from time to time you may need to use some other header breifly for
> compilation (like the bug that was causing segfaults a few months ago with
> old version of wireless tools when you didnt use the kenrel header) but
> does not mean you should use all the kernel headers form the latest kernel
> that may o may not work with your userspace.
> Linus and other kernel people have said time and time again that they make
> guarntees of behavior of user space for this, tit is up to the glibc
> proivide the interface (a stable working interface).
> So do otherwise at your own risk I suppose.
> See You
> sjh at wibble.net http://wibble.net/~sjh
> Look Up In The Sky
> Is it a bird? No
> Is it a plane No
> Is it a small blue banana?
More information about the wireless