Puppy Linux Discussion Forum

[rcrsn51]

A flash drive install of Puppy runs in PUPMODE=13 as opposed to PUPMODE=12 for a normal frugal install on a hard drive. This means that any files you add or change are temporarily held in memory, then flushed back to the pupsave file at regular intervals.

The intent of this system is to reduce excessive writing to the flash drive and prevent it from wearing out prematurely. But it also results in some annoying pauses, especially when you want to shut down.

Now that flash drives are cheaper and have wear-leveling technology, it may be simpler to run your USB install in regular PUPMODE=12. Be aware that the following procedure is somewhat experimental. YMMV.

1. Build a Puppy flash drive as usual, create a savefile and confirm that it is working correctly.

2. Boot off your hard drive and install the editinit-1.0.pet attached below. It adds a script to /root/my-applications/bin.

3. Mount your flash drive. Copy the file initrd.gz to a temporary location in your Linux filesystem, like /tmp. You cannot change the file while it is on a FAT32 drive!

4. Go to /tmp and open a terminal window. Run the command:

[Sylvander]

Would it be possible to make a pupsave on a HDD act like it's on a Flash Drive?
e.g. Being able to configure no auto-save DURING a session [back to the pupsave]...
And also to be able to choose to NOT-SAVE [or save] at shut-down/reboot of a session.

[rcrsn51]

Try using the above procedure, but with "PUPMODE=13".

[Edit] Or better yet, use jemimah's suggestion here.

[nooby]

rcrsn51 , Jemimah suggest two different ways to do it?

[DaveS]

Thanks rc., this is a REALLY useful script. Though I can see the need for PUPMODE=13, I always hated the long shutdown and pauses. Works like a charm.
I tried to edit initrd myself a couple of times, but always got in a mess. thanks again............. Dave.

[rcrsn51]

Now we need to know whether PUPMODE=12 actually kills a flash drive prematurely. Can you keep some records and report back in the future?

[DaveS]

[Sylvander]

1. "Try using the above procedure, but with "PUPMODE=13"."
PROBLEMS:
(a) That looks complicated as it is, but to attempt to transpose to do the opposite I fear is beyond me.
Could you give explicit instructions for making the Puppy treat the HDD like a Flash Drive?

(b) I'm booting "live" Puppy CD-RW disks, with pupsave+SFS filepairs in partitions on an 8GB Flash Drive.
My PC's BIOS doesn't boot USB, so I didn't install to USB.
I then copied the pupsave+SFS filepairs to folders only one layer down on a partition on an internal HDD.
If I connect the Flash Drive, Puppy finds both sets of filepairs, and asks which it should use.
I'd like the [FASTER!] HDD arrangement to give the choice to NOT-SAVE just like the Flash Drive arrangement.
The initrd.gz file is on the CD-RW, so how to edit it?
Having fun with all the wonderful things Puppy can do.

2. "Or better yet, use jemimah's suggestion here."
PROBLEMS:
(a) "Just add pmedia=ataflash to the bootloader"
But there is no bootloader used in my setup.

(b) "This will let the kernel know that the drive is an SSD"
I'm confused...
I'm not using an SDD.

[nooby]

Sylvander,

[DaveS]

Suddenly started getting this error message on boot. Any clues? Everything else is fine...................

[rcrsn51]

Check that the file is still there and is readable/writable.

When I have been playing with a PUPMODE=12 flash drive, I found it was essential to leave it plugged in at shutdown until it had quit flashing and all activity was completed.

[DaveS]

[the last saviour]

Thank a lot for your advice.
Cheer...

[fyujj]

[nooby]