All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [OFFTOPIC] udev question
Date: Sat, 18 Jun 2005 08:24:36 +0000	[thread overview]
Message-ID: <20050618082436.GA29763@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0506181213560.27030@www.buraphalinux.org>

On Sat, Jun 18, 2005 at 12:18:14PM +0700, John Gatewood Ham wrote:
> Hello,
> 
>     I upgraded from udev 0.54 to udev 0.58 and had many problems.
> I finally tracked it down to my rules for /dev/null and /dev/zero.
> These rules worked for 0.54:
> 
> SYSFS{dev}="1:3", NAME="null", OWNER="root", GROUP="root", MODE="0666"
> SYSFS{dev}="1:5", NAME="zero", OWNER="root", GROUP="root", MODE="0666"

I can't reproduce this. These rules work perfectly on my box. According
to the code I can't see how udev can create block devices here.

> I believe that somehow using SYSFS{dev} now assumes anything is
> a block device instead of looking it up somehow (like KERNEL does).
> Perhaps if the lookup is difficult or expensive, you could have
> a way to specify block or character device?  Maybe there is a way to
> sneak that into the MODE specification?

No, the type of device is determined by the sysfs path. /dev/zero comes from
DEVPATH=/class/mem/zero. All DEVPATH's starting with /class/* will be
created as char devices.

No idea what is going wrong on your box.

Kay


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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

  reply	other threads:[~2005-06-18  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18  5:18 [OFFTOPIC] udev question John Gatewood Ham
2005-06-18  8:24 ` Kay Sievers [this message]
2005-06-18  8:55 ` John Gatewood Ham
2005-06-18  9:11 ` Kay Sievers
2005-06-19  5:17 ` 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=20050618082436.GA29763@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 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.