(old)Puppy Linux Discussion Forum

Posted: **Mon 09 Apr 2012, 12:57**

jemimah wrote:
Code: Select all
losetup -d "$LOOPDEV"
was crashing it sometimes. I just commented that out and it seems to work ok. What does that do? Is it important?

Great. I have made tests on pemasu's Dpup Exprimo 3.2.11 and 3.2.14 kernel. The loop device, should be automatically free by unmounting, but frequently it fails. There is no way to free them once it fails. And the command 'losetup -d "$LOOPDEV" hangs...

Ok, i removed all the 'losetup -d' command from sfs_load-1.9.1. The loop devices stick on if the freeing fails, and we take another loop device, as the Mad Tea Party in Alice.

Try sfs_load-1.9.1. Hopefully more stable and usable.
# 9 Apr 2012 v1.9.1: clean up whiteout once for load, busybox umount and not do 'losetup -d'(jemimah), where to mount(pup_ro?), always register EXTRASFSLIST, no wide search for full path

Posted: **Mon 09 Apr 2012, 16:02**

RSH wrote:Tested the --list command. Works great. But i can not use --skip-fixmenus and --list together.

Is this the way it has to be or could this be changed?.

If i could use these two commands together, it would made me able to load the needed sfs's and while working with the wanted program (called by the run-script) all the dependencies of the dependent loaded sfs's would be loaded in background.

Then just calling one time fixmenus at the end of my run-script and everything would be fine. I think...

This would be user and programmer friendliness

Hello, shinobar.

It is not necessary, to implement possibility of using --skip-fixmenus and --list at the same sfs_load command. I did solve this using a little script, that does exactly what i want.

So again, thank you very much to implement the --skip-fixmenus command/parameter, for having an ear to my suggestions and also for doing this great job - which means mainly your sfs_load in general.

Posted: **Mon 09 Apr 2012, 16:45**

Hi Shinobar,
Clicking sfs_load-1.9.1 on the first post of this thread results in downloading of pet named sfs_load-1.9. Note absence of the suffix ".1".

mikesLr

Posted: **Tue 10 Apr 2012, 00:16**

mikeslr wrote:Clicking sfs_load-1.9.1 on the first post of this thread results in downloading of pet named sfs_load-1.9. Note absence of the suffix ".1".

Thanks. Fixed.

Posted: **Tue 10 Apr 2012, 01:26**

Why does it now say restarting X is necessary after an unload?

I'm mainly just curious.

Posted: **Tue 10 Apr 2012, 04:08**

jemimah wrote:Why does it now say restarting X is necessary after an unload?

The alert "You may need to restart X to reflect changes." is issued if the sfs loaded/unloaded has fonts or startup scripts.
The changes have done by the sfs_load afterwork, but may not be perfect.

The other case, that the sfs_load does not warn but can be a problem, is treating /etc/profile.d.
You need to reboot PC or do 'exit' on console to reflect the contents of /etc/profile.d.

Posted: **Wed 11 Apr 2012, 07:16**

Hi, shinobar.

sfs_load 1.9 did crash.

I used

Code: Select all

sfs_load LP2_Internet.sfs

to load sfs file. sfs file is stored in /mnt/sdd1 which means /mnt/home if i would use a pupsave. This never did happen on any other version of sfs_load. I do every day, several times, load sfs files on the fly.

I had to push the reset button (like power off).

Posted: **Wed 11 Apr 2012, 07:45**

RSH wrote:sfs_load 1.9 did crash.

Will you try sfs_load-1.9.1?
What is the kernel? 2.6.33.2?

EDIT: if it occurs only with the LP2_Internet.sfs specific, it may be caused by the contents like the libraries under /usr/lib.

Posted: **Wed 11 Apr 2012, 08:34**

shinobar wrote: Will you try sfs_load-1.9.1?
What is the kernel? 2.6.33.2?

EDIT: if it occurs only with the LP2_Internet.sfs specific, it may be caused by the contents like the libraries under /usr/lib.

Yes, the kernel is 2.6.33.2.

