How to re install kernel from slackware current

[jsfarinet]

The other day i had found a How To about how to install a kernel from slackware current and how to arrange so that the old working kernel rests. Unfortunately, i do not find this link anymore.

Someone knows it by chance?

TIA

[Atip]

Your might search the Internet or what I do which is easy.
I have Slackel Openbox installed. That distro (a close relative of Salix)
keeps one always current.
From there I copy all what is in /boot, /lib/modules and /lib/firmware to my
Salix working box. Don't forget to run lilo

[jsfarinet]

Your might search the Internet or what I do which is easy.
I have Slackel Openbox installed. That distro (a close relative of Salix)
keeps one always current.
From there I copy all what is in /boot, /lib/modules and /lib/firmware to my
Salix working box. Don't forget to run lilo

As i said, i've found one good instruction (iirc just on the slackware site) how to install the kernel as an alternative to your existing working kernel and not to have to compile your own kernel. But stupidly i missed to save that site and now i don't find it anymore.

My hope was someone here could know which site it was . . .

[gapan]

I don't know which site it was, but the summary of it should be something like this:

1. Download all kernel-* packages that you're interested in (except the kernel-headers package)
2. Install every one of them with

Code: Select all

sudo installpkg package.txz

(you can use *.txz if you have them in the same directory and nothing else in there)
3. Look in your /boot for vmlinuz-* files. Pay close attention which one is symlinked to vmlinuz.
4. Edit your lilo.conf and add similar entries with the one that you already have
5. Run lilo.

[jsfarinet]

Kernel headers means the same like in Debian? in any case the files i downloaded from slackware-current look like this:

Code: Select all

kernel-firmware-20141106git-noarch-1.txt
kernel-firmware-20141106git-noarch-1.txz
kernel-firmware-20141106git-noarch-1.txz.asc
kernel-huge-3.14.24-x86_64-1.txt
kernel-huge-3.14.24-x86_64-1.txz
kernel-huge-3.14.24-x86_64-1.txz.asc
kernel-modules-3.14.24-x86_64-1.txt
kernel-modules-3.14.24-x86_64-1.txz
kernel-modules-3.14.24-x86_64-1.txz.asc

Would be those (the *.txz) i should install?

[gapan]

Yes. You can upgradepkg the firmware package and installpkg the other two.

[jsfarinet]

Yes. You can upgradepkg the firmware package and installpkg the other two.

Did it and it works! Thanks.

Two questions:

1) The upgrade-notifier always prompts me to "upgrade" the kernel 3.14 > 3.10.How can i avoid that?
2) Why not install the kernel headers? May be that's a stupid question, but from debian i'm used the kernel headers (with the same version number as the kernel) are needed for compiling ... (?)

[gapan]

1) The upgrade-notifier always prompts me to "upgrade" the kernel 3.14 > 3.10.How can i avoid that?

That is not the default behaviour. You caused that by unblacklisting the kernel-* packages in gslapt.

2) Why not install the kernel headers? May be that's a stupid question, but from debian i'm used the kernel headers (with the same version number as the kernel) are needed for compiling ... (?)

The kernel-headers package is tied with glibc, not the kernel. Unfortunate naming I guess. What you are thinking about is probably the kernel-source package.

[jsfarinet]

1) The upgrade-notifier always prompts me to "upgrade" the kernel 3.14 > 3.10.How can i avoid that?

That is not the default behaviour. You caused that by unblacklisting the kernel-* packages in gslapt.

2) Why not install the kernel headers? May be that's a stupid question, but from debian i'm used the kernel headers (with the same version number as the kernel) are needed for compiling ... (?)

The kernel-headers package is tied with glibc, not the kernel. Unfortunate naming I guess. What you are thinking about is probably the kernel-source package.

Thanks a lot for your patience!

Ad 1) Yes, i corrected that (i've the same problem witg claws-mail; i got from SBO the newer version 3.11 since the version in gslapt doesn't contain the spamassassin plugin).

Ad 2) Probably. For sure you're right.

I'm not so into kernel and "./configure make sudo make install" but i remember, to be able to do that, in debian, you had to have installed the headers. May be over there they are connected in some way to kernel-source ??).

Cheers.

[gapan]

I'm not so into kernel and "./configure make sudo make install" but i remember, to be able to do that, in debian, you had to have installed the headers. May be over there they are connected in some way to kernel-source ??).

Yes, you need the kernel-headers package for that, but that isn't tied to the kernel, but to glibc instead.

You can take a look here for more info: http://alien.slackbook.org/dokuwiki/dok ... rs_package