Hi all,

I don't understand what the Non-SMP kernel SDK in the extras directory is
actually for. Why do you need a different kernel source tree to make a
non-SMP version? You could just reconfigure an existing set. And why the
kernel headers? Nothing should be different about kernel headers installed
along with glibc. As long as the kernel headers are those installed when
glibc was built, nothing needs to change, so why supply any more kernel
headers than we already have in the main repo? And what's all this about
module compatibility? Are we going to break stuff by reinstalling an
existing set / is there some sort of ABI difference between SMP and
non-SMP?

<Nicely confused.>

Cheers,
Sabahattin

--
Sabahattin Gucukoglu <mail<at>sabahattin<dash>gucukoglu<dot>com>
Address harvesters, snag this: feedme@yamta.org
Phone: +44 20 88008915
Mobile: +44 7986 053399
http://sabahattin-gucukoglu.com/

Sabahattin Gucukoglu wrote:
> And why the
> kernel headers? Nothing should be different about kernel headers
> installed
> along with glibc. As long as the kernel headers are those installed when
> glibc was built, nothing needs to change, so why supply any more kernel
> headers than we already have in the main repo?

Pat doesn't distribute 'sanitized' kernel headers - so in theory, yes, your
kernel headers shouldn't be configuration dependent.

On Slackware, this is not the case - we just get a straight copy + paste of
the kernels includes, hence Pat has to maintain two sets of 'headers' (I've
asked him about this before to use the proper "make headers_install" to get
away from this problem).

-Carlos
--
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D