![]() ![]() Now, copy the contents of this across to the empty 'profile' directory in the portable-Palemoon directory. If you already created the 'profile' directory by starting Palemoon with the 'plmn' script, then delete the contents. If you wish to do this before you fire up for the first time, manually create the 'profile' directory. Click through 'palemoon' to reach your 'fault' profile. To run with an existing profile, locate your existing /root/.moonchild productions directory. Palemoon will create the 'profile' directory at first run, thereafter always using this profile directory on subsequent runs.as long as you start Palemoon using the start script. It works a treat.įor anybody who would like to try this out, you can find it at my Google Drive:-Īs with the other Palemoon 'portable', unzip move the resulting 'palemoon32' directory anywhere you like, then click on the 'plmn' scipt to start Palemoon. It's been tested in my Lucid & Racy installs, temporarily adding 'pfix=ram' to menu.lst so as to get Pup to boot as a pristine install. (I must be starting to get the hang of this 'variable' stuff, because amazingly it fired-up straight away on the first trial run!) The same '$LAUNCHDIR' variable as used in the 'plmn' start script has been specified, and every reference to the original '/usr/lib/palemoon/' location has been replaced with this variable.Ĭlicking on 'plmn' now runs the 'launch' script, which in turn starts Palemoon, using the glibc 2.19 components. The 'plmn' start script now points to this rather the main palemoon binary.ī) 'Launch' has been re-jigged a bit. Obviously, I've had to make a few modifications, especially with the inclusion in the mix of the glibc 2.19 'upgrade'.Ī) The 'palemoon' launch script has been moved from /usr/bin into the browser directory itself, and renamed 'launch'. It's been built along the same lines as my other Mozilla 'portables', FF60esr and Palemoon28. ![]() To make this even more usable, I'm pleased to be able to offer a 'portable' version of this SSE-only edition of Palemoon. It also runs well in newer Pups, too, since the CPU doesn't work so hard to process the browser's code. My own Lucid (lupu-super2) and Racy 5.5 are a case in point. It brings life back to many older Puppies, which, but for a decent browser, are otherwise still perfectly usable on a day-to-day basis. We all know how popular watchdog's 27.9.4 SSE-only build of Palemoon is, incorporating as it does the glibc 2.19 'tweak'. 'Portable' Palemoon 27.9.4-SSE with glibc219 'tweak' Unless anyone out there knows better.because previous versions of the JRE weren't causing this behaviour, that's for certain.! ![]() Something, somewhere in the Java Runtime Environment, is interfering with the PaleMoon startup sequence.but what? That's the million-dollar question, because I fail to comprehend why PaleMoon is going anywhere near the JRE in the first place. Crazy kinda workaround, but it's working for me. If you run JRE, and are on the newest version, run it as an SFS.and, for now, unload the SFS before you start the browser. Why is PaleMoon even looking at JRE in the first place? To test a theory, I temporarily reverted back to JRE 8_181, and fired PaleMoon up again. I recently upgraded from JRE 8_181 to JRE 8_191 a few days ago. Now I use it for loads of 'common', sym-linked stuff across the kennels.including 32/64-bit versions of JRE.) It's where XP used to be until a couple of years ago. (I keep 'common' installs of many apps/progs on /mnt/sda1. opt/palemoon/palemoon: symbol lookup error: /mnt/sda1/opt/jre/lib/i386/libnpjp2.so: undefined symbol: _ZSt7getlineIcSt11char_traitsIcESaIcEERSt13basic_istreamIT_T0_ES7_RNSt7_cxx1112basic_stringIS4_S5_T1_EES4_ Code: Select all # /opt/palemoon/palemoon ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |