SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
you can make a slackpkg of the whole kernel source by cd-ing into the base of the kernel (ie cd /usr/src/linux) and then doing makepkg linux2.x.x.tgz
or, install checkinstall (available in /extras in disc 2 of slackware) and then go into the base of the kernel source and do checkinstall (note: this one is a guess, it may or may not work)
or, you can manually make a package buy copying your vmlinuz file from /boot and your modules from /lib/modules and then tarring them
Well i am looking to make a package like the one found under slackware/a on the slackware install disc.... only the one I make will be just for my system.
So you could take vmlinuz and the contents of /lib/modules (lets say it is kernel 2.6.2) and transfer them to a machine with the same setup... (of course in the same location) then do a little update to lilo and it should work? Right?
For the modules just:
cd /lib/modules
makepkg kernel-modules-2.4.??-i?86-?.tgz
make sure there's only one set of modules there. this will make a package that you can install and remove just like any otjer Slack package except that it won't have any package description
For the kernel itself, just save it somehwere that's convenient. Or make a directory /tmp and copy it there(might want to include the config file and System.map as well). then cd /tmp makepkg kernel-??????? have a look at some of the regular slack packages and name your packages using the same syntax so that pkgtool can work with them.
do man makepkg for more details
I would do checkinstall, makepkg has never worked properly for me. In fact, when I try to install using the packages I create with makepkg, it doesn't install.
Originally posted by gnashley For the modules just:
cd /lib/modules
makepkg kernel-modules-2.4.??-i?86-?.tgz
make sure there's only one set of modules there. this will make a package that you can install and remove just like any otjer Slack package except that it won't have any package description
For the kernel itself, just save it somehwere that's convenient. Or make a directory /tmp and copy it there(might want to include the config file and System.map as well). then cd /tmp makepkg kernel-??????? have a look at some of the regular slack packages and name your packages using the same syntax so that pkgtool can work with them.
do man makepkg for more details
I'm still not really clear on all of the files that are needed. How about a list, shall we?
1337 list of stuff necessary to effectively transfer one's kernel to another system using a different kernel:
-vmlinuz (kernel)
-contents of /lib/modules
Create a directory /somewhere/tmp, then make a /boot directory inside that. Copy the kernel (named vmlinuz-2.4.??-version), the System.map and config to the /tmp/boot dir.
then cd inside the /tmp dir. 'ls' should show /boot. Now run makepkg kernel-2.4.??-i386-1.tgz makepkg will create a tgz file there and preserve the /boot. now just copy the tgz file to some place safe. the rm -rf ./boot
Then, from the same spot: mkdir lib lib/modules
the copy the contents of /lib/modules/2.4.?? into /somewhere/tmp/lib/modules.
The from inside /somewhere/tmp (ls should show /lib) do:
makepkg kernel-modules-2.4.??-i386-1.tgz
then copy the resulting tgz to a safe place.
You should observe the Slackware package naming conventions so that pkgtools can work with the package. You may want to create a description file (package-name.txt) as well. Just use another package desc. file as a pattern.
I have been making several of these lately and had no problems installing or uninstalling any of them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.