Puppy Linux Discussion Forum

mikeslr wrote: ↑Wed Sep 02, 2020 12:12 am Hi All,

I also like Seamonkey. Just prefer running web-browsers as portables from /mnt/home where they don't occupy my SaveFile and don't locate profiles and especially tons of cache in /root which takes up RAM. fredx181 figured out how and has automated it for firefox. But, I'm not that clever. So I 'flinched' a couple of files, those in the 'extralibs' folder from fredx181's firefox64, the smky 'wrapper' from Mike Walsh's 32-bit Seamonkey porables, and threw in a seamonkey.png I gimped.

Your download from the Seamonkey Website will arrive as a tar.bz2 package. Extract it and within will be a folder just named 'seamonkey'. Move that wherever you want, such as to /mnt/home.

Download the attached portablize.tar.gz and extract it. Move its contents into your seamonkey folder. Start Seamonkey by left-clicking the smky script. Although it generates some files in /root it creates a profile folder (bookmarks, addons, settings) within its own folder and will also place subsequent cached files in that folder. Deleting the hidden files in /root/mozilla and /root/.cache does no harm.

You can use the enclosed icon to 'fancify' your seamonkey folder. Open two flle-browers, one to the folder itself and one so that you can see the icon. Right-Click the folder and select "Set icon". Check the "Only for this file" button. Drag and drop the icon into the window. The effect is operating system specific. portablize.tar.gz

You can use the pet from this post to create a menu entry, viewtopic.php?p=2206#p2206. Remember to edit it to provide the exact path to the smky wrapper.

Hello Mike

If I were to try this trick is there any way I could use the profile, particularly the mail boxes, from a Seamonkey installation from another PC? Would copying it over the one created by the first run of Seamonkey via your script work?

Thaks
Will

@mikeslr/all :-

mikeslr wrote: ↑Wed Sep 02, 2020 12:12 am

You can use the enclosed icon to 'fancify' your seamonkey folder. Open two flle-browers, one to the folder itself and one so that you can see the icon. Right-Click the folder and select "Set icon". Check the "Only for this file" button. Drag and drop the icon into the window. The effect is operating system specific.

Mike:-

You can do this another way, too. Taking the cue from the /root/spot directory - this always shows an icon of 'Spot' the dog - you can make your directory icon permanent, i.e., it'll 'stick' regardless of where you move it to.....and it's NOT OS-specific.

Rather than the 'Rt-clk->Set icon as' route, place your icon inside the directory you want to 'iconify'. Now, re-name it to

.DirIcon

The '.' denotes it as a 'hidden' item, of course. Make sure you also delete the extension (.jpg, .png, whatever). Then, 'refresh' the folder.....or just go back out a level. Now your directory has a permanent icon..!

I believe ROX has had this ability for a very long time, although certain releases of JWM do NOT 'play nice' with it. If you find it doesn't show in one Puppy (but shows in all your others), don't mess around with it.....it's almost certainly JWM playing 'silly buggers'.

Hope that helps.

Mike.

If I were to try this trick is there any way I could use the profile, particularly the mail boxes, from a Seamonkey installation from another PC? Would copying it over the one created by the first run of Seamonkey via your script work?

I keep my portable outside the savefile, and have had success by copying contents of /root/.mozilla/seamonkey/abcdefg.profile from the old install to /seamonkey/profile of the new install.

you might be money ahead to make your new seamonkey from the same version as your old seamonkey

I love seamonkey and use it quite often.Just as fast and responsive as any other browser i have installed.

Hello

@FeodorF @mikeslr @mikewalsh

I started a thread viewtopic.php?f=4&t=1545&p=11566#p11566
I am switching over to this thread as I think you have some of the answers I am seeking.

My machine:
Computer Vendor: LENOVO
Product Name: 10117
Version: Lenovo H535
Serial Number: ES13191202
no HDD

My distro:
Distro: bionicpup64 8.0
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm
frugal install on 3.1 flash drive

