From: Jim Serack <jserack@sy...> - 2008-02-24 14:27:27
I'm still running an FC2 linux.
I run misterhouse under it's own user that automatically startups up in a
vnc server session, that way I can remotely log in to the session and see
what's happening. I wrote a post a long time ago about the security
I remember having to add the port and audio changes to the boot sequence so
the misterhouse user could write to them - can't remember offhand the actual
file I changed - I tried to look but it was a long time ago and it may have
changed but what you need to do is have the root automatically change the
permissions on each restart.
On the separate userid - here is the directory structure I use - I'm happy
with it (currently running 2.103)
------------ from a Previous post on Linux directory structure
1) The ability to completely move forward AND backwards in releases in both
mh and my own code that is logically exhaustive. That is so I can use the
"production system" as development and know for a fact that I can move back
to the last production completely when I am done making mistakes in the
2) Limit the ability for mh (and likely my own code) from doing anything
nasty to the server.
3) Make sure that the mh distribution is pure on my system so I can share
any issues or innovations with others.
How I go about doing this is as follows: I would be interested to hear from
others how they do it.
OS: linux FC 2
Disk structure: software RAID 10 including all volumes (can boot off either
Users: root (admin rights), mrhouse (regular user)
+misterhouse-2.96 (owned by root)
..........>+misterhouse-2.97 (owned by root)
. +misterhouse-x.xx (owned by root)
. +myhouse-1.01 (owned by mrhouse)
. ...>+myhouse-2.01 (owned by mrhouse)
. . +myhouse-x.xx (owned by mrhouse)
. ... |myhouse <-- symbolic link to the active localization
.......... |mh <-- symbolic link to the active mh distribution
mh is run from a startup script as user mrhouse in the myhouse directory
structure which points to the distribution bin/mh.
Now with the distribution being owned by another user ( in this case root)
but the process only having the regular user rights it can not change
anything in the distributions. So say I'm doing some thing experimental and
it changes some state files - I want them to be changed in the active
localization data files directory - not in the distribution so when I go
back to production I can be certain that the mh active distribution is
exactly as it came out of the box and returning to the previous myhouse
directory pointer will return the behaviour to exactly what it was before
The same with the distributions. If I upgrade and I think something is
different I can easily switch back to an earlier distribution and confirm if
that is true.
So that is why I install the distributions as root, and then work as my
regular user, and run the code as a specific regular user.