From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-024-2 for Fedora
Date: Fri, 16 Apr 2004 23:29:44 +0000 [thread overview]
Message-ID: <20040416232944.GB22383@kroah.com> (raw)
In-Reply-To: <407E3F31.3030801@redhat.com>
On Thu, Apr 15, 2004 at 09:52:17AM +0200, Harald Hoyer wrote:
> In udev-024-2, which will appear on fedora development this day I have
> done the following:
>
> o added central config file for udev
> /etc/sysconfig/udev which contains
> -----------------------------------------------
> # set USE_UDEV to yes, if you want to use udev
> #
> USE_UDEV="yes"
>
> # if selinux file attributes
> # should be restored (leave to yes, if unsure)
> UDEV_SELINUX="yes"
>
> # if console permissions (pam_console)
> # should be restored (leave to yes, if unsure)
> UDEV_CONSOLE="yes"
>
> # if dbus messages should be sent
> UDEV_DBUS="no"
> -----------------------------------------------
>
> for that, I had to make /etc/hotplug.d/default/udev.hotplug
> a shell script, which tests for USE_UDEV and then
> exec's udevsend
>
>
> o added dbus, selinux and pam_console support through these scripts:
> /etc/dev.d/default/dbus.dev
> /etc/dev.d/default/pam_console.dev
> /etc/dev.d/default/selinux.dev
>
> dbus.dev calls /usr/sbin/udev_dbus which has Kay's
> latest dbus patch
>
> pam_console.dev calls pam_console_setowner, which is basically
> a modified pam_console_apply, which only modifies one file.
> (no glob on /dev, thus no readdir on /dev every time)
>
> selinux.dev just calls
> # restorecon $DEVNAME
> which makes udev_selinux somehow obsolete.
>
> o set up the config file to use directories for permissions and rules
> /etc/udev/permissions.d/00-udev.permissions
> /etc/udev/rules.d/00-udev.rules
Looks very nice, I've added most of the dev.d files to the udev tarball,
thanks.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-04-16 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 7:52 udev-024-2 for Fedora Harald Hoyer
2004-04-15 12:10 ` Kay Sievers
2004-04-15 12:20 ` Harald Hoyer
2004-04-16 23:29 ` Greg KH [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=20040416232944.GB22383@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/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).