From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: lrhorer@satx.rr.com
Cc: "'Martin K. Petersen'" <martin.petersen@oracle.com>,
'Mikael Abrahamsson' <swmike@swm.pp.se>,
linux-raid@vger.kernel.org
Subject: Re: Adding a smaller drive
Date: Wed, 01 Jul 2009 01:25:43 -0400 [thread overview]
Message-ID: <yq1k52tgejs.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20090701041219526.QNFU19322@cdptpa-omta02.mail.rr.com> (Leslie Rhorer's message of "Tue, 30 Jun 2009 23:12:11 -0500")
>>>>> "Leslie" == Leslie Rhorer <lrhorer@satx.rr.com> writes:
>> That's how it's supposed to be.
Leslie> You mean that's how IDEMA specs read. Unless there is some
Leslie> legal agreement signed by the drive manufacturer (or whomever)
Leslie> requiring adherence to a certain spec, they can do just about
Leslie> anything they want. Compliance with a published spec is great,
Leslie> but unless some licensing agreement is in place, it isn't
Leslie> enforceable.
Oracle is not a member so I'm not sure what (if any) leverage is
available as part of the IDEMA membership agreement.
I do think, however, that you are underestimating the power of industry
associations and standards bodies. System manufacturers, enterprise
customers and governments absolutely refuse to buy things that are not
compliant. So this is not about whether you can legally cut corners.
It is about being able to sell your product in the first place.
In this particular case IDEMA is an organization founded and run by the
drive manufacturers themselves. They collaborated on the LBA spec and
have all publicly stated that they'll adhere to it. It is not a
requirement that was forced upon them by an external entity. Although
it was, of course, motivated by customers unhappy with the annoying
variation in LBA count between brands and even drive models...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-07-01 5:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 18:31 Adding a smaller drive Leslie Rhorer
2009-06-28 19:05 ` John Robinson
2009-06-28 19:47 ` Leslie Rhorer
2009-06-28 21:09 ` John Robinson
2009-06-28 21:22 ` Leslie Rhorer
2009-06-28 22:52 ` John Robinson
2009-06-28 23:07 ` John Robinson
2009-06-29 10:05 ` Goswin von Brederlow
2009-07-01 4:16 ` Leslie Rhorer
2009-06-28 21:33 ` Martin K. Petersen
2009-06-28 21:49 ` Martin K. Petersen
2009-06-28 22:33 ` Mikael Abrahamsson
2009-06-28 22:51 ` Martin K. Petersen
2009-06-28 23:37 ` Mikael Abrahamsson
2009-06-28 23:43 ` Martin K. Petersen
2009-06-28 23:57 ` Mikael Abrahamsson
2009-07-01 4:12 ` Leslie Rhorer
2009-07-01 5:25 ` Martin K. Petersen [this message]
2009-07-03 15:46 ` Leslie Rhorer
2009-07-06 0:05 ` Martin K. Petersen
2009-07-07 3:15 ` Leslie Rhorer
2009-06-28 23:54 ` John Robinson
2009-06-29 0:02 ` Mikael Abrahamsson
2009-06-29 10:07 ` Goswin von Brederlow
2009-06-29 14:45 ` Martin K. Petersen
2009-07-03 16:12 ` Leslie Rhorer
2009-07-03 17:23 ` Billy Crook
2009-07-04 14:59 ` Bill Davidsen
2009-07-04 15:20 ` John Robinson
2009-07-05 22:03 ` Leslie Rhorer
2009-07-05 22:12 ` John Robinson
2009-07-07 2:57 ` Leslie Rhorer
2009-06-30 17:01 ` Bill Davidsen
2009-06-30 18:22 ` Greg Freemyer
2009-07-01 18:53 ` Bill Davidsen
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=yq1k52tgejs.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
--cc=swmike@swm.pp.se \
/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).