> Though, i just did this for diagnostic reasons.
if you learn the system runs better (or perfectly) while logged into
KED/Gnome/etc as root, how does that affect your diagnostic process?
that is, since running normally as root is NOT an option, in what way
are you then better prepared to fix the problem you are diagnosing
if it happens to run perfectly in root, which you booted to only for
what if runs worse as root? then what?
> Its an experimental system im working on.
and, since you now know you may have accidentally damaged your system
in a number of different, and non-obvious ways, by logging into
KDE/Gnome/etc as root it certainly is both experimental and of
then only way to ensure a stable system which has not been damaged by
logging into KDE/Gnome/etc as root is to never do that… (which is
easy to do since there is NEVER any administrative task–including
diagnostic reasons–which requires logging in as root, ever)
> But i actually got a new fault with rct, after no changes at all:S
but, you don’t actually if you made “no changes at all” while logged
in as root–that is the point of not logging into the GUI as root.
btw, i have no idea what “rct” is…
> When i start it i get a windows window with fault:
> Error trapper:
> Error location : Windows unknown driver
> Why is that?
no idea, i never run Windows, ever…
perhaps you broke something while logged into the GUI as root–as
mentioned, don’t do that…
DenverD (Linux Counter 282315)
posted via NNTP w/TBird 220.127.116.11 | KDE 3.5.7 | openSUSE 10.3
18.104.22.168-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio