linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Fri, 16 Jan 2004 02:25:08 +0000	[thread overview]
Message-ID: <40074B84.5060802@vgertech.com> (raw)
In-Reply-To: <20040113235213.GA7659@kroah.com>

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


[CC to lkml removed and I'm not in linux-hotplug-devl]

Hi!

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'

...

Jan 16 01:57:07 puma udev[18779]: New device! Metrics: BUS='scsi', 
ID='72:0:0:0', KERNEL='sda'
Jan 16 01:57:07 puma udev[18779]: name, 'sda' is going to have owner='', 
group='', mode = 0600
Jan 16 01:57:07 puma udev[18779]: creating device node '/udev/sda'

...

Jan 16 01:57:18 puma udev[18791]: New device! Metrics: BUS='usb', 
ID='5-1:1.1', KERNEL='lp0'
Jan 16 01:57:18 puma udev[18791]: name, 'lp0' is going to have owner='', 
group='', mode = 0600
Jan 16 01:57:18 puma udev[18791]: creating device node '/udev/lp0'

I think this output is nice, easy to read and /etc/udev/rules oriented 
so, sooner or later, people will find it "natural".

Thanks,
Nuno Silva


[-- Attachment #2: udev-bk-details.diff --]
[-- Type: text/plain, Size: 730 bytes --]

diff -Naur udev/namedev.c udev-report/namedev.c
--- udev/namedev.c	2004-01-16 01:59:03.000000000 +0000
+++ udev-report/namedev.c	2004-01-16 01:53:10.000000000 +0000
@@ -723,6 +723,13 @@
 		udev->owner[0] = 0x00;
 		udev->group[0] = 0x00;
 	}
+	/* notify syslog and report some of the configuration: */
+	/* FIXME: add SYSFS_* nodes, too */
+	info("New device! Metrics: BUS='%s', ID='%s', KERNEL='%s'",
+	    sysfs_device->bus, sysfs_device->bus_id, class_dev->name);
+	info("name, '%s' is going to have owner='%s', group='%s', mode = %#o",
+	    udev->name, udev->owner, udev->group, udev->mode);
+
 	dbg("name, '%s' is going to have owner='%s', group='%s', mode = %#o",
 	    udev->name, udev->owner, udev->group, udev->mode);
 

  parent reply	other threads:[~2004-01-16  2:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 23:52 [ANNOUNCE] udev 013 release Greg KH
2004-01-14  1:38 ` Frédéric L. W. Meunier
2004-01-14  2:14 ` Jon Smirl
2004-01-14  5:15 ` Nuno Silva
2004-01-14 17:15   ` Greg KH
2004-01-14 17:46     ` Chris Friesen
2004-01-14 19:23       ` Nuno Silva
2004-01-14 21:14         ` Greg KH
2004-01-15  7:48           ` Nuno Silva
2004-01-15 23:03             ` Greg KH
2004-01-14 20:34       ` Clay Haapala
2004-01-14 20:47         ` Chris Friesen
2004-01-14 21:12           ` Greg KH
2004-01-14 21:10         ` Greg KH
2004-01-14 17:27 ` Greg KH
2004-01-15  4:14 ` Kay Sievers
2004-01-15 14:32 ` Kay Sievers
2004-01-15 22:40 ` Greg KH
2004-01-16  2:25 ` Nuno Silva [this message]
2004-01-16  3:24 ` Kay Sievers
2004-01-16  3:45 ` Nuno Silva
2004-01-19 20:29 ` Olaf Hering
2004-01-19 20:40 ` Greg KH
2004-01-19 20:44 ` Olaf Hering
2004-01-19 20:50 ` 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=40074B84.5060802@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --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).