Puppy Linux Discussion Forum

[sunburnt]

I also suggested a ram disk layer be added to the union to hold the SFSs config. files and links.
The basic setup:

[jrb]

Hi Guys,
Sorry to be so inattentive. I had no idea anything was happening on this thread. I depend on the forum to notify me and, it hasn't.

Let me just point out that I have posted a new SFS_Linker-431bk-1.0.pet in the additional software thread based on the work I started here. Its designed specifically to be an addon to Puppy431.

I've been using it for over a week and it is performing flawlessly, although a few SFS's have required tweaking to get them working.

I'm just heading out for the evening but tommorrow I'll try to come up to speed on the conversation going on here.

Thanks sunburnt for letting me know, J

[jrb]

Here's a summary of what SFS_Linker-431bk-1.0.pet does:

SFS_Linker has 4 basic parts:
1.)sfs_boot_handler
2.)sfs_linker
3.)sfs_unlinker
4.)sfs_remove.sh

1.)sfs_boot_handler:
sets up 19 new loops in Puppy431 so up to 24 SFS's can be mounted.
identifies and creates symlinks in /root/my_links/sfs_mnt_home to either SFS4 or SFS3 depending on the kernel
removes any SFS links left from last work session
loads any SFS's linked into /root/my_links/sfs_boot_links

2.)sfs_linker
checks to make sure SFS chosen is proper type
mounts the SFS to /mnt/$SFSNAME
checks to make sure it mounted properly by looking for /mnt/$SFSNAME/usr
renames seamonkeys /root/.mozilla if the SFS contains /root/.mozilla
creates a symlink from each file in /mnt/$SFSNAME to /$FILEPATH
copies any special need files from /mnt/$SFSNAME/choice to /$FILEPATH
creates a text file, /root/.packages/$SFSNAME.files
adds an entry to /root/.packages/user-installed-packages
adds lines to etc/ld.so.conf listing the standard, i.e. /mnt/$SFSNAME/usr/bin, lib_paths in the SFS then runs ldconfig (included in .pet) to add them to lib_path
creates a symlink to the SFS in /root/my_links/sfs_loaded
makes any new fonts available with mkfonddir

3.)sfs_unlinker
unmounts the SFS
checks to make sure it unmounted properly, quits and gives error message if not, SFS will be unlinked at next bootup in this case.
calls sfs_remove.sh to delete all symlinks to the SFS
removes the lib_path lines from /etc/ld.so.conf
removes empty folders from all except /root, /tmp, /var, /mnt
fixmenus and restart jwm

4.)sfs_remove.sh
uses code from puppy package manager to remove the symlinks listed in /root/.packages/$SFSNAME.files

[jrb]

I have uploaded SFS_Linker-431bk-1.1.pet

This one creates a new loop if needed. I have had up to 30 SFS's installed at once. It creates new loops when you want to simply mount an SFS as well. I have had up to 50 SFS's mounted at one time. Doesn't seem to be any limit although common sense says there must be. Does away with having to put

[technosaurus]

I think the kernel may be limited to 255 loops unless patched. Maybe this has changed though?

[jrb]

I have uploaded SFS_Linker-no_def-1.1.pet which does not have modified /usr/local/defaultprograms for people who wish to have SFS_Linking without changing the desktop icon or MIME-type behavior.