linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 047 release [u]
Date: Fri, 17 Dec 2004 00:08:30 +0000	[thread overview]
Message-ID: <20041217000830.GA11689@kroah.com> (raw)
In-Reply-To: <1102783489.12795.20.camel@nosferatu.lan>

On Sat, Dec 11, 2004 at 07:59:53PM +0200, Martin Schlemmer [c] wrote:
> On Sat, 2004-12-11 at 18:46 +0100, Kay Sievers wrote:
> > On Sat, 2004-12-11 at 18:44 +0200, Martin Schlemmer [c] wrote: 
> > > On Wed, 2004-12-08 at 10:58 -0800, Greg KH wrote:
> > > 
> > > > Lots of changes here in this release, see the full changelog below.
> > > > Highlights are:
> > > > 	- massive change with the way udevd can now work.  See
> > > > 	  http://thread.gmane.org/gmane.linux.hotplug.devel/6173 for
> > > > 	  more details on this (Kay's changes are now part of udev
> > > > 	  proper, you don't have to apply anything for this to work,
> > > > 	  just follow the directions in
> > > > 	  http://article.gmane.org/gmane.linux.hotplug.devel/6192
> > > > 	  to enable this mode.)
> > > 
> > > Any suggestions to determining the version of the installed udev?
> > > This is now during startup, to see if we can make use of using
> > > udevsend as hotplug agent.  If the system was up, udevinfo could
> > > be used, but that is in /usr/bin that might be on a seperate /usr.
> > > I know we might move udevinfo to /bin, but that might be an issue
> > > for some, and adding a -V switch to /sbin/udev might be a better
> > > choice if you do not have have any nit's against it ....
> > 
> > Good idea, we should do that. I've added it to my tree at:
> >   http://vrfy.bkbits.net:8080/udev/
> > 
> > The next version will print:
> >   [kay@pim udev.kay]$ /sbin/udev -V
> >   048
> > 
> 
> Ah, great, thanks.
> 
> Greg, sorda OT for this list, but mind adding patch to portage,
> then I can whip up some /sbin/rc changes ....

The 049 version is in portage, and you can use that now.

While we're OT, and Gentoo specific, what about moving all of the udev
specific startup and shutdown stuff to a separate file, owned by the
udev package?  Or is that just too messy now?

Just trying to make your life easier.

thanks,

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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

  parent reply	other threads:[~2004-12-17  0:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 18:58 [ANNOUNCE] udev 047 release Greg KH
2004-12-08 19:28 ` Greg KH
2004-12-08 19:46   ` [ANNOUNCE] udev 048 release Greg KH
2004-12-08 21:56     ` Tomasz Kłoczko
2004-12-08 22:05       ` Greg KH
2004-12-08 22:15         ` Kay Sievers
2004-12-08 23:25         ` Tomasz Kłoczko
2004-12-08 22:22     ` Marco d'Itri
2004-12-08 23:56     ` Marco d'Itri
2004-12-09  0:08     ` Mike Frysinger
2004-12-09 21:47     ` Andrew Walrond
2004-12-09 23:25       ` Greg KH
2004-12-10  8:46         ` Andrew Walrond
2004-12-09 21:56     ` Kay Sievers
2004-12-09 22:07     ` Andrew Walrond
2004-12-09 22:18     ` Kay Sievers
2004-12-09 22:24     ` Andrew Walrond
2004-12-09 22:27     ` Kay Sievers
2004-12-09 22:33     ` Andrew Walrond
2004-12-11 16:44 ` [ANNOUNCE] udev 047 release [u] Martin Schlemmer [c]
2004-12-11 17:46   ` Kay Sievers
2004-12-11 17:59   ` Martin Schlemmer [c]
2004-12-13 16:44   ` Martin Schlemmer [c]
2004-12-13 17:08   ` Kay Sievers
2004-12-13 19:18   ` Martin Schlemmer [c]
2004-12-14  0:46   ` Kay Sievers
2004-12-17  0:08   ` Greg KH [this message]
2004-12-17 17:11   ` Martin Schlemmer [c]
2004-12-17 23:32   ` 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=20041217000830.GA11689@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).