Messages in this thread | | | Date | Mon, 5 Apr 2004 10:59:40 -0700 (PDT) | From | Sergiy Lozovsky <> | Subject | Re: kernel stack challenge |
| |
--- Timothy Miller <miller@techsource.com> wrote: > > > Sergiy Lozovsky wrote: > > > > > I put LISP interpreter inside the Kernel - > > > > I'm dying to know why you need a LISP interpreter > inside the kernel.
It is explained at my project home page - http://vxe.quercitron.com
Basically there are two reasons.
1. Give system administrator possibility to change security policy easy enough without C programminig inside the kernel (we should not expect system administartor to be a kernel guru). Language of higher lavel make code more compact (C - is too low level, that's why people use PERL for example or LISP). Lisp was chosen because of very compact VM - around 100K.
2. Protect system from bugs in security policy created by system administrator (user). LISP interpreter is a LISP Virtual Machine (as Java VM). So all bugs are incapsulated and don't affect kernel. Even severe bugs in this LISP kernel module can cause termination of user space application only (except of stack overflow - which I can address). LISP error message will be printed in the kernel log.
Serge.
__________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |