You've really had to work this point in the forum!kirk wrote:rian,
Firefox normally runs as user spot in Fatdog64, so can only write to folders owned by spot (spot, Downloads). To run as root open a terminal and type firefox or drag /usr/bin/firefox to the desktop.
.
Let's have bit of a go at it, then. Here's my experience, in case it helps anyone out there.
I prefer to put downloads outside the personal save file on the actual harddrive.
Namakura (aka firefox) does not use symlinks to directory outside of spot.
Symlinks are not seen as links, but as files. Mounted drives are also refused. This applies to up and down loads.
My workaround is to have a script (movit):
# #!/bin/sh
# if ls /root/spot/Downloads/* 1> /dev/null 2>&1; then
# mv /root/spot/Downloads/* /mnt/home/fd64-500/Downloads/
# echo Moved Spot\'s \/Downloads to fd64-500\/Downloads -- outside pupsave.
# else echo No files to move in Spot\'s \/Downloads at this time.
# fi
# exit
[nb. each line has been prefixed with a hash mark. Remove leading # to use code.]
It resides in /usr/bin and can work from /root/my-applications/bin, too.
I call movit from the CLI and /etc/rc.d/rc.shutdown (after script displays shutdown message). Thus downloads can be moved manually or left to be moved at shutdown automatically.
From the terminal it gives a message explaining what it did.
The result message is suppressed by the "less verbose" line at the top of rc.shutdown so won't clutter your shutdowns.
This 'solves' a downloads issue, not the uploads difficulty.
Perhaps there's even a better way to direct downloads outside of the personal save file?
I strongly support sandboxing web-browsers, especially graphical multimedia browsers.
I would try to copy the method when installing browsers in Puppy everywhere.
Kind regards,
moB