If you included support for initrd and you didnt make an initrd.2.6.7.img in your /boot partition...
Yeah that's what causes it, I guess.
So I need
It's tough to remember your kernel configuration by heart. But I guess the config is still stored in the folder for the kernel source is/was, or? Maybe I included initrd support, maybe not.
My filesystem is not a module, is compiled to the kernel.
About the boot partition... I'm not quite sure about that since ZipSlack doesn't have partitions. So if I put initrd in /boot, will it be able to find it? I hope so...
Kernel Panic: No init found. Try passing init=option to Kernel
How about the init= option, do I need that then?
This thread belongs to the Slackware forum...