From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug "rename" event for kobject_rename()?
Date: Wed, 15 Sep 2004 00:35:52 +0000 [thread overview]
Message-ID: <20040915003552.GB24492@kroah.com> (raw)
In-Reply-To: <1095095673.15966.47.camel@localhost.localdomain>
On Mon, Sep 13, 2004 at 07:14:33PM +0200, Kay Sievers wrote:
> Hi,
> we currently get hotplug events for kobject "add" and "remove". Wouldn't
> it be nice to get the same kind of event for a kobject "rename"?
I don't know, what controls a rename, a userspace event, right?
> We currently fake a hotplug-event with udev while renaming a net-device.
> We compose the new DEVPATH and call the network hotplug script from a
> dev.d/ callout. If we would get a real "rename" event we can get rid of
> that indirection and the rest of userspace can act properly too :).
>
> What do you think about emitting a "rename" event from:
> kobject_rename(struct kobject * kobj, char *new_name)
Wouldn't it just be the same as a "remove" and an "add" event?
> and add the old name to the environment?
What would the environment variables look like to show the old and new
names?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
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-09-15 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 17:14 hotplug "rename" event for kobject_rename()? Kay Sievers
2004-09-15 0:35 ` Greg KH [this message]
2004-09-15 1:34 ` Kay Sievers
2004-09-15 3: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=20040915003552.GB24492@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).