nanogui: microwindows ..
Subject:
Re: microwindows ..
From:
Alex Holden ####@####.####
Date:
23 Sep 2000 11:29:04 -0000
Message-Id: <Pine.LNX.4.04.10009231138060.572-100000@hyperspace.linuxhacker.org>
On Fri, 22 Sep 2000, KIM,KYOUNG-IL (HP-Cupertino,ex1) wrote:
> How can I integrate microwindows and my kernel ?
Why do you want to do that? It's not a good idea to put the window server
in the kernel for many reasons, including:
A bug can crash the whole machine due to the lack of memory protection.
The stack is quite limited in size.
Only a very limited subset of the libc functions are available.
Getting access to things like the framebuffer, keyboard and mouse input
can be awkward.
The kernel malloc() implementation probably isn't very well suited to the
application.
You have to recompile the kernel and reboot the machine with the new
kernel image in order to upgrade to a new version of the server (unless
it's a module, which seems to defeat your object of having it compiled
into the kernel).
You probably won't even see any significant speed improvements, due to the
aggregation of requests into blocks.
Memory in kernel space can't be swapped out, however tight memory is.
> What output file from microwindows should I add to my
> kernel image and how can it be started when system boot up?
What you would be better doing is simply putting the executable in your
RAM disk and starting it from init.
--
--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------
