> Surely the point of ELKS is that it's an *embedded* Linux system
> (routers, settop boxen, etc), so even if multi-user is a possibility,
> it's not a major design feature, eh? And if we're sticking the netstack
> in userspace, this re-enforces the principle that "C2 compliant"
> multi-user environment is a secondary point. Let alone the programming
> nightmare a netstack in userspace presents to a coder <fx:unfond
> memories of coding network daemons for BeOS, who's netstack is also in
> userspace>
I have to agree that in the interest of speed and code size that security
isn't that important, and especially on an embedded system. My suggestion
would be to use a 386 or other system is if that's really an issue, or
maybe find a way to add memory protection to a special version of ELKs
destened for the 286 (the 186 doesn't have memory protection as well, does
it?).
Dan
