SELinux mystery

[Joe Smith]

Daniel J Walsh wrote:
> You redirected stdout/stderr to a file labeled user_home_t and started
> the Xserver.  From that point on ...

Wow. Interesting. So SELinux is actually checking for accesses that 
haven't occurred yet? Simply having modprobe run and inherit an open 
file descriptor that "looks out of place" (a file in my a user dir) is 
enough to trigger a warning (SELinux hasn't actually denied any access, 
right?). Pretty slick actually, even if it is mysterious.

Thanks so much for explaining!

<Joe