(old)Puppy Linux Discussion Forum

There is Seamonkey-2.11-en-1.sfs:
http://www.murga-linux.com/puppy/viewtopic.php?t=78601

shinobar wrote:There is Seamonkey-2.11-en-1.sfs:
http://www.murga-linux.com/puppy/viewtopic.php?t=78601

This is not a criticism nor does it intend to be a distraction.

I am very clear on the auguments of Pros and the Cons of SFS versus PET in Puppy Linux packaging, installation, and use.

I, personally, do NOT have any position in either direction; simply, that it just works.

But, this is an appeal for understanding by those who develop subsystems and packages for Puppy.. Please acknowledge the existence of Puppy Package Management and provide a PET as well as an SFS whereever possible for all community members. Some members do not have sufficient skill levels to understand SFS use in PUppy distros,

Hope this helps

gerry wrote:Oscar- there must be a simpler way!

I downloaded.

I unpacked (in /tmp).

Where does the renaming come in?

And do I have to go through /usr/lib/seamonkey/ and check each file against the unpacked one, and replace the old by the new one if they are different?

What I have done is actually very simple. In fact the only renaming I did was as a precaution. I renamed (rather than deleting) the existing seamonkey directory in /usr/lib (which is the old version) to seemonkeyold in case there was any problem and I needed to restore back (which I didn't - it has worked OK on 2 machines running Slacko 5.3.3 so I have now deleted).

The downloaded tarball unpacks as a single directory named seamonkey (so does not need renaming). This can be done anywhere. After the rename just move the new directory into /usr/lib so it replaces the renamed one. No need to do anything with the files inside it.

I guess you could say all you need to do is download (to /mnt/home or /root), delete (seamonkey folder from /usr/lib), unpack (to /usr/lib).

You will find that features such as automatic and manual updates and the crash reporter are now included. Profile information such as bookmarks and settings are not lost because they are stored elsewhere.

Wow! that was easy enough. Thanks-

EDIT: I mean the OscarTalks method. I assume, if updater works now, it will be up-to-date for ever?

Gerry

gerry wrote:Nope, none of that worked.

Edit> Preferences> Advanced> BLANK

and Help has no check for updates option.

Hmmm..

The message appears on a red bar under the menu bar, and has a "check for updates" button, nothing happens there either.

Do we have Seamonkey in full, or are bits cut out to make it lighter?

(edit>preferences>advanced)
You need to click the little triangle to the left
of the word advanced.

gerry wrote:if updater works now, it will be up-to-date for ever?

I think that in most cases, with most recent Puppies, the update process for Seamonkey goes OK. There will now be a few extra tick-boxes that have appeared in your preferences menu including one for the crash reporter. You can enable automatic updates and I think that will work, although I believe it is better to disable that and just do a manual check and update from the help menu at a time of your choice when you are able to monitor the process.

Hi All, but especially for gcmartin:

Pet or SFS? Why either?

Some time ago playdaz wrote about the advantages of "program folders" and provided a tutorial. Then DaveS followed it up by creating pets called Foxyfox and Opera-from-mnt/home (I think). Essentially, to use a program folder all you do is download the latest tgz from Seamonkey, Opera, Firefox, whatever; unpack it in mnt/home and create a symlink of its executable in one of the directories in puppy's executable path. Drag & Drop the symlink onto the desktop and give it a nice icon. Or fancy things up by creating a .desktop file so it shows up in your menu. Voila! the latest Seamonkey, Firefox, Opera. Usable/Accessible in every Puppy. Create a pet of the symlink, icon and .desktop to avoid having to manually recreate them in another puppy.
Program folders work in almost every Puppy configuration: Frugally Installed to a hard-drive, a USB-Drive, included on a CD/DVD [but if the latter, a SaveFile must be used if you want to preserve changes]. I'm fairly certain they'll even work with Full Installs.
Of course, if you're a fanatic about minimalization just unpacking a tgz may leave you with some “unnecessary

grump wrote:I'm now happy to say that it is stable again. The defrag seems to have fixed matters. Now all that remains is to re-do the installs of the few things I like using.

I wrote earlier today: -

I'm sad to say that Slacko 5.3.3 has cacked itself on my old Toshiba A200 laptop after months of reliable service, and I can't revive it. I run it from a CD and save on the HDD. I've even tried starting from scratch - copied off the save file and deleted the slacko sfs, and it runs ok first time but fails to save the initial setting (eg hostname etc,) properly at shutdown. It saves something but on restart I have a screen full of caution triangles, the default background is missing and it wants to do the initial setup stuff again. Back to Lupo for the time being. I'll defrag the HDD on XP and try again later.

Also posted in the Puppy on laptops thread.

I learned from my mistakes that once I get a good setup going, I make weekly backups of my savefile in case it gets corrupted or I screw something up. I put it on a flash drive, and also another copy on the HD of the computer. All I have to do is delete the corrupted savefile and replace it with my backup. I'm up and running again.

Sylvander wrote:1. I've just downloaded...
slacko-5.3.3-highmem-PAE-SCSI.iso

2. If I burn the live CD and run it with access to the slackosave.3fs file for...
slacko-5.3.3.1-SCSI.iso
Will this cause a problem?
Or will it be able to update the slackosave file OK?

Well, this would really be downgrading the save file from Slacko 5.3.3.1 to 5.3.3
Only way to know is try it.
Not really sure what the update process, for save files, would do with that.
I do not think the PAE would be an issue and the difference between Slacko 5.3.3.1 and 5.3.3 is not much.
I think the best answer is nobody knows till you try it.
Make a backup copy of the save file, you know why.

Sylvander wrote:Tried to do THIS with the ISO file, but it couldn't be mounted [as per part 1].

I've done that OK with the ordinary ISO file [slacko-5.3.3.1-SCSI], and that worked OK, and is in use and doing the necessary.

Detailed many step process you are trying to do.
First idea is just did step in error.
From my experience with mounting iso files in file managers, it does not mount sometimes and seems to lock in a state where it will not. Nothing seems to work to fix.
I have done a complete reboot of Puppy and mounting an iso file now works.

bigpup wrote:First idea is just did step in error.
From my experience with mounting iso files in file managers, it does not mount sometimes and seems to lock in a state where it will not.

Previous to this problem event, every time I tried to complete the process there was no problem; it "just worked".
Or at least, the process could be completed, though sometimes the config change was ineffective.
So this failure to successfully mount the ISO seems most unusual to me.

sorry

Sylvander wrote:Tried to do THIS with the ISO file, but it couldn't be mounted [as per part 1].

I've done that OK with the ordinary ISO file [slacko-5.3.3.1-SCSI], and that worked OK, and is in use and doing the necessary.

Did you check the md5? I had no problems mount/unmounting the ISO in Rox, it's on a FAT32 filesystem if that matters.

Don't know about updating the savefile, but doesn't Slacko use a Slackosave.xxx where LuPu uses a lupusave? I don't have a frugal install to check on.

Slacko uses "slackosave-xxx.xxx savefile naming. I use Grub4dos to boot it from a ext2 partitioned full size SD card mounded in a USB convertor on my older Acer laptop with great success. You can even manually lock the SD card to "read only" if you want absolutely no saves made to your OS.

Will someone please give me the full paths for the ROX "rescan directory contents" and "change to home directory" icons.

I have used pfind with every *.png, *.rpm combo I can think might work and have viewed hundreds of icons but not these two exact icons. Thanks ... KJ

1.

kevin bowers wrote:Did you check the md5?

Yes, and it was OK.

2.

kevin bowers wrote:I had no problems mount/unmounting the ISO in Rox, it's on a FAT32 filesystem if that matters.

It won't mount using ROX either.
The ISO file is in a folder on an NTFS filesystem.

3.

kevin bowers wrote:Don't know about updating the savefile

I can choose to manually copy or save the changes made during the session [back to the pupsave file], either during the session or at shutdown/reboot, or not at all.

4.

kevin bowers wrote:doesn't Slacko use a Slackosave.xxx where LuPu uses a lupusave?

Correct.
In this case I'd be using a different version of Slacko to the original version of Slacko.
The personal save file is named slackosave.3fs, but can it be used for 2 [fundamentally?] different Slacko versions?

OscarTalks wrote:

gerry wrote:Oscar- there must be a simpler way!

I downloaded.

I unpacked (in /tmp).

Where does the renaming come in?

And do I have to go through /usr/lib/seamonkey/ and check each file against the unpacked one, and replace the old by the new one if they are different?

What I have done is actually very simple. In fact the only renaming I did was as a precaution. I renamed (rather than deleting) the existing seamonkey directory in /usr/lib (which is the old version) to seemonkeyold in case there was any problem and I needed to restore back (which I didn't - it has worked OK on 2 machines running Slacko 5.3.3 so I have now deleted).

The downloaded tarball unpacks as a single directory named seamonkey (so does not need renaming). This can be done anywhere. After the rename just move the new directory into /usr/lib so it replaces the renamed one. No need to do anything with the files inside it.

I guess you could say all you need to do is download (to /mnt/home or /root), delete (seamonkey folder from /usr/lib), unpack (to /usr/lib).

You will find that features such as automatic and manual updates and the crash reporter are now included. Profile information such as bookmarks and settings are not lost because they are stored elsewhere.

Downloaded from where?

Sylvander wrote: The ISO file is in a folder on an NTFS filesystem.

It's a long shot, but try copying the .iso to a FAT32 or ext(x) filesystem? Sometimes NTFS and Puppy (well, all Linux) don't get along.

kevin bowers wrote:try copying the .iso to a FAT32 or ext(x) filesystem? Sometimes NTFS and Puppy (well, all Linux) don't get along.

Here's the thing...
Every other time previous to this failure to mount the ISO...
When I was normally able to mount various ISO files with no problem...
ALL such ISO files are on this very same partition that uses an NTFS filesystem.
So it would seem that Puppy has had no problem with this NTFS filesystem.

Kevin- I Googled "Seamonkey", top hit was the Seamonkey site, clicked on "Download", .........

EDIT: Chose "save" rather than "Run". It downloaded the file into the /tmp directory.

Gerry