On Tue, 8 Aug 2000, Robert Elz wrote:

> Personally I'd prefer it if it were ripped out completely.   The alternative
> would be to leave the code in the kernel intact, but delete all references to
> it from options(4), GENERIC and all other sample kernel config files (so the
> only way to discover it exists is to read the source).  Then you can still
> turn it on if you really need it, with there being close to zero chance that
> it is going to surprise any of those who don't understand what is happening.
> That is, don't even include it commented out in GENERIC with warnings not
> to use it.   It isn't as if this would be a new strategy, the MAXBSIZE option
> is already buried just like that (which I found when I needed it just a
> week or two ago).

While removing it from GENERIC might be ok, if we keep the COMPAT_AOUT
code in the kernel, we shoudn't remove it from OPTIONS(4). We should be
increasing our documentation, not decreasing it. :-)

Take care,

Bill