(old)Puppy Linux Discussion Forum

Works weird, but works. Everything installed, so I'm basically happy. I'm not the best tester, so I can say no more, sorry...

Thanks bugman, hopefully it's real close now, should only be minor bugs.


### CRITICAL: Be SURE to gunzip & untar in the dir.: /root/my-applications


### Change log:
code cleaned up
checkbox to enable rxvt display of files

Lots of little stuff changed again, I may have created bugs...

### NOTE:
If someone has setup a TESTING Full-HD install, please test these items:

Verify install & uninstall as well as you can.
If preexisting files are backed up & restored properly.
If checkbox, the rxvt display shows & is killed when done (install & uninstall).
If no checkbox, messagebox display shows & is killed (install & uninstall).


This should be this apps. final form, so final testing is all that's to be done.
If we can test it out fairly well, I'll submit it to Barry for inclusion in Puppy.

### CRITICAL: Be SURE to gunzip & untar in the dir.: /root/my-applications

Oops...

I put it in /usr/local/apps as I'd seen from using the sfs files in a live-CD install that that was where the sfs files were installing, and knew that there's always some filesystem tinkering going on in Western Oz.

Maybe that's why it ran so weird? Oh well, Gimp works, OOO works, and all's well with the world for now...

bugman; Just move the dir.: /sfsInstaller_full-HD & it's contense to: /root/my-applications

The lists of installed files & other paths are hard coded to: /root/my-applications/sfsInstaller_full-HD

Done, thanks. Btw, my sfslist is empty and was throughout the installation. But I have enough space for a few stray programs, so no worries...

bugman; Yep, the install tracking file is made during installation.
With the app. in the wrong place it couldn't make the file (no dir.).
If you want, I can give you instructions to make one using Xterm.
However... If your not going to want to uninstall it, don't bother.

If the apps. in the correct path now, then future installs should show.
The installed SFS file shows in the list because there's an install tracking file.

Actually, I thought about it some and wouldn't mind making the list all proper-like.

A: I'm okay today, but tomorrow the unwanted programs will be driving me nuts.

B: Using the terminal makes me feel powerful.

C: My inability to read instructions is my own problem and I shouldn't expect others to bail me out of--oh, wait, nevermind...

Pick a reason, any reason!

LOL...

I'll post some cli commands for you to make an "install file" (not at my PC).
Unfortunately simply reinstalling the SFS file again won't do the trick.
Basically instructions to mount the SFS file & generate a correct install file.
Terry

bugman; Here's the fix to make the install file.

### Run each one of these commands separately in Xterm or rxvt.
### HiLite each line one at a time & Paste (middle mouse button) into Xterm.

### The first line, enter the path & filename of the SFS file between the 2: ''
### Example: sfsFILE='/mnt/home/devx_214.sfs' Run sfsInstaller & you should now see the SFS file listed.

Unfortunately SFS files usually are larger collections of apps.
(as they should be), so they have to be installed & removed all at once.
However installing from Unleashed PET files is done one at a time (better),
but I guess some may not be fully configured (correct me if I'm wrong).

Let me know if you have any problems... Terry

I tried it for "OOo_215.sfs", but what came up in the sfs installer window was "sfsFILE.inst". Thanks for trying (though it was probably something I did wrong), I then just tracked down as many of the folders for progs I didn't need in /root/, usr/whatever and deleted.

Besides, I already had my Unix-stud moment today. I was working on a friends Mac (shudder!) and they mentioned a file on their desktop that had suddenly appeared and wouldn't go away. It was some weird bit of web-junk that they must have accidentally summoned into being, and resisted all efforts at deleting the regular way. So I opened up a terminal and did rm /Users/mac/Desktop/srvurl and voila! They were amazed that such a primitive tool existed on their Aqua-fresh post-modern doorstop.

The best thing of all is that they thought I actually knew what I was doing...

Geek to Guru in a flash!

Sorry about the extra work bugman... Terry

I can't mount my sfs file on 216 alpha (with full installation). But with sfsinstaller i'd mounted successfully my sfs file. Thank all

Hi vanchutr; So it installed the sfs file sucessfully?
If you try UNinstalling it, please post here how well it worked.
So far I have no idea if the uninstall function works at all.
Terry

Where should the sfs files be in a full install situation?

Hi Fishy; A Full-HD install of Puppy can't use SFS files directly (it won't work).

That's why I made this app., it copies the contense of the SFS file to the full install.

To use it, click: [Install SFS file] & a file chooser pops up.
So the SFS files can be anywhere when installed with my app.: sfsinstaller
After installing the SFS file, it's no longer needed, but is good for a backup.

The reason I asked is that I had openoffice.sfs in / root and when I ran your installer all the office files were opened and placed in / not something like /usr/share or whatever.

I suspect that a certain amount of Linux expertise is assumed before one meddles with something like this but with me it is like matches in the hand of a child.

Mighty odd... No one else had any install problems.
The uninstall is the main untested part of the app.

Note: SFS files made for Puppy-1 won't work for Puppy-2, & vise-versa.
Puppy-1 SFS files are based at: /usr, where as Puppy-2 is based at: /

Hi sunburnt

Had the same problem as Fishy. The app puts all the files in the / (root) of the HD. It does however create all the directories correctly, but they are empty.

Thanks

That's just too weard, the command is: cp -a (sfsMntPt) /

I can't see anything that could be bad with a simple command like that.
It should copy the dirs. & files from the SFS file to / just like in the SFS file.
I'll look at it to see if there's something obvious, but not much can go wrong.

FOUND IT (I think), files are being copied individually, so path had to be added.
This would explain why it made dir. paths but put the files in / & I've fixed it.

I don't have a full install of Puppy so I've relied on users to test this app.

Will someone with a Full-HD install please make sure it's installing correctly?

The NEW app. is above at the original file download... Terry