linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg KH <greg@kroah.com>,
	linux-hotplug-devel@lists.sourceforge.net,
	SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: udev has had udev_selinux removed - argh!
Date: Thu, 29 Jul 2004 22:14:34 +0000	[thread overview]
Message-ID: <20040729221434.GP9950@lkcl.net> (raw)
In-Reply-To: <1091133915.3283.25.camel@localhost.localdomain>

On Thu, Jul 29, 2004 at 10:45:15PM +0200, Kay Sievers wrote:
> On Thu, 2004-07-29 at 21:40 +0100, Luke Kenneth Casson Leighton wrote:
> > hello greg,
> > 
> > well i tried compiling udev-024 and it was a pain, plus i got udev-030
> > to work and decided it wasn't worth the effort, the users can
> > JustLiveWithIt(tm) until it's fixed properly.
> > 
> > greg, do you have any objections to me doing a "proper" job, which
> > is to patch udev-add.c to use some libselinux1 functions that will
> > "prime" the selinux module with the right context, such that
> > when the node (and the symlink!) are individually created, they
> > are individually created with the correct context - there and then.
> 
> How do we solve the klibc build, if selinux is used internally? We've
> moved it to a external program for that reason.
 
  if i understand you correctly (i don't know what klibc is):

  i'd recommend leaving it up to distributions to decide
  to create (or not) two _separate_ packages, se_udev and udev.

  if you can at least provide an option --with-selinux in the
  configure script, distros can make the decision.

  l.



-------------------------------------------------------
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

  reply	other threads:[~2004-07-29 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29  9:47 udev has had udev_selinux removed - argh! Luke Kenneth Casson Leighton
2004-07-29 18:50 ` Greg KH
2004-07-29 20:40   ` Luke Kenneth Casson Leighton
2004-07-29 20:45 ` Kay Sievers
2004-07-29 22:14   ` Luke Kenneth Casson Leighton [this message]
2004-07-30  8:57 ` Marco d'Itri

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=20040729221434.GP9950@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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).