> Xorg needs access to the display hardware (mmap device memory) so it
> needs to be root. This is just the way it is. :)
on all my desktops suid for /usr/bin/Xorg is unnecessary.
Probably because X server is started by *dm as root anyway?
nope.
/usr/bin/X was, at least partially, the right
> > Xorg needs access to the display hardware (mmap device memory) so it
> > needs to be root. This is just the way it is. :)
>
> on all my desktops suid for /usr/bin/Xorg is unnecessary.
Probably because X server is started by *dm as root anyway?
signature.asc
Description: This is a digitally s
> "aa" == arne anka writes:
>> Xorg needs access to the display hardware (mmap device memory) so
>> it needs to be root. This is just the way it is. :)
aa> on all my desktops suid for /usr/bin/Xorg is unnecessary.
Yep, it's X that must be setuid root to access root-only writabe files :).
-
Xorg needs access to the display hardware (mmap device memory) so it
needs to be root. This is just the way it is. :)
on all my desktops suid for /usr/bin/Xorg is unnecessary.
___
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
ht
On Sun, 2009-01-11 at 20:04 +0100, arne anka wrote:
> i just restartet X (or at least tried so) but had to notice that
> /usr/bin/Xorg has to be set uid root to work.
> i am not that famliar with the intricacies of suid and X bot it seems odd
> to me that such a measure has to be be taken just
i just restartet X (or at least tried so) but had to notice that
/usr/bin/Xorg has to be set uid root to work.
i am not that famliar with the intricacies of suid and X bot it seems odd
to me that such a measure has to be be taken just be make X get up and
running.
is this something in my con