On Wed, 13 Jul 2005 07:47:43 +0400 Stas Sergeev <[EMAIL PROTECTED]> wrote:
> to beleive it really uses a symlink. > I remember Patrick Volkerding claimed > in that very list that Slackware doesn't > do this, but it looks like it was changed, > or at least there is some bug... > If some distro really does this, then > rooting out this tendency among users > is going to be really troublesome:( > And some people claim that even > installing the 2.6 headers from the > slackware package still gives an error! > And only that the 2.4 headers work > properly. After some googling I think I finally found the correct linux-libc-headers (as they are now called). http://ep09.pld-linux.org/~mmazur/linux-libc-headers/ So I will splice these to my devel box and see if 1.3.2 works better with Linux 2.6.7 (It does not work too bad with the 2.6.7 Kernel headers on 2.6.7, but not as well as with the 2.4.31 headers and kernel 2.4.31) The thing about Slackware is that they stuck with the 2.4 kernel for a long time, since very conservative. It was just now that they have an alternate 2.6 kernel in the distribution and note that it is an alternate! So I have been using plain 2.6 kernel headers for 2.6 development (dangerous, but most of time works for my purposes) but now I am going to switch to the libc headers or "sanitized kernel headers", since they seem robust enough and I am now aware of them... TonyB __ __ _ I N C. http://www.sysdev.org / __|\\// __|| \ __ __ / [EMAIL PROTECTED] \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
