From: o1bigtenor <o1bigtenor@gmail.com>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Raid settings
Date: Mon, 29 Aug 2016 13:13:29 -0500 [thread overview]
Message-ID: <CAPpdf58qnEqobw8q1LTOAbT0MGRssV4HF2NO7a1-Mra8XnADkA@mail.gmail.com> (raw)
In-Reply-To: <57C42840.6040103@youngman.org.uk>
On Mon, Aug 29, 2016 at 7:19 AM, Wols Lists <antlists@youngman.org.uk> wrote:
> On 29/08/16 13:11, o1bigtenor wrote:
>> Would be willing to assist in the document crafting if I were given good
>> information (see it as a way to 'help' knowing bupkis about code!).
>>
>> Wol, do you have any pointers to documents that discuss the variable
>> to be considered?
>>
>> What kind of shape would you think the document should have?
>>
>> What should be included/excluded?
>
> Take a look at the website -
> https://raid.wiki.kernel.org/index.php/Linux_Raid
>
> In particular look at "Raid setup" and the "Advanced Options" section,
> which is where this should probably go. Something to fit in there, I guess.
>
> Once I've got access, I can sort out access for you, and if it works out
> well, we can work on this together :-) It'd be nice to get an up-to-date
> resource out there :-) Times move on, and the two original guys have
> moved on in their lives - now's as good a time as any to pass the baton :-)
>
I'm starting to think that documents should be checked for
'currentness' at least
annually if not more often. The software is constantly being worked on and
hardware stuff is changing likely on a semi-annual basis.
TTYL
Dee
next prev parent reply other threads:[~2016-08-29 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 21:43 Raid settings o1bigtenor
2016-08-28 21:59 ` Wols Lists
2016-08-29 2:28 ` o1bigtenor
2016-08-29 2:46 ` Adam Goryachev
2016-08-29 9:26 ` o1bigtenor
2016-08-29 11:16 ` Wols Lists
2016-08-29 12:11 ` o1bigtenor
2016-08-29 12:19 ` Wols Lists
2016-08-29 18:13 ` o1bigtenor [this message]
2016-08-29 18:43 ` Wols Lists
2016-08-29 6:18 ` Brad Campbell
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=CAPpdf58qnEqobw8q1LTOAbT0MGRssV4HF2NO7a1-Mra8XnADkA@mail.gmail.com \
--to=o1bigtenor@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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).