Double post sorry. I want to know more. I tested Lupu 528 but found no
Fido.

Do we have some list of which puppies that have Fido?

Wary 514?
Snow puppy 20.
Polar puppy 5
Slacko Beta II

These are the only ones one can test Fido on?

Get going again folks! :Friendly Smile:
To not disturb the flow here I try to only be active in my own thread
about fido and spot for noobs and beginners.
http://www.murga-linux.com/puppy/viewtopic.php?t=67885_________________I use Google Search on Puppy Forum
not an ideal solution though

BarryK wrote:
I don't see why having /root as fido's home is a problem

Of course I realise why fido was sharing root's HOME.. for size, but I reckon if users want the added "security" (note loose use of term) of a "user" account then they have to pay the price, both in kilobytes and time. (my password is 4 chars.. not very "secure" eh? It's certainly taking it's toll on those 4 corresponding keys!)

If someone had the time maybe it could be determined what dotfiles in /root actually get modified during a typical session, so that those that don't can be just symlinked back to root from the $HOME directory of fido or whatever username is being used. That might be one idea to save space.

I find that if you are only running firefox as a restricted user then the amount of writable files at issue aren't so great. Mainly they are in $HOME/.mozilla directory (firefox profile etc) (and the files .gtk-bookmarks, .gtk-custom-papers and .gtkrc-2.0 need to be copied from /root to $HOME to keep the theme if it differs from default).

Someone that knows enough about unionfs, aufs etc might be able to figure out a way to mirror the root directory with a writable one for a restricted user. which may or not be an idea worth looking at. Sorry don't know enough to do this, if it can be done at all.

... I would like to get the current implementation of Fido fixed such that it works as painlessly as possible. This at least gives the "root" nay sayers no excuse not to at least try Puppy. If it's not fixed then Fido will be disabled in Slacko.

I'm at work just now and don't have a copy of Puppy to look at. However, as far as I remember user fido is by default a member of the group users.

That being the case, getting programs (including config files for these programs to work) with fido could be pretty much achieved by:

giving group "users" group-ownership to all relevant files in /root and /tmp, and read, write and execute permissions to directories /root and /temp, so that members of group "users" have rights to create/modify files in these directories (I did something like that to get Precord working with fido in a test I did at home).

Then any normal user (spot or whoever created) could run any app currently available for Puppy if these "normal" users were made to be members of group "users"

Having said that, I don't personally like any group (or fido for that matter) having such rights and would prefer fido to have its own home directory (/home/fido), its own copies of relevant program config files in there, and Puppy scripts/gtkdialogs and so on to eventually be modified accordingly ...

My problem with all this Fido stuff is that my computer gets used by young grandchildren- so I need things to be arranged so that if one of them boots up the computer, they are unable, without my password, to wreck things. Like in Debian or other distros that need administrator privileges to change or delete vital software.

You set up one version of puppy that you use that are password
protect so it does not even boot without your username and password.

Another puppy for guests but there it should be set up with Fido.
But the Devs don\t seem to be happy about Fido.
Too many details to take care of, too many unknown complications?_________________I use Google Search on Puppy Forum
not an ideal solution though

...
Sounds like a KISS solution does it not? I know nothing and have no
idea how to test it...

No, it is KSASNSAA: Kept Simple And Surely Not Sure At All

Test yourself:

Open a virtual console by klicking on the icon labeled "Console"
Type into this :
su spot
and press the Enter key

Then your are user spot (but on this one console only)
You can start application if you know their name. 2 examples:
Let us start rox and geany.
Here is how this is looking on my system:
# su spot
# rox
#
** (ROX-Filer:5938): CRITICAL **: Unable to save '/root/.config/rox.sournet/ROX-Filer/panels.new'

So what was/where he proposing?
Does he actually know more than Barry about how Puppy works
or did he misunderstand or not realize that Puppy being a special
version of a single user Linux that it would not act like his other linux OS?

Well I go the bed now and will read his answer tomorrow hopefully.

Will be interesting.
Thanks for explaining to me and giving examples. I did try Fido
and Spot too and I barely survived. I felt so intimidated not getting
a thing about how to get things going. I am a confused user._________________I use Google Search on Puppy Forum
not an ideal solution though

fix:
change line 8 of /etc/sudoers
from
#120110 added /usr/sbin/delayedrun to SYSTEM category. also, see sudo line added to script.
to
# 120110 added /usr/sbin/delayedrun to SYSTEM category. also, see sudo line added to script.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum