From: Greg KH <greg@kroah.com>
To: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] udev 019 release
Date: Sat, 28 Feb 2004 01:22:27 +0000 [thread overview]
Message-ID: <20040228012227.GA14082@kroah.com> (raw)
I've released the 019 version of udev. It can be found at:
kernel.org/pub/linux/utils/kernel/hotplug/udev-019.tar.gz
rpms built against Red Hat FC2-test1 are available at:
kernel.org/pub/linux/utils/kernel/hotplug/udev-019-1.i386.rpm
with the source rpm at:
kernel.org/pub/linux/utils/kernel/hotplug/udev-019-1.src.rpm
udev allows users to have a dynamic /dev and provides the ability to
have persistent device names. It uses sysfs and /sbin/hotplug and runs
entirely in userspace. It requires a 2.6 kernel with CONFIG_HOTPLUG
enabled to run. Please see the udev FAQ for any questions about it:
kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
For any udev vs devfs questions anyone might have, please see:
kernel.org/pub/linux/utils/kernel/hotplug/udev_vs_devfs
Major changes from the 018 version:
- hopefully all string handling is now correct, and audited for
any possible overflows.
- user and group names now work properly if you build with klibc
- initial SELinux support.
- lots of small fixes (including build fixes)
- update to scsi_id program
Thanks to everyone who has send me patches for this release, a full list
of everyone, and their changes is below.
udev development is done in a BitKeeper repository located at:
bk://linuxusb.bkbits.net/udev
Daily snapshots of udev from the BitKeeper tree can be found at:
http://www.codemonkey.org.uk/projects/bitkeeper/udev/
If anyone ever wants a tarball of the current bk tree, just email me.
thanks,
greg k-h
Summary of changes from v018 to v019
======================
Kay Sievers:
o TODO update
o udev - correct relative symlink
o udev - safer string handling - part four
o udev - safer string handling - part three
o udev - safer string handling - part two
o udev - man page update
o udev - safer string handling all over the place
o manpage update
o udev - allow all files in a directory as the config
o udev - simple klibc textual uid/gid handling
Andrey Borzenkov:
o do not remove real .udev.tdb during RPM build
Greg Kroah-Hartman:
o add new TODO item about local user permissions
o Add initial SELinux support for udev
o fix build for very old versions of make
o remove limit of the number of args passed to PROGRAM
o force udev to include the internal version of libsysfs and never the external one
o fix up libsysfs header file usage to fix bug reports from users that have sysfsutils installed already
o remove udevtest on 'make clean'
o remove udevd priority TODO item, as it's not needed at all
Patrick Mansfield:
o update udev scsi_id to scsi_id 0.4
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
reply other threads:[~2004-02-28 1:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040228012227.GA14082@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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).