So far, I've made coasters....Dang cdrw drive...Well, it is 7 years old...lol
I will outline what I did when I successfully complete it.... |
I did done did it!
Give me a bit to write up how I did it. I'm getting old and creaky here, and the brain doesn't work as fast as it used to.
But It DOES install your custom kernel right off the bat. You do have to install sources, modules later, just like test26.s. But I'll have everything outlined in the article. |
Not For Newbies!!!!!!!!!
NOT FOR NEWBIES!!!!!
Here's how I did it: 1: Make sure your custom kernel has the cdrom filesystem and ext2 options COMPILED IN. (Or you'll get the dreaded VFS: Kernel Panic error). 2: Make a /saved directory: Code:
mkdir /saved Code:
cd /saved 3: Make sure you have 'checkinstall' installed on your system. If not, you can install it from the 'extras' directory that will be made later. 4: Get this file: http://www.slackware.com/~alien/tools/mirror-slackware-current.sh Edit it to your specs, and add in the 'forced' option so it always makes an iso, then save it. I put it in /sbin, then make it executable. 5: Run 'mirror.sh'. Burn a copy of the resultant iso's to make sure everything works. 6: Go to your kernel source directory, i.e. /usr/src/linux (I always symlink linux to my current kernel). Run 'makepkg' to make a 'source' package. Name it something with 'source' in the filename, and save it to /saved. 7: Stay in /usr/src/linux, and run 'checkinstall', saving the resultant file with 'kernel' in the name, and in /saved again 8: Copy your vmlinuz, config, and System.map to /saved/custom.i . Compress your System.map to a .gz file, and delete the System.map file. Rename the files so they are 'bzImage','config' and 'System.map.gz' 9: Go to /lib/modules/name-of-kernel and run 'makepkg' with 'module' in name, and save it to /saved 10: Go to your 'slackware-current' dir. 'cd' to 'isolinux', and open the 'isolinux.cfg' file. Add in the 'custom.i' kernel. Here's mine as an example: Code:
default /kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=6464 rw root=/dev/ram SLACK_KERNEL=bare.i 11: Open edit the 'f3.txt' file, and add in your 'custom.i' kernel info, and save to /saved 12: Go to your 'mirror.sh', and edit that. Find the following lines: Code:
cd ${SLACKROOTDIR}/${SLACKCURRENT} Code:
mv /saved/isolinux.cfg /slackware-current/isolinux/isolinux.cfg Now, I haven't done a full install again yet, just the beginning part to see if the custom.i kernel loads, and it does. After install is over, and you rebooted, go to 'testing', and installpkg on all your new kernel packages. Hope this helps. I am now going to 'recompile' my bloody kernel again, and do the same process, including a fresh install.... My next post on this thread should be with the new custom.i kernel installed by the installer.... |
Whoa. Man, once you've started on something, you don't let go, do you? Nice work.
One trivial suggestion... and I hope this isn't annoying after all the heavy lifting you did to solve this. Since you built packages for the modules and source, you could move them to the appropriate disk sets and add the package name to the tagfiles. That way the install disk will do the work instead of installing them by hand afterwards. I appreciate your taking the time to write this up. I'm definitely doing this for 11.0. |
I was limted to the 'mirror.sh' and rsync. When mirror.sh runs, rsync erases everything that is not on the 'master' mirror....And for whatever reason, I couldn't write a script that would do what I wanted, so...
It works. A little kludgy, but it works. It's installing right now on my spare, so I'll let you know. |
Dang it. Forgot to have ext2 support compiled.
Once more into the breech (At least I'm using rw disks...Third time's the charm...) |
OK. It works. I need to work on the kernel-modules and source, but it DOES install the custom kernel.
Unfortunately it does not work correctly if you START with the custom kernel and try to install over the network (no module for the ethernet card.) Minor inconvenience, I just booted with the test26.s, at the end installed the custom.i, extracted the modules to the correct place, extracted the source also, and here I am. Anybody know how to get the packages (module,source) to auto-install/extract to the correct directories? I haven't looked into makepkg or checkinstall much. I could just be missing a switch or something. Plus, for whatever reason, 'testing' did not burn to my 2 cd's. Any help? |
All times are GMT -5. The time now is 03:36 AM. |