LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel >= 2.6.10 with slackware 10.0 (https://www.linuxquestions.org/questions/slackware-14/kernel-%3D-2-6-10-with-slackware-10-0-a-323750/)

xPhoenix 05-15-2005 12:57 PM

Kernel >= 2.6.10 with slackware 10.0
 
Hi!

I've had this problem with kernels 2.6.10 and newer and slackware 10.0....
I'm rather new to linux, and I thought hey! if there's a kernel 2.6.11.9 out there, why use the old 2.6.7 version that went with the distribution?
Well, to put it simply, it didn't work. I tried with kernels 2.6.10, 2.6.11 and 2.6.11.9, I even tried using config files from the 2.6.7 kernel( which worked fine) and configuring the additional options...
The problem is the following: after using a new kernel, less stops working. I tried recompiling less with the proper kernel headers, I tried recompiling ncurses and I don't know what else could affect it.
Most notably, since less didn't work, man didn't work either. After running man I got an error saying that a given command could not be executed. The command was listed, and i checked all the executables it referred and they all worked except less. Also, man said the command terminated with error code 256.
Invoking less directly from the command line( either with a pipeline or with a file as a parameter) doesn't do anything - no error reports, no nothing - I just get the prompt in the next line.

After installing slackware 10.1( it's got kernel 2.6.10) i recompiled kernel 2.6.11.9 with the same options as earlier and it works fine. I'm curious as to what could have caused that error in the previous release....

david_ross 05-15-2005 01:15 PM

Welcome to LQ.

It's a problem with the way udev is set up - see:
http://kerneltrap.org/node/4474

xPhoenix 05-15-2005 03:15 PM

Thanks! It seems to do the job :)


All times are GMT -5. The time now is 04:18 PM.