(old)Puppy Linux Discussion Forum

tcl is up to 3.X now so the 2.X repo may start to go stale.

ftp://distro.ibiblio.org/pub/linux/dist ... ux/3.x/tcz

Jrb,

Nice work on getting the Dev sfs to work.

I've been using this script on a rox right-click menu just to properly link the Dev files. My script looks for just broken links and copies those over. Since I usually only run the Dev sfs in ram, I never needed to unlink anything

As many of the SFS files, not specifically made for Puppy, need some additional help for configuration persistence or other customization, here is something else you might find interesting.

The following code is in the linker script If an SFS file needs some additional commands, I make up a script called "nameofsfs.sfsSETUP" with whatever commands necessary.

Now when the sfs linker is run, any code that's in my "nameofsfs.sfsSETUP" script, is run specifically for that sfs file

I use this system for Thunderbird and several other sfs files and usually avoid any repetitive work or having to edit SFS files this way.

Regards,
s

technosaurus wrote:tcl is up to 3.X now so the 2.X repo may start to go stale. ftp://distro.ibiblio.org/pub/linux/dist ... ux/3.x/tcz

Thanks technosaurus, I'll update that in sfs_linker-1.9

seaside wrote: As many of the SFS files, not specifically made for Puppy, need some additional help for configuration persistence or other customization, here is something else you might find interesting.

The following code is in the linker script

Code: Select all

if [ -f "/mnt/"$SFSNAME"SETUP" ]; then
	/mnt/"$SFSNAME"SETUP
	fi

If an SFS file needs some additional commands, I make up a script called "nameofsfs.sfsSETUP" with whatever commands necessary.

Now when the sfs linker is run, any code that's in my "nameofsfs.sfsSETUP" script, is run specifically for that sfs file

I use this system for Thunderbird and several other sfs files and usually avoid any repetitive work or having to edit SFS files this way.

Regards,
s

Nice idea seaside. These SETUP scripts could be in the SFS and run once the SFS is mounted. More elegant than my setting up a special directory in the SFS to copy from. Just change /mnt/"$SFSNAME"SETUP to /mnt/"$SFSNAME"/"$SFSNAME"SETUP. Will definitely keep this in mind for sfs_linker-1.9.

Will compare your script for dealing with symlinks with mine when I get a few spare minutes. Busy times right now.

Thanks, J

jrb wrote:
Nice idea seaside. These SETUP scripts could be in the SFS and run once the SFS is mounted. More elegant than my setting up a special directory in the SFS to copy from. Just change /mnt/"$SFSNAME"SETUP to /mnt/"$SFSNAME"/"$SFSNAME"SETUP. Will definitely keep this in mind for sfs_linker-1.9.

Will compare your script for dealing with symlinks with mine when I get a few spare minutes. Busy times right now.

Thanks, J

Jrb,

Thanks, and I should elaborate to say that the "sfsname.sfsSETUP" files are not in the SFS file itself, but in the same directory as the SFS file. The linker code looks for the *SETUP file (if any) and executes any commands.

Your symlink script looks for any symlinks, while mine looks for broken ones (the ones pointing back to the main puppy files).

Cheers,
s

Just a couple of thoughts after testing SFS-TCZ_Linker-1.8

Great idea and well-thought out! I especially appreciate the efforts to test on Lighthouse and other Puplets.

Would you consider moving the /choice directory (for files that need copying rather than linking) to /etc/choice? I think it is best to avoid adding directories to the top level /. Or at least add /etc/choice to the code that checks /choice.

Maybe /root and /home should be copied instead of linked--many apps need their config files writable.

Thanks,
TazOC

@jrb
I want to share this with you as you may not have this info AND, I want to ask a question about use of the Linker.
Share:

tazoc wrote:

gcmartin wrote:I saw your post on SFS processing.

Does this have ANY impact on SFS processing on LiveCD if a /mnt/home folder is copied to the root of the LiveCD?

Thanks in advance
P.S. Great idea on "update announcement" PET.

Thanks, gcmartin. As I understand it, Puppy BootManager cannot layer extra SFS files into the / file system from first boot PUPMODE=5. Layering is done during the second reboot, after a pupsave is created and BootManager has run.

I tried SFS-TCZ_Linker and had mixed results. I think maybe /root and /home should be copied instead of linked--many apps need their config files writable. To get some of the Lighthouse SFS files to work with it I had to manually remove the links in /root and copy the files over instead.
-TazOC

Question:
Does the following mean that a reboot is REQUIRED after installing you PET V1.8? "I run a LiveCD environment and have run into problems when trying to your PET in the past."

jrb wrote:

tlchost wrote:Does this remove the requirement for ldconfig430 and my_links?

Yes, they are both built in to this SFS_Linker. Click once on the .pet, reboot and you're ready to start using SFS's.

tazoc wrote:Would you consider moving the /choice directory (for files that need copying rather than linking) to /etc/choice? I think it is best to avoid adding directories to the top level /. Or at least add /etc/choice to the code that checks /choice.