The LP2_Internet is several times a day used and loaded and never did happen something similar. I will try to use 1.9.1.
Thanks - just didn't see there is 1.9.1.

Posted: **Sat 14 Apr 2012, 06:07**

Small fix and change.
#13 Apr 2012 v1.9.2: fix was missing mountedpart, skip fixmenus for 'start', on RAM with remastered, saluki stuff

Posted: **Wed 02 May 2012, 04:18**

Test release: sfs_load-1.9.3.pet (2012-05-01)
NLS (seperated from 1.9.3): sfs_load_NLS-1.9.3.pet
[url]Download: http://shino.pos.to/linux/puppy/[/url]
Small improvement from 1.9.2:
#1 Mar 2012 v1.9.3: fix was clean up whiteout do not see pup_z, incleased RESERVHDD/RAM, version info, jwm -reload without flicker
Messages are refined by jemimah, in the English NLS

in the main PET.

Posted: **Mon 07 May 2012, 08:06**

Test release: sfs_load-1.9.4.pet (2012-05-07)
Download: http://shino.pos.to/linux/puppy/

#6 Mar 2012 v1.9.4: fix excess(>6) load was messing up with some version of busybox(lupu), fix was menu disappeared for excess sfs, fix was error but already mounted, avoid 'losetup -d' for some kernel
#6 Mar 2012 v1.9.4: fix 'restart X' warning, never use external download_file, 'Back to sfs_load' button, gtkdialog4

Note that this is a test release, but has many important fixes. All users and pupplet makers using version 1.9.x series are recommended to upgrade.

Posted: **Mon 21 May 2012, 00:59**

Typing "sfs_load --help" generates:-

usage: sfs_load [--unload] [--cli] [+/-][EXTRA_SFS_FILE]
Load or unload extra sfs files on-the-fly.

Two questions:-

1. What's the "--cli" option for?

2. Do "sfs_load --unload xxx.sfs" and "sfs_load -xxx.sfs" do the same thing? If not, what's the difference?

Many thanks.

Posted: **Mon 21 May 2012, 02:25**

puppypeter wrote:Typing "sfs_load --help" generates:-

usage: sfs_load [--unload] [--cli] [+/-][EXTRA_SFS_FILE]
Load or unload extra sfs files on-the-fly.

It depends on the version what option is accepted, but most recent sfs_load explains:

Code: Select all

# sfs_load --help
SFS-Load on-the-fly v.1.9.5
Load or unload extra sfs files on-the-fly.
usage: sfs_load [OPTION] [OPTION2 ...] [+|-][FILE_NAME] [+|-][FILE_NAME2] ...
      +FILE_NAME: load, same as FILE_NAME without '+'.
      -FILE_NAME: unload, same as --unload FILE_NAME.
  Options (short, or long):
    -u, --unload: unload the extra sfs files.
    -c, --cli: commandline interface, without dialog.
    -d, --debug: verbose output for debugging information.
    -h, --help: print this help and exit.
    -l, --list=FILE_LIST : read file names from the list file FILE_LIST.
    -q, --quiet: skip the 1st confirmation dialog.
    -v, --version: print version and exit.
    - (without file name): read file names from standard input. Imply '--cli'.
  Examples:
        ls -1 DIR_NAME | sfs_load -
        sfs_load - < FILE_LIST
        sfs_load --list=FILE_LIST
      Note that FILE_LIST contains each filename per a line.
  Other options(sfs_load internal use):
    -n, --no-afterwork: suspend fixmenus and etc. after (un)loading.
    -a, --afterwork (without file name): only do suspended afterwork.
    -s, --skip-fixmenus: skip fixmenus (but do startup scripts and etc.).
    start: auto load at boot (called from /etc/initd.d/sfs_load)
    stop: clean up at shutodpwn (called from /etc/initd.d/sfs_load)

Posted: **Mon 21 May 2012, 02:44**

Test release: sfs_load-1.9.5.pet (2012-05-21)
#19 May 2012 v1.9.5: fix was no move but always copy
#18 May 2012 for lupu-528JP: SUPPORTSIG=yellow

