linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: xsdg <xsdg@freenode.org>
To: linux-hotplug@vger.kernel.org
Subject: renaming causes incorrect device creation
Date: Wed, 17 Mar 2004 02:14:53 +0000	[thread overview]
Message-ID: <20040317021453.GA13348@perl.xsdg.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

Normally, when I plug in my camera, I see (in /udev/):

brw-------    1 root     root       8,   0 2004-03-17 01:53 sda
brw-------    1 root     root       8,   1 2004-03-17 01:53 sda1

I then add to udev.rules:
BUS=3D"scsi", SYSFS{model}=3D"Sony DSC        ", NAME=3D"removable/camera%n"

after adding, I see:
brw-------    1 root     root       8,   0 2004-03-17 01:55 camera
crw-------    1 root     root      21,   1 2004-03-17 01:55 camera1

I'm starting off with the default installed udev.rules.  This also occurs when
I try to get my key drive going with:

BUS=3D"scsi", SYSFS{vendor}=3D"LEXAR   ", SYSFS{model}=3D"JUMPDRIVE PRO   ", NAME=3D"removable/jdrive%n"

brw-------    1 root     root       8,  16 2004-03-17 01:31 jdrive
crw-------    1 root     root      21,   2 2004-03-17 01:31 jdrive2

Also note that jdrive2 should not exist; only disc and generic exist in devfs, 
and I set the drive up _without_ partitioning (mkfs.vfat /udev/sda)


-- 
| If you have to do something wrong to get what you |
|   want, it's really not worth having.             |
) http://www.cuodan.net/~xsdg/    xsdg@freenode.org (


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-03-17  2:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17  2:14 xsdg [this message]
2004-03-17  7:44 ` renaming causes incorrect device creation Bob Barry
2004-03-17  8:33 ` Bob Barry

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=20040317021453.GA13348@perl.xsdg.org \
    --to=xsdg@freenode.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).