CML 1.8.4 is available
The latest version is always available at http://www.tuxedo.org/~esr/cml2/
Release 1.8.4: Tue Nov 13 17:31:15 EST 2001
* Resync with 2.4.15-pre4 (except for SH port).
* Rulebase corrections from Keith Owens and Colin Slater.
* DANGEROUS is now a warndepend condition; this means there is a policy symbol DANGEROUS, and any symbol dependent on it will show DANGROUS in its legend.
* Visibility improvement from Romain BEAUGRAND.
* Complete coverage check -- CML1 fossil symbols eliminated.
* Matthieu Verbert's configtrans.py fix.
CML2 is now fully caught up with the CML1 rulebase in the most current kernel version, with symbol coverage mechanically checked in both directions.
Signature · 5 lines
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a> "Those who make peaceful revolution impossible will make violent revolution inevitable." -- John F. Kennedy
Quoted 3 lines · Eric S. Raymond
CML2 is now fully caught up with the CML1 rulebase in the most current kernel version, with symbol coverage mechanically checked in both directions.
The following symbols should be allowed to be set to 'm' but are not:
CONFIG_USB
CONFIG_UHCI
CONFIG_UHCI_ALT
If CONFIG_USB_SERIAL is set to 'y' CONFIG_USB_SERIAL_DEBUG should be allowed to be chosen. I do not see this happening.
And why is the CONFIG_USB_SERIAL options in the drivers/usb directory? In the CML1 version they live in their own subdirectory quite nicely :) Either way they should be in the USB port drivers section, not the "USB devices" section of the menu.
There doesn't seem to be any rules set up for drivers/hotplug.
thanks,
greg k-h
Greg KH <[email protected]>:
Quoted 2 lines
The following symbols should be allowed to be set to 'm' but are not:
CONFIG_USB
That's odd. M shows up as a choice when I do xconfig.
Quoted 2 lines
CONFIG_UHCI
CONFIG_UHCI_ALT
My error. These are declared bool rather than trit in the 1.8.5 rulebase. I've just fixed tht.
Quoted 2 lines
If
CONFIG_USB_SERIALis set to 'y'CONFIG_USB_SERIAL_DEBUGshould be allowed to be chosen. I do not see this happening.
Another rulebase bug, now fixed.
Quoted 4 lines
And why is the
CONFIG_USB_SERIALoptions in thedrivers/usbdirectory? In the CML1 version they live in their own subdirectory quite nicely :) Either way they should be in the USB port drivers section, not the "USB devices" section of the menu.
Historical reasons. My rulebase was opriginally one big file for editing conveniece. What directory whould the USB serial stuff live in?
Quoted 1 line
There doesn't seem to be any rules set up for
drivers/hotplug.
What symbols should be in there,
Signature · 7 lines
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Such are a well regulated militia, composed of the freeholders,
citizen and husbandman, who take up arms to preserve their property,
as individuals, and their rights as freemen.
-- "M.T. Cicero", in a newspaper letter of 1788 touching the "militia"
referred to in the Second Amendment to the Constitution.Quoted 5 lines · Eric S. Raymond
Greg KH <[email protected]>:
Quoted 2 lines
The following symbols should be allowed to be set to 'm' but are not:
CONFIG_USBThat's odd. M shows up as a choice when I do xconfig.
Ok, this was a user error. I didn't realize that the USB config option was under the "System buses and controller types" menu. This confusion was caused by the error that you get when pressing "m" when the "USB support" menu is selected on the main screen of the ncurses version.
Quoted 7 lines
Quoted 4 lines
And why is the
CONFIG_USB_SERIALoptions in thedrivers/usbdirectory? In the CML1 version they live in their own subdirectory quite nicely :) Either way they should be in the USB port drivers section, not the "USB devices" section of the menu.Historical reasons. My rulebase was opriginally one big file for editing conveniece. What directory whould the USB serial stuff live in?
drivers/usb/serial
Quoted 3 lines
Quoted 1 line
There doesn't seem to be any rules set up for
drivers/hotplug.What symbols should be in there,
CONFIG_HOTPLUG_PCICONFIG_HOTPLUG_PCI_COMPAQCONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
See the Config.in file in that directory for the dependencies they have on each other.
thanks,
greg k-h
Greg KH <[email protected]>:
Quoted 7 lines
Quoted 2 lines
Historical reasons. My rulebase was opriginally one big file for editing conveniece. What directory whould the USB serial stuff live in?
drivers/usb/serialQuoted 2 lines
Quoted 1 line
There doesn't seem to be any rules set up for
drivers/hotplug.
Quoted 8 lines
Quoted 1 line
What symbols should be in there,
CONFIG_HOTPLUG_PCICONFIG_HOTPLUG_PCI_COMPAQCONFIG_HOTPLUG_PCI_COMPAQ_NVRAMSee the Config.in file in that directory for the dependencies they have on each other.
OK, this wiull be in 1.8.6. I'm going to have to figure out why my coverage tools didn't catch those three symbols.
Signature · 5 lines
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Where rights secured by the Constitution are involved, there can be no
rule making or legislation which would abrogate them.
-- Miranda vs. Arizona, 384 US 436 p. 491Quoted 10 lines · Eric S. Raymond
Quoted 7 lines
CONFIG_HOTPLUG_PCICONFIG_HOTPLUG_PCI_COMPAQCONFIG_HOTPLUG_PCI_COMPAQ_NVRAMSee the Config.in file in that directory for the dependencies they have on each other.
OK, this wiull be in 1.8.6. I'm going to have to figure out why my coverage tools didn't catch those three symbols.
Thanks. 2.4.15-pre4 didn't allow the user to select these options. The attached patch is necessary for them to show up. Perhaps this is the reason.
thanks,
greg k-h
arch/i386/config.in +2 -0
@@ -234,8 +234,10 @@ if [ "$CONFIG_HOTPLUG" = "y" ] ; then source drivers/pcmcia/Config.in + source drivers/hotplug/Config.in else define_bool CONFIG_PCMCIA n + define_bool CONFIG_HOTPLUG_PCI n fi bool 'System V IPC' CONFIG_SYSVIPC