From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Questions concerning udev and removeable media, dvd and links
Date: Tue, 29 Jun 2004 07:00:56 +0000 [thread overview]
Message-ID: <20040629070056.GA3614@kroah.com> (raw)
In-Reply-To: <20040629060122.GH14667@gamma.logic.tuwien.ac.at>
On Tue, Jun 29, 2004 at 08:50:52AM +0200, Norbert Preining wrote:
> Hi Greg!
>
> Thanks for the hints:
>
> On Mon, 28 Jun 2004, Greg KH wrote:
> > > Thus, is it possible to do some changes that the partition devnodes are
> > > *always* also created for these kinds of disks, or all?
> >
> > Yes, look at the section in the udev manpage that talks about
> > NAME{all_partitions}.
>
> I have added the following to /etc/udev/rules.d/local.rules:
Why "local.rules"? Try "00-local.rules" instead to make sure that file
is read first.
Anyway, it looks like your rules are not matching the device properly,
because of:
> BUS="scsi", SYSFS{model}="HS-CF", NAME{all_partitions}="sda"
> BUS="scsi", SYSFS{model}="HS-MS", NAME{all_partitions}="sdb"
> BUS="scsi", SYSFS{model}="HS-SM", NAME{all_partitions}="sdc"
> BUS="scsi", SYSFS{model}="HS-SD/MMC", NAME{all_partitions}="sdd"
>
> But restarting udev didn't create the partitions:
> udev[7998]: creating device node '/dev/sdd'
> udev[8000]: creating device node '/dev/sdc'
> udev[8002]: creating device node '/dev/sdb'
> udev[8004]: creating device node '/dev/sda'
> udev[8006]: configured rule in '/etc/udev/rules.d/udev.rules' at line 19 applied, 'hdd' becomes '%k'
No mention of using the local.rules file :(
Are you sure the sda device has a SYSFS{model}="HS-CF" field?
What does:
udevinfo -p /sys/block/sda -a
show?
> > > Where should I configure this.
> >
> > Add a symlink for ttyUSB1 with a rule like:
> > KERNEL="ttyUSB1", SYMLINK="pilot"
>
> ok, thanks.
> BUT: Is it will create it *in advance* so that pilot-xfer etc do not
> bomb out because device is not existent!
pilot-xfer knows better than to die these days. Anyway, creating a link
that points to a device node that isn't there isn't going to help
pilot-xfer out any. This is just the way the hardware works for pilot
devices, sorry.
greg k-h
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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-06-29 7:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 6:01 Questions concerning udev and removeable media, dvd and links Norbert Preining
2004-06-29 6:15 ` Greg KH
2004-06-29 6:50 ` Norbert Preining
2004-06-29 7:00 ` Greg KH [this message]
2004-06-29 7:22 ` Norbert Preining
2004-06-29 7:22 ` Norbert Preining
2004-06-29 7:24 ` Greg KH
2004-06-29 7:29 ` Norbert Preining
2004-09-29 10:17 ` Harald Hoyer
2004-09-29 23:16 ` 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=20040629070056.GA3614@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.