.pet downloads: what partition types?

Talk about and post software packages known to work or packaged for Puppy.
Post Reply
Message
Author
User avatar
Mike7
Posts: 400
Joined: Tue 19 Feb 2013, 00:31

.pet downloads: what partition types?

#1 Post by Mike7 »

Hi, All.

Don't know if this is the right forum, my apologies if not. Query: What partition types can be used for .pet downloads?

I'm running Carolite-1.2 from a 16G flash drive partitioned:

Code: Select all

/dev/sdb1     ext2    3.9G  658M  3.1G  18% /initrd/mnt/dev_save
/dev/sdb2     vfat    9.8G  2.5G  7.4G  25% /mnt/sdb2
plus a 1G swap partition.

I've been keeping all my own files in sdb2 (vfat) in order to keep down the save file size and make saves quick. I've also been downloading .pets, ISOs, and tar.xz files to a directory in sdb2 (vfat). Is that okay, or do these files have to be downloaded to, as well as run from, an ext partition?

Thanks.

Miike
Carolite-1.2 w/FF38 on bootable 16G flash drive; Asus eeePC 1000HA, Atom CPU, 2G RAM, 160G HDD.

disciple
Posts: 6984
Joined: Sun 21 May 2006, 01:46
Location: Auckland, New Zealand

#2 Post by disciple »

Download them wherever you like, but don't extract them there as FAT amd NTFS don't support symlinks.
Also, if you have problems after downloading to a path with a space in it you have found a bug which you should report.
Do you know a good gtkdialog program? Please post a link here

Classic Puppy quotes

ROOT FOREVER
GTK2 FOREVER

User avatar
Mike7
Posts: 400
Joined: Tue 19 Feb 2013, 00:31

#3 Post by Mike7 »

Hi, disciple.

Thanks for your help with this question. I will do as you suggest: download them to the sdb2/vfat partition, then copy them over to sdb1/ext2 when I want to extract and/or execute them. (That's what you are advising, right?)

I have never yet seen this bug of the path with a space in it, but will report it if I do.

M.
Carolite-1.2 w/FF38 on bootable 16G flash drive; Asus eeePC 1000HA, Atom CPU, 2G RAM, 160G HDD.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#4 Post by bigpup »

or execute them.
From any location,
You can left click on a pet package to install it.

All the pet installer does is read the package data and installs it into Puppy.
All the operations of installing the pet package are done inside the running Puppy, which is an active Linux file system.

Hope you understand you are doing this from a Running Puppy.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
Mike7
Posts: 400
Joined: Tue 19 Feb 2013, 00:31

#5 Post by Mike7 »

bigpup wrote: From any location, You can left click on a pet package to install it. . . Hope you understand you are doing this from a Running Puppy.
I'm still a little unclear about this. Are you saying that I can download a .pet to a vfat partition and run it from there, to install it into the pup that's running from the booted ext partition (rather than putting it into the ext partition and installing it from there)?

Sorry of I'm being difficult. I think I understand the logic of what you're saying (that as long as the .pet is installed by and into the same running system, it should work). It just seems a little strange that it can be read correctly from a vfat partition.

Plus what you say doesn't jibe with what disciple wrote.

M.
Carolite-1.2 w/FF38 on bootable 16G flash drive; Asus eeePC 1000HA, Atom CPU, 2G RAM, 160G HDD.

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#6 Post by musher0 »

Hello, Mike7.

There's no contradiction: to extract a file is not the same as to run or
execute a file.

You can extract a Linux package on a windows or dos partition. Problem
is... important symlinks, if there are any, will be lost if you extract the
Puppy package (or any Linux package) there.

On the other hand, when you run a *.pet package stored from a windows
or dos partition, it is immediately "gobbled up" by your running Puppy in
the Puppy's RAM, it's not stored on any disk.

A *.pet package is like a *.zip archive. It can be stored anywhere, you
can list the contents, any inactive process is ok.

But to run it, you have to run it from a Puppy.

The same is true in reverse: you can store a Windows *.zip package
anywhere on your Puppy, but you won't be able to run it. You can unpack
it, but if it has windows-type links in it, they will be lost too.

Linux and WhineDose both have a link function, but they implement it
differently: links from one system are incompatible on the other.

I hope this gets you un-stuck? :)

BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
Mike7
Posts: 400
Joined: Tue 19 Feb 2013, 00:31

#7 Post by Mike7 »

musher0 wrote:when you run a *.pet package stored from a windows
or dos partition, it is immediately "gobbled up" by your running Puppy in
the Puppy's RAM
Okay, I guess that's why it doesn't matter where it's being run from. As long as it's being "run", it's being run in Puppy.

M.
Carolite-1.2 w/FF38 on bootable 16G flash drive; Asus eeePC 1000HA, Atom CPU, 2G RAM, 160G HDD.

Post Reply