My goal is to eliminate Palemoon browser from the distro altogether and replace with Seamonkey.

I see FeodorF and mikeslr have found a way to 'portablize' Seamonkey. But doesn't that leave Palemoon still as the built-in browser?

How do I get rid of Palemoon as the built-in browser in Bionicpup(64) 8.0 and replace with Seamonkey?

Please suggest GUI tools if possible.

Thank you in advance,

Sky

Hello

I just wanted to follow up my post further up and williwaw's reply about using an existing Seamonkey profile in a new portable folder. I have now had chance to try this and it works fine. I copied the profile from Seamonkey 2.49.x on one PC into the portable Seamonkey 2.5 folder on another, making it a sub-folder called "profile", and this new Seamonkey starts up with all the old mail server settings etc - success with that one.

Sky
I don't know about actually removing Palemoon from a Puppy distro but I have managed to change what loads from the desktop "browse" and "mail" icons and is used for the help pages etc.
In

 /usr/local/bin 

there are two scripts, defaultemail" and "defaultbrowser", here's mine for e-mail

#!/bin/sh
exec thunderbird "$@"

I realized that editing these to name whichever programme that you want to use after "exec" means that this is the one used whenever "defaultemail" or defaultbrowser" is called. to use Seamonkey name the "smky" launcher from the Seamonkey portable.

Hope this might be some help
Will

Sky Aisling wrote: ↑Sun Dec 13, 2020 10:02 pm

...
My goal is to eliminate Palemoon browser from the distro altogether and replace with Seamonkey.

I see FeodorF and mikeslr have found a way to 'portablize' Seamonkey. But doesn't that leave Palemoon still as the built-in browser?

How do I get rid of Palemoon as the built-in browser in Bionicpup(64) 8.0 and replace with Seamonkey?

That's 2 questions. The second is easy. Barkingmad posted one way to change the default web-browser. Bionicpup64 has a GUI for doing that which should work: Menu>Setup>Default Application Chooser, Click All, click the selector next to the "Web Browser" field. Seamonkey may be a choice offered if you installed the menu pet. If not, you can type it in. If you didn't install the pet you can still type it in but you'll have to supply the entire path, e.g. /mnt/home/Seamonkey/seamonkey.

Getting rid of palemoon is a horse of a different color. It exist in the puppy_bionicpup64_8.0.sfs from which it is copied into RAM each time you boot up. You can use Menu>Setup>Remove Builtin Packages to 'white-out' in RAM the link to its copy in RAM, but its will still be on the SFS. To get rid of it you have to Remaster. Frankly, having done several remasters, they are not worth the effort unless you're making a great many significant changes with the intention of publishing your remaster.

Hi All,
@mikeslr
@Barkingmad
Thank you mikeslr, you helped me change my mind about eliminating Palemoon altogether.
Yes, I know how to change the default applications. Thanks Barkingmad.
I've decided to try a different route.
I'm going to explore BarryK's new effort of 'EasyOS'.
I have a hunch Barry is developing another sweet distro much like the early simple Puppys but with contemporary adjustments.

Sky

Hello.
I am using SeaMonkey 2.53.5.1 with 'Dpup Stretch' .
I can play video,but no audio.
Does someone else has the same problem or i am doing something wrong ?
Palemoon works well.
Thanks in advance .

Seamonkey under most Puppies needs apulse libraries to produce sound. IIRC, you can edit /usr/share/seamonkey-xxx.desktop's Exec= argument so that apulse is started along with seamonkey:

Exec=apulse seamonkey

Alternative: Add apulse to the actual bash-script which starts seamonkey. See the thread on which this http://www.murga-linux.com/puppy/viewto ... 21#1041321 was posted, substituting 'seamonkey' where 'firefox' appears.

Thank you.
May be is just my imagination, but
on my old lappi SM looks a little bit snappier
than palemoon so i think to replace it.
Thanks again for your help.

