From: Andre Hedrick <t13@linux-ide.org>
To: "'t13@tgi.com'" <t13@tgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [temp t13] Re: FW: Open Letter to NCITS T13 on Access Control s
Date: Sat, 3 Mar 2001 22:07:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10103032159370.4530-100000@master.linux-ide.org> (raw)
In-Reply-To: <D973CF70008ED411B273009027893BA4D1C55D@irv-exch.phoenix.com>
On Sat, 3 Mar 2001, Curtis Stevens wrote:
> ** This is the quasi-official and semi-temporary T13 email list server. **
>
> Andre
>
> I think We've gone out-of-bounds on this one. None of us are
> lawyers, and nobody can predict what is happening. Personally, I do not see
> the difference between placing a GUID in the vendor specific are or placing
> a GUID in the E0112r1 area. Both places are set aside for people to do
> things without bringing them to standards. The only significant piece that
> E0112r1 brings to the table is that a specific set of command codes can be
> re-used without having a secret society setup the rules.
This is the one and only reason why I have to strongly consider voting YES
for you proposal. Had it been only on the merit of the GUID and CPRM had
never entered the picture it would have been a hands down YES.
> My opinion is that lawyers can make a case for virtually anything.
> Nothing is fool-proof and there are no guarantees. Ultimately it ends up in
> the hands of judges or in the hands of the consumers. I am more than
> willing to work up a better understanding of the legal issues off-line.
And the purpose of "lawyers" is to turn a lie into truth, because it will
not stand on its own merit. We all know this fact. At this point in time
when people ask me for drives to buy, I can only suggest the one company
that voted NO and I hope that their sales blow through the roof as a form
of financial protest to the rest.
We can go offline with the legal issues, and the nice thing about that is
as a person you are trustworth and honest.
Respectfully,
Andre Hedrick
Linux ATA Development
next prev parent reply other threads:[~2001-03-04 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 0:13 [temp t13] Re: FW: Open Letter to NCITS T13 on Access Control s Curtis Stevens
2001-03-04 6:07 ` Andre Hedrick [this message]
[not found] <D973CF70008ED411B273009027893BA4D1C559@irv-exch.phoenix.com>
2001-03-03 21:56 ` Andre Hedrick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.10.10103032159370.4530-100000@master.linux-ide.org \
--to=t13@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t13@tgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).