> cases even ELKS code is too complicated. Alan has pointed this
> out with the #ifdef madness and other very little used options.
Most of IFDEFs were there due to bugs in the source .. old code was just
#if 0ed out and replaced with new one. At least that's what i did in
parts of kernel i touched; Al then included whole patch (or file),
without removing old code. Anyway, it was harmless.
> on a personal basis. I doubt that ELKS has ever run more than 15
> processes, for instance.
No, it probably hasn't. I had some 10 running but then again i was only
testing it. If there was _any_ daemon present it would occupy another
process slot, ...
bye, Ab