From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Roadmap to restoring working usb module autoloading?
Date: Sun, 21 Jan 2001 02:25:23 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98004392902513@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97999756331097@msgid-missing>
>> = Adam Richter
> = David Brownell
>> [...] The big advantage of using version numbers
>> for each ID structure instead of having depmod decide based on the
>> kernel version string
>> is that you can update different components
>> of the kernel if yours is somewhat customized (e.g., imagine a 2.5.x
>> USB backport to 2.4). However, this is currently defeated by an
>> error check in depmod which compalins "Modules have a mixture of
>> version ___ and version ___". Also, integer version numbers that
>> increase by one create an ID allocation problem if somebody wants
>> to ship a modified device ID structure and a modutils that will
>> recognize it.
>I'm not sure we'd want to encourage or support that. It'd
>effectively be a kernel fork.
It's free software, so "forks" that work tend to weave back
into the standard versions and are in integral part of the process.
In practice, I believe just about every Linux distribution has had
to modify their kernels, and this often helps get those changes into
Linus's kernels. I believe at least one Linux distribution shipped
the 2.4 "back port" of the USB code in their 2.2 kernel, which, was
probably a net benefit to the world.
Of course, it's also easy enough to stip out the code from
depmod that complains about the device ID version number differences
without changing anything else if device ID version numbers do get
integrated.
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 prev parent reply other threads:[~2001-01-21 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 13:32 Roadmap to restoring working usb module autoloading? Adam J. Richter
2001-01-20 20:55 ` David Brownell
2001-01-21 2:25 ` Adam J. Richter [this message]
2001-01-21 2:47 ` Keith Owens
2001-01-21 3:17 ` Adam J. Richter
2001-01-21 3:21 ` Keith Owens
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-98004392902513@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).