1. If I install CML2 and go directly to "make xconfig", it deduces it needs
to set top level options because some of the low level options are set. For
example SCSI enabled because some SCSI device is set or hot plug because
PCMCIA is set...because some PCMCIA device is set. The _problem_ is...none
of these options were set in the CML1 generated .config file... and it
_extremely_ tedious to use xconfig to clear out all the cruft.
A much better (but not yet right) way is to use "make ttyconfig" to quickly
generate config.out from .config relatively fewer errors and ability to say
no at a top level and cause all the lower level stuff to go away. make
ttyconfig seems to parse the .config file in a different (and better) order.
Suggestion: On the first pass of CML2 processing through .config, before
first config.out created, trust the top level setting and ignore lower level
settings if top setting off.
2. So after some playing around, I want to go back to CML1. But the .config
generated by CML2 is not compatible. I don't know if it's supposed to be
but there's lots of problems.
Suggestion: Save your .config before you play with this stuff.
Bottom line: looks promising but I still haven't gotten a good compile from
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:13 EST