linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] udev 013 release
Date: Tue, 13 Jan 2004 23:52:13 +0000	[thread overview]
Message-ID: <20040113235213.GA7659@kroah.com> (raw)

I've released the 013 version of udev.  It can be found at:
 	kernel.org/pub/linux/utils/kernel/hotplug/udev-013.tar.gz

rpms built against Red Hat FC1 are available at:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-013-1.i386.rpm
with the source rpm at:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-013-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

NOTE:  The udev.rules file format has changed!  If you have a modified
config file it MUST be changed in order to work properly.  Here's what
needs to be done:
	- The "<METHOD>, " at the beginning of the line should be
	  removed.  <METHOD> is one of the following: LABEL, CALLOUT,
	  NUMBER, TOPOLOGY, REPLACE.
	- The result of the externel program is matched with RESULT	  instead if ID	- The PROGRAM= key is only valid if the program exits with zero
	  (just exit with nozero in a script if the rule should not
	  match)

Also note the following changes in the way the udev.rules file is
processed:
	- Rules are processed in order they appear in the file.  There
	  are no priorities anymore.
	- if NAME="" is given, udev is instructed to ignore this device,
	  no node or symlink will be created.

As a result of these changes, we can now create much more powerful rules
by combining multiple key fields.  Here's two new rules that show how
you can do this:
  # combined BUS, SYSFS and KERNEL
  BUS="usb", KERNEL="video*", SYSFS_model="Creative Labs WebCam*", NAME="test/webcam%n"

  # exec script only for the first ide drive (hda), all other will be skipped
  BUS="ide", KERNEL="hda*", PROGRAM="/sbin/ide-devfs.sh %k %b %n", RESULT="hd*", NAME="%1c", SYMLINK="%2c %3c"

Also, the result of the PROGRAM call is now cached accross multiple
rules as long as a new PROGRAM key is not specified.  As an example:
    PROGRAM="/bin/echo abc", RESULT="no_match", NAME="web-no-2"
    KERNEL="video*", RESULT="123", NAME="web-no-3"
    KERNEL="video*", RESULT="abc", NAME="web-yes"
The last rule would match properly.

Many thanks for these changes go to Kay Sievers.  I really appreciate
all of the development effort.

If anyone has any problems converting existing rules files, please see
the example rules that are in the udev tarball, and feel free to ask
questions on the linux-hotplug-devel mailing list.

Thanks again 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 v012 to v013
======================

<eike-hotplug:sf-tec.de>:
  o LSB init script and other stuff

<elkropac:students.zcu.cz>:
  o fix udev directory for Debian init script

<tiggi:infa.abo.fi>:
  o udev 012 old gcc fixup

Christophe Saout:
  o add IGNORE rule type
  o small cleanup

Greg Kroah-Hartman:
  o update TODO with some new, small items
  o Cset exclude: greg@kroah.com|ChangeSet|20040113010256|48515
  o update the README in a few places
  o fix -d typo in the manpage update
  o Fix stupid gcc "optimization" of 1 character printk() calls.... Ick
  o oops, forgot to fix up the PROGRAM result from ID to RESULT in the config files
  o Add alsa device rules and a few other devfs rules
  o fix a few stale comments in namedev.c
  o convert the default rules files to the new format
  o convert the test shell scripts to the config file format
  o add bus test for usb-serial bus
  o Add some helpful messages if the user uses the older config file format
  o added dri rule to the default config file
  o added init.d udev script for debian
  o add a script that tests the IGNORE rule
  o add silly script that names cdrom drives based on the cd in them
  o add cdrom rule for ide cdrom
  o replace list_for_each with list_for_each_entry, saving a few lines of code
  o add a blacklist of class devices we do not want to look at
  o 012_bk change
  o v012 release TAG: v012

Kay Sievers:
  o fix klibc with printf() and gcc
  o udev - small script optimization
  o udev - introduce format escape char
  o udev - more CALLOUT is PROGRAM now
  o udev - CALLOUT is PROGRAM now
  o update documentation for new config file format
  o more advanced user query options
  o udev - simple debug tweak
  o udev - drop all methods :)
  o udev - advanced user query options
  o udev - Makefile error
  o udev - make exec_callout() reusable
  o udev - exec status fix for klibc
  o fix Silly udev script



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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-01-13 23:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 23:52 Greg KH [this message]
2004-01-14  1:38 ` [ANNOUNCE] udev 013 release Frédéric L. W. Meunier
2004-01-14  2:14 ` Jon Smirl
2004-01-14  5:15 ` Nuno Silva
2004-01-14 17:15   ` Greg KH
2004-01-14 17:46     ` Chris Friesen
2004-01-14 19:23       ` Nuno Silva
2004-01-14 21:14         ` Greg KH
2004-01-15  7:48           ` Nuno Silva
2004-01-15 23:03             ` Greg KH
2004-01-14 20:34       ` Clay Haapala
2004-01-14 20:47         ` Chris Friesen
2004-01-14 21:12           ` Greg KH
2004-01-14 21:10         ` Greg KH
2004-01-14 17:27 ` Greg KH
2004-01-15  4:14 ` Kay Sievers
2004-01-15 14:32 ` Kay Sievers
2004-01-15 22:40 ` Greg KH
2004-01-16  2:25 ` Nuno Silva
2004-01-16  3:24 ` Kay Sievers
2004-01-16  3:45 ` Nuno Silva
2004-01-19 20:29 ` Olaf Hering
2004-01-19 20:40 ` Greg KH
2004-01-19 20:44 ` Olaf Hering
2004-01-19 20: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=20040113235213.GA7659@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).