LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Puppy (http://www.linuxquestions.org/questions/puppy-71/)
-   -   puppy can't find cram.fs on usb install (http://www.linuxquestions.org/questions/puppy-71/puppy-cant-find-cram-fs-on-usb-install-458241/)

bernied 06-25-2006 05:09 PM

puppy can't find cram.fs on usb install
 
Similar to tracer009 in another thread on this forum, I couldn't get the script that is supposed to install puppy onto usb to work for me. So I did it the hard way using grub.
When I boot puppy with grub using the isolinux.cfg settings, I get something like 'can't find cram.fs on cd. You can work around this by putting cram.fs on /dev/hda2'

So I did and it works, but I'd rather the puppy install on the stick was a bit more self sufficient and that 50+MB file wasn't just taking up space.

So, how can I adapt the usb install so that it looks on the usb stick, and not on the cd, for cram.fs? Is there a kernel option that specifies the correct location?

Here's my grub entry:
Code:

title        puppy
root        (hd0,1)
kernel        /vmlinuz root=/dev/ram0 initrd=image.gz acpi=on PFILE=pup001-none-262144
initrd        /image.gz
boot

I don't suppose that the reason is that puppy only looks for FAT filesystems, is it? Because I installed it onto a ext2 filesystem (that hda2 that puppy likes so much is a FAT filesystem).

slvrldy17 06-25-2006 05:25 PM

File systems and Puppy
 
One of the mildly annoying traits of the Puppy 1.0.x series is that it insists on putting the pup001 file on the first suitable partition it comes to be it FAT, ext2, or whatever. Also it doesn't detect USB drives until after that stage of the boot process. Thus, if you have a pup001 file on different partition Puppy will often make a new save file on that first drive it comes to rather than look further! This has been mostly addressed and fixed in the new 2.0 series - recomend that you give that a try. As for booting from USB drives - there are people way more expert than I on that subject on the main Puppy forum - best to try there. Hope this helps.

Nathan F 06-25-2006 05:32 PM

Looking at your post it seems like this must be in the Puppy-1.x series, since it's still using usr_cram.fs and image.gz. You might try setting the PHOME variable, which specifies which partition has the personal storage file. This is important because Puppy should also look there for usr_cram.fs. Just add it to the kernel line something like this: PHOME=hd0

Personally I've never had a problem with the usb installer script, other than the fact that you must have a single bootable fat partition on it before you begin. In your case the drive would have to be reformatted since it's not fat. The biggest problem is usually that a person does not make the drive bootable, and the script will not give much help here.

Not having ever tried what you are doing I probably won't be much more help than this. It's possible to manually mount usr_cram.fs and create the union on /usr, but preferably you would want to get this right from bootup.

Nathan

bernied 06-25-2006 06:09 PM

Thank you Nathan. I will try that kernel option.

Yes, I think your theory that the stick wasn't FAT formatted is correct - I should have just read the manual. I think by the time I read that bit I had already put slax onto a stick, so stopped caring so much about puppy. But this time I'm trying to put multiple live-cds onto a single usb stick (for no real reason), and puppy has a certain something.


All times are GMT -5. The time now is 04:58 PM.