From: Greg KH <greg@kroah.com>
To: Scott James Remnant <scott@netsplit.com>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev LABEL not working: sysfs_path_is_file: stat() failed
Date: Mon, 22 Dec 2003 12:40:24 -0800 [thread overview]
Message-ID: <20031222204024.GF3195@kroah.com> (raw)
In-Reply-To: <1072090725.1225.19.camel@descent.netsplit.com>
On Mon, Dec 22, 2003 at 10:58:45AM +0000, Scott James Remnant wrote:
> One question though, it only ever seems to create a device for the
> actual usb-storage disk and not the partition. Is there some magic to
> create the partition device instead?
Do you have a partition show up in /sys/block? If not, then udev will
not create it. It works here for my usb-storage devices that have
partitions on them.
thanks,
greg k-h
next prev parent reply other threads:[~2003-12-22 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 1:00 udev LABEL not working: sysfs_path_is_file: stat() failed Scott James Remnant
2003-12-22 9:23 ` Greg KH
2003-12-22 10:58 ` Scott James Remnant
2003-12-22 20:40 ` Greg KH [this message]
2003-12-23 7:29 ` Scott James Remnant
2003-12-23 22:13 ` Greg KH
2003-12-28 9:11 ` Scott James Remnant
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=20031222204024.GF3195@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@netsplit.com \
/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