Puppy works perfect from a CD because it starts fresh each time and does not get anywhere near full in one session.
A full install to a hard drive also works well for me.
I have trouble with frugal installs to the HD because the available space fills up. The available space is much smaller than the size of the HD or even the available RAM. This is a big deal because FatDog-64-600 is dropping support for a full install in favor of the frugal install. Clearing history/cache in firefox helps but eventually a frugal install gets clogged up with data I don't know how to get rid of.
Any suggestions?
Personal space filling up??
A full install is the only method I've used In the almost 5 years I've been using Puppy, (except for live cd and usb to carry
around).
I wouldn't use or support the version you mentioned.
around).
I wouldn't use or support the version you mentioned.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Re: Personal space filling up??
Menu->Utility->Resize personal storage filelakedude wrote:I have trouble with frugal installs to the HD because the available space fills up.
Be aware that...
If you attempt to copy or move stuff to a partition...
And that partition_file_system isn't mounted...
The Puppy will instead copy/move the stuff to its own filesystem.
And if that filesystem is inside a pupsave file...
The pupsave file will have some of its space [possibly a LOT] used by that.
If you attempt to copy or move stuff to a partition...
And that partition_file_system isn't mounted...
The Puppy will instead copy/move the stuff to its own filesystem.
And if that filesystem is inside a pupsave file...
The pupsave file will have some of its space [possibly a LOT] used by that.
Where does it copy it to? Any way to remove it afterwords?Be aware that...
If you attempt to copy or move stuff to a partition...
And that partition_file_system isn't mounted...
The Puppy will instead copy/move the stuff to its own filesystem.
And if that filesystem is inside a pupsave file...
The pupsave file will have some of its space [possibly a LOT] used by that.
(I think I might have recently done that-- which would explain a sudden drop in savefile space I just had)
Ahhh, lots of good tips. I'm pretty sure that the "data" drive was unmounted one time so the personal file got filled up. Good call!
As far as not supporting FD-64-600, well that is not really an option. BOINC project GPUGRID only works on a 64bit OS so all the 32 bit puppies are out of the question.
FatDog-64 is an awesome distro that is made to run on modern systems. I'm pretty sure it is faster than 32bit versions....
As far as not supporting FD-64-600, well that is not really an option. BOINC project GPUGRID only works on a 64bit OS so all the 32 bit puppies are out of the question.
FatDog-64 is an awesome distro that is made to run on modern systems. I'm pretty sure it is faster than 32bit versions....
1.
(b) It may have been in the "/tmp" folder, but that's just a guess.
2.
(a) I cannot remember where, but it should be easy enough to find out; just deliberately copy something [a small file?] to a partition that isn't mounted, then use "Find" to look for it.sfeeley wrote:Where does it copy it to?
(b) It may have been in the "/tmp" folder, but that's just a guess.
2.
Once you "Find" it, just move it to its correct home, or else delete it.sfeeley wrote:Any way to remove it afterwords?
-
Bruce B
Almost always our mount points are directories. If the directory is mounted it will copy to the mounted device. If the directory is notSylvander wrote:1.(a) I cannot remember where, but it should be easy enough to find out; just deliberately copy something [a small file?] to a partition that isn't mounted, then use "Find" to look for it.sfeeley wrote:Where does it copy it to?
(b) It may have been in the "/tmp" folder, but that's just a guess.
mounted, it will copy to the directory.
~
1. 
I don't know what a "mount point" is.
Nor what "mount points are directories" means.
2.
I think I understand what "it will copy to the mounted device" means.
3.
Is "it will copy to the directory" the same or different to "it will copy to the mounted device"?
No comprendi.Bruce B wrote:Almost always our mount points are directories.
I don't know what a "mount point" is.
Nor what "mount points are directories" means.
2.
I don't understand what "If the directory is mounted" means.Bruce B wrote:If the directory is mounted it will copy to the mounted device.
I think I understand what "it will copy to the mounted device" means.
3.
Don't understand "If the directory is not mounted" as with "If the directory is mounted" mentioned above.Bruce B wrote:If the directory is not mounted, it will copy to the directory.
Is "it will copy to the directory" the same or different to "it will copy to the mounted device"?
@Sylvander
You've been away from rox for too long (perhaps), mmmount point is where the connection to the file system takes place (it can be read-only like an *.sfs or writeable like .2fs or similar) - I think puppy uses this internally as well in the /initrd/pup_ro* system (useful for examining things).
An example of 2) would be if you look at some stuff in a .2fs file(system or it can be thought of as a dir), close the .2fs and then try to save something to that closed dir .. it will go to the parent (say the usb stick that .2fs is on, which is still mounted even if the .2fs is not). Usually you'd get a warning (somewhat the same case as with read-only like .sfs and so on), but it might end up elsewhere (like lost&found sometimes, but that is mostly with powerouts or 'unclean' happenings). Think of it as the delivery can't be made since the door (dir) is closed .. so it's left on the doorstep (parent dir).
Bruce B is much more expert in these matters, I only swipe at the fog some on a good day (but maybe the swiping helped?)
You've been away from rox for too long (perhaps), mmmount point is where the connection to the file system takes place (it can be read-only like an *.sfs or writeable like .2fs or similar) - I think puppy uses this internally as well in the /initrd/pup_ro* system (useful for examining things).
An example of 2) would be if you look at some stuff in a .2fs file(system or it can be thought of as a dir), close the .2fs and then try to save something to that closed dir .. it will go to the parent (say the usb stick that .2fs is on, which is still mounted even if the .2fs is not). Usually you'd get a warning (somewhat the same case as with read-only like .sfs and so on), but it might end up elsewhere (like lost&found sometimes, but that is mostly with powerouts or 'unclean' happenings). Think of it as the delivery can't be made since the door (dir) is closed .. so it's left on the doorstep (parent dir).
Bruce B is much more expert in these matters, I only swipe at the fog some on a good day (but maybe the swiping helped?)