From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] The Mandriva Collection
Date: Wed, 04 Jan 2006 01:20:59 +0000 [thread overview]
Message-ID: <20060104012059.GA12798@vrfy.org> (raw)
In-Reply-To: <m3k6eaqki0.fsf@dynamo.mandriva.com>
On Tue, Jan 03, 2006 at 08:55:23PM +0100, Olivier Blin wrote:
> Kay Sievers <kay.sievers@vrfy.org> writes:
>
> >> We've also moved udevinfo in /bin, since it is needed early at boot to
> >> apply permissions on device nodes, before /usr is mounted. It uses the
> >> pam_console.dev agent, that we install as /lib/udev/pam_console.dev
> >
> > You probably just want to add the symlinks to the event environment?
>
> Yes, it would be better.
I added this after the last mail, it's DEVLINKS in the current udev.
> > Hey, but matching on device node names with pam_console in a udev environment
> > sounds pretty strange anyway...
>
> What's that strange?
You can name devices whatever you like with udev and having a separate
config file in /etc which matches on device names is just silly.
Infrastructure to provide access to devices must know the kind/class of
device what pam_console can't know. We are thinking about integrating that
functionality in HAL as SUSE already does, but not in away we would like
to see upstream. Todays systems must also support user switching
what pam_console's simple chgrp() can't provide. You want to have ACL's on
device nodes like we do with resmgr. We will work on
integrating/replacing resmgr into/with DBUS/HAL, when the needed SUSE kernel
patches for ACL's on tmpfs show up in the upstream kernel.
> >> We also provide a script to convert hotplug usermaps to udev rules.
> >> Camera and scanners aren't yet handled by hal, and some drivers still
> >> don't use the standard way to load firmwares in the kernel. See:
> >> http://qa.mandriva.com/twiki/bin/view/Main/Udev#Hot_plug_usermaps
> >
> > That certainly belongs to HAL. There should be almost no overlap between
> > the need for "user permissions" and system without HAL these days.
>
> Right, gphoto stuff is now handled in hal, it's the way to go.
Fine.
> >> By the way, the ueagle-atm author want to use fxload in this new
> >> driver, is there any good alternative? A ticket is opened there:
> >> https://gna.org/task/?funcÞtailitem&item_id'08
>
> But what for these fxload stuff? We still need some usermaps
> equivalent (i.e. apply the same action for different device IDs).
How many map entries we are talking about?
> >> Finally, we added some agents for ieee1394, net, and input (all copied
> >> from the old hotplug agents).
> >
> > IDE and input should get MODALIAS soon.
>
> Yep, that should remove some more non-standard patches/scripts.
Yes, I think that are the last ones that are widely used.
> >> For a complete list of patches, scripts, rules, and packaging files,
> >> see: http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/SPECS/udev/
> >
> > Don't you have the nice persistent /dev/disk rules? But I still can see
> > devfs disk crap, bah ... :)
>
> I happen to use theses nice symlinks as well, in the Mandriva package,
> we use the etc/udev/persistent.rules file from the udev tarball.
Ah nice, that's great.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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:[~2006-01-04 1:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 17:43 [PATCH] The Mandriva Collection Olivier Blin
2005-12-12 18:21 ` Marco d'Itri
2005-12-12 18:25 ` Scott James Remnant
2005-12-12 18:37 ` Olivier Blin
2005-12-12 18:47 ` Marco d'Itri
2005-12-12 19:13 ` Olivier Blin
2005-12-12 19:17 ` Marco d'Itri
2005-12-12 19:44 ` Olivier Blin
2005-12-12 21:45 ` Olivier Blin
2005-12-13 0:49 ` Marco d'Itri
2005-12-13 5:08 ` Kay Sievers
2005-12-21 17:46 ` Olivier Blin
2005-12-21 17:47 ` Marco d'Itri
2005-12-21 17:51 ` Olivier Blin
2005-12-21 18:04 ` Marco d'Itri
2006-01-03 19:55 ` Olivier Blin
2006-01-04 1:20 ` Kay Sievers [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=20060104012059.GA12798@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).