Puppy Linux Discussion Forum

[sunburnt]

Hi dinky; With any luck MU will have the time to modify his great app.

Last night I simplified the identifing of image file types & their mounting.
Today I'll be testing that work, I'll try a few SFS file builds & check them.
If all looks good I'll repost "mksfs" here in the Software forum for testing.

[dinky]

Look forward to it matey, will be happy to test things. Cheers.
~dinky

[sunburnt]

After much work...
It seems the top mount directory being saved to the SFS file is a real mksquashfs problem.
I looked at the docs & there's no way to control it to keep from doing it...
Explanation:
If there's just one dir., then it's contense is put in the SFS file.
If there's several dirs., then the selected dirs. & their contenses are put in the SFS file.
Some times this is exactly what you want, like what I was doing, but sometimes it's not.

What this means for mounted iso, sfs. ext2, & ext3 files is the last mount point dir. is included.
Like this mount point for an SFS file: /mnt/sfs, so /sfs is stored in the SFS file as top dir.

Sadly... The only option left is to do one source (dir. or file), & then append the next, etc.
This way all the sources will have their contenses stored in the SFS file.
I didn't have any luck appending to a SFS file before but I'll try it again, maybe this'll work.

ADDENDUM:
Success at appending each dir & file to the SFS file, just the contenses were stored.
We need a way to control this, sometimes you want the dirs. stored & sometimes not.
All the mounted files definitely need their contenses stored, but dirs. need it both ways.
To get the top dir. stored, all I can think of is to do an empty dir. with the source one.
Several sources store the top dirs., & just reuse the same empty /0 dir. over & over.

Using an empty dummy dir. to force storing of the top dir. works, but...
Each time it's used a number is appended to it, like this: /0, /0_1, /0_2, etc.
The same thing happens to all dirs. stored several times, like: /bin, /bin_1, etc.
This seems acceptable to me to be able to control the building of SFS files.
Otherwise, copying files into a ext2-3 image file or partition is the only other way.
Again... If anyone else has any info or ideas to offer on this, speak up!

[sunburnt]

Got it working (I think), posting it in Software forum.
MU; I'll send the bits & pieces of code if you want, or you can DnLd & pick it apart.
Let me know what you want & what you think... Terry

[dinky]

Hi Sunburnt, can I get a link to your post? I can't find it. I don't understand much of what you wrote, but am eager to try it. I'm off to Sydney for the next week, and will hopefully get a chance to try it up there, if not will give you my feedback when I return. Cheers!
~dinky

[MU]

Sunburnts program mksfs is here:
http://murga-linux.com/puppy/viewtopic.php?t=29839
Mark

[Béèm]

Does the SFS-Combiner work in the SFS4 environment?

[gyro]

[seaside]

[Béèm]

I installed the SFS-Combiner with gtlbasic003 included on a dpup 482 and a upup 466 machine
In both I have an error which seems to be the same.

I issue first:

[MU]

Salut Bernard,
please use the pet mentioned here in the beginning, it contains the latest version of Gtkbasic and the include files:

http://www.murga-linux.com/puppy/viewtopic.php?t=32575

Mark

[Béèm]

Merci Marc,
Toujours rapide à répondre.
Always a quick answer.
Bernard

[Béèm]

Mark,
J'ai dû télécharger PuppyBasic2.6 également pour que SFS Combiner fonctionne.
I had to download PuppyBasic 2.6 also for SFS-Combiner to function.
Thank you,

Bernard

[HiDeHo]

Hi does this application work in lupu series and wary and quirky to combine sfs files.

they have included it in lighthouse pup. but lighthouse has be modified to run up to 40 so i dont see the need for sfs combiner there.

i am wanting as said for other pups.