runtime kernel modules are plain kernel modules. the runtime particle is
added as an emphasis on the fact that they can be load/unload during
kernel runtime and not at boot.
cristi
At 05:55 PM 6/14/00 +0200, you wrote:
On Tue, 13 Jun 2000, Cristi wrote:
That is what I was actualy
. Probably the principial question is if ELKS will need runtime
kernel modules or not.
cristi
At 09:11 PM 6/13/00 +, you wrote:
On Tue, 13 Jun 2000, Cristi wrote:
I would rather wait for a solid kernel and then add networking. I
think
networking should be a module as you don't need networking
I think a userspace process for networking is the right answer here. Keep
the kernel small.
cristi
At 09:43 AM 6/13/00 +0200, Jakov af Wallby wrote:
On Mon, 12 Jun 2000, Emilio Joel Macias Gomez
wrote:
hello
i dont speak english very well but i do my best
i want use the ELKS in my 286
I would rather wait for a solid kernel and then add networking. I think
networking should be a module as you don't need networking everywhere.
Biulding it modular you can deal with limited resources.
cristi
At 10:20 PM 6/12/00 -0400, Gregg C Levine wrote:
Hello from Gregg C Levine usually
Yes, I got one last week when I re: to a message.
cristi
At 08:53 AM 6/12/00 +1200, Rod Boyce wrote:
Does anybody else get these messages when
trying to reply to the Linux-8086
list?
I most defiantly have not subscribed to whatever this is.
Regards,
Rod Boyce.
-Original Message
At 10:38 PM 6/8/00 -0400, David Lloyd-Jones wrote:
Seems to me there will always be space for
lotsa sixteen-, eight- and
four-bit stuff with the clean good lines that we associate with
Linux.
Indeed. Just because you have a fast Alpha or i686 doesn't
stop the pleasure of hacking with an old Z80
