I don't think that the warnings against evil corporate drivers were
strong enough. Is there any _good_ reason for a company to keep its
driver code secret? If not, I would recommend requiring driver code to
be GPL-compatible Open Source. (GPLCOS?). Another interesting
possibility would be a rather stronger form of warning. The first
couple times you boot with evil corporate hardware, the screen flashes,
a siren goes off, and you are warned that the provided device driver is
causing a breach of security, and that you should call the vendor to get
the secure GPLCOS version. ;)
-- ______________________________ / David Feuer \ | dfeuer@binx.mbhs.edu | | feuer@his.com | | daf@cygnus.usno.navy.mil | | david@feuer.his.com | \ 301-320-4990 / ------------------------------ To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/