From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Automatic download and installation of drivers.
Date: Wed, 17 Oct 2001 19:24:45 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100334687131463@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100319421829170@msgid-missing>
The _full_ quote of that last paragraph contains the disproof to
your claim about timeliness and competitiveness ...
> With a patch, "knowledgeable" users can get going right away. All
> others are going to need to wait for a new release in any case, or
> will ask their "knowledgeable user" friends for help.
It's well known that even in the Windows world, most support
comes from friendly local experts ("power users"). Those are
the folk that get called in when a vendor's driver disk doesn't
install correctly (the ones I get usually don't).
So far as I know, there isn't even an authoritative list of all
the USB and CardBus devices supported by, say, the 2.4.12
kernel. Or even a good way to extract the subset of that list
that's packaged as the MODULE_DEVICE_TABLE entries,
short of building a kernel with every driver configured as a
module (a bit painful IMO).
- Dave
----- Original Message -----
From: "Tim Jansen" <tim@tjansen.de>
To: "David Brownell" <david-b@pacbell.net>; <linux-hotplug-devel@lists.sourceforge.net>
Sent: Wednesday, October 17, 2001 11:47 AM
Subject: Re: Automatic download and installation of drivers.
> On Wednesday 17 October 2001 04:01, David Brownell wrote:
> > Easy fix: provide a patch to the kernel source, rather than going with
> > a binary distribution model. The model of binary driver distributions
> > is a problem.
> > With a patch, "knowledgeable" users can get going right away. All
> > others are going to need to wait for a new release in any case
>
> But this means, in other words, that Linux is not competitive in this area.
> Then regular users have to wait up to 6 months before they can use new
> devices because they have to wait for the next Red Hat distribution while Mac
> and Windows users can already use the device. It would also force them to
> update a stable system only for getting a new device driver.
> And it would result in hardware manufactures being unable to sell their new
> devices to the majority of Linux users before most distributions have been
> updated.
>
> bye...
>
>
>
_______________________________________________
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 prev parent reply other threads:[~2001-10-17 19:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 0:02 Automatic download and installation of drivers Stamatis Mitrofanis
2001-10-16 5:29 ` Greg KH
2001-10-16 7:35 ` David Brownell
2001-10-16 7:58 ` Tim Jansen
2001-10-16 11:38 ` Keith Owens
2001-10-16 16:52 ` Greg KH
2001-10-16 18:44 ` Tim Jansen
2001-10-16 18:58 ` Tim Jansen
2001-10-16 19:19 ` Greg KH
2001-10-17 2:01 ` David Brownell
2001-10-17 2:03 ` David Brownell
2001-10-17 18:47 ` Tim Jansen
2001-10-17 19:24 ` David Brownell [this message]
2001-10-17 23:31 ` Tim Jansen
2001-10-17 23:32 ` Greg KH
2001-10-18 0:07 ` Dmitri
2001-10-18 0:19 ` Stamatis Mitrofanis
2001-10-18 0:47 ` Tim Jansen
2001-10-18 2:17 ` Keith Owens
2001-10-18 2:35 ` Dmitri
2001-10-29 21:53 ` Greg KH
2001-10-30 8:26 ` Tim Jansen
2001-10-30 17:21 ` Greg KH
2001-10-30 21:24 ` Tim Jansen
2001-10-30 21:51 ` Dmitri
2001-10-31 12:36 ` Keith Owens
2001-10-31 20:49 ` 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=marc-linux-hotplug-100334687131463@msgid-missing \
--to=david-b@pacbell.net \
--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).