(old)Puppy Linux Discussion Forum

snayak wrote:Hello Friends,

Can we have these big iso files in torrent.

I am interested to use it. However, I am not able to download it because, my Internet goes off time to time. Also I have severe bandwidth limitation per month.

Hope, if we can have all the big files in torrent, we can have a taste of newly released puppies, when we have some leftover bandwidth in the last week of months.

Sincerely,
Srinivas Nayak

wget -c ftp://ftp.nluug.nl/pub/metalab/distributions/fatdog/iso/Fatdog64-611-seamonkey.iso

Terryphi wrote:Where is the resize personal file option in Fatdog?

rcrsn51 wrote:

Terryphi wrote:Where is the resize personal file option in Fatdog?

Menu > Control Panel > System > Fatdog64 Savefile Tool

Terryphi wrote:

rcrsn51 wrote:

Terryphi wrote:Where is the resize personal file option in Fatdog?

Menu > Control Panel > System > Fatdog64 Savefile Tool

This gives a dialog message::

Fatdog64 Savefile Tool can only be used when you run without using a savefile. Reboot your system and specify savefile=none as your boot options.

But I am running with a savefile. I now want to increase the size.

Terryphi wrote:But I am running with a savefile. I now want to increase the size.

Sage wrote:Blwyddyn newydd dda i chi, Terry!

More importantly it does not include a plugin for Quicktime videos. Is one available?

Terryphi wrote:rcrsn51,

Thanks, I had worked it out.

I have to say I prefer BarryK's resize at next boot method.

smokey01 wrote:Fatdog is a little smarter than most puppies thanks to kirk and jamesbond.

Terryphi wrote:

smokey01 wrote:Fatdog is a little smarter than most puppies thanks to kirk and jamesbond.

Perhaps too smart because it makes it more complicated for the user involving two reboots of Fatdog.

Equally annoying is the fact that on normal boot Fatdog does confine the search for a savefile to a specified directory but searches everywhere. Even re-named backup copies are found! I seem to recall BK tried this idea on a version of Quirky but thankfully dropped it quickly.

This parameter tells Fatdog64 where to find the savefile. It can be specified in three different ways:

    savefile=layer:location
    This instructs Fatdog64 to load the savefile from the specified location, and using the layering mode specified.

    savefile=none
    This instructs Fatdog64 not to use any savefile at at all. In earlier version of Fatdog, this parameter is called pfix=ram)

    savefile=ask
    This instructs Fatdog64 to ask for the savefile details during boot time. At boot time, you can either specify none or layer:location.

You can choose layer from one of the following:

    direct
    This tells Fatdog64 to use the savefile directly - any writes will go direct to the savefile.

    ram
    This tells Fatdog64 to use the RAM layer. Any writes will first be stored and collated in RAM, to be periodically flushed to the actual savefile.

smokey01 wrote: This is worth a read:
[url]file:///usr/share/doc/faqs/boot-options.html[/url]
I agree it can be a little frustrating at first but it's worth persevering with, many don't, their loss, I guess.

Cheers

Terryphi wrote:Equally annoying is the fact that on normal boot Fatdog does confine the search for a savefile to a specified directory but searches everywhere. Even re-named backup copies are found! I seem to recall BK tried this idea on a version of Quirky but thankfully dropped it quickly.

search=n

Control searching of possible savefiles in subdirectories. This parameter tells the boot process "at which subdirectory level in a given path, searching for savefiles is to end". If n is not specified it defaults to 1. Fatdog will search for fd64save* (or whatever filename you specify in the savefile parameter) starting in the directory you specified there too (default is root directory).

If, for example, you want it to search in subdirectories up to 3-level deep, specifiy search=3 instead. If more than one savefile matching the pattern if found, they will be listed and you will be asked to choose the one to use.

Search is only performed when savefile specifies a location of "local" or "usb". Other location types do not perform searching regardless of this parameter. We generally recommend not to depend on this parameter on as searching slows down the boot process; it is always better to specify the exact location of the savefile (using device / uuid / label locations) if possible.

nooby wrote:When it boots up it give an error message
that I fail to write down it is shown too briefly
for me to remember.

It fails to find a lib file due to no such directory?
Can one looks at that in some tempory file somewhere
so I can quote it here and also to compare if it is same
message in the other computer that also works well with FD.

Another questions. All these Samba servers they only work
if I tell them to or are they always active in the background by default?