> Jeff Garzik <jgarzik@mandrakesoft.com>
>
> [...]
>
> > I -do- know the distrinction between hosts and devices. I think there
> > should be -some- way, I don't care how, to filter out those unknown
> > commands (which may be perfectly valid for a small subset of special IBM
> > drives). The net stack lets me do filtering, I want to sell you on the
> > idea of letting the ATA stack do the same thing.
>
> The net stack does filtering for handling traffic from _untrusted_ external
> sources, either for local consumtion or as a service for dumb machines
> downstream, and as a way of limiting outward access to _untrusted_
> users. Here we are talking of the ultimate _trusted_ user (root,
> CAP_SYS_RAWIO, whatever). It makes no sense for the _kernel_ to get in the
> way. Create a userland proggie for prodding IDE drives, and give it ways to
> check (as far as terminal paranoia demands, a little, or not at all) as
> desired. Unix ultimate simplicity is all about giving root enough rope to
> shoot at his own feet.
Greetings Dr. von Brand,
One of the issues that has been confused in the stack is the command
parser and/or sequencer. It is used internally to allow quick and rapid
command additions as needed. Most are not clear how the IOCTL works and
thinks it runs via the command parser, this is totally wrong. The sad
part is the lenght of the rope does not hit the feet, it hits the head.
Regards,
Andre Hedrick
-
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/