From: Jim McCullough <jwmccull@bellsouth.net>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Russell Coker <russell@coker.com.au>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: dpkg-reconfigure xserver-xfree86
Date: Wed, 02 Jun 2004 01:26:45 -0400 [thread overview]
Message-ID: <40BD6515.2090802@bellsouth.net> (raw)
In-Reply-To: 20040601122114.GI8312@lkcl.net
I have noticed the same issue with woody on one build when using
xf86config to build the config file for X. Same system also gave me
errors out the wazzu with handling support for X11-forwarded sessions
over ssh. Rerunning the postinst script usually fixes anything i decide
to monkey around with and break. Plus checking iptables first to make
sure I didnt add any ports that I shouldnt have.
Jim McCullough
Luke Kenneth Casson Leighton wrote:
>russell, hi,
>
>ah ha, you missed one :)
>
>i frequently use dpkg-reconfigure xserver-xfree86 to reconfig X.
>
>and of course a run_init /etc/init.d/kdm restart throws a wobbly
>because the /etc/X11/XF86Config-4 file is owned by
>root:sysadm_r:sysadm_t instead of system_u:...
>
>so!
>
>the setfiles trigger, /etc/dpkg/postinst.d/selinux, needs to
>be re-run after people use dpkg-reconfigure.
>
>[luke smiles widely - or more specifically, turns corners of
> mouth up and shows lots of teeth]
>
>
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-06-02 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 12:21 dpkg-reconfigure xserver-xfree86 Luke Kenneth Casson Leighton
2004-06-02 5:26 ` Jim McCullough [this message]
2004-06-02 7:19 ` Russell Coker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40BD6515.2090802@bellsouth.net \
--to=jwmccull@bellsouth.net \
--cc=lkcl@lkcl.net \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.