From: Stan Hoeppner <stan@hardwarefreak.com>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: SSD + Rust as raid1
Date: Fri, 31 May 2013 23:37:11 -0500 [thread overview]
Message-ID: <51A97A77.2090406@hardwarefreak.com> (raw)
In-Reply-To: <8qun7axaui.ln2@goaway.wombat.san-francisco.ca.us>
On 5/31/2013 8:19 PM, Keith Keller wrote:
> On 2013-06-01, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>
>> Today "HDD" can mean either mechanical hard disk drive or SSD. To easily
>> differentiate, it has become commonplace to refer to mechanical hard
>> drives simply as "rust" because it's quicker to type and universally
>> understood. If this is the first time you're seeing this term that's a
>> bit surprising.
>
> I think this is the only list I've ever seen "rust" used in this way.
Then I'd guess you're not subbed to other storage specific lists, such
as linux-scsi, linux-ide, xfs, etc. Obviously not everyone uses this
jargon, but it's becoming much more common. I've been using it myself
for quite some time. Some people use "SRD" as well meaning "spinning
rusty disk". You'll commonly see "array of rust", "rusty RAID6", "SRD
array", etc. "rust" is here to stay. Get used to it.
--
Stan
next prev parent reply other threads:[~2013-06-01 4:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 21:23 SSD + Rust as raid1 Dominic Raferd
2013-05-31 0:22 ` Mathias Burén
2013-05-31 7:02 ` Dominic Raferd
2013-05-31 7:30 ` Roman Mamedov
2013-05-31 7:47 ` Dominic Raferd
2013-05-31 7:54 ` Roman Mamedov
2013-05-31 8:52 ` Dominic Raferd
2013-06-04 8:13 ` Dominic Raferd
2013-06-07 22:23 ` Bill Davidsen
2013-06-08 10:22 ` Roman Mamedov
2013-06-08 17:11 ` Bill Davidsen
2013-06-08 21:58 ` Roberto Spadim
2013-06-10 8:57 ` Dominic Raferd
2013-06-01 0:25 ` Stan Hoeppner
2013-06-01 1:19 ` Keith Keller
2013-06-01 4:37 ` Stan Hoeppner [this message]
2013-06-07 22:16 ` Bill Davidsen
2013-06-01 1:30 ` Sam Bingner
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=51A97A77.2090406@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=kkeller@wombat.san-francisco.ca.us \
--cc=linux-raid@vger.kernel.org \
/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).