Needless mention of non-SMP kernels in slackware64-current/CHANGES_AND_HINTS.TXT ?

FeyFre · 09-14-2012, 05:30 PM

Correct me if I'm wrong.
Accidentally found in slackware64-current/CHANGES_AND_HINTS.TXT

Quote:

If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-3.2.28-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.

I think it is needless here, since AFAIK there is no non-SMP x86_64 kernels prebuilt in Slackware64 and no such directory /extra/linux-<version>-nosmp-sdk exists too. And I'm not sure if there is such hardware configurations which are both not-smp and x86_64 are widely available.

rworkman · 09-14-2012, 09:48 PM

Yeah, that's because C&H is the same file in both 32 and 64 bit trees. I don't care to maintain two copies, so my nonbinding opinion is "oh well." Sorry :-)

bormant · 09-15-2012, 12:15 AM

Is it a not bad idea to unify smp/nosmp naming between 32 and 64 bit versions and use empty localversion for smp (as in 64 now) and -nosmp for nosmp? We have nosmp-sdk already. For ex.:
huge.s, hugenosmp.s,
kernel-huge-x.x.x, kernel-huge-nosmp-x.x.x_nosmp,
kernel-generic-x.x.x, kernel-generic-nosmp-x.x.x_nosmp,
kernel-modules-x.x.x, kernel-modules-nosmp-x.x.x_nosmp,
and so on...

wildwizard · 09-15-2012, 04:40 AM

Robby perhaps you could clarify that section by adding a statement that if you are running Slackware64 then all the kernels are SMP enabled.

FeyFre · 09-15-2012, 05:25 AM

rworkman, just poped-up notice. If there are reasons to leave it there I have not any counter-arguments yet.

chrisretusn · 09-15-2012, 12:15 PM

In the for what is worth department....

I don't see this as a problem, it's sort of understood, at least by me that the file is used for both 64 and 32 bit version.

Didier Spaier · 09-15-2012, 03:05 PM

Let's bear in mind that CHANGES_AND_HINTS.TXT is intended to be read by new slackers as well.

So IMHO wildwizard's advice is a sound suggestion, which would provide accurate information as well as avoid the hassle of maintaining two versions of this file.