From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] [dolecek@ics.muni.cz: Re: LKMs]
Date: Sat, 25 Nov 2000 12:06:58 +0200 [thread overview]
Message-ID: <20001125120657.A28417@cackle.proxima.alt.za> (raw)
Interesting coincidence, this...
I think I agree with Jaromír that debugging is a lot simpler, and with
Presotto that a generic kernel matching the union of the needs of a
large number of workstations is unlikely to be optimal in any other
fashion.
----- Forwarded message from Jaromír Dolecek <dolecek@ics.muni.cz> -----
From: Jaromír Dolecek <dolecek@ics.muni.cz>
Subject: Re: LKMs
In-Reply-To: <Pine.NEB.4.21.0011250148110.20903-100000@love.warhead.org.uk>
"from Al Snell at Nov 25, 2000 02:02:38 am"
To: Al Snell <alaric@alaric-snell.com>
Date: Sat, 25 Nov 2000 10:03:04 +0100 (CET)
CC: NetBSD Kernel list <tech-kern@netbsd.org>
X-Mailer: ELM [version 2.4ME+ PL78 (25)]
Precedence: list
Delivered-To: tech-kern@netbsd.org
Al Snell wrote:
> What is the intended future of LKMs? I see that there are changes afoot in
> -current to try to enable emulations to be loaded as LKMs, but are there
> any plans to try to actually move stuff out of the kernel and into LKMs
> instead?
There are some plans to revamp the thing, adding some advanced
features as clean interdependencies, less memory wasting, correct
symbol visibility etc. The linker would run in kernel, userland
would then only upload the raw module.o file to kernel. However,
the work is in very initial stage ATM.
The definite plan is surely to have ~all loadable. The most immediate
effect is that it eases debugging tremendously; obviously, it's
nice even for user not to have to recompile kernel :)
Jaromir
--
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.ics.muni.cz/~dolecek/
@@@@ Wanna a real operating system ? Go and get NetBSD, damn! @@@@
----- End forwarded message -----
reply other threads:[~2000-11-25 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001125120657.A28417@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).