From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 16 Jan 2004 03:24:51 +0000 Subject: Re: [ANNOUNCE] udev 013 release Message-Id: <20040116032451.GA17090@vrfy.org> List-Id: References: <20040113235213.GA7659@kroah.com> In-Reply-To: <20040113235213.GA7659@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Jan 16, 2004 at 02:25:08AM +0000, Nuno Silva wrote: > Greg KH wrote: > > > >Hm, I just took Kay's patch instead. Care to make up a patch for this > >based off of it? > > > > You did the right thing :-) Now it's simplier and is almost a one-liner. > (Anyway, still missing the SYSFS_* details). > > Sample output: > Jan 16 01:53:42 puma udev[18505]: New device! Metrics: BUS='scsi', > ID='71:0:0:0', KERNEL='sr0' > Jan 16 01:53:42 puma udev[18505]: name, 'sr0' is going to have owner='', > group='', mode = 0600 > Jan 16 01:53:42 puma udev[18505]: creating device node '/udev/sr0' > > I think this output is nice, easy to read and /etc/udev/rules oriented > so, sooner or later, people will find it "natural". > > + info("New device! Metrics: BUS='%s', ID='%s', KERNEL='%s'", > + sysfs_device->bus, sysfs_device->bus_id, class_dev->name); Huh, what if sysfs_device = NULL ? And why print it, if we apply a configured rule to a known device? Kay ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ 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