How to Make a Flash Drive Install Work Like a Hard Drive
In some new Puppies, the default behaviour is to NOT load the sfs file into memory when booting from a hard drive. So when you convert a flash drive to PUPMODE=12, you will get the same thing.
This means that the flash drive will boot faster but may run a little slower. You can fix this by adding "pfix=copy" to your syslnux.cfg file.
The original instructions state that you must format your flash drive as ext. This is because the editinit procedure cannot be done in a FAT32 environment. However, you can copy the initrd.gz into your home directory or another ext environment and modify it there. Then copy the file back to your FAT32 flash drive. It will work fine.
This means that the flash drive will boot faster but may run a little slower. You can fix this by adding "pfix=copy" to your syslnux.cfg file.
The original instructions state that you must format your flash drive as ext. This is because the editinit procedure cannot be done in a FAT32 environment. However, you can copy the initrd.gz into your home directory or another ext environment and modify it there. Then copy the file back to your FAT32 flash drive. It will work fine.
rcrsn51 wrote:In some new Puppies, the default behaviour is to NOT load the sfs file into memory when booting from a hard drive. So when you convert a flash drive to PUPMODE=12, you will get the same thing.
This means that the flash drive will boot faster but may run a little slower. You can fix this by adding "pfix=copy" to your syslnux.cfg file.
The original instructions state that you must format your flash drive as ext. This is because the editinit procedure cannot be done in a FAT32 environment. However, you can copy the initrd.gz into your home directory or another ext environment and modify it there. Then copy the file back to your FAT32 flash drive. It will work fine.
Have it formatted to ext . Will try pfix=copy, but it seems fast anyway. (actually extlinux.conf)
Spup Frugal HD and USB
Root forever!
Root forever!
It probably doesn't make a big difference. In the case of your web browser, all the content that is stored in your profile has to be read from the pupsave file regardless of how the actual program code has been loaded. The former may have a greater impact on speed than the latter.DaveS wrote:but it seems fast anyway.
Haha.. moral of story... 'don't do this from within the Puppy you are modifying'. Booted from HD, modified initrd on USB from within a HD install, re-booted from USB, all fine. Off for a glass of wine nowrcrsn51 wrote:WFM. I created a standard PUPMODE=13 Slacko flash drive. The sound was working and I made a save file. I verified that sound was still working after a reboot, then switched to PUPMODE=12. I inserted the line after line 806. Sound still worked in the new setup.
Spup Frugal HD and USB
Root forever!
Root forever!
Forgive me for thread-dredging, but I have to give a shout-out to rcrsn51.
I frugally installed a puppeee to an ssd partition and could not get out of the pupmode=12 state until I found this thread and the great init editing tool.
Put a pupmode=13 in the init and now I have a true frugal install on an ssd partition with no need to boot off usb/sd card.
rcrsn51--many, many thanks,
Jake
I frugally installed a puppeee to an ssd partition and could not get out of the pupmode=12 state until I found this thread and the great init editing tool.
Put a pupmode=13 in the init and now I have a true frugal install on an ssd partition with no need to boot off usb/sd card.
rcrsn51--many, many thanks,
Jake
Oh, dear, this didn't work out as well as I thought.
While I am running in pupmode 13, I'm unable to save manually. The cpu goes to 100% and no changes are written to pupsave.sfs.
I thought of a corrupted save file, but even with starting fresh, I wasn't even offered a choice to make a save file at the end of the initial startup.
If I run this puppeee, fresh, with the original init file, then I am offered a chance to save at the end of the first session.
Changing the syslinux.cfg file to pmedia=ideflash, or ataflash, or usbflash does not help.
Jake
While I am running in pupmode 13, I'm unable to save manually. The cpu goes to 100% and no changes are written to pupsave.sfs.
I thought of a corrupted save file, but even with starting fresh, I wasn't even offered a choice to make a save file at the end of the initial startup.
If I run this puppeee, fresh, with the original init file, then I am offered a chance to save at the end of the first session.
Changing the syslinux.cfg file to pmedia=ideflash, or ataflash, or usbflash does not help.
Jake
How to Make a Flash Drive Install Work Like a Hard Drive
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
Jemimah made her suggestion here and it apparently worked for nooby in Quirky. Maybe puppeee doesn't recognize "pmedia=ataflash".
PUPMODE=13 is a much more complicated environment than 12. You may not be able to force it just by changing the init.
PUPMODE=13 is a much more complicated environment than 12. You may not be able to force it just by changing the init.
Yes, when in pupmode 13 and it was trying to save, it appeared to be making a copy of everything, if only b/c all the folders in root and above were suddenly in bold text, puppy's signal that changes have been made.
But it never finished the save properly and remembered very little of what I had asked it to save.
Jake
But it never finished the save properly and remembered very little of what I had asked it to save.
Jake
- dalebednell
- Posts: 120
- Joined: Fri 12 Feb 2010, 09:44
- Location: portugal
- Contact:
How to Make a Flash Drive Install Work Like a Hard Drive
Hi
Thanks for this script works like a dream nice not to have the wait to shut down.
Thanks for this script works like a dream nice not to have the wait to shut down.