From: Keith Owens <kaos@ocs.com.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: Network protocol for linux-hotplug.
Date: Mon, 08 Oct 2001 01:50:31 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100250588226245@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100250374523386@msgid-missing>
On Mon, 08 Oct 2001 01:05:45 +0100,
Stamatis Mitrofanis <ewstam@softhome.net> wrote:
>... a server will return info about how the client can
>find appropriate driver software (like a precompiled kernel module
>packaged together with appropriate driver agent scripts... or the source
>code for a kernel module... maybe a ready-to-install
>RPM/Debian/Slackware package...).
A precompiled kernel module will not work, trust me on this. Modules
must be compiled with the same config options, with a compatible[*]
version of gcc, for SMP or non-SMP and for multiple architectures. The
only way that will scale is a source driver. But that assumes that
everybody using the server has a current set of sources and config for
their kernel.
I am not knocking the idea, but until you can solve the problem of
building and loading modules on the fly, worrying about file formats
and download protocols is a waste of time.
[*] Different versions of gcc generate different code for the kernel.
Blindly loading a gcc 2 module into a kernel compiled with gcc 3
or vice versa is a good recipe for Oops.
_______________________________________________
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-08 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 0:05 Network protocol for linux-hotplug Stamatis Mitrofanis
2001-10-08 1:50 ` Keith Owens [this message]
2001-10-08 1:57 ` Dmitri
2001-10-08 14:22 ` Randy.Dunlap
2001-10-08 19:01 ` Tim Jansen
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-100250588226245@msgid-missing \
--to=kaos@ocs.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.