Portable Google Chrome for Puppy

Message

Rope · #46 Post by **Rope** » Mon 29 Sep 2014, 22:55

Hello, does this installer need to be in an ext partition?
I have Puppy in NTFS.
The insataller fails
Google Chrome Installer 0.7: fatal ERROR

Failed to create
'/mnt/+mnt+home+puppy+google-chrome-portable+google-chrome-portable-work.3fs/google-chrome-0.7.sfs'.

sunburnt · #47 Post by **sunburnt** » Tue 30 Sep 2014, 02:01

Hi Rope; The std. Chrome and Firefox browsers are made of Linux files, so yes they have to be on a Linux partition.

However... If these apps were made in SFS, or AppDir packages, then they would run from any partition type.

# Submit a request for app builders to package their apps in AppDir packages.

shinobar · #48 Post by **shinobar** » Thu 09 Oct 2014, 22:08

google-chrome-portable shold work on NTFS.
Check your NTFS is healthy.
I am not sure on NTFS compressed. uncompress is recommended.
Check disk and defragment the partition on Windows.

If the partition is not /mnt/home, but say /mnt/sda2, unmount the partition and ensure /mnt/sda2 is empty when it is unmounted.

sunburnt · #49 Post by **sunburnt** » Thu 09 Oct 2014, 23:30

Sorry Shinobar; I didn`t read your first post completely, it is an AppDir.
The AppDir dir. must be in the Save file, but the SFS can be anywhere.
How does the startup script know where the SFS file is.?

I find this useful as Firefox just keeps getting worse and worse it seems.
.

gcmartin · #50 Post by **gcmartin** » Fri 10 Oct 2014, 02:02

I have alway run "compressed NTFS" partitions for data on every platform I have used since 2000. Excepting for the fact that sometimes I have had to boot MS to clear a flag, I have not had ANY major issues with this technology. And, I have used Chrome/Chromium over the years.

Portable apps have a place. I would like to see a recommendation of a skeleton of the directory structure users can maintain for a simple understanding of the separations of program files from cache, download, and config files which can be used so that ANY distro booted could use the browser.

Any pictoral would be useful as a guide.

sunburnt · #51 Post by **sunburnt** » Fri 10 Oct 2014, 06:02

Frankly all apps should be written to work portably, like apps. like Firefox and Chrome that are well written.

If all apps. were portable, then no union file system is needed. It`s just a hack to blend different file systems.

backi · #52 Post by **backi** » Sat 11 Oct 2014, 19:45

I am just a newbie ok sunburnt ... why could not every puppy programm app be portable and if , why is this not be done more frequently ? .....

..i like that portable style . I wouldfind it a great idea doing more portable .All apps should be portable .Is this possible ? Or is this a naive question ?
Cheers !

sunburnt · #53 Post by **sunburnt** » Sun 12 Oct 2014, 18:22

Hi backi; I don`t want to steal the thread in any way, but in short...

There`s about 4 ways to make a portable app:
1) The app author writes the app that way ( the correct way it should be done ).
2) Compiling the app properly ( this only works on a little over half the apps ).
3) Use chroot or fake chroot to set up a new execution environment for the app.
4) Use scripts to setup a portable execution environment for the app.

Newer apps are written better, so compiling works for more of them I think.
None of the "hack" methods ( 3 & 4 ) compare to well written apps of course.
.

gcmartin · #54 Post by **gcmartin** » Mon 03 Nov 2014, 21:41

@PeeBee offers a Chromium packaging, as well.

Here is a brief synopsis of what Chrome on 64bit distros provides for us.

Griot · #55 Post by **Griot** » Thu 13 Nov 2014, 17:34

Hi shinobar. Just for the sake of curiosity I tried to run this package on my PC (CPU is not SSE2 capable, frugal installed Precise 5.72 with PAE kernel, save2dir) and the following error occured:

The .log file looks like this:

Code: Select all

/initrd/mnt/dev_save/google-chrome-portable-0.7/google-chrome-portable
/lib:/usr/lib:/usr/X11R7/lib:/root/my-applications/lib:/usr/local/lib:/usr/lib/seamonkey:/mnt/home/google-chrome-portable-0.7/lib
'/mnt/home/google-chrome-portable-0.7/google-chrome-0.7.sfs' is mounted on '/mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-0.7.sfs'.
'/mnt/home/google-chrome-portable-0.7/google-chrome-config.3fs' is mounted on  '/mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-config.3fs'.
HOME=/mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-config.3fs /mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-0.7.sfs/opt/google/chrome/google-chrome --user-data-dir=/mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-config.3fs/google-chrome-config --disk-cache-dir=/mnt/home/google-chrome-portable-0.7/Cache --disk-cache-size=104857600 --madia-cache-size=104857600 file:///usr/share/doc/home.htm
Unable parse command line: Unknown option --warning
1:'/mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-0.7.sfs' unmounted.
'/mnt/+mnt+home+google-chrome-portable-0.7+google-chrome-config.3fs' unmounted.

Is this related to non-SSE2 CPU or is it something else that causes
this error? I know I'm being nosey

though it might help others with the same problem. Cheers!

kosmos87 · #56 Post by **kosmos87** » Wed 10 Dec 2014, 16:47

Hi, I'm a new user, I just made a full install of Wary 5.5 on a veeeery old laptop (an ancient 2003 Acer Travelmate), because my usual laptop (with a fresh up-to-date Ubuntu) has some battery issues and I can't fix them until new year.

So I only need this pc to "survive" a few weeks, to surf the web, write a few documents, check my e-mail, etc. The thing is, i'm used to work a lot with google drive, my work is basically there. So i was hoping to make chrome work with this (lovely) puppy, but I couldn't. Yes, I already tried Seamonkey and yes, I liked it, it works fine but... if is not too much trouble, can someone help me?

This is the error message on my screen.
P.S: I updated the libraries written in the help file (the link didn't worked, but I found the packages on the official Ubuntu file), so these must be some others...

gcmartin · #57 Post by **gcmartin** » Fri 09 Jan 2015, 06:53

Hello @Shinobar and Happy New Year to you.

I've just installed Portable Chrome on a PUP distro named ChromeCastPUP by @ETP. Interesting enough it comes to this screen.

I wonder if an option would be appropriate to LIST any locations in the filesystem that contain existing Chrome bookmarks seen in the running system? This makes it easy to "tag and acquire" the existing for users who are not knowledgeable of the existing installation's location of Chrome.

I am not aware of any downside to having the portable utility search and present this for user selection? There, of course, would be a small time penalty to have the installation utility do this, but, it is nothing compared to the time required for manual searching for bookmarks.

If its an appropriate feature I'm sure it may be added in the future. Hope this is helpful as this utility matures toward 1.0

Rock · #58 Post by **Rock** » Wed 13 May 2015, 21:11

Just a quick question:
what does it mean that chrome is "portable" for puppyLinux?

Thanks!

starhawk · #59 Post by **starhawk** » Wed 13 May 2015, 21:20

It means that you can put Chrome Portable on any external medium (such as a flash drive) and it will run from that drive as if it was installed on your system -- except when you unmount and remove the drive you will leave no traces of the program within your Puppy install (it'll still be on the flash drive tho).

It's quite useful for situations where you have multiple Pups that all need to run the same set of applications. Well, as long as they will all actually run the apps! (Different versions of different things, can get in the way of that.)

caiosama · #60 Post by **caiosama** » Thu 14 May 2015, 15:09

I tried to install this in Carolina Vanguard Frugal, but this happened:

Code: Select all

google-chrome-portable:/initrd/mnt/dev_save/google-chrome-portable-0.7/google-chrome-portable
google-chrome-portable:/lib:/usr/lib:/usr/X11R7/lib:/root/my-applications/lib:/usr/local/lib:/opt/qt4/lib:/mnt/home/google-chrome-portable-0.7/lib
google-chrome-portable:Build
google-chrome-stable_current_i386.deb
google-chrome-portable:Extracting  '/root/Downloads/google-chrome-stable_current_i386.deb'
to '/var/tmp/google-chrome-portable-root...
dpkg-deb: file `/root/Downloads/google-chrome-stable_current_i386.deb' contains ununderstood data member data.tar.xz     , giving up
find: `./etc': No such file or directory

starhawk · #61 Post by **starhawk** » Thu 14 May 2015, 15:28

Haha, yeah, Caro Vanguard I think has an older version of PetGet so it doesn't dance with modern DEBs...

caiosama · #62 Post by **caiosama** » Thu 14 May 2015, 18:18

The Petget is updatable?

starhawk · #63 Post by **starhawk** » Thu 14 May 2015, 18:36

PetGet would be the backend portion of your Puppy Package Manager. You'll have to beg Geoffrey and battleshooter for that

and battleshooter's not been on in a while, I think...

greengeek · #64 Post by **greengeek** » Tue 14 Jul 2015, 09:18

shinobar wrote:you need seamonkey-solibs-2.26.1, but I couldn't find on the Puppy Package Manager.
Here is a direct link:
http://slackbuilds.org/mirror/slackware ... ck14.0.txz

Does anybody have a current link for these solibs please?
cheers!

darry1966 · #65 Post by **darry1966** » Tue 14 Jul 2015, 09:56

http://osdir.com/ml/bugtraq.security/20 ... 00147.html

P.s. Opps just tried download links bugger dead. Will keep looking.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Portable Google Chrome for Puppy

google-chrome-portable on NTFS

Benefits list write-up

Re: chrome on Phat Slacko