From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 18 Jun 2005 08:24:36 +0000 Subject: Re: [OFFTOPIC] udev question Message-Id: <20050618082436.GA29763@vrfy.org> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.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_id492&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