From: Alessandro Rubini (rubini@linux.it)
Date: Tue Jan 30 2001 - 09:54:24 EST
> EtLinux sounds like a brother of uClinux, in many aspects. Yes and no. It's small, but that's the end of similarities. It's actually used only on x86 (to my knowledge) and requires MMU support in the kernel. Most of the work was done in user space, to keep it small. No busy box, though, just a Tcl interpreter for everything. > Having Tcl for uClinux would be pretty interesting. I'll run it on my 68302 device as soon as I get the kernel running. But it's not interesting per-se, in my opinion. > Could you please comment on how difficult it is modify the > interpreter to use vfork? As long as you use the normal "exec" command, it should not make any difference. The trick to save memory in EtLinux, though, is in never calling exec(2). This can't be used in uclinux. When I run my 68302 demo with a web server and telnet server integrated in /sbin/init, it will only serve static pages. > What's the footprint of the interpreter? Especially, is the data+bss > size above 32KB? Definitely. I've not way to compile it under m68k currently, but on x86 it's 200kB: morgana% size ettclsh text data bss dec hex filename 200746 8016 4408 213170 340b2 ettclsh morgana% size ettclsh.static text data bss dec hex filename 402600 10844 9040 422484 67254 ettclsh.static /alessandro This message resent by the uclinux-dev@uclinux.org list server http://www.uClinux.org/
This archive was generated by hypermail 2.1.4 : Thu Sep 19 2002 - 13:19:28 EDT