Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 20 Nov 2019, 00:10
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
How to Create an SFS from filezilla-project.org download
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [10 Posts]  
Author Message
mikeslr


Joined: 16 Jun 2008
Posts: 3489
Location: 500 seconds from Sol

PostPosted: Mon 24 Nov 2014, 22:14    Post subject:  How to Create an SFS from filezilla-project.org download
Subject description: General Instructions for Building SFS or Pet from download
 

Hi All,

Edit: The following didn't work under Tahrpup. See http://www.murga-linux.com/puppy/viewtopic.php?p=879405#879405 which provides details about creating an SFS using Ubuntu Tahr debs obtained via Puppy Package Manager. I'll leave the balance of this post since the next official version of filezilla may again be usable, and may still be usable running other Pups.


3.5.3 was the last version of FileZilla available to Puppies. Stimulated by Blackfish's interest in obtaining a current version which would run under LxPup Precise-retro, I decided to investigate. The resulting FileZilla SFS is version 3.9.0.6 and should work in ANY Pup whose Glibc is more current than Lupu 5.2.8. Ran on Ubuntu based Pups from Precise thru Tahr, Slacko 5.7, and Carolina with updated kernel and Glibc. Attempting to start it via terminal in Lupu discloses that required Glibc version is not met.

I know it can locate files on my computer and reach a host on the web and download from it. But I don't know if it can upload to a website as I don't have a current account with a host. Let me know if you were able to use it to upload files to a website. So I'll know whether to delete just the "ALMOST CERTAIN" in the title, or this entire post.

This is not the way I usually build SFSes, and I was surprised that the resulting SFS did anything. But the fact that woof enables the building of Pups using the binaries of “any” distro suggests (a) their differences aren't always insurmountable; (b) building Pups via Woof may have brought Puppy closer to other distros; and (c) Puppy's structure may be sufficiently robust to handle some variation. Moreover, having examined the files, it appears that FileZilla is pretty much self-contained: not very dependent on whatever else may be on or absent from your system*.
I did this running OBPrecise where my File-manager is Rox. If your Pup uses a different File-manager, that's OK. But if Rox isn't installed either install it from Puppy Package Manager, or you'll have to figure out how your file-manager does things. A standard Puppy's version of Rox has many right-click options built in. These instructions assumes you have Rox.
Steps:
1. Open Rox to any folder within Puppy's structure –your home folder is OK-- or any Linux formatted partition. Right-click an empty space. From the drop-down menu, select New>Directory and give it a name. In these instructions I've called it Temp1.
2. Open your web-browser to https://filezilla-project.org/download.php?type=client.
3. Ignore that its supposed to be for Debian 7.0 (Wheezy) and download the offered file into Temp1.
4. Have Rox open Temp1. Within it you'll see a file named FileZilla_3.9.0.6_i586-linux-gnu.tar.bz2. Tar.bz2 is the designation of a compression technique Puppy's default archiving program, Xarchiver, knows how to handle. [Of course, if you follow these instructions some time from now, the version may be higher than 3.9.0.6.].
5. Just left-click that file. Xarchiver will open. Click “Select All” and the click “Extract”. Within Temp1 will appear a new folder named FileZilla3.
6. Click FileZilla3 to open it. Within will be two folders. One named “bin”, the other “share”.
7. (Optional-Recommended) Right click an empty space and select New>directory. Name it “usr” without the quotes –all small letters. Place your mouse-cursor on the “share” folder, then press your left-mouse button. You'll notice that you can now move the share folder. Drag and drop it onto the usr folder and select MOVE. An SFS built without doing this step did function. But having “share” at / isn't Puppy's way of structuring files. And your Window Manager may not be able to generate a menu listing. There's an alternative to insure a menu listing involving creating symbolic links. But it takes more work.
8. Click the usr folder to open it. Then click the share folder to open it. Then click the applications folder to open it. Within it you'll see a file named filezilla.desktop. .desktop files are what Puppies use to generate menu entries.
9. Right-click that file and select “open as text”.
10. Edit these two arguments to read exactly as follows:

Icon=/usr/share/pixmaps/filezilla.png

Categories=X-Network-transfer;

