linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: John Stoffel <john@stoffel.org>
Cc: Dylan Distasio <interzone@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Looking for some advice on best way to identify drives / recover from issues
Date: Mon, 06 Jan 2014 11:54:51 -0500	[thread overview]
Message-ID: <52CADFDB.5060605@turmel.org> (raw)
In-Reply-To: <21194.53857.185374.195036@quad.stoffel.home>

On 01/06/2014 10:57 AM, John Stoffel wrote:
>>>>>> "Phil" == Phil Turmel <philip@turmel.org> writes:
> 
> Phil> I created a script for precisely this type of documentation task, keyed
> Phil> to drive serial numbers and UUIDs wherever identifiable.
> 
> Phil> https://github.com/pturmel/lsdrv
> 
> Phil,
> 
> Thanks for the script, it looks good, but I wanted to poke you about
> the continuation and corner vars, which are defined with funky graphic
> chars.  Would it be hard to put in simpler plain ASCII graphics there
> by default, and offer a switch for UTF-8 (???) output?

I'll take patches that make the script locale-aware using python2's
normal methods.  I hadn't bothered to figure out how to do so since
distros have been installing with utf-8 by default for years now.  I do
not want to give up the utf-8 line drawing characters for the majority.

> Also, I wonder if having it going the other way, which is from mount
> point down to the device(s) would make sense as well?  Now I just need
> to find the time to hack your code and see what I can do.

Shouldn't be hard.

I chose not to go in that direction as it would leave out unmounted
devices.  My intent is to document the relationships amongst everything
present (with SNs and UUIDs) to the fullest extent possible.

Thanks for the feedback.

Phil

      reply	other threads:[~2014-01-06 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 15:04 Looking for some advice on best way to identify drives / recover from issues Dylan Distasio
2014-01-05 15:44 ` Mark Knecht
2014-01-05 17:01   ` Dylan Distasio
2014-01-05 18:05     ` Mark Knecht
2014-01-05 16:33 ` Roger Heflin
2014-01-05 17:06   ` Dylan Distasio
2014-01-05 19:37     ` Krzysztof Adamski
2014-01-22 17:16     ` Dylan Distasio
2014-01-05 18:34 ` Phil Turmel
2014-01-06 15:57   ` John Stoffel
2014-01-06 16:54     ` Phil Turmel [this message]

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=52CADFDB.5060605@turmel.org \
    --to=philip@turmel.org \
    --cc=interzone@gmail.com \
    --cc=john@stoffel.org \
    --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).