Download: http://shino.pos.to/linux/puppy/
NLS (seperated as for 1.9.3 and later): sfs_load_NLS-1.9.3.pet

Posted: **Thu 31 May 2012, 00:25**

Download: http://shino.pos.to/linux/puppy/
Test release: sfs_load-1.9.6.pet (2012-05-31)
NLS (seperated as for 1.9.3 and later): sfs_load_NLS-1.9.3.pet

#31 May 2012 v1.9.6: fix was everytime rc.update run when the number of additional sfs > 3, also when >6

Posted: **Sun 12 Aug 2012, 02:08**

shinobar wrote:Download: http://shino.pos.to/linux/puppy/
Test release: sfs_load-1.9.6.pet (2012-05-31)
NLS (seperated as for 1.9.3 and later): sfs_load_NLS-1.9.3.pet

#31 May 2012 v1.9.6: fix was everytime rc.update run when the number of additional sfs > 3, also when >6

Tried this out today on libreoffice-3.60.sfs on full install ext4 partition using lucid-528-005

Seemed to load ok - was able to bring up word processor, spreadsheet, etc.

Then I uninstalled. I have a question on the uninstall - Using Pfind I searched for libreoffice and found 401 files remaining after the uninstall.
They are files ending in .png, .svg, .desktop, etc - How do I get rid of these files?

Posted: **Mon 13 Aug 2012, 00:16**

majorfoo wrote:Tried this out today on libreoffice-3.60.sfs on full install ext4 partition using lucid-528-005

Seemed to load ok - was able to bring up word processor, spreadsheet, etc.

Then I uninstalled. I have a question on the uninstall - Using Pfind I searched for libreoffice and found 401 files remaining after the uninstall.
They are files ending in .png, .svg, .desktop, etc - How do I get rid of these files?

Have you ever installed the same or older version of libreoffice?
If so, you need to uninstall the previous install before loading new.
If you installed the older libreoffice manually, that is other than PET or SFS packages, you need to remove the files manually.

Posted: **Tue 28 Aug 2012, 16:25**

A bit less technical (mmhm, manual is good practice/exercise)

The words are mostly in a screenie @387k, not so much bigger than the jpg I did along with. Until I get racy (and my old personal sfs') squared away, any large stuff on disc will have to wait (a few mm sliver on the rim is all that's left and I'm really set on keeping it on cdrw disc if I can).

As more than a few have found, a running devx helps with damage control (the wm in the cap reverts to less than a joy if the devx isn't loaded). Maybe I'll check out what's after 1.4 stable (small I can do on the near horizon).

Good work, all

Posted: **Wed 28 Nov 2012, 11:12**

Hello all the SFS experts....

The way I like to manage sfs's on my system, given that I frugally install and test quite a few Puppy versions, is to put each Puppy version into it's own subdirectory but put all the sfs's into a common directory.

I then create a symlink in the Puppy subdirectory to the sfs I want to use in the common directory and then load it with sfs-load-on-the-fly.

This seems to work 100% for some sfs's but for some when I reboot I get the "Configuring filesystem - next boot will be quicker" message as though the boot system always thinks that the sfs has been newly loaded.

So I'm wondering why do different sfs's behave differently in this respect?? and is there anything I can do to make them all be permanent on reboot in this way of working?

Many thanks for any insights or help anybody can provide. It's not a showstopper as obviously I can copy the "misbehaving" sfs into the Puppy subdirectory rather than making a symlink.

Cheers
peebee

(old)Puppy Linux Discussion Forum

sfs_load-2.4 on-the-fly

sfs_load-1.9.1

Wrong link? Wrong name?

Re: Wrong link? Wrong name?

restarting X

crash

Re: crash

sfs_load-1.9.2

sfs_load-1.9.3

sfs_load-1.9.4is out

sfs_load command line usage

Re: sfs_load command line usage

UPDATE: sfs_load-1.9.5

sfs_load-1.9.6

Re: sfs_load-1.9.6

uninstall

Managing SFSs