Re: kernel mode console

[Rob Couto <rpc@cafe4111.org>]

On Thursday 04 March 2004 07:58 pm, you wrote:
> i think perhaps i need to expound upon what i have a vision of. a kernel
> mode console is just that: a console designed to run in kernel mode. it
> could have built in commands to allow for quick and dirty examination of
> stuff (anything really, like memory dumps) and a command processor for
> scripted stuff, but the true power of it comes in when you issue a command
> that is not internal to the console. it could run a special debugger, an
> application that installs a probe, a memory monitor, etc., etc. in short it
> is not a debugger per-say, but a "god mode" console for the linux kernel.
> that is what i had a vision of. the executables it would run would
> necessarily be compiled for that. again, i ask is that worth the time
> coding it?

a kbash? ksh is taken... kash would become instantly confusing to some 
english-speakers... fun for some, but others would hear it and think 'cache' 
and immediately be thrown out of sync ;)

you could extend proc (or is it just sys?) that way, creating files that can 
trigger events ('echo (desired range) > /proc/sh/memdump/range', 'echo 1 
> /proc/sh/memdump/go' or even simply 'cat /proc/sh/memdump/out' after 
inputting range) and stick with the cat/echo control... some of your 
userspace shell's commands could simply be wrappers for ordinary 'echo foo 
> /proc/foo' already

OTOH, someone said proc's been abused already, having it do things that aren't 
its job and causing disorganization in the kernel. i dunno, that's why im not 
in charge

-- 
Rob Couto
rpc@cafe4111.org
Rules for computing success:
1) Attitude is no substitute for competence.
2) Ease of use is no substitute for power.
3) Safety matters; use a static-free hammer.
--