Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 2 Apr 1996 16:14:32 -0700 (MST) | From | tpeters <> | Subject | Starting kernel threads (or something like that) |
| |
First question: When the kernel loads, what is the _FIRST_ operation it does after initializing itself? (I'm looking at replacing _EVERYTHING_ below the kernel and want an idea of where I start)
And a second question: How difficult is it to start a daemon that hooks into a kernelspace driver and handles, say, consoles?
I was admiring the new (1.3.57?+) virtual memory management and this thought came to mind.
And a stranger thought: (don't freak out anyone :) What if that daemon (ish) were an X server?
Would have to run in userspace. Would have ta handle sockets (or whatever X does now). The big trick (and the one I haven't figured out how to do yet) is to kill the consoles and take over.... from boot time.
Thanks all! - Teunis
| ![\](/images/icornerr.gif) |