(old)Puppy Linux Discussion Forum

Have just uploaded SFS-TCZ_Linker-2.0

Fixed a bug from 1.9 and fine tuned sfs_boot_handler a little more for improved speed.

Cheers, J

jrb wrote:Have just uploaded SFS-TCZ_Linker-2.0

Another location/url ... the Merga machine tells me:

The selected Attachment does not exist anymore


Fixed a bug from 1.9 and fine tuned sfs_boot_handler a little more for improved speed.

Try it again Thom, I think I messed up the first upload. Hopefully fixed now.

Good Luck, J

jrb wrote:Try it again Thom, I think I messed up the first upload. Hopefully fixed now.

Got it...thanks

This seems obvious, but I thought I'd ask since I'm in a non-rebooted LiveCD system with Linker 1.9 installed...BUT, can I installed the PET for 2.0 and just continue running or am I required to reboot going from 1.9 to 2.0?

Thanks in advance...

I just uploaded SFS-TCZ_Linker-2.1.pet

I tuned up the .setup script caller a bit and also placed a restart window manager in the pinstall script. This will make sfs_linker immediately useable without worrying about rebooting.

You will still have to reboot to get /root/my_links/sfs_mnt_home populated with links to SFS's on /mnt/home but thats just a luxury.

I'm hoping this is the final version. Not that its not fun to work on, but its embarrassing to have to confess to soooo! many bugs.

gcmartin wrote:This seems obvious, but I thought I'd ask since I'm in a non-rebooted LiveCD system with Linker 1.9 installed...BUT, can I installed the PET for 2.0 and just continue running or am I required to reboot going from 1.9 to 2.0?

Thanks in advance...

Rebooting is not required to use SFS_Linker. It just activates some of the extra features, my_links folder on the desktop, symlinks in /root/my_links/sfs_mnt_home, etc. These are already present if you're updating.

Just remove the older .pet, install the newer and you're good to go.

Cheers, J

Thanks for the understanding when running LiveCD.
In PUP5.2 I:

1. remove the current "Linker"
2. Opened QuickPET on the desktop
3. On its menubar, click SFS, click sfs_linker which takes me to this Puppy thread.
4. Double click the "linker" url to start the installation and when done, I have the new Linker installed on my LiveCD system.

Edited 11/22/10 at 17.39. - The Linker remains in system after LiveCD reboot (Save to CD at shutdown, of course!)

Sent you a PM to you with correction for the Readme

gcmartin wrote:Sent you a PM to you with correction for the Readme

Thanks GC, Will use it in the next release.

I replaced a couple of the large binaries with statically linked uclibc versions / busybox scripts (recommended that you have a statically linked busybox) ... cuts the size by over 90%, but this is just for testers

• Is size an issue with this PET?
• how does this affect a system after the PET is started?
• Does this affect the download size or the size when it is run when linking SFSs?
• Does static links "lock" this in somehow?

I'm curious, ONLY?

jrb wrote:the /choice folder which you could place files in to copy them into the filesystem instead of linking them has been moved to /etc/choice. So if you're making SFS's and know that files need to be copied place them in their path structure in /etc/choice. (ie. /etc/choice/root/.config/your_app).

Hi Jrb,
Thank you for including /etc/choice.

Lighthouse Mariner ISO 5.00 G, released yesterday has SFS-TCZ_Linker-2.1-LHP.pet with an 'experimental in LHP' notification added to it. The Linker seems to work, I just don't think enough of us have used it in LHP yet, so I felt that was prudent. The new SFS files I built for G have /etc/choice.

Thanks again for developing and improving this useful tool!

Regards,
TazOC

gcmartin wrote:

• Is size an issue with this PET?

Anything that static links against glibc is going to have a size issue (in this case ldconfig and sln)

gcmartin wrote:

• Does this affect the download size or the size when it is run when linking SFSs?

Both

gcmartin wrote:

• how does this affect a system after the PET is started?

it _shouldn't_ (aside from using less resources => _may_ be faster)

gcmartin wrote:

• Does static links "lock" this in somehow?

the existing binaries are already static linked against static glibc (very bloaty) ... this is so that they can be used to fix borked up shared libraries

(btw I hacked my own minimal version of sln from embutils that is only a couple kb static linked with dietlibc, but the script to use busybox seemed a better option since it has support for more than just -s -f and -v ... I don't know for sure what options are needed)

technosaurus wrote:I replaced a couple of the large binaries with statically linked uclibc versions / busybox scripts (recommended that you have a statically linked busybox) ... cuts the size by over 90%, but this is just for testers

Very nicely done. I have downloaded your version and will start testing.

Hoping for a successful test, J

I didn't realise SFS-Linker had gone into this thread so have missed out on the latest updates!

This is just a plant to ensure future changes appear in 'My Posts' list.

I LOVE this tool. Now in the Lighthouse Pup.

Keep up the solid work jrb!

technosaurus wrote:I replaced a couple of the large binaries with statically linked uclibc versions / busybox scripts (recommended that you have a statically linked busybox) ... cuts the size by over 90%, but this is just for testers

I've used technosaurus shrunken version of 2.1 for a week now in Quirky130, Wary102, Lupu511 and Puppy431. It has worked flawlessly. The only improvements I have for 2.1 are some grammar corrections in the readme file suggested by gcmartin. If no one reports any problems in the next few days I will incorporate technosaurus' and gcmartin's improvements into version 2.2.

Cheers, J

I have just uploaded version 2.2 to page 1 of this thread

Technosaurus has worked his compiling magic on the included binaries and shrunk them to 10% of what they were, WOW Thanks technosaurus!

GCmartin has corrected my literary shortcomings to make a more understandable Readme. Thanks gcmartin!

Barring unforseen eventualities I think this is it, the final version. Have been testing for a couple of weeks and its performed perfectly so far. (Hope I don't regret saying that)

Cheers, J

@jrb
Silly question but, how many sfs's can I load using your linker?

Now that 5.2 is completed and stable (except for bugfixes) I'm finally starting my puppy project. Having just found your package, I'd like to use it as it would give me more flexability than having to use Bootmanager.

As a wish, i'd like to have between 17 and 24 sfs's if I use your package as it will allow much smaller component groups to be dealt with.

Maybe you could even think of adding a pet linker to your package, now that would turn you mainstream

regards
scsijon
edit: ammended down to one per menu group after some redesigning and rethought, may eventually be down to 16 total. Do note technosaurus's answer to the third item, shame would have been a good addition.

a pet linker wouldn't work, because even though they are basically tar.gz - they have an md5 tacked on at the end that would cause errors with avfs, and gvfs and other tools that can mount them - you'd have to convert to tgz with pet2tgz for pets to be usable this way