From: Mathieu Segaud <matt@minas-morgul.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Bug] udev creates nodes in the wrong place.
Date: Sun, 11 Jan 2004 12:50:02 +0000 [thread overview]
Message-ID: <87zncusl8l.fsf@minas-morgul.org> (raw)
In-Reply-To: <87fzemu1t0.fsf@minas-morgul.org>
Kay Sievers <kay.sievers@vrfy.org> writes:
> On Sun, Jan 11, 2004 at 01:06:51PM +0100, Mathieu Segaud wrote:
>> But, mouse0 and mouse1 only are in /udev/input whereas mouse2 and
>> mouse4 (?) are created directly under /udev.
>
> Plese have look at the relevant sysfs files.
> It's easy to look with "tree /sys" if there is any difference between
> mouse0/1 and mouse2/3.
> Oh, and please build udev with "make DEBUG=true" and post the relevant syslog.
DEBUG option gave me the answer:
My USB mouse gave 2 devices: event4 that is substituted with
mouse%n, so mouse4 and another which is mouse2 by matching a rule
Just replacing:
LABEL, BUS="usb", SYSFS_product="Microsoft 3-Button Mouse with IntelliEye?", NAME="mouse%n"
with
LABEL, BUS="usb", SYSFS_product="Microsoft 3-Button Mouse with IntelliEye?", NAME="input/%k"
makes the correct behaviour.
>
>
>> input/*:root:root:660
>> gives 660 access rights to the directory, too, which I guess is not
>> what we want; I as a normal user can't walk into it and it can be
>> relevant for snd/* devices which I, as audio group member, should be
>> allowed to access.
>> snd/*:root:audio:660 prevents me to access them
Well now, it seems to work... :)
In fact, it did not work when I ran it for the first time
but it works with the udev I recompiled (no reason just enabled
debugging this time)
>
> What is the RULE for snd ?
> And the syslog would help here too.
>
> Kay
Sorry for the annoyance.
Thanks.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> 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
>
--
Mathieu Segaud
> Yes *please*! Finally we could introduce proper support for 64-bit
> inode numbers too!
Right. As soon as userland is audited for places where it uses int
for storing inode numbers - just a couple of months after MS fixes
all security holes in their software. By then we'll need 128bit time_t,
though...
- Al Viro on linux-kernel
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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-01-11 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 12:06 [Bug] udev creates nodes in the wrong place Mathieu Segaud
2004-01-11 12:16 ` Kay Sievers
2004-01-11 12:50 ` Mathieu Segaud [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=87zncusl8l.fsf@minas-morgul.org \
--to=matt@minas-morgul.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).