(old)Puppy Linux Discussion Forum

this will probably get a smile:

http://murga-linux.com/puppy/viewtopic. ... 19#1009419

BarryK wrote:My Chromium PET is 87.3MB! Big, but it is only gzip compressed. I am intending to convert it to a SFS for the next release, going over to using SFSs more.

hi all

just a question and a request

does anyone know of an sfs
or can they make an sfs

that has the latest firefox

and pulseaudio and all the other stuff added or compiled in

so that one doesn't have to mess with it

i assume the gurus can do it
but it is of course beyond me

it would be useful for me
but also im sure for everyone who uses firefox

thanks in advance

wanderer

Hi Wanderer:

I haven't followed corepup closely enough to know how to do it under that OS. But if it's like Puppy in general, and you can live without PulseAudio, I'd use the applications available from here, http://murga-linux.com/puppy/viewtopic. ... 010#978010:

You're probably aware the Puppies have difficulty with PulseAudio.

1. To hold the following, create a folder named below as "firefox_quantum" without the quotes for the sake of simplicity.
2. Right-click it and within create an opt folder.
3. Download fredx181's firefox-60.0.1-XX-bit.tar.gz, substituting XX with your choice of 32 or 64.
4. Unpack it, and drop the resulting firefox(number) folder with all its contents into your /firefox_quantum/opt.
[fredx181 built the package (and resulting app) to be portable and self-contained. It can run from anywhere, but locating it in /opt is a good choice for an SFS. It already includes apulse, an application which uses alsa when system/application calls are made to pulse-audio. The version later can be updated, as and when necessary, from firefox's help menu. And profiles --addons, bookmarks, settings-- are preserved within the folder rather than in /root/.mozilla].
5. Download Mike Walsh's FF_Quantum-MenuEntry.pet. Unpack the pet and copy its contents into your firefox_quantum folder --not /opt/firefox. Select merge if necessary. Open /usr/share/application desktop in geany/text-editor and make certain Exe=the name of your /opt/firefox folder)
6. (If necessary, download Mike Walsh's gtk3 pet from the link fredx181 provided. Firefox Quantum (AFAIK even the current firefox-esr) requires gtk3. My experience is that this pet will work with any 32-bit Puppy. Unpack the pet and copy its contents into your firefox_quantum folder --not /opt/firefox. Select merge if necessary. Alternatively, download and mount fredx181's gtk SFS and copy its contents into yourfirefox_quantum folder, not /opt/firefox. But, best to install gtk3 into corepup via its package manager if not already present. Other new applications may need it.)
7. dir2sfs your firefox folder_quantum, not /opt/firefox.

thanks for all the info and help mikeslr

will try your instructions

i think corepup and puppy are close enough for it to be compatible

will post if i have anything of interest

wanderer

Hi wanderer, just mentioning in case Mike's suggestions are not working for you:
The firefox-esr v60.3 packages from Debian do not depend on pulseaudio (or apulse) so sound can work with just alsa.
Should be possible to install and make module on Dcore, I guess.
https://packages.debian.org/search?keywords=firefox-esr

Fred

fredx181 wrote:Should be possible to install and make module on Dcore, I guess.

yes it is possible....and a good tip with firefox-esr v60.3 Debian package! thanks!

thanks fredx181

i will try them both

and thanks for making this package

i (and certainly everyone else) really appreciate your work

wanderer

mikeslr wrote:Hi Wanderer:

I haven't followed corepup closely enough to know how to do it under that OS. But if it's like Puppy in general, and you can live without PulseAudio, I'd use the applications available from here, http://murga-linux.com/puppy/viewtopic. ... 010#978010:
....
....

Bug fixed and newer firefox version, see here:
http://murga-linux.com/puppy/viewtopic. ... 21#1010621

Fred

thanks once again Fredx181

will try your new creation

very awesome

wanderer

hi all

just a post to remind everyone of this little project

and the ideas behind it

and to encourage everyone to look into this system

as an efficient method of building small modular systems


here are some details for those that may be interested


corepup is a modification of tinycore


the basis of this system

is to load a small ramdrive in ram

and then mount tcz (the same as puppy sfs files)

and symlink them to the ramdrive


these are the two lines of the tce-load script

that do the job


sudo /bin/mount "$THISAPP" /tmp/tcloop/"$APPNAME" -t squashfs -o loop,ro,bs=4096 2>&1

sudo /bin/cp -ais /tmp/tcloop/"$APPNAME"/* / 2>/dev/null


in corepup/tinycore

the tc-config script

is equivalent to the init script in puppy

so this is a logical place to add functions

either from puppy or elsewhere


so there you have it

puppy sfs files can be made into tcz files and symlinked and

puppy init functions can be added to the tc-config script


i continue to play with corepup

and have worked out the main outlines of the system

so i consider the project complete

and my original goal accomplished


but of course there are an infinite number of things

that can still be done


well

have a nice day

see you soon

wanderer

Hi wanderer,

I've been following this thread with interest since I started playing with CorePlus. I love how quickly it loads and runs, and have been having lots of fun with it! The only thing I miss is Iron browser. I have the latest Firefox, but I prefer Chrome-based browsers for some tasks and the repository only has an old one. I've yet to work out how to install the latest Iron.

Would you be so kind as to share a working copy of your CorePup? If I can use the .sfs as a .tcz on there, I might start using CorePup instead of CorePlus on my netbook.

Not to worry if you can't share it at the moment. It's great to hear you're still working on it!

Hope you're keeping well

hi redquine

thanks for your interest
and kind words

if you are using coreplus or any newer tinycore
you may be able to simply change any puppy sfs to a tcz
by unsqashing the sfs
and resquashing it with the squashfile version tinycore uses
then make sure the ending is tcz instead of sfs
and put it in your tce/options folder with the other tcz

it should then load normally and be available to use

the only other problem may be that some dependencies are missing
so you may have to run them down and include them in your tcz
or if they are available in the repository load them from there

there are a cornucopia of puppy sfs files on this forum
and I assume there is a version of iron that you can use
and the person that made it probably would help with the dependencies

I intend to post an up to date corepup from tc 9 plus this week if I can
but the modifications are minor when it comes to function
and in the meantime tc plus is essentially the same

if you have and questions or thoughts on all of this
please post and I will try to answer them

great hearing from you
and good luck
and stay well yourself

wanderer

hi all

with my customary lack of foresight

i thought i would move this thread to misc

to get out of the way of the main puppy threads

however wiak is right

that thread is too filled with ... misc things

i now move things back here

i will wait until the gurus decide

what us non-puppy based projects should do

anyway now that i have a little more personal time

i will try to do more work on this project

i will annoy you all again soon

regards

wanderer

hi all

now that i (hopefully) have a little more time
i will proceed to turn tc plus 9 into corepup 9
this really entails (intentionally) very minor modifications
and until it is ready
tc plus 9 can be used and is essentially identical
so for anyone who is interested and waiting
just use tc plus 9

i will only do this with tc plus 9 not the smaller versions
since it contains the extra stuff for wireless
and the extra desktops
and if anyone wants a smaller system
all they have to do is remove some tcz
which is very easy

i also want to turn fredxs apulse firefox into a tcz

and apparently there is a script that will turn a deb into a tcz
and i will look into that

i have already done a lot with corepup
using tc 6.4.1
and all of that transfers easily to later versions

as noted before
tc and puppy are very similiar
the tc-config file in tinycore
is equvalent to the init file in puppy
and tcz are equivalent to sfs files and pets

well as usual
i encorage whoever would like to build a minimal modular system
to look into corepup/tinycore
i think you will be impressed with its power and elegance

see you soon

wanderer

Great to hear you're working on it again, wanderer! Just to let you know, I managed to get Iron working in CorePlus.

It didn't run from a converted .sfs as (1) in Puppy, Iron needs to run as spot; (2) there were missing dependencies. So I extracted the .deb instead, which gave me the control file listing the dependencies. All I had to do was create a .dep file containing:

libXcursor.tcz
atk.tcz
at-spi2-atk.tcz
libXcomposite.tcz
libXtst.tcz
libcups.tcz
nss.tcz
gtk3.tcz
libXss.tcz
gst-ffmpeg.tcz
libasound.tcz

After fetching these from the repository, it worked perfectly. There are warning messages in the terminal, but I get those in Puppy as well and it still seems to run OK.

I look forward to trying it in CorePup, and seeing if I can convert a few more applications when I get the chance.

awesome work RedQuine

what you are doing is what its all about

i will try to follow in your footsteps

post any info on how you do things if you get the chance

thanks so much

wanderer

hi all

to those interested

there is another way of adding applications to corepup
besides making a tcz (a compressed read only file)

one can also put the application in an ordinary directory
for example in home
and then symlink its contents to root
using the busybox copy command

this means the application will be uncompressed and read/write
and can modify its control files as needed in that directory

just one of the many variations possible because of the elegance of this system

wanderer

hi all

one of the keys to making corepup
both more puppy and more useful
is to make puppy applications/functions
usable in corepup

what i want to have in corepup
is a forefox that uses apulse
instead of pulse audio
so i am going to try to put fredx's firefox into corepup

so now im going to bug fredx for advice

wanderer

[quote="wanderer"
what i want to have in corepup
is a firefox that uses apulse
instead of pulse audio
so i am going to try to put fredx's firefox into corepup

so now im going to bug fredx for advice

wanderer[/quote]

Before you bug fred: His firefox quantum, as well as Mike Walsh's firefox-esr and palemoon are portables.. They do NOT have to be installed. Under Puppies, all you do is download them, unpack the downloaded tar.gz, move the folder where you want it, and start them by clicking the bash-scripts named "ff" for firefox and "plmn" for palemoon.

If corepup employs BASH, that may be all that is necessary. If it doesn't employ bash, you may just need to translate the scripts to whatever corepup uses instead.

You'll find on the same post from which you download firefox quantum a menu pet. It's structured to find firefox quantum in /opt. But I run portables from /mnt/home. So I deconstructed the menu-pet, edited its path, and rebuilt it. Used it as a template for firefox-esr and palemoon, merely changing the path specifics and executable called.

thanks mikeslr

forefox will start but can't find some files

i will have to run down where to get them


wanderer