From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] netdev - udevdb+dev.d changes
Date: Wed, 31 Mar 2004 23:14:10 +0000 [thread overview]
Message-ID: <20040331231410.GI5490@kroah.com> (raw)
In-Reply-To: <20040328184840.GA5877@vrfy.org>
On Sun, Mar 28, 2004 at 08:48:40PM +0200, Kay Sievers wrote:
> Hey, Chris fixed the udevd hole and Treeve found the timestamp bug,
> so there was nothing left for me at the weekend :)
>
> Here is a patch to change the netdev handling in the database and for
> the dev.d/ calls. I applies on top of the udevd.patch, cause klibc has
> no sysinfo().
Thanks, I've applied this now.
> o netdev's are also put into our database now. I want this for the
> udevruler gui to get a list of all handled devices.
> All devices in the db are stamped with the system uptime value at
> the creation time. 'udevinfo -d' prints it.
nice.
> o the DEVPATH value is the key for udevdb, but if we rename
> a netdev, the name is replaced in the kernel, so we add
> the changed name to the db to match with the remove event.
>
> NOTE: The dev.d/ scripts still get the original name from the
> hotplug call. Should we replace DEVPATH with the new name too?
Yeah, we should.
> o We now only add a device to the db, if we have successfully created
> the main node or successfully renamed a netdev. This is the main part
> of the patch, cause I needed to clean the retval passing trough all
> the functions used for node creation.
>
> o DEVNODE sounds a bit ugly for netdev's so I exported DEVNAME too.
> Can we change the name?
Can you think of a better name?
> o I've added a UDEV_NO_DEVD to possibly skip the script execution
> and used it in udev-test.pl.
> udevstart is the same horror now, if you have scripts with logging
> statements in dev.d/ it takes minutes to finish, can we skip the
> scripts here too?
No, a system will want to have those scripts run when udevstart is run
(at boot time.) Otherwise how will devices get mounted, dbus messages,
etc. ?
> o The get_device_type() function is changed to be more strict, cause
> 'udevinfo -a -p /block/' gets a class device for it and tries to
> print the major/minor values.
I cut this out, as I had already applied it from a previous patch.
> o bugfix, the RESULT value has now a working newline removal and a test
> for this case.
Nice.
thanks a lot,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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
next prev parent reply other threads:[~2004-03-31 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 18:48 [PATCH] netdev - udevdb+dev.d changes Kay Sievers
2004-03-31 23:14 ` Greg KH [this message]
2004-03-31 23:40 ` Kay Sievers
2004-04-01 0:22 ` Greg KH
2004-04-01 0:41 ` Kay Sievers
2004-04-01 1:02 ` 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=20040331231410.GI5490@kroah.com \
--to=greg@kroah.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).