linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Schmidlkofer <kernel@pacrimopen.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 0.2 release
Date: Sat, 26 Jul 2003 00:18:21 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105917914429536@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105917102320963@msgid-missing>

On Fri, 2003-07-25 at 14:47, Greg KH wrote:
> Hi,
> 
> I've released the 0.2 version of udev into the wild, after surviving a
> live demo at the 2003 Ottawa Linux Symposium during a presentation.  It
> can be found at:
> 	kernel.org/pub/linux/utils/kernel/hotplug/udev-0.2.tar.gz
> 
> udev is a implementation of devfs in userspace using sysfs and
> /sbin/hotplug.  It requires a 2.5/2.6 kernel to run properly.  The major
> changes since the last release is that persistent device naming schemes
> are now implemented.  Yeah, it's pretty rough, but it does prove that
> the concept is sane and will end up working well for users.
> 
> There's a BitKeeper tree of the latest stuff available at:
> 	bk://kernel.bkbits.net/gregkh/udev/
> 
> I've also placed the slides from my OLS talk up at:
> 	http://www.kroah.com/linux/talks/ols_2003_udev_talk/
> 
> The paper which attempts to explain the background of udev, what it
> does, and where it is going is at:
> 	http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Kroah-Hartman-OLS2003.pdf
> 
> 
> Due to the rush of the development of udev in this past week (hacking at
> it during the conference in an attempt to have something to show) there
> are still a number of very rough corners present, a few known memory
> leaks, and at least one hard coded path to my home directory for a
> config file...  Please feel free to take it for a spin to see how well
> things are progressing.
> 
> Patches are always welcome, and discussions of the implementation, and
> future directions that the project should entail are welcome for now on
> the linux-hotplug-devel mailing list (if it's over-run, a new list will
> be started up, but I don't think that's necessary for now.)
> 
> thanks,
> 
> greg k-h

This looks cool!   I was so excited about devfs when it was written.
Since then I;ve felt a huge sense of disappointment as the
implementation never quite became something cool as it could be.  

Since this is mostly userspace it looks awesome.  I have not looked at
anything besides your slides yet.  Will this affect existing apps?  Does
udev act as a /dev replacement, or will it actually need some app-level
work?

thanks,
   joshua



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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

  reply	other threads:[~2003-07-26  0:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 21:47 [ANNOUNCE] udev 0.2 release Greg KH
2003-07-26  0:18 ` Joshua Schmidlkofer [this message]
2003-07-26 15:57 ` Greg KH
2003-07-31  7:46 ` Guo, Min
2003-07-31  7:47 ` Guo, Min
2003-07-31 23:04 ` Greg KH
2003-08-01  0:48 ` Guo, Min
2003-08-05  0:19 ` Greg KH
2003-08-05  2:22 ` Guo, Min
2003-08-05 10:08 ` Daniel Stekloff
2003-08-12  7:17 ` Guo, Min
2003-08-12  7:24 ` Guo, Min
2003-08-13  9:35 ` Daniel Stekloff

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=marc-linux-hotplug-105917914429536@msgid-missing \
    --to=kernel@pacrimopen.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).