From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: [ANNOUNCE] udev 007 release
Date: Mon, 24 Nov 2003 00:29:01 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106963388124982@msgid-missing> (raw)
I've released the 007 version of udev. It can be found at:
kernel.org/pub/linux/utils/kernel/hotplug/udev-007.tar.gz
udev is a implementation of devfs in userspace using sysfs and
/sbin/hotplug. It requires a 2.6 kernel to run. Please see the udev
FAQ for any questions about it:
kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
Note:
The CALLOUT rule format has changed. If you have a config file
using this rule, please change it to follow the new order. See
the man page for the proper style.
The major changes since the 006 release are:
- better parsing of the udev.permissions file
- string owner and group names in the udev.permissions file will
now work if you build against glibc.
- fix the CALLOUT rule to look the same as the other rules.
- add format char for CALLOUT rule output
- support arguments in callout exec
- add ability for CALLOUT program to accept format modifiers.
- drop Makefile.klibc. To build using klibc, use:
make KLIBC=true
- updated man page documenting new changes.
Again, many thanks to Kay Sievers, for lots of great patches in this
release. Thanks also to Marco d'Itri and Olaf Hering, both of whom
submitted patches for this release.
I think with the ability to capture the output of the CALLOUT rule,
combined with the ability to put format modifiers in the CALLOUT program
string, we now have everything in place to emulate the existing devfs
naming scheme. Anyone want to verify this or not?
The full ChangeLog can be found below.
udev development is done in a BitKeeper repository loacated at:
bk://linuxusb.bkbits.net/udev
Daily snapshots of this tree can be found at:
http://www.codemonkey.org.uk/projects/bitkeeper/udev/
Many thanks to Dave Jones for managing this.
thanks,
greg k-h
Summary of changes from v006 to v007
======================
<md:linux.it>:
o fix segfault in parsing bad udev.permissions file
Greg Kroah-Hartman:
o update default config file with a CALLOUT rule, and more documentation
o updated the man page with the latest format specifier changes
o added ability to put format specifiers in the CALLOUT program string
o tweak udev-test.pl to report '0' errors if that's what happened
o only build klibc_fixups.c if we are actually using klibc
o add support for string group and string user names in udev.permissions
o add getgrnam and getpwnam to klibc_fixups files
o remove Makefile.klibc
o add udev-test perl script from Kay Sievers <kay.sievers@vrfy.org> which blows away my puny shell scripts
o added debian's version of udev.permissions
o change to 006_bk version
Kay Sievers:
o format char for CALLOUT output
o more namedev whitespace cleanups
o support arguments in callout exec
o namedev.c - change order of fields in CALLOUT
o namedev.c whitespace + debug text cleanup
o man page with udev.permissions wildcard
Olaf Hering:
o static klibc udev does not link against crt0.o
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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 reply other threads:[~2003-11-24 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 0:29 Greg KH [this message]
2003-11-24 3:19 ` [ANNOUNCE] udev 007 release Arnd Bergmann
2003-11-24 23:40 ` Greg KH
2003-11-25 13:29 ` Marco d'Itri
2003-11-26 19:28 ` Greg KH
2003-12-01 10:51 ` Marco d'Itri
2003-12-02 0:55 ` Greg KH
2003-12-02 15:16 ` Kay Sievers
2003-12-02 16:27 ` Kay Sievers
2003-12-02 17:21 ` Marco d'Itri
2003-12-02 17:42 ` Kay Sievers
2003-12-02 17:54 ` Greg KH
2003-12-02 17:55 ` Greg KH
2003-12-02 18:04 ` 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=marc-linux-hotplug-106963388124982@msgid-missing \
--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).