> Have an xterm open which is su'd to root, then work in there for
> whatever needs root access.  Any X applications started from a root
> shell will be running as root.  You can run most X apps as root (but
> netscape refuses to run)
> 
> Another option is to log in as root (bad idea but its how windows works
> all the time)

All these suggestions don't cut it as they fail to address the most
pressing issue of X11 connect permissions not being carried over by su.

It would then also require to set localhost as being allowed to connect
for everyone (bad idea), and to edit #DISPLAY to be :0. Allowing 
localhost by default sucks.

Try to use kdesu instead. Also, your distro should have a "root shell"
or "root xterm" or similar somewhere in your KDE menues. Mine has, it
works extremely well and beginners never need to know about xhost or
$DISPLAY. At least not for editing lilo.conf, which is a very good
thing.

Volker

-- 
Volker Kuhlmann                 is possibly list0570 with the domain in header
http://volker.orcon.net.nz/             Please do not CC list postings to me.

Reply via email to