Installed slackware on a usb-stick - no problems whatsoever.
I want to carry that li'l sucker around as my personal linux-on-a-stick - no matter which machine I put it into and boot from it.
My problem is booting - and I'm using 'grub legacy' (and please, grub2 is an OS looking for a bootloader - I don't want it!)
What happens is that I get the (in)famous:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My layout of the stick is as follows:
part #1: ext2, 64M (my 'grub'-partition)
part #2: swap, 2 gigs
part #3: jfs, 30 gigs, slackware in all its glory
I probably should explain my 'grub-partition', it is something I always use (as I generally have at least 3 different distros on each harddrive/computer).
Then, whenever I install a new distro, I let its bootloader reside on the partition of its root fs - be it grub or grub2. Then my menu.lst just contains 'root (hd0,X)' and 'chainloader +1' ... ez ...
I always use ext2 for my first partition - it is never mounted unless I change anything in there. In this example, the stick comes out as sdc - all depends how many hard-disks in the computer; on my laptop it would be sdb.
mkfs ext2 /dev/sdc1
mount /dev/sdc1 /mnt/pen
cp /usr/lib/grub/i386-pc/* /mnt/pen/grub
Then I make my menu.lst-file
- and it looks like this:
kernel /boot/vmlinuz ro root=UUID=abc.... rootdelay=30
The way I understand it - when you boot from any disk, that disk will be device (hd0) - then the kernel gets loaded and your bootdisk might be demoted to eg. the 3rd disk - all depends on the bios.
After installing slackware, I also change the /etc/fstab to use UUID for the swap and rootfs so I should not be dependent upon which sdX my stick will end up as.
So yes, the kernel boots and everything looks good until it attempts to mount the root filesystem ...
And yes, I _have_ googled and got some few thousand hits ...
Anyone here that can solve my li'l problem?
Thank yall in advance!