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.
I'm pretty sure checkinstall can be used for that. Seems pointless though. All you need to do is delete the old kernel in /usr/src, your modules in /lib/modules and kernel in /boot directory.
checkinstall "make modules_install && make install"
After you've built your modules and you *should* get one package that contains the kernel & the modules. Running checkinstall with arguments, checkinstall will execute the arguments passed to it instead of running (by default) `make install`.
checkinstall "make modules_install && make install"
After you've built your modules and you *should* get one package that contains the kernel & the modules. Running checkinstall with arguments, checkinstall will execute the arguments passed to it instead of running (by default) `make install`.
o You normally would su and make install. Now it's only su:
su
password: xxxxx
o Run checkinstall:
checkinstall
NOTE: If you give no arguments to checkinstall it will run a "make install".
If you give arguments, the first non-option argument will be used as the
install command. This is useful when the install command is not "make install"
but something else like "make install_packages" or "setup" or whatever, i.e.
checkinstall make install_packages
checkinstall make modules_install
checkinstall install.sh
checkinstall setup
checkinstall rpm -i my-package-1.0.i386-1.rpm
== 2.6.1 == Slackware packages
o checkinstall will ask if you want to see the installation results, then run
the modified Slackware package maker "makepak". If you want checkinstall to
use the original Slackware's "makepkg" then change the MAKEPKG variable
inside the checkinstall script and read this:
makepkg will ask you a couple of questions:
If there are any symbolic links in the installed package it will ask you
to remove them and make an installation script to re-create them whenever
you install the package. This is a GOOD THING, so answer YES. --> BTW,
makepkg doesn't always ask you this (depending on whether you have symbolic
links or not) so be careful and read before you answer, you could be
answering the wrong question. Read on:
makepkg will *always* ask if you want to change the owner, group and
permissions of EVERY file in the package to root:root:755. This is BAD most
of the times, always answer NO to that question, unless you know
what you are doing, of course
o In the end, checkinstall will install the package with installpkg so you
can remove it later with Slackware's removepkg (Our initial intention ).
Additionally, it will leave a copy of the package in the source directory,
the package's name will be name-version-architecture-release.tgz. Using the
Afterstep example, the file would be named Afterstep-1.8.4-i386-1.tgz.
Starting with checkinstall-1.5.1, the created packages will be named
using the new (post-Slackware 8.0) Slackware package naming scheme.
o You can add a customized installation script which will be run by "installpkg"
every time you use it to install your new package.
Write it and name it "install-pak" or "postinstall-pak" and checkinstall will
include it for you.
This script can be useful to set up the system to fit the newly installed
package: create new users, set permissions, initialize databases, rcscripts,
etc.
I'm pretty sure checkinstall can be used for that. Seems pointless though. All you need to do is delete the old kernel in /usr/src, your modules in /lib/modules and kernel in /boot directory.
Why?
Because maybe I can use this to make a pkg that will install with pkgtools and not have to do all the steps you just describes. Also I am very meticulous about everything. It all needs to be registered with pkgtools and I am going to do this for all my programs. It is just new to me and I wanted to know if it could be done. I guess you could say it is pointless, but not to me since I asked. This might seem a like a mean response, but it isn't. I am in a happy mood and appreciate every comment.
The kernel is just one file; why use Checkinstall? I doubt it could even be used for this...
Not quite a single file. Usually you also would need System.map too. Also even now one can choose to include config.gz to the compiled kernel, it is a good habit (an a Slackware tradition) to have a copy of the kernel config in the /boot directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
).
This might seem a like a mean response, but it isn't. I am in a happy mood and appreciate every comment.