Not sure if this is really relevant to what's been discussed with regard to profiles and taking up space in the savefile, but I moved /root/.mozilla (the profile folder) to /mnt/home years ago. I then put a link to it back in /root.

There it's accessible not only to Seamonkey in my normal day-to-day install but to Seamonkey browsers in alternative frugal installs with a simple link in /root. And of course it doesn't take up savefile space and doesn't create additional duplicate profiles in other pups.

I actually do the same with /root/.wine but that's definitely OT for this discussion.

@vtpup

vtpup writes:

Not sure if this is really relevant to what's been discussed with regard to profiles and taking up space in the savefile, but I moved /root/.mozilla (the profile folder) to /mnt/home years ago. I then put a link to it back in /root.

There it's accessible not only to Seamonkey in my normal day-to-day install but to Seamonkey browsers in alternative frugal installs with a simple link in /root. And of course it doesn't take up savefile space and doesn't create additional duplicate profiles in other pups.

Will this work for Firefox.esr also?

Sky

Sky, it works with the Firefox I have, but I don't know what "esr" is.

Anyway, just try an experiment. With your browser closed, make a copy of .mozilla in /mnt/home. Then rename the one in /root to .mozilla.bak, so you can restore it (if needed) by renaming without the ".bak"

Now drag the one in /mnt/home back into /root, except not as a copy but as a link. Done.

Try opening Firefox. It it's normal, you're set.
If you install other puppies to dual boot, you can drag .mozilla links there, too, and all will use the same settings, bookmarks, etc.

You can delete the .mozilla.bak in /root to regain space in your savefile -- or keep it as a backup. You could also move it to /mnt/home, since the name doesn't conflict with .mozilla there.

@vtpup
Thank you, I'll give a try this weekend.

Overview of Firefox.esr

Firefox offers an Extended Support Release (ESR) for organizations, including schools, universities, businesses and others who need extended support for mass deployments. Firefox ESR can be downloaded here. The ESR release is based on the regular release cycle of Firefox for desktop.

I am just a single user but Firefox.esr has a plugin feature called 'widevine' that makes viewing video content without issues.
https://www.mozilla.org/en-US/firefox/7 ... easenotes/
https://www.mozilla.org/en-US/firefox/a ... esktop-esr

I am quite fond of seamonkey and use it on my 32bit xenialpup..i am having a slight problem.There was an update released today and i have downloaded the tar.bz2 file but i am clueless as to how to update seamonkey.i run seamonkey by simply clicking the seamonkey icon in the folder.

Does anyone know how i can update please.?

I just updated my SeaMonkey on Precise Light from 2.53.5.1 to 2.53.6 this evening.

I keep my SeaMonkey in /mnt/home/seamonkey, so after downloading the new 2.53.6 tar.bz2 file, I placed it in /mnt/home, clicked on it, and extracted all the contents (left-click, wait for the GUI to populate the list of files, do a SELECT ALL and then EXTRACT).

The tarball has all its files in a "seamonkey" folder, so the extracted files will overwrite the old files in /mnt/home/seamonkey with the new versions.

BTW I'm happy to say that if you are using mikeslr's "portabilizing" tools, as I am, the extraction does not disturb any of mike's "magic" stuff, so you don't have to re-apply the "portabilizing" procedure.

PS: Because I have great respect for Murphy's Law, before I did the update, I moved my /mnt/home/seamonkey/profile folder to a safe place. Then I moved it back after the update was done. All my customizations survived the update with no problems.

6502coder wrote: ↑Sat Jan 23, 2021 5:11 am

I just updated my SeaMonkey on Precise Light from 2.53.5.1 to 2.53.6 this evening.

I keep my SeaMonkey in /mnt/home/seamonkey, so after downloading the new 2.53.6 tar.bz2 file, I placed it in /mnt/home, clicked on it, and extracted all the contents (left-click, wait for the GUI to populate the list of files, do a SELECT ALL and then EXTRACT).

