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 would like to create a custom image for a Slack 8.1 CD using the 2.4.19 kernel. The laptop I want to install it on (Fujitsu P2000) has problems with the stock 2.4.18 kernel. bzImage I can manage. Same for config. Is the System.map.gz just a gzipped version of the System.map? Also would I need to do anything beyond creating an appropriate folder in the kernels directory?
Anybody think/know if it would work? It would also save me a couple of steps on installing Slack f I started with 2.4.19 (+ source)
The process you requested is possible, I have reauthored both the install iso and the 2nd CD of the set. I use the 2nd CD, the live system CD, with a 2.4.19 kernel to support IEEE-1394 Firewire devices not supported by 2.4.18 kernel. I can provide some thoughts and/or directions below. The process here is definitely for an advanced user. A lot of CDR's can be wasted.
You can find the directions for the authoring process in the isolinux directory on the install CD, filename README.TXT. If the installation is the problem area then a new kernel for 2.4.19 can be built and installed as the boot kernel by replacing the kernels/bare.i directory contents with your new files. The System.map.gz is just a gzipped System.map file. If you wish to create your own directory, then please look at the isolinux/isolinux.cfg file. I believe it would require modifications for your boot options to work. I would highly suggest that you start your 2.4.19 build using the 2.4.18 bare.i config file. Then verify or change what is needed to resolve the compatiblity issues. Be sure to change what you require to kernel built options and do not use any modules. If you include your 2.4.19 tar ball on the CD then you can extract it after the install is complete and transfer your config file. Then after rebooting, build the kernel system under 8.1, and include the modules that you would like to have built. You should then be able to install the modules into the proper driectory.
The Slack 8.1 iso requires 700 MByte CD at present. You will probably require more space than available. You can elliminate KDE or GNome from the slackware directory to achieve the space. If you desire both then you can either install one of them later or mount the original install CD for the install process. If you use the later then you need to update the kernel manually after the install is complete.
Good luck and I hope the info will be of some assistance.
Thanks for the info. Of course given I know my hardware I can eliminate some of the images (*.s). Maybe Latex. Given those tradeoffs I think I can cram it in. If not I'll take out KDE and install it later.
Replacing bare.i is a good idea, did not think of that one. I actually don't need to be terribly precise in the kernel, the problem revolves around an issue with the PCI chipset getting hung during install. There is a patch out for 2.4.18 that was folded into 2.4.19. I suppose I could take the bare.i config and compile a 2.4.18 kernel with patch in place, but that seems like a lot of work since I am going to upgrade to 2.4.19 after the install is done. I'll give it some thought.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.