-----BEGIN PGP SIGNED MESSAGE-----
Justin Emmanuel schrieb:
> What if a DDL (Driver Description Language) framework could be devised
> that was easy to learn and write for? Included modern mechanisms to
> capture programming errors. Was only allowed to be linked to the device
> that it was to be operating.
How would you expect that to work? The problem, as you stated above, is
_not_ that we cannot limit what the driver is allowed to do, but that we
have to believe it that it really needs the capabilities it asked for.
> System policies can be applied because it
> is the kernel itself that is writing the code.
It is translating the code. This is a major difference. Even if the
compiler/translater was bug-free, the highlevel code could still contain
bugs (you cannot, e.g., check for certain logic errors, as that'd
require understanding of the device, wich is what drivers are needed for
in the first place).
> Once the DDL Driver is
> written, it could actually be portable???
> Qualified User installs DDL Driver
> System Recognises DDLD
> System Compiles DDLD
> System Uses Driver
I'd say yes, but it doesn't solve the initial problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
-----END PGP SIGNATURE-----
L4-hurd mailing list