(old)Puppy Linux Discussion Forum

shinobar wrote:

darkcity wrote:see thread:-

http://www.murga-linux.com/puppy/viewto ... 949#586949

The permission setting breaks CUPS, is there a way SFS Load could detect and even work around this problem?

Tnx darkcity for the report. But maybe nothing the SFS_load can do for this.

It also helps to backup/restore your cups permissions. cups_filemanager.pet should work.

I haven't seen a Spanish translation for this app. Just in case, I made one

EDIT

Checked and had to correct a couple of mistakes, if you use the former file users will believe they're unloading an SFS when they're actually downloading one from the Internet. Please use this file instead.

ferro10n wrote:I haven't seen a Spanish translation for this app. Just in case, I made one

Tnx ferro10n. Will be contained in next release.

Calling for other language. Now only have spanish, russian and japanese.

Sorry, I had to correct a couple of lines in the Spanish locale See the corrected version two posts above.

This is the Portuguese translation:

Sfs_load-1.3 on-the-fly failed to load the devx and kernel source files for Classic Pup 214X-TOP9, after informing unionfs support is experimental.

PenguinPupLin wrote:Sfs_load-1.3 on-the-fly failed to load the devx and kernel source files for Classic Pup 214X-TOP9, after informing unionfs support is experimental.

Tnx for the report. Maybe it does not work on Puppy-4.0 and older.
(There are no report on Puppy 3.x.)

Here is a small patch for the afterwork to deal with the icon cache and to compile glib schemas. I haven't tested it yet.

shinobar, Would you say that 1.2 or 1.3 would be better for Lucid 5.2.8? One person (Tman) thought 1.2 might be better. Thanks.

playdayz wrote:shinobar, Would you say that 1.2 or 1.3 would be better for Lucid 5.2.8?

In any case 1.3 would be better, i suppose.
v1.3 has many fixes from v1.2, and i still have not found new bugs in v1.3.

Hi,

i can confirm this "strange behavior" of sfs_load-1.3 like Tman described. But i did not take it as a bug, because i do use my home workstation 100% in live mode (without pupsave) and have been warned before loading the sfs. By using no pupsave at all there is no trouble after reboot. It is a LazY Puppy build in feature.

So, though that strange behavior: to me it seems all fine, but would be better if it would unload the sfs at all times.

RSH

Test release: sfs_load-1.3.9.pet (2012-03-02)
Enhanced RAM mode, multisession live CD support and more. Feed back welcome as the reply of this topic.
Need to refine the translations. Download the po files for the contributors on translation.

(see the top post)

Quick review
Some changes made
Not perfect yet

Hi.

I did made some changes an did correct some writing errors. Mainly i did change the formal title of informing a user.

Example:

Is - Möchtest Du
Changed - Möchten Sie

Is - Du kannst
Changed - Sie können

Explanation:

In English the word "you" is used the same way as "Sie" is used in German.
It is a respectful title.

The German word "Du" is more privat and used under friends and in families.

"Du" could be translated like it is saying in the bible: "Thou"

Example:

You are a friendly Person.
Sie sind eine freundliche Person.

Thou shalt not kill.
Du sollst nicht töten.

---

I am sure: most German people would prefer to get respectful messages from their computers.

i did also change

- "im Flug" to "während der Arbeit" because we don't fly with our computers, we do work with them and while working (während der Arbeit) we do load sfs files.
- "font-cache" to "Schriftarten-Speicher"
- Script-Hintergrund" to "Hintergrund-Skript"
- "Queue" and "Schlange" to "Warteschleife"
- i am continuous using "SFS-Datei" and "SFS-Dateien"
- "Dein PC kann einfrieren, falls Du weitermachst." to "Die Bedienungsmöglichkeiten Ihres Computers können unterbrochen werden, falls Sie weitermachen."

and surely something i did forget.

Hello Shinobar,
Here is the french one.
Cordialement

Spanish and Portuguese updated

Tanks to all the contributors. The archive of the po_files updated.
http://shino.pos.to/linux/puppy/sfs_loa ... 307.tar.gz

I have updated Russian translation.

Hi Shinobar,
I am interested in this from a Live media standpoint. But, I need help from this threads community on whether this works same as PET additions to a system.

Everyone of us know that we can use PPM to add functionality to the system. This has worked for Live media users ever since I began with Puppy years ago.

In explantion (not that anyone need an explanation) you are running your Live media system. You need some functionality. You open the PPM and when all is said and done, that functionality has been added to your system. This works fine for, say, JRE for example. When I am ready to power-off, my running system asks wherher I want to save my work (the session) and proceeds to save the "state" of my machine for subsequent reboot.

But, for SFSs, I have seen no such method of saving the ssytem's state such that it will return to that desktop with all of the files and programs that exist prior to shutdown.

I saw your refereence to Live media being experimental. But, I don't think anyone should call a published facility experiment as it is useful and functional over the many years it has been available to all of us.

Question
If I use SFS_Load-on-th-fly, will the JRE that was installed before shutdown be saved in the system and be included in the PC's state at reboot? In other words, will JRE beome a permanent part of the system?

I just trying to get a level of understanding of what to expect with its use as, in this case, we would NOT be interested in loading and unloading and remembering and.... jus tto have the JRE included in our running desktop.

Thanks in advance.

gcmartin wrote:from a Live media standpoint. (snip)
If I use SFS_Load-on-th-fly, will the JRE that was installed before shutdown be saved in the system and be included in the PC's state at reboot?

I assume the Live media means CD or DVD. Three cases:

1. Saving the session as a file(pupsave) in the hard dirve or in a USB device.
   Yes. You need the SFS at the same place with the pupsave.
   If your Puppy has both the sfs_load and the pupsaveconfig (not the shutdownconfig of Barry's), you are better to determin the place of the pupsave before using the sfs_load. If you do the pupsaveconfig, the sfs_load offers to copy the sfs to the correct place.
2. Saving the session back to the Live media.
   Yes. The sfs_load offers where to copy the sfs to persist it after reboot. Please try and report. But i think this mode itself is still experimantal and do not recommend. You can use USB media instead for the modern PC's.
3. Remastering.
   Depends. Because the remastering need to treat the files under /etc and /root manually and it is hard.
   As for the JRE sfs, you need to copy the /etc staff of the sfs to the /tmp/etc when the remasterpup2 prompts.
   Or, you can burn the CD/DVD with the SFS in parallel with the Puppy stuf, vmlinz, inird.gz and main SFS. (Do not load the sfs before remastering.) The remasterpup2 also prompts. In this case the loading is not automatic but easy to load manually.

The last case above is complex and i am still investigating.

v1.4: extrasfsfind, upadate nls

The script extrasfsfind lists up sfs and pet on the live cd and in the folder(only in the sub folder if it is not the top layer) where the pupsave to be saved, and offers to load.
Works with the firstrun and the pupsaveconfig.
http://www.murga-linux.com/puppy/viewtopic.php?t=58312