From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] namedev.c - change order of fields in CALLOUT
Date: Fri, 21 Nov 2003 03:26:44 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106943642518562@msgid-missing> (raw)
On Friday 21 November 2003 18:08, Kay Sievers wrote:
> Fine, please don't forget to mention it with the next release,
> cause people need to change their config file if CALLOUT was used before.
>
> Maybe we should put a line in the example config too, that says:
> "The order of the fields does matter."
> I needed approx. 10 minutes to realize :)
Hmm, maybe the order /shouldn't/ matter, then. I already thought about
making a patch that lets you have some other interesting fields, without
the order mattering at all. E.g.
# no ID=, but DRIVERCALLOUT, DRIVER="dasd-eckd", PROGRAM="/sbin/dasdname", NAME="%c"
# new CLASS=, NAME= first
REPLACE, NAME="tape/norewind/nst%n", CLASS="tape", KERNEL_NAME="nst*"
Btw, can someone explain to me the difference between TOPOLOGY and NUMBER?
The documentation suggests that they are used differently, but I
could not find any difference in the code.
Arnd <><
-------------------------------------------------------
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-21 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 3:26 Arnd Bergmann [this message]
2003-11-21 6:49 ` [udev] namedev.c - change order of fields in CALLOUT Greg KH
2003-11-21 17:08 ` Kay Sievers
2003-11-23 6:01 ` Greg KH
2003-11-23 6:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 22:05 Kay Sievers
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-106943642518562@msgid-missing \
--to=arnd@arndb.de \
--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).