Maybe /root and /home should be copied instead of linked--many apps need their config files writable.

Thanks,
TazOC

Hi TazOC, Sorry for the lateness of reply, was contemplating an answer and got distracted.

The /choice directory that I have included in some of my SFS's and built into the Linker gets deleted out of the top level after serving its purpose when SFS's are initially linked. You are absolutely right that some apps need there config files copied. Thats what the /choice folder is for. For instance:

When I made my OO3.1 SFS I wanted scripts to start the applications copied, i.e. /usr/local/bin/writer. So in my SFS I made /choice/usr/local/bin/writer. When the SFS gets linked the writer script is copied to /usr/local/bin. Any links from the choice folder in the SFS are deleted at the end of the Linker install.

This may not be the ideal way to do it. I kind of like seaside's idea of an accompanying install script. It is a more versatile approach acting like the pinstall script in a .pet.

I continue to contemplate (among other things) and at some point may come to a decision.

Cheers, J

gcmartin wrote: Does this have ANY impact on SFS processing on LiveCD if a /mnt/home folder is copied to the root of the LiveCD?

In the latest version of SFS-Linker I set it up to check if PUPMODE=77, live CD/DVD. If so it creates a new folder, /root/SFS and then links this as /mnt/home. SFS's placed in this folder will be detected by both SFS-Linker and Bootmanager and will be useable (I think I tested this in Bootmanager?, definitely tested and worked in SFS-Linker).

I tried making this folder at the top level, /, but it didn't work so I put it one level down in /root and it worked.

Does the following mean that a reboot is REQUIRED after installing you PET V1.8?

Actually no. SFS-Linker will work perfectly fine without a reboot or anything else. Just install the .pet and you're good to go. The reboot does two things: It places the my_links folder on the desktop (restarting the X server will do this too) and it checks /mnt/home for appropriate SFS's and links them to /root/my_links/sfs_mnt_home/ where they are available to right click and install.

Hope that helps, J

Edit: I should also mention for running from Live CD/DVD to create /root/SFS and use SFS's saved on your CD/DVD you must reboot and save after installing SFS-Linker.

jrb wrote:The /choice directory that I have included in some of my SFS's and built into the Linker gets deleted out of the top level after serving its purpose when SFS's are initially linked. You are absolutely right that some apps need there config files copied. Thats what the /choice folder is for.

Hi Jrb,
Thanks for replying J, I'm glad to hear from you! I received a request to include SFS-TCZ_Linker in Lighthouse Pup, primarily for Live-CD usage, and apart from the layering order concerns I have with Lighthouse SFS files, (the order that SFS files are linked could be critical as some SFS may have different versions of the same files, and I solved that with a naming convention--files that begin with a numeral are layered above), I'm struggling with how to build future SFS that can be used either with SFS-TCZ_Linker, or the traditional BootManager Puppy--layered SFS after reboot method.

I understand that /choice is deleted by the Linker, but when the SFS is used in the traditional way, without the Linker, /choice would probably not be deleted. That's why I'd prefer /etc/choice.

Thanks again,
TazOC

tazoc wrote:I understand that /choice is deleted by the Linker, but when the SFS is used in the traditional way, without the Linker, /choice would probably not be deleted. That's why I'd prefer /etc/choice.

Doh!!! Of course, I should have thought of that. Will make the change in SFS-TCZ_Linker-1.9.pet (coming soon). I want to give people the option of using Seaside's technique as well and also update the TCZ link that technosaurus mentioned.

Getting to work now, J

Hi jrb!

Just to inform you that I am really fascinated with what you have done with this wonderful pet. It is really useful indeed. I Hope that this linker will also be included in the Lucid Puppy development. (just an additional of 424k will make me happy )

Tried your program many times and it is operational.

Congrats! I can't wait to test your updated version of SFS-TCZ Linker.

God Bless to all devs and testers and to Sir BK too.

Have just uploaded SFS-TCZ_Linker-1.9.pet. See the write up on page one.

Incorporated suggestions by technosaurus, seaview and tazoc. Thanks guys!

Cheers, J

Jrb,

I downloaded a couple of TCZ's from the depository, made some .setup files and all linked and ran "smooth as silk".

The "dev" file linked perfectly and all testing was on Pup 431.

No testing of the unlinking part, because I don't use pup save files now.

At this point, it's hard to imagine any further improvements, and thank you for all your good work.

Regards,
s

@jrb Check your PM
Does the LInker work without rebooting if running on a LiveCD? I run LiveCDsfron the following 4 environments:

1. LightHouse - (Yes/No)
2. Lucid 5.1.1 - (Yes/No)
3. Lucid 5.2 - (Yes/No)
4. QuickSET - (Yes/No)

Thanks in advance. Great work

Edited 10/02/10: You have already answered this days ago. Sorry as I missed that response.

Your answer is "LIveCD works" without reboot. Thanks again for all of your good work.

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...