The tarball has all its files in a "seamonkey" folder, so the extracted files will overwrite the old files in /mnt/home/seamonkey with the new versions.

BTW I'm happy to say that if you are using mikeslr's "portabilizing" tools, as I am, the extraction does not disturb any of mike's "magic" stuff, so you don't have to re-apply the "portabilizing" procedure. They're not my tools. They're fredx181's; I stole them from MIke Walsh.

PS: Because I have great respect for Murphy's Law, before I did the update, I moved my /mnt/home/seamonkey/profile folder to a safe place. Then I moved it back after the update was done. All my customizations survived the update with no problems.

I also have great respect for Murphy's Law. Although I've never had the problem with Seamonkey, there have been posts about updates of palemoon and firefox not working. Since I'm building a portable, what I usually do is unpack the tar.gz somewhere (usually /mnt/home/downloads) copy the profile and other 'added' folders into it, and test it. Only when satisfied that it's an improvement over the 'old' version --and not a disaster-- do I delete my old version and move the new version into the place where Puppy expects to find it; i.e. symbolic links and a menu entry to /mnt/home/Pup-Apps.

Thank you for the wonderful replies.I have moved my seamonkey folder to mnt/home.I have extracted to this same location.I removed my previous seamonkey files altogether and extracted the new version into mnt/home.

I am assuming i can run seamonkey from this location..also what are the benefits of running extracted files in this location.?
Sorry for the dumb questions as i am still a newbie in regard to puppy.

See the second post in this thread, where mikeslr explains the advantage of installing to /mnt/home

Hi xenial,

As 6502coder mentioned I posted the main reason for preferring portables: it keeps web-cache out of RAM. AFAIK the original publishers of All Web-browsers design them to write cache to your --the user's-- home folder. Under almost operating systems /home is a folder on your hard or USB-drive. But under Puppies, a User's 'home' folder is /root; and Puppies 'run in RAM' creating /root in RAM by copying it anew from your system files on storage on boot-up. RAM is also where during a session all changes are written. The more information held in RAM, the longer it takes to effect any change --slowing operations at best, resulting in a crash at worst. In order for the contents a website to display on your monitor, those contents have to be in RAM. And in order for that Website not to have to transmit it again, it stores files on your computer; even if you have no reason to ever view it again. Visit graphic rich websites and the files being cached can quickly add up to hundreds of megabytes.
With cache in RAM and Automatic Save not removed, on the next boot-up you will have immediately populated your RAM with all the cache previously accumulated. That lead to the question of what to do about it. Before fred and Mike developed and popularized portables, a couple of techniques were developed which I summarized here, viewtopic.php?p=2235#p2235.

portablizing removed the need to physically move the cache folder and symlink it back.

But it has another advantage. Although I'm not as committed as Mike Walsh is to linking external applications to all/most of my Puppies so that all/most will share one applications and the profile/settings made to it --i.e., I don't have to customize setting for each Puppy-- I do run multiple puppies. Currently, my 'go-to' Puppy is Bionicpup64 into which I gradually transitioned from Xenialpup64. When the time comes I'll be able to transition to fossapup64: all my portable web-browsers are already linked into both of them as well as Xenailpup64 and even tahrpup64.

The operative word being 'gradually'. Every Puppy has it strengths and weaknesses and it own 'feel'. Xenialpup64 remains a fine system: I had almost forgotten how fine until I ran it in a container under EasyOS. Bionicpup64 didn't become my go-to Puppy until I felt just as 'at-home' under it as under Xenialpup64; and convinced that there wasn't anything I wanted to accomplish which could not be accomplished under Bionicpup64 as easily as under Xenialpup64.

mikeslr wrote: ↑Sun Jan 24, 2021 1:07 am

Hi xenial,

As 6502coder mentioned I posted the main reason for preferring portables: it keeps web-cache out of RAM. AFAIK the original publishers of All Web-browsers design them to write cache to your --the user's-- home folder. Under almost operating systems /home is a folder on your hard or USB-drive. But under Puppies, a User's 'home' folder is /root; and Puppies 'run in RAM' creating /root in RAM by copying it anew from your system files on storage on boot-up. RAM is also where during a session all changes are written. The more information held in RAM, the longer it takes to effect any change --slowing operations at best, resulting in a crash at worst. In order for the contents a website to display on your monitor, those contents have to be in RAM. And in order for that Website not to have to transmit it again, it stores files on your computer; even if you have no reason to ever view it again. Visit graphic rich websites and the files being cached can quickly add up to hundreds of megabytes.
With cache in RAM and Automatic Save not removed, on the next boot-up you will have immediately populated your RAM with all the cache previously accumulated. That lead to the question of what to do about it. Before fred and Mike developed and popularized portables, a couple of techniques were developed which I summarized here, viewtopic.php?p=2235#p2235.

portablizing removed the need to physically move the cache folder and symlink it back.

But it has another advantage. Although I'm not as committed as Mike Walsh is to linking external applications to all/most of my Puppies so that all/most will share one applications and the profile/settings made to it --i.e., I don't have to customize setting for each Puppy-- I do run multiple puppies. Currently, my 'go-to' Puppy is Bionicpup64 into which I gradually transitioned from Xenialpup64. When the time comes I'll be able to transition to fossapup64: all my portable web-browsers are already linked into both of them as well as Xenailpup64 and even tahrpup64.

The operative word being 'gradually'. Every Puppy has it strengths and weaknesses and it own 'feel'. Xenialpup64 remains a fine system: I had almost forgotten how fine until I ran it in a container under EasyOS. Bionicpup64 didn't become my go-to Puppy until I felt just as 'at-home' under it as under Xenialpup64; and convinced that there wasn't anything I wanted to accomplish which could not be accomplished under Bionicpup64 as easily as under Xenialpup64.

But you don't have to customize each puppy with new settings if you use the same browser with the move to/symlinking back method. The fact is you only do the moving part once. Your cache/settings will now be stored on your partition. All you need to do with all your other puppys to link it to the same browser cache/settings, is to make a symlink from it's location on the partition back to the /root of the other puppy. The portable files take more space and can also be corrupted more easily which is a disadvantage in comparison to running an sfs addon.

mikeslr wrote: ↑Wed Sep 02, 2020 12:12 am

Hi All,

I also like Seamonkey. Just prefer running web-browsers as portables from /mnt/home where they don't occupy my SaveFile and don't locate profiles and especially tons of cache in /root which takes up RAM. fredx181 figured out how and has automated it for firefox. But, I'm not that clever. So I 'flinched' a couple of files, those in the 'extralibs' folder from fredx181's firefox64, the smky 'wrapper' from Mike Walsh's 32-bit Seamonkey porables, and threw in a seamonkey.png I gimped.

Your download from the Seamonkey Website will arrive as a tar.bz2 package. Extract it and within will be a folder just named 'seamonkey'. Move that wherever you want, such as to /mnt/home.

Download the attached portablize.tar.gz and extract it. Move its contents into your seamonkey folder. Start Seamonkey by left-clicking the smky script. Although it generates some files in /root it creates a profile folder (bookmarks, addons, settings) within its own folder and will also place subsequent cached files in that folder. Deleting the hidden files in /root/mozilla and /root/.cache does no harm.

You can use the enclosed icon to 'fancify' your seamonkey folder. Open two flle-browers, one to the folder itself and one so that you can see the icon. Right-Click the folder and select "Set icon". Check the "Only for this file" button. Drag and drop the icon into the window. The effect is operating system specific. portablize.tar.gz

You can use the pet from this post to create a menu entry, viewtopic.php?p=2206#p2206. Remember to edit it to provide the exact path to the smky wrapper.

Thank you very much!! Now I am running the seamonkey last version in fatdog811. Works like a charm.