Messages in this thread |  | | | From | "J. Dow" <> | | Subject | Re: [patch] My AMD IDE driver, v2.7 | | Date | Mon, 11 Mar 2002 18:54:12 -0800 |
| |
From: "Linus Torvalds" <torvalds@transmeta.com>
> Yeah yeah. You can add additional levels of protection, and we have > capabilities. > > Add a special password-protected capability, so that only YOU can enable > certain hardware access stuff. Where does it end? Is one such capability > enough? How do you initialize the default values for the system if you > need to be there to type in the password at bootup every time? We're > talking about some rather fundamental things here, and these are issues > that go _far_ beyond some silly ATA stack layer.
Linus, this discussion hung on long enough I decided to start reading it. So I may have missed something. However, I notice you speak of a networking example. I believe it is a strawman. The real comparison is closer to that between IDE and SCSI. Do the SCSI device drivers filter? What and how do they filter if they do at all? Aren't they a better model to adopt for a system consistent interface philosophy?
{^_^} Joanne Dow, jdow@earthlink.net
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |