public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] confused udev?
Date: Thu, 17 Nov 2005 11:14:29 -0700	[thread overview]
Message-ID: <7573e9640511171014p1b5dd90ay29e841abd7310bbe@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0511171737200.7664@weber.math.ist.utl.pt>

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> On Thu, 17 Nov 2005, Richard Fish wrote:
> >
> > Can you post your current rules.  Also, don't forget Dirk's suggestion
> > regarding BUS=="usb" instead of scsi.
> >
> > You could use the SYMLINK target instead of changing the name.  Something like:
> >
> > BUS=="usb" ... NAME="%k", SYMLINK="plextor_memstick%n"
> >
> > This would keep the default sdX device nodes, but give you symlinks
> > for your persistent names.
> >
> > -Richard
> >
> >
> Current:
>         BUS=="scsi", SYSFS{vendor}=="PLEXTOR*", SYSFS{model}=="PlexFlash-2*", NAME="%k", SYMLINK="plextor_memstick%n"
>         BUS=="scsi", SYSFS{vendor}=="Maxtor 6*", SYSFS{model}=="L250R0*", NAME="%k", SYMLINK="external_hd%n"
> No change (i.e., still no /dev/external...)
> /dev/plextor_memstick and /dev/plextor_memstick1 exist as symlinks.
> With "usb" instead of "scsi", also no change. With
> NAME="plextor_memstick%n" etc, no change (except that there are dev
> nodes, not symlinks)

Hmm, looks ok.  Could you set udev_log=7 in /etc/udev/udev.conf, and
post the entries that are added to /var/log/messages when you turn on
the hard drive.

-Richard

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-17 18:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  9:26 [gentoo-user] confused udev? Jorge Almeida
2005-11-17  9:49 ` Dirk Heinrichs
2005-11-17 12:43   ` Jorge Almeida
2005-11-17 13:54     ` Dirk Heinrichs
2005-11-17 14:14       ` Jorge Almeida
2005-11-18 10:21         ` Dirk Heinrichs
2005-11-18 10:29           ` Neil Bothwick
2005-11-18 10:40             ` Dirk Heinrichs
2005-11-18 10:31           ` Jorge Almeida
2005-11-20  2:21             ` Richard Fish
2005-11-20 11:21               ` Jorge Almeida
2005-11-21 15:18                 ` Richard Fish
2005-11-22 11:46                   ` Jorge Almeida
2005-11-23  4:10                     ` Richard Fish
2005-11-23  9:32                       ` Jorge Almeida
2005-11-23 15:07                         ` Richard Fish
2005-11-23 21:13                           ` Jorge Almeida
2005-11-17 14:14     ` Richard Fish
2005-11-17 16:19       ` Jorge Almeida
2005-11-17 17:11         ` Richard Fish
2005-11-17 17:47           ` Jorge Almeida
2005-11-17 18:14             ` Richard Fish [this message]
2005-11-17 18:23               ` Jorge Almeida
2005-11-17 20:15                 ` Richard Fish
2005-11-17 20:49                   ` Jorge Almeida
2005-11-17 21:11                     ` Richard Fish
2005-11-17 22:04                       ` Jorge Almeida
2005-11-17 23:57                         ` Richard Fish
2005-11-18  8:33                           ` Jorge Almeida
2005-11-18  7:03                       ` Dirk Heinrichs
2005-11-18  6:56         ` Dirk Heinrichs
2005-11-18  8:36           ` Jorge Almeida

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=7573e9640511171014p1b5dd90ay29e841abd7310bbe@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.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