Firefox 23.0.1

Message

sunburnt · #21 Post by **sunburnt** » Wed 27 Nov 2013, 07:23

Hi koulaxizis; I`ve been doing 3 or 4 things at once, so it took awhile to get to this.

Here`s a no-install "Virtual AppPkg" using your Firefox-23 SFS file.
# Notice the small download size of: 21 KB.
It downloads your SFS file at first run, after that it mounts and runs it without a union.

There are no links that need to be made, or paths that have to be set for it to run.
What a wonderfully built application.!!! All apps should be made like this.

I intend the Virtual Package idea for the Ubuntu or Slackware repositories.
So there would be multiple downloads to build most apps.

### New revised file uploaded.

http://www.murga-linux.com/puppy/viewto ... 061#741061
.

Keef · #22 Post by **Keef** » Wed 27 Nov 2013, 22:13

sunburnt,

I think the script is missing - directory is empty.
You've still got that:
/root/0_sda3/AppPkg/apps_virtual/Firefox-23.AppPkg
thing going on.

sunburnt · #23 Post by **sunburnt** » Thu 28 Nov 2013, 01:17

Thanks Keef; Try the new one with the fixed path. It should work.
I`ve run it a number of times and it worked all of them ( Precise-5.4 ).

Really need to setup a Rox desktop icon to Zip stuff properly..!
### Have done this... Made a nice utility: "zipdrop" + a nice filer icon.

koulaxizis;

SFS files are very easy to use! But i like PET files too!

Yes, unfortunately both formats are used by many people.
Settling on just one, like AppDir would solve a lot of work for you guys.
AppDir / RoxApp / AppPkg are all no-install like SFS, but don`t need a union.
No-install so they can be anywhere, CD-DVD, USB, HD, RAM, LAN, and Web too.
I`ve mounted & unioned SFS files over Samba before, but it`s more stuff to go wrong.
.

Keef · #24 Post by **Keef** » Thu 28 Nov 2013, 19:51

sunburnt,

Sorry to be a pain, but still had a few problems. It looks like it depends on xdlg.dnldprogress and it needs to be in the directory. Copied it in, but still no joy.
Then changed this line:

Code: Select all

${Path%/*}/0/xdlg.dnldprogress $SFS $URL

to

Code: Select all

${Path%/*}/xdlg.dnldprogress $SFS $URL

(removed the none existant directory '0')
Worked fine after that.

sunburnt · #25 Post by **sunburnt** » Thu 28 Nov 2013, 21:52

Keef; Worked for me.
$Path = /(path).AppPkg/firefox-23.0.1-en_5.6.0
So ${Path%/*} = /(path/.AppPkg with the /0 dir. in it.
So ${Path%/*}/0/xdlg.dnldprogress should be good.

Generic files are in .AppPkg/0
App specific files are in .AppPkg/(App)

### Has anybody else tried it.? ... koulaxizis ?
.

Keef · #26 Post by **Keef** » Thu 28 Nov 2013, 22:03

Bizarre, it works now.
Ignore me from now on.

sunburnt · #27 Post by **sunburnt** » Fri 29 Nov 2013, 00:29

My thought was... Yep, now it works, and now it doesn`t. Strangely my "file" quit working.
This is about right, a decade ago I`d write a diddy and take it next door to show the neighbor.
It`d immediately crash his PC and a hard reboot was all that`d get it back. So I wasn`t surprised.

I thought about making the line: ${Path%/*}/0/xdlg.dnldprogress $SFS $URL
Into this relative path for clarity: ../0/xdlg.dnldprogress $SFS $URL
But I tend to like full paths for test echos. Otherwise you need to echo a pwd for relative paths.

# If the download url list is say, Ubuntu binary files, then the Ubuntu mirror pays the IP bill.

# I made a note to setup some way for an option to load the SFS file to RAM before mounting.
Maybe if > 300MB of free ram. ( Code to get truly free ram.? ) OR... A config. file setting.

I think loading apps to ram is stupid, it just gets swapped back to the HD. But many like it.
mikeb points out that a fatal crash exits better with fewer mounts, and no FS corruption.

koulaxizis; Are you still here buddy.? Haven`t heard from you and this is your thread.
If you get a chance let me know what you think of Virtual Apps.
.

Karl Godt · #28 Post by **Karl Godt** » Fri 29 Nov 2013, 00:58

sunburnt wrote:Keef; Worked for me.
$Path = /(path).AppPkg/firefox-23.0.1-en_5.6.0
So ${Path%/*} = /(path/.AppPkg with the /0 dir. in it.
So ${Path%/*}/0/xdlg.dnldprogress should be good.

Generic files are in .AppPkg/0
App specific files are in .AppPkg/(App)

### Has anybody else tried it.? ... koulaxizis ?
.

I would suggest to post in the cutting edge section with a link here and
after the bugolettis are out, post in the internet section with a link here and a link to the cutting edge section.

Some people think that this is scattering, but posts here should be made in regards of the internals of the pkg made by koulaxizis .

Add-ons deserve a separate thread .

Looking for the script, though, because that might work to load it into a full installation .

Karl Godt · #29 Post by **Karl Godt** » Fri 29 Nov 2013, 01:44

Code: Select all

#####           Terence Becker          SunBurnt                Nov. 24  2013
#####           No Warranty...          Use at your own risk.!

Path=`realpath $0`
Path=${Path%/*}
PKG='firefox-23.0.1-en_5.6.0'


#*** changes by KRG ***
PKG='firefox-16.0a2.en-US.linux-i686'
#*** changes by KRG ***


SFS="$Path/$PKG.sfs"
MNT="/tmp/AppPkg/$PKG.mnt"

dlhandler=${Path%/*}/0/xdlg.dnldprogress
dlhandler=wget

#####   SFS file made by:  koulaxizis
URL='http://sourceforge.net/projects/puppystuff/files/Internet/Firefox/firefox-23.0.1-en_5.6.0.sfs/download'


#*** changes by KRG ***
busybox tcpsvd -vE 0.0.0.0 21 ftpd /mnt/sda2/load_sfs/ &
sleep 2s
URL='ftp://0.0.0.0:21/firefox-16.0a2.en-US.linux-i686.sfs'
#*** changes by KRG ***


if [ ! -f $SFS ];then                                                                   # dnld. firefox SFS file
        #${Path%/*}/0/xdlg.dnldprogress $SFS $URL
        $dlhandler $SFS $URL
        [ $? -gt 0 ]&& exit 3
        msg="\n   #>>  NOTICE:  Ready to Run.\n\n   Click on AppPkg Folder:\n\n   ${Path%.AppPkg*}\n "
        echo -e "$msg"
        xmessage -center "`echo -e $msg`"
        exit 0
fi

#########       Could Copy SFS File to RAM ( If there`s Lots of it...).

if [ ! "`mount |grep '$SFS'`" ];then                                    # mount firefox SFS file
        mkdir -p "$MNT"
        mount -r -t squashfs -o loop "$SFS" "$MNT"
        if [ $? -gt 0 ];then
                msg="$0:  ERROR:  Failed to Mount Firefox SFS File."
                echo -e "$msg"
                xmessage -center "`echo -e $msg`"
                exit 3
fi ;fi

#$MNT/usr/bin/firefox
#/tmp/AppPkg/firefox-16.0a2.en-US.linux-i686.mnt/lib/firefox/firefox-16.0a2.en-US.linux-i686/firefox                                                                  # run firefox-23


#*** changes by KRG ***
$MNT/lib/firefox/firefox-16.0a2.en-US.linux-i686/firefox
#*** changes by KRG ***


#umount -d "$MNT"                                                                                        # unmount firefox SFS
#if [ $? -gt 0 ];then
#        msg="$0:  ERROR:  Failed to Unmount Firefox SFS File."
#        echo -e "$msg"
#        exit 5
#fi

Worked for me !
Needed older ff for 23 wants glibc-2.7,
so I setup busybox tcpsvd -vE 0.0.0.0 21 ftpd /mnt/sda2/load_sfs/ & for my local repo and changed the dlhandler to wget . Also the path to exec ff is different at mine .
But overall : really nice for PUPMODE 2 Full installation ! Have some problems with /tmp dir as mountpoint directory though, but changing /tmp to /mnt might not that bad problem.

sunburnt · #30 Post by **sunburnt** » Fri 29 Nov 2013, 04:14

Karl; I suppose /mnt could be used for files, I think it`s for partitions, so Barry put them in initrd.
I like /tmp because it`s not unioned with the Save file which would require resolving the union.
Most Save files are on a partition, so are slow to resolve of course. And /tmp cleans itself up.
Anywhere else in the FS is covered by the Save file and the union. Only /tmp and /shm aren`t.

# I have a generic download script that reads a file with a url list ( repository packages ),
and can contain script commands to modify the pkg. and do any setup that`s needed.

It`s a simple idea, if used with Debian, Ubuntu, and Slackware repositories it has great potential.
Build scripts can assemble binary files, or source files and compile them ala amigo`s AppDirs.
If a std. Puppy base distro can be settled on, binary files are the easiest of course ( bloated ).
.

Karl Godt · #31 Post by **Karl Godt** » Fri 29 Nov 2013, 15:13

sunburnt wrote:Karl; I suppose /mnt could be used for files, I think it`s for partitions, so Barry put them in initrd.
I like /tmp because it`s not unioned with the Save file which would require resolving the union.
Most Save files are on a partition, so are slow to resolve of course. And /tmp cleans itself up.
Anywhere else in the FS is covered by the Save file and the union. Only /tmp and /shm aren`t.
# I have a generic download script that reads a file with a url list ( repository packages ),
and can contain script commands to modify the pkg. and do any setup that`s needed.
It`s a simple idea, if used with Debian, Ubuntu, and Slackware repositories it has great potential.
Build scripts can assemble binary files, or source files and compile them ala amigo`s AppDirs.
If a std. Puppy base distro can be settled on, binary files are the easiest of course ( bloated ).
.

I consider steady files as steady , not temporary :

felt really helpless when I committed the mistake of mounting all drives in /tmp, forgetting to unmount them and shutting down the system.

I was wondering, why was puppy taking so much time to shut down Confused

Next boot discovered that none of the linuxes were bootable.

Had to buy a new CD to run puppy and discovered that all my linux partitions were empty.

From that day I never mount anything under /tmp.

http://murga-linux.com/puppy/viewtopic. ... 465#705465

And /mnt contains also the mounted - not loaded - loop files as .iso and .sfs ; not only partitions .
You should know that, since you are the initial author of /usr/sbin/filemnt !

sunburnt · #32 Post by **sunburnt** » Sat 30 Nov 2013, 00:16

He pulled the plug is what caused his problems. Did not shutdown.
He mistakenly believed that /tmp is deleted at shutdown, which it is not.

I`m not sure but I think Puppy ummounts everything at shutdown anyway.
We`re talking mounted Squash files, so there can`t be much of a problem.

I wrote filemnt over 6 years ago when I was starting out with Bash.

Karl Godt · #33 Post by **Karl Godt** » Sat 30 Nov 2013, 04:24

#120514 WARNING: i don't have this problem, as no longer deleting /tmp/* (120409), however Karl Godt reported that 'fuser -k -m' may kill rc.shutdown then if no /tmp/bootcnt.txt then X restarts, ref: http://bkhome.org/blog/?viewDetailed=02827

solo · #34 Post by **solo** » Sat 21 Dec 2013, 16:21

For those people who use the SFS file of Firefox, I suggest you go to -Edit-Preferences-, click on the -Advanced- tab, select the -Updates- tab under that, and disable updates.
If you don't, a new update will install itself the moment you click on -About Firefox- in the Help menu. That would pretty much defeat the purpose of using an SFS in the first place.

Also, you can delete the files in folder /usr/share/firefox/updates/0/ , which are updates.mar (the big one), and update.status, and this will free up quite a bit of memory as well.

Of course after that it is up to you to update Firefox.

earlytv · #35 Post by **earlytv** » Fri 27 Dec 2013, 09:48

solo wrote:For those people who use the SFS file of Firefox, I suggest you go to -Edit-Preferences-, click on the -Advanced- tab, select the -Updates- tab under that, and disable updates.
If you don't, a new update will install itself the moment you click on -About Firefox- in the Help menu. That would pretty much defeat the purpose of using an SFS in the first place.

Also, you can delete the files in folder /usr/share/firefox/updates/0/ , which are updates.mar (the big one), and update.status, and this will free up quite a bit of memory as well.

Of course after that it is up to you to update Firefox.

I use Browserlinux 501 and the firefox did its own update to ver26 thru the About Firefox. It seems to work fine? Being a hardware not software guy I always have questions. Can 501 use SFS? Is that SFS a better way? WHY?

solo · #36 Post by **solo** » Fri 27 Dec 2013, 21:28

earlytv wrote:I use Browserlinux 501 and the firefox did its own update to ver26 thru the About Firefox. It seems to work fine? Being a hardware not software guy I always have questions. Can 501 use SFS? Is that SFS a better way? WHY?

Actually, that is what happened to me. I had the SFS loaded, and then ran the update by clicking -About Firefox-, and it installed v26, which ran without any problems. But then I noticed that because I had Firefox loaded through the SFS file, I suddenly had two instances of Firefox installed, one in /usr/firefox, and one in /usr/bin/firefox.
I don't know if you can use SFS files with Browserlinux 501, and if you can, I don't know if anyone has any available suitable for that particular distro.
I am very new at all this, but as far as I can assess, the biggest advantage of using SFS files, is that allows you to run your Puppy Linux with a relatively small amount of personal storage space, and this may come very handy if you are running it on computers with less memory.
And so if the memory requirements are smaller, the more flexibel your setup is.
But if it's about saving personal storage space, there are bigger advantages to achieve when it comes to Firefox, like the one discussed here:

http://208.109.22.214/puppy/viewtopic.p ... 15ff8adf77

earlytv · #37 Post by **earlytv** » Fri 27 Dec 2013, 22:28

Browserlinux is diff, cant find it in either (/usr/firefox, and one in /usr/bin/firefox)?

solo · #38 Post by **solo** » Sat 28 Dec 2013, 10:36

earlytv wrote:Browserlinux is diff, cant find it in either (/usr/firefox, and one in /usr/bin/firefox)?

My mistake, I meant /usr/share/firefox and /usr/bin/firefox.

Browserlinux is a distro specifically designed to be lightweight and meant for browsing the web. I don't believe using an SFS version of Firefox would yield a lot of advantage. Because the Internet browser is such a core component of the distro, it would be more advantageous to have it installed normally, so as to allow normal updating.
If you are eager to keep your save file as trim as possible, I'd suggest to apply the method discussed in the link I posted earlier.

earlytv · #39 Post by **earlytv** » Sat 28 Dec 2013, 12:59

/usr/share/firefox and /usr/bin/firefox.

Still can not find firefox at those places, and the other files that I could delete not there also?
I have browserlinux installed wih grub and it looks like it takes up only 371 meg bytes on the 230 gig bytes drive.

solo · #40 Post by **solo** » Sat 28 Dec 2013, 19:01

earlytv wrote:/usr/share/firefox and /usr/bin/firefox.

Still can not find firefox at those places, and the other files that I could delete not there also?
I have browserlinux installed wih grub and it looks like it takes up only 371 meg bytes on the 230 gig bytes drive.

Earlytv, when you have Firefox installed, like you have, and it updates normally, like it is in your case, it makes no sense deleting the files responsible for completing updates.
So I would strongly suggest that you do not delete any files at all, and I would also suggest that you would allow Firefox to perform updates, and not disable it by changing the settings.

In other words, your setup seems to be working for you just fine as it is, and I would not try to modify it if I were you.

My suggestions in previous posts pertained to those people who are running Firefox loaded as an SFS file in Puppy Linux, and are not advisable for those who have a setup in which Firefox is a regularly installed program like you have.

So don't change or delete anything please.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Firefox 23.0.1