From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: /sbin/udev block and /bin/cat: /proc/ide/hd[a-h][1-10]/media: No such file or directory
Date: Fri, 06 Feb 2004 19:40:12 +0000 [thread overview]
Message-ID: <20040206194012.GA5928@vrfy.org> (raw)
In-Reply-To: <1075922647.29575.8.camel@moen.bioinf.mdc-berlin.de>
On Fri, Feb 06, 2004 at 05:23:12PM -0200, Frédéric L. W. Meunier wrote:
> On Thu, 5 Feb 2004, Bob Barry wrote:
>
> > On Wed, 04 Feb 2004 20:24, Juergen Rose wrote:
> > > during the initilization of udev (/etc/init.d/udev start) I get a lot
> > > messages like "/bin/cat: /proc/ide/hda1/media: No such file or
> > > directory".
> >
> > I see the same thing, and I've been watching for an answer.
> >
> > I use the rule for cdrom from the tarball /etc/udev/udev.rules:
> > BUS="ide", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom", NAME="%k", SYMLINK="cdrom"
> >
> > Links exist in /proc/ide to hda, hdc and hdd. After startup, the cat works:
> > > /bin/cat /proc/ide/hd[acd]/media
> > disk
> > cdrom
> > cdrom
> >
> > Is /proc/ide being used before it is built?
>
> I'm also seeing it, even running it after the system boots.
>
> /bin/cat: /proc/ide/hda1/media: No such file or directory
> /bin/cat: /proc/ide/hda10/media: No such file or directory
> /bin/cat: /proc/ide/hda11/media: No such file or directory
> /bin/cat: /proc/ide/hda12/media: No such file or directory
> /bin/cat: /proc/ide/hda2/media: No such file or directory
> /bin/cat: /proc/ide/hda5/media: No such file or directory
> /bin/cat: /proc/ide/hda6/media: No such file or directory
> /bin/cat: /proc/ide/hda7/media: No such file or directory
> /bin/cat: /proc/ide/hda8/media: No such file or directory
> /bin/cat: /proc/ide/hda9/media: No such file or directory
> /bin/cat: /proc/ide/hda3/media: No such file or directory
>
> Is it because I also have devfs enabled ?
No it's cause you try to read 'media' on an partition.
Just ignore it or use:
BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom", NAME="%k", SYMLINK="cdrom"
It will ignore all kernel names ending with a digit.
hope that works for you,
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
next prev parent reply other threads:[~2004-02-06 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 19:24 /sbin/udev block and /bin/cat: /proc/ide/hd[a-h][1-10]/media: No Juergen Rose
2004-02-05 17:23 ` /sbin/udev block and /bin/cat: /proc/ide/hd[a-h][1-10]/media: No such file or directory Greg KH
2004-02-05 20:29 ` Bob Barry
2004-02-06 14:51 ` /sbin/udev block and /bin/cat: /proc/ide/hd[a-h][1-10]/media: Juergen Rose
2004-02-06 19:23 ` Frédéric L. W. Meunier
2004-02-06 19:40 ` Kay Sievers [this message]
2004-02-06 19:54 ` Frédéric L. W. Meunier
2004-02-06 20:10 ` /sbin/udev block and /bin/cat: /proc/ide/hd[a-h][1-10]/media: No such file or directory Greg KH
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=20040206194012.GA5928@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).