Manoj Srivastava writes: > Hi, > >>"Luiz" == Luiz Otavio L Zorzella <[EMAIL PROTECTED]> writes: > > Luiz> I wish to send a mail to the OSS tech support about this > Luiz> situation with debian. Is there anything you think I should > Luiz> suggest to fix the problem in a clean way (all the dists, > Luiz> including Debian)? > > Yes. Tell them not to use grep. There are ways to include a > linux header to tell what kernel version is being used (if they do > not know what I mean, tell them to look at the sources of modules in > the kernel to determine how to do that). At run time, they can call > uname. Using grep and trying to second guess the installation about > whivh headers were used is evil, and shoddy software practice. >
Forgive my dumbness... I've been thinking exactly what are the implications of what your're saying. Please correct me if I'm wrong: 1) sndshield, at *compilation time*, greps autoconf.h to guess which kernel version is being used. In my case, since it did not find any at /usr/src/linux/include, it found one at /usr/include, which was a symlink to 2.0.32 headers. This way it thought it was being compiled in a 2.0.32 system. 2) sndshield, at *run time*, does a "uname -a" (or something) to find which kernel version is being run. In my case it found 2.0.33, and threw a mismatch. 3) Most important: are you saying that even compiled against 2.0.32 headers, since it was compiled under 2.0.33 it was supposed to run without any problem? Question "3" is crutial for what I'm gonna suggest to OSS people. Before you wrote me, I was thinking of suggesting them to "-I" /usr/src/kernel-headers-`uname -r` in a debian system... Thanks a lot for the support. -- Luiz Otavio L. Zorzella Product Engineer [EMAIL PROTECTED] http://www.conexware.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
