From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>,
Linux Hotplug Dev List
<linux-hotplug-devel@lists.sourceforge.net>
Subject: Re: udev
Date: Mon, 09 Aug 2004 12:36:53 +0000 [thread overview]
Message-ID: <20040809123653.GG3868@lkcl.net> (raw)
In-Reply-To: <20040808224737.GA3825@lkcl.net>
these additions make it hardly necessary to add anything stackingly
significant to the selinux policy files.
in particular, no special exceptions for /dev/* because it's already
device_t by default (fscontext=....default_t)
no special stuff like having to create a udevfs_t and then going
through the policy looking for ways to add support for it *whew*.
no need to add "allow .... tmpfs_t or shmfs_t ... " stuff.
i _have_ had to add a few bits and pieces to allow init_t and initrc_t
access to /dev prior to /etc/init.d/udev starting.
i wish i knew if it was okay to swap the order of /etc/init.d/modutils
and /etc/init.d/udev.
l.
On Sun, Aug 08, 2004 at 11:47:37PM +0100, Luke Kenneth Casson Leighton wrote:
> okay, combination of patches and mods.
>
> 1) xattr one which is up on http://hands.com/~lkcl/selinux/2.6.6
>
> 2) remove stuff which tells mount 'fscontext=' option to bog off
> if it supports xattrs.
>
> don't know if this patch is needed, don't care either.
> ItWorksForMe(tm) hey for all i know i missed out an option
> which makes it unnecessary to stop fscontext=....device_t
> from working.
>
> 3) make mount take option fscontext=....device_t .... /dev
>
> 4) patch /etc/init.d/udev _and_ /etc/init.d/modutils to call a
> little program /sbin/restoredevicefiles.
>
> the horrible hack to make extra nodes in /dev needs to have
> a restorecon done on each node so created: quickest way is
> to do them all at once.
>
> 5) restoredevicefiles greps everything in /dev hey i just noticed
> it only does /dev/* not /dev/*/* oh well.
>
> i also had to copy /usr/bin/cut to /bin/cut hey there's probably
> a way to do it with sed or something.
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-08-09 12:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 22:47 udev Luke Kenneth Casson Leighton
2004-08-09 12:36 ` Luke Kenneth Casson Leighton [this message]
2004-08-09 12:40 ` udev Marco d'Itri
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 18:28 udev Greg KH
2005-08-11 18:29 ` udev Mike
2005-08-11 19:16 ` udev Greg KH
2005-08-11 19:21 ` udev Mike
2005-08-11 19:36 ` udev Kay Sievers
2005-08-12 15:33 ` udev Mike
2005-08-12 18:03 ` udev Greg KH
2009-11-02 11:10 ` udev Oleg Puchinin
2009-11-02 11:50 ` udev Oleg Puchinin
2009-11-02 14:35 ` udev Andrey Borzenkov
2009-11-02 16:57 ` udev Alan Jenkins
2011-03-22 19:48 ` Udev Paulo Eliseu Weber
2011-03-22 19:58 ` Udev Kay Sievers
2010-08-18 9:51 UDEV Тима
2010-08-18 12:49 ` UDEV Greg KH
2010-08-19 15:27 ` UDEV Greg KH
2010-08-24 12:50 ` UDEV Greg KH
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=20040809123653.GG3868@lkcl.net \
--to=lkcl@lkcl.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).