| 1 |
On Fri, Dec 16, 2016 at 3:12 PM, Ian Zimmerman <itz@×××××××.net> wrote: |
| 2 |
> On 2016-12-16 14:16, Rich Freeman wrote: |
| 3 |
> |
| 4 |
>> If you don't have USE=-suid on your xorg-server package, then X is |
| 5 |
>> probably running suid root. |
| 6 |
>> |
| 7 |
>> In order to not have it run this way you need support for kernel |
| 8 |
>> modesetting. I was surprised when I found out that X11 even worked |
| 9 |
>> that way (we're talking late 90s here). It seems a bit like running |
| 10 |
>> pppd as root so that it can directly talk to a UART because you have |
| 11 |
>> an aversion to using /dev/ttyS*. In any case the kernel devs have |
| 12 |
>> generally been making the move to kernel modesetting so that your |
| 13 |
>> device drivers actually are in the kernel and not in random userspace |
| 14 |
>> programs (I'm all for microkernels, but not like this). |
| 15 |
>> |
| 16 |
>> If you don't have kernel modesetting enabled then X11 won't be able to |
| 17 |
>> run with -suid set. Google for gentoo kernel modesetting for a guide |
| 18 |
>> on how to enable it on most modern hardware. |
| 19 |
> |
| 20 |
> There's another dimension to this dilemma: if one wants to avoid using a |
| 21 |
> display manager and start X server directly (or via startx or similar), |
| 22 |
> then the X server must be suid for that reason, even with KMS. |
| 23 |
> Unfortunately. |
| 24 |
> |
| 25 |
|
| 26 |
I've never had issues starting X using startx on a radeon using kms, |
| 27 |
and my server is not suid. Offhand I couldn't say why you've had |
| 28 |
issues with it, I haven't really looked into it in detail. |
| 29 |
|
| 30 |
-- |
| 31 |
Rich |
Archives