Cliff Albert wrote:
 
> >/usr/bin/arachne
> /usr/sbin/arachne... as svgalib executables have to be suid root. arachne
> should reside in /usr/sbin..

I am not yet sure how I am going to overcome this... I have heard that
SVGAlib gives up root privileges just after acquiring console... maybe I
will manage to write some suided arachne launcher (open source, so
everyone can check it), and launch Arachne just after everything is
initialized, but with normal uid... I want any user to be able to launch
Arachne anyway, so even for suided executabls, Arachne will setuid back
to user's normal ID, not only for security reasons, but to be able to
read personalized files in /home/user/.arachne/
 
> >/usr/ will be replacable by /usr/local/ or /opt/arachne/, or even
> >~/arachne/ if necessary. It is just recommended location.

No... Arachne won't be open source anytime soon....
 
> >Linux Arachne definitely won't share current DOS style directory
> >structure, it will allow (but not force) you to make it integral part of
> >your system, which is standard in Linux world....
> 
> System-wide configuration should be certainly added.. also a System-wide
> fixed configuration for proxy settings and so on..

I think what I will probably want to do is copy of system wide
configuration when new user profile is created.... it will be relatively
hard to read two configuration files and save only changes done to user
part of config file... hmmmmmmmm.....
it is not really impossible. If more people want Arachne to use BOTH
system wide and local configuration... but then user won't be able to
override default settings!

What about some rule like "touch ~./arachne/config; chmod a-x
~./arachne/config" so it is empty file, and set it read-only, so Arachne
will read global config each time, and won't be able to store it as
local config ?

Reply via email to