Hi, all.
Just to prove the concept separate kernel works without issues I decided to do quick and dirty experiment and it worked like charm. I'm more than happy with the result
Tested with KDPup-484 main sfs module (renamed to 01-KDpup-484.squashfs)
http://murga-linux.com/puppy/viewtopic.php?t=55301
placed in /live folder with 011-kernel-486.squashfs separate kernel module and initrd1.img and vmlinuz1 from DebianDog here:
http://www.smokey01.com/saintless/Light ... g-test.iso
On the picture you can see the content of /live boot folder.
Here is the boot code if someone like to experiment the same:
Code: Select all
title DebianDog initrd1.img 486
rootnoverify (hd0,0)
kernel /live/vmlinuz1 boot=live config swapon noprompt nofastboot autologin persistent
initrd /live/initrd1.img
boot
Note puppy sfs module has its own firmware and Kernel 2.6.30-5. There is no firmware in the kernel 3.2.0.4-486 module.
This means we can boot puppy main module with debian kernel and initrd.img but getting debian system structure and debian save file options. And getting back the option to load up to 9 modules on boot.
KDPupup is debian based puppy so it is not 100% sure this will work with any puppy module but I guess it will.
Of course puppy save file will not work like in puppy. You can create save file from the same running Kdpup + debian kernel system but after this rename it to live-rw and place it on the top of the partition /
The save file will work in pure debian live way.
Here is the kernel output:
Code: Select all
# uname -r
3.2.0-4-486
# uname -a
Linux puppypc 3.2.0-4-486 #1 Debian 3.2.51-1 i686 GNU/Linux
#
Keep in mind the structure is different:
/initrd/pup_rw = /live/cow
/initrd/pup_ro2 (or /mnt/home) = /live/image
Toni