Make sure there's a semi-colon at the end of the Categories argument. Openbox –and maybe some other window-managers-- won't create a menu listing without it. Openbox also may need specific instructions where to find the icon for the menu entry.
Save the changes and close your text editor.
10a. (Optional) Click rox's up-arrow once. You'll see 3 folders. One is named “man”. It contains documents relating to FileZilla. If you never read such documentation, you can safely delete this entire folder. Right-click>delete. The second is named “locale”. It contains files which will translate FileZilla's menu and dialogs to languages other than English. If you are a Native English Speaker and aren't building for any who isn't, you can delete any unnecessary “mo” files. There also a folder named “filezilla” containing files and folders whose value I wasn't certain about. Someone else might know if any can safely be deleted.
11. Click rox's up-arrow until you are again looking at the FileZilla3 folder within Temp1.

11a. (Optional) Right-click the FileZilla3 folder and select “rename”, renaming it FileZilla3906: If you do this, your SFS will have 906 in its name making it easy to distinguish it from other FileZilla3's. The next step assumes you've taken this option.
12. Right-click an empty space and select Window > Terminal Here. In the terminal which opened, type exactly, code:

dir2sfs FileZilla3906

On my system an SFS named FileZilla3906_14.07.26.sfs was created within the Temp1 folder. The 14 and such identifies the Puppy (Kernel?) version in use when the SFS was created. Yours may be different. It's safe to right-click the SFS and rename it by deleting that detail.

13. Move this FileZilla3906.sfs to /mnt/home.
14. Uninstall any current FileZilla pet.
15. Menu>Setup>SFS-Load on the fly. Unload your old Filezilla.sfs if any was loaded & click continue. Load your new Filezilla.sfs. It should open.
16. You might have to reboot to see your new Filezilla on the menu, in the network folder.

17. (Optional) If, after you've tested your new FileZilla sufficiently to be satisfied that it is working properly, you can convert it to a Pet and install it by:
(a) Open Rox in Temp1 and repeat Step 12, except type the following in the terminal, Code:

dir2pet FileZilla3906

or
(b) Copy your FileZilla3906.sfs to, say, Temp1. Right-click an empty space in Temp1 and select new>directory. Give it a name, such as FileZilla3906. Click the FileZilla3906.sfs and select “View Contents”. Click next to the Left-most (or right-most) folder which appeared, then drag your mouse-cursor to the furthest edge of the folder furthest away. This should highlight all the folders. Now drag them onto the FileZilla3906 folder and select copy. Click the FileZilla3906.sfs again to close/unmount it. Now follow the instructions of Step 17 (a).

Have fun,

mikesLr

* Opening the Filezilla.sfs via a terminal –just type “filezilla” without the quotes-- produces the following display.

(filezilla:24202): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed

Gtk is an acronym for graphics built using the Gimp Tool Kit. Googling suggest that whoever wrote that warning doesn't know what critical means. Or maybe I don't. In any event, it doesn't seem to effect FileZilla's operation.
https://gnunet.org/node/1918

Last edited by mikeslr on Thu 31 Dec 2015, 14:54; edited 1 time in total
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3489
Location: 500 seconds from Sol

PostPosted: Tue 25 Nov 2014, 21:04    Post subject: FileZilla3 External in 2 minutes after downloads --Easy
Subject description: Untested on non-Linux partitions, e.g. VFAT USB-Key
 

Hi All,

Edit: If you've created an SFS following the instructions I linked to in my first post's edit, you can still create an filezilla3 folder on /mnt/home and access it using the attached pet.

After building the SFS, Right-click an empty space on /mnt/home and Select New>Folder. Name it FileZilla3. Note the capital F and Z. Then Left-Click your FileZilla.SFS, click View, Click Show All, simultaneously hold down the Ctrl-Key while pressing "a" --for All. All files will be high-lighted. Click-And-Hold any highlighted file and drag it into the FileZilla3 folder. All the other files will be dragged along. Select Copy.

Returning to original post:

It occurred to me that since the FileZilla downloaded direct from the FileZilla-Project appeared to function in any Puppy whose Glibc was high enough,
(1) there was little reason not to run it as an External Application (=from a folder on your Home Partition); and
(2) I could save you a lot of time and effort by providing a pet to do so.

Running an application from a Program Folder uses less computer resources than via an SFS, and doesn't use up one of the (usually only) 6 slots for SFSes.

It will take you about 2 minutes after the downloads complete.

Step 1: Open your web-browser to https://filezilla-project.org/download.php?type=client, and ignoring that the offered file is “for” Debian 7.0 (Wheezy) download it to the folder of your choice.
Step 2. Left-click that file named FileZilla_3.9.0.6_i586-linux-gnu.tar.bz2. Xarchiver will open. Click “Select All” and the click “Extract”. You'll now see a new folder named FileZilla3. [The date of this post is November 25, 2014. The file you download may contain a later version and the folder created may have a different name].
Step 3. Move the FileZilla3 folder to /mnt/home.
Step 4. Download and install the pet accompanying this post.
Step 5. Restart X.

Filezilla should appear on the INTERNET submenu.

Step 6. The accompanying pet was built with the assumption that the folder created by Xarchiver would be named FileZilla3. If it wasn't, you'll have to edit one script file. Browse to /root/my-applications/bin and open the file named "filezilla" --without the quote-- in a text editor. One of its two lines reads:

exec /mnt/home/FileZilla3/bin/filezilla "$@"

The part of the argument, FileZilla3 in the above, has to be identical to the name of the folder on /mnt/home.

Alternatively, you can just rename the folder rather than edit the script.

Other Linux applications I run as External Applications have run from Vfat and Ntsf formatted partitions. But I haven't tested this one.

mikesLr
filezilla_external-3.9.0.6.pet
Description  Requires FileZilla3 folder on /mnt/home. See above instructions
pet

 Download 
Filename  filezilla_external-3.9.0.6.pet 
Filesize  2 KB 
Downloaded  207 Time(s) 

Last edited by mikeslr on Thu 31 Dec 2015, 15:04; edited 1 time in total
Back to top
View user's profile Send private message 
Blackfish


Joined: 26 Feb 2014
Posts: 314
Location: Mostly Southern Nevada and Northern Arizona USA

PostPosted: Thu 27 Nov 2014, 07:17    Post subject:  

This is all starting to make sense. Workin' on it.

Now, there's "rox" and there's "Rox". Does it matter which I use?
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3489
Location: 500 seconds from Sol

PostPosted: Sat 29 Nov 2014, 00:47    Post subject: Rox & rox  

Hi Blackfish,

AFAIK, there's only one Rox. Sometimes I'm just careless about capitalizing words.
It's menu>Filesytem>Rox-Filer file manager. With jwm as window-manager, there's a desktop icon, usually at the top-left, with the name either "Files" or "home" --not sure of the capitalization as I installed Openbox-- which will open rox to /root. When open, click the up arrow on the tool bar to take you to /, the top of the tree. You'll see all the folders which hang from it. So it's click a folder to enter it; click the up-arrow to exit to a folder's "parent." The "home" icon takes you back to /root -- your home folder.

Rox's tool bar has other icons which call various tasks. If you hover over them tool-tips will appear.
One I find handy is the bookmark tool. If you press the icon it will show you which bookmark's you already made, and offer to add the current folder to your bookmarks. I usually bookmark /mnt/home [the partition on which your PuppyOS resides]; /usr --where files and folders installed by the creator or you reside; /usr/share --from which the application and backgrounds folders can be opened without scrolling; and /usr/share/pixmaps --where I usually add icons. The applications folder, as its name suggests, is where you'll find the .desktop files used by the Menu creation module. The backgrounds folder holds wallpapers.
Try right-clicking any desktop icon. Among the optioned offered is "backdrop". If you select it, you can drag and drop any jpg onto the window which opens changing your wallpaper to that jpg. But it easiest if you stored any wallpapers you like in /usr/share/backgrounds. That's where other wallpaper selection applications will look for them.
A couple of other "Rox tricks" you'll find handy are the icon on Rox's toolbar to change the view of files in the folder. Right-clicking turns thumbnail view on and off. Left-clicking shows hidden files.
Play with the icons on Rox's toolbar to see what they do. There are other file-managers with nice features; and Rox is perhaps as unlike Window's Explorer as you can get. But once you used to it you may appreciate why I think Barry K made a wise choice in using Rox-filer as Puppy's default file-manager.

mikeslr
Back to top
View user's profile Send private message 
Blackfish


Joined: 26 Feb 2014
Posts: 314
Location: Mostly Southern Nevada and Northern Arizona USA

PostPosted: Sat 29 Nov 2014, 21:41    Post subject:  

Yes, I found Rox very cool. I have been using Puppy for a few months now and never knew Rox did all that stuff. I found out about it by opening a terminal, striking control+tab-tab. When that opens, you can see all the commands in alphabetical order. I looked up Rox and noticed there were two: rox and Rox. I typed them both into separate terminals and checked them out. Rox is definitely cool. I was messing around in there for a half hour. A new toy! rox is just plain ol' plain ol'.
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3627

PostPosted: Sun 30 Nov 2014, 06:50    Post subject:  

I run a frugal version of Puppy (Thin Slacko 5.3.3t) with no savefile.

Despite using Puppy for around 9 months only recently have I played around with Rox a little more.

IMO a continual puppy savefile is just a slow way to do a full install. Savefiles are better used for short periods when you want to make some changes, are testing those changes until you're satisfied and then remaster to create the fixed image (that you can boot without a savefile from).

My core (fixed) puppy is minimalistic and weighs in at around a 60MB puppy sfs. That provides a fixed unchanging desktop that is the exact same each time its booted, so you can play around to your hearts content installing apps etc and then just reboot to clear those changes out.

When I find a program that I like I was keeping it as a sfs and loading that as/when required. A problem however is that in having no savefile any program config changes are lost when you reboot. To circumvent that I've started using RoxApps. i.e. install the program onto the HDD and run it from there. As part of the program installation/loading in that manner I copy whatever configuration file(s or directory) the program creates/uses under /root to the HDD and when the program is loaded/run as part of the start up I delete the /root copy of the configuration file(s) and symbolic to the one on the HDD so that any program config changes are preserved across reboots.

For instance if a program 'myprog' creates a file /root/.config/myprog.cfg in which configuration changes are recorded then I copy that to outside of puppy space - perhaps /dev/sda1/myprog/myprog.cfg and then delete/symbolic link to that from the /root/.config directory.

I've started to combine various programs into the same ROXApp directory on the HDD and have added (drag/drop) that RoxApp directory onto the desktop so that I have a right click option to launch various programs/tasks.

So to get to the chase, perhaps you could install (extract) the filezilla tar content to within a roxapp directory and add (or create) a desktop icon for that RoxApp directory such that it became a right click/select of that desktop icon launch choice.

In my case I keep a SFS of the program (such as Libre office) in the appdir and the launch code does the sym linking etc and then sfs_loads that sfs (so it populates puppy menu etc). For that purpose I create a cut down version of sfs_load that doesn't to any prompting (nor copying of the sfs).

My understanding is that a rox app directory needs to be made executable and contain AppInfo.xml and AppRun files

AppInfo is the right click menu items that are added when the icon is right clicked and the option parameter associated to each menu item is passed to AppRun if that item is clicked.

My AppRun is generic and simply calls another script in which all of the symbolic link creating, program loading etc is performed/coded. So far in my case I have a sound setup launch choice, libre office install and firefox install choices. For firefox I'm using shinobar's portable firefox, so that preserves all changes outside of puppy space (bookmarks etc) across reboots - and updates to the latest version of firefox as/when released (help, about, check for updates).

AppInfo
Code:
<?xml version="1.0"?>
<AppInfo>
  <Summary>Libre Office</Summary>
  <About>
    <Purpose>ROX Wrapper for Libre Office</Purpose>
    <License>GPL: http://www.gnu.org/licenses/gpl.txt</License>
    <Version>1.0 - Ruf Woof Nov 2014</Version>
    <Homepage></Homepage>
  </About>
 <AppMenu>
    <Item option="Sound">
    <Label>Install Sound Card</Label>
    </Item>
    <Item option="">
    <Label>Install Libre Office</Label>
    </Item>
    <Item option="Firefox">
    <Label>Install Firefox Portable</Label>
    </Item>
  </AppMenu>
</AppInfo>

AppRun
Code:
#!/bin/sh
PROG=loadprogs
APP_DIR=`dirname "$0"`
APP_DIR=`cd "$APP_DIR";pwd`; export APP_DIR
BIN="$APP_DIR/$PROG"
exec "$BIN" "$@"

A minimalistic fixed (no savefile) remastered version of puppy that I like and boots the exact same each and every time (no savefile), together with other apps being loaded as SFS's as/when required, and where changes to those programs (configuration changes etc) are preserved across reboots, and not storing any data files (docs etc) inside puppy space but on the HDD instead (preserved across reboots) works well for me.

Sorry for the long descriptive posting - but I thought images of the code and longer description might help others who like me might not be aware of what Rox can do.
roxapp-rightclick.png
 Description   
 Filesize   18.44 KB
 Viewed   370 Time(s)

roxapp-rightclick.png

roxapp.png
 Description   
 Filesize   131.71 KB
 Viewed   382 Time(s)

roxapp.png

Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 2007
Location: Germany

PostPosted: Sun 30 Nov 2014, 23:04    Post subject: ROX Apps  

Maybe you might be interested to have a look at this:

Modularity Package incl. RoxApp Builder

Information in thread: A vote for a modular use of Puppy Linux

_________________
RSH

"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) Laughing

No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! Wink
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3627

PostPosted: Tue 02 Dec 2014, 20:56    Post subject: Re: ROX Apps  

LazY Puppy wrote:
Maybe you might be interested to have a look at this:

Modularity Package incl. RoxApp Builder

Information in thread: A vote for a modular use of Puppy Linux

Thanks Lazy Puppy. Interesting thread. I intend to also have a look at the low compression remastering mentioned in the thread. Currently I use max compression so it will be interesting to compare speeds.

My RoxApp sfs/apps menu is starting to grow. Recently been installing a PXE server so other family members might net boot Puppy.
ra-menu.jpg
 Description   
 Filesize   27.21 KB
 Viewed   314 Time(s)

ra-menu.jpg

Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3627

PostPosted: Tue 02 Dec 2014, 21:51    Post subject:  

Just tested out the low compression mksquashfs provided in that other thread. For my no save ram boot being fixed I simply added a new RoxApp apps menu item

<Item option="mksquashfs">
<Label>Install low compress remasterpup2</Label>
</Item>

and in the loadprogs script that AppRun calls I added code to replace /usr/sbin mksquashfs and remasterpup2 with versions that are appropriate for the low compression choice. i.e. a CASE script statement of
Code:

 (mksquashfs)

    # Install a low compression version of mksquashfs
    yaf-splash -bg orange -text "Replacing mksquashfs with a low compression version" &
    X3PID=$!
    if [ ! -f /usr/sbin/mksquashfs.orig ]; then
      cp /usr/sbin/mksquashfs /usr/sbin/mksquashfs.orig
      cp /usr/sbin/remasterpup2 /usr/sbin/remasterpup2.orig
      cp $APP_DIR/.mksquashfs /usr/sbin/mksquashfs
      cp $APP_DIR/.remasterpup2 /usr/sbin/remasterpup2
      chmod a+x /usr/sbin/mksquash.fs
      chmod a+x /usr/sbin/remasterpup2
    fi
    sleep 2
    kill $X3PID
    exit;;

Flew threw remastering. initrd.gz (into which I insert puppy sfs) now 116MB compared to 79MB for high compression, but frugally booted doesn't seem any slower, if anything quicker.
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3627

PostPosted: Wed 03 Dec 2014, 06:29    Post subject:  

For that RoxApp launcher I've extended the code so that right click brings up the rox menu as normal whilst left click brings up an alternative of a gtkdialog selection method.
leftclick.jpg
 Description   
 Filesize   21.33 KB
 Viewed   296 Time(s)

leftclick.jpg

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [10 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0868s ][ Queries: 13 (0.0169s) ][ GZIP on ]