From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-hotplug@vger.kernel.org
Subject: device id version _string_?
Date: Sun, 21 Jan 2001 03:29:37 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98004776106627@msgid-missing> (raw)
Hello, Keith.
I was wondering what you think of the idea of having a
short version string for a device ID structure rather than a version number.
The advantage of this is that it allows modified kernels to ensure
that an incompatible version of depmod will complain about an
unknown version string without requiring central coordination to
hand out version numbers or determine an order to them. It could
also make the naming more mnemonic.
For example, let's say Yellow Dog decides to ship an
enhanced version of (future) FireWire ID's. They might set their
firewire_device_id version string to string to "yellow1" to ensure
that people use a depmod that supports their kernel (or at least get
a warning about it so they can expect firewire hot plugging not to work).
Later, if that format is rolled into the standard kernel or you want
to support it from the stock modutils, you could integrate the code
that handles that particular version string value.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-01-21 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 3:29 Adam J. Richter [this message]
2001-01-21 3:47 ` device id version _string_? Keith Owens
2001-01-21 4:33 ` Miles Lane
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-98004776106627@msgid-missing \
--to=adam@yggdrasil.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).