From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Chris Babcock <cbabcock@luthresearch.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>, linux-kernel@vger.kernel.org
Subject: Re: [SE/Linux] warning about debian hotplug package 20040329-9!
Date: Tue, 13 Jul 2004 11:19:08 +0100 [thread overview]
Message-ID: <20040713101908.GB3732@lkcl.net> (raw)
In-Reply-To: <2500.68.6.187.64.1089667018.squirrel@mxlx1.surveysavvy.com>
On Mon, Jul 12, 2004 at 02:16:58PM -0700, Chris Babcock wrote:
> So then what if (horror of horrors) somebody puts "/var" on a usb disk
> device. (or some other type of device initialized by hotplug?)
or an nfs-mounted partition.
the suggestion in that case that i received by one of the hotplug
developers / people-monitoring-debian-bugs-for-hotplug was that you
should modify the /etc/hotplug scripts to use /devfs/shm/tmp instead,
assuming that you have a debian initrd.
now, on SE/Linux that isn't possible, and the reason isn't entirely
clear, but i believe that the access permissions to the tmpfs
created by the debian initrd are such that when the umount tmpfs
occurs, it actually _does_ unmount it.
on a standard debian/linux system (no selinux kernel) the initrd
scripts attempt, amongst other things, to mount various filesystems
and these are successful, but they are not _un_mounted properly later
on.
anyway, i digress: the idea i came up with was that the debian
package be modified such that it's possible to specify the
state directory, even if that's one of a list of possible
locations e.g. choose one: /etc/hotplug, /etc/hotplug/run,
/var/run/hotplug, /devfs/shm/tmp, other.
consequently, if this were to be implemented, at least people mad
enough to use usb disks or nfs mounted stuff, they'd be able to
at least get going without having to hack the source of hotplug.
> > dear selinux and linux kernel,
> >
> > i am after some assistance in clarifying how hotplug works, with
> > a view to solving an issue with SE/Linux where the default
> > SE/Linux policy is to deny write permission to /etc/hotplug
> > (with good reason) but the hotplug package is presently demanding
> > write permission.
> >
> > a simple request for a change to writing to /var/state/hotplug
> > instead has thrown up a number of issues with kernel (2.6.6)
> > hotplugging and i would greatly appreciate some confirmation
> > and some assistance.
prev parent reply other threads:[~2004-07-13 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040709201413.GB3168@lkcl.net>
[not found] ` <200407112050.08313.russell@coker.com.au>
[not found] ` <20040711112237.GI3390@lkcl.net>
[not found] ` <40F16D8B.4010601@bellsouth.net>
2004-07-11 20:50 ` Luke Kenneth Casson Leighton
2004-07-12 21:16 ` Chris Babcock
2004-07-13 10:19 ` Luke Kenneth Casson Leighton [this message]
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=20040713101908.GB3732@lkcl.net \
--to=lkcl@lkcl.net \
--cc=cbabcock@luthresearch.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®