UPDATE:
# 29 Jan 2011 v0.2: fix under RAM mode (PUPMODE=5), multisession CD support (PUPMODE=77)
See the top of this topic._________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Sat 29 Jan 2011, 18:41; edited 1 time in total

Would it be possible to patch the bootmanager to do this?
I think a new and improved bootmanager would be less confusing than two boot managers.

I agree. The bootmanager can be modified or replaced when we are sure this method is stable.

Excellent! I will add this to the next release of Fluppy to get some more testing.

Great idea. I hope Barry considers adding this functionality to woof.

I think the update layered filesystem part of the init script does some stuff with whiteout files. I guess in cases where there is a conflict a reboot would still be needed but most of the time, I think it'll be no problem. It may also work to clean the whiteouts on a mounted filesystem - but that would need to be tested.

As I like the sfs method, on my 128mb toshiba, I mainly use choicepup 4.1.2 cd with jrb's pre installed "open with sfs load/unload" and sfs 412 on usb.
Simultaneously I use your pupsaveconfig, pupsave=-0 (never) pupmode =13 .
When I tried yours, it said "failed to append "initrd/pup-ro4" to unionfs. "x-sfs moved to initrd/mnt/dev_save"
Maybe cause jrb's is already in there ?

EDIT:
Also tested on 4.1.2 and 4.3.1.
That is, tested and works: Puppy-4.1 through 5.0(wary) and 5.2(Lucid).
But seems not work on Puppy-4.0._________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Sun 30 Jan 2011, 07:46; edited 1 time in total

I am in the middle of testing other things, so cannot install this one yet, so have a few questions:

1. How does this differ from the otf-sfs-loader by goingnuts? Does it use the same method?
(Because the goingnuts otf-sfs-loader doesn't work in puppy 5)

2. Does this allow users to change the maximum number of loops available - so that users can choose how many SFSs are loaded on the fly?
(Very useful!)

3. Have you added ROX right click options for SFS files to load them?
I did it in Puplite, it is very convenient!

3. Do you check for incompatible SFS version, and load Trios SFS convertor, if it is installed?
(That would be great, I will do it in Puplite.)

4. Can I load a 200mb SFS file on the fly, using only a 128mb save file?
(Because when using the goingnuts otf-sfs script, the size of any SFS file loaded on the fly must not be larger than the free space in the save file, during initial unsquashing...)

1. How does this differ from the otf-sfs-loader by goingnuts? Does it use the same method?
(Because the goingnuts otf-sfs-loader doesn't work in puppy 5)

Basically same method i guess. The sfs_load is designed to keep the compatibility with traditional bootmanager.
Of course there are small tweaks matching with Various Puppy versions. The sfs_load is tested on Puppy version 4.1 through 5.0(wary) and 5.2(lucid).

sc0ttman wrote:

2. Does this allow users to change the maximum number of loops available - so that users can choose how many SFSs are loaded on the fly?
(Very useful!)

No. The sfs_loader keeps the compatibility with the traditional bootmanager and has same limit.
Barry thinks too many layers to the unionfs slows down the performance.

EDIT: sfs_load-0.9 and later supports sfs more than 6(experimental). I don't know the upper limit

sc0ttman wrote:

3. Have you added ROX right click options for SFS files to load them?
I did it in Puplite, it is very convenient!

Yes.

sc0ttman wrote:

3. Do you check for incompatible SFS version, and load Trios SFS convertor, if it is installed?
(That would be great, I will do it in Puplite.)

Yes checking, but does not have the button or launcher.
I think the sfs version converting is not so easy for beginners.
It consumes large space and requires Linux partition or work space.

sc0ttman wrote:

4. Can I load a 200mb SFS file on the fly, using only a 128mb save file?
(Because when using the goingnuts otf-sfs script, the size of any SFS file loaded on the fly must not be larger than the free space in the save file, during initial unsquashing...)

Yes, you can. Well... i wonder why the goingnuts otf-sfs cannot. Maybe for the auto converting the sfs version?_________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Wed 23 Feb 2011, 20:58; edited 1 time in total

2. Does this allow users to change the maximum number of loops available - so that users can choose how many SFSs are loaded on the fly?
(Very useful!)

No. The sfs_loader keeps the compatibility with the traditional bootmanager and has same limit.
Barry thinks too many layers to the unionfs slows down the performance.

I know what you're feeling about this. That being said, can I persuade you to implement a "non-persistent" SFS loading beyond the traditional 6 SFSes limit? Yes I know it may be slow - you can include a pop-up warning etc when a user tries do this - but it has its uses, especially for testing multiple SFS-es ==> however slow it is, it's still faster than a reboot, and some of us can live with the degraded performance. Especially since the newer kernels have dynamic loop devices (for older kernels, you can disable this functionality).

Worked nicely in Lucid 5.2 with an extra.sfs package that contained apps/files from remastered lucid_520.sfs. Apps installed/uninstalled without rebooting, and worked fine. After uninstalling, a few empty links remained, but it got everything else. Thanks shinobar...very useful utility.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum