David S. Miller writes:
> Date: Sun, 9 Apr 2000 21:24:25 -0400 (EDT)
> From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
>
> Hardware vendors can not expect users to know about compiling. It
> would be very dangerous to have hardware vendors supplying whole
> kernel upgrades, but what else can they do?
>
> There really is not a whole lot preventing the "install" script
> on a driver cdrom from building the kernel module from source.
> It can even pop up a little "building driver module" dialogue
> with a cute little thermometer moving along as the thing builds
> itself. :-)
>
> The one thing preventing that would be if no compiler tools at
> all are installed on the user's machine. And that would be
> the one issue preventing this scheme from working.
>
> It then would not matter if the user was using kernel-2.2.x from
> Debian, or Slackware, or whoever. It also would not matter if the
> person was running on a Sparc, a PPC, an Alpha, an x86, or whatever
> PCI based platform on which the card works.
>
> I mean, am I the only person for whom this strikes them as being
> desirable? :-)
Sounds like a good idea. There might be a problem with vendors writing
a robust "install" script, though. Your scheme requires competance on
the part of vendors. Pretty tenuous assumption, really.
We could nurse them by providing them with a sample script in the
kernel sources.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:13 EST