From: Nix <nix@esperi.org.uk>
To: Wol's lists <antlists@youngman.org.uk>
Cc: William Morgan <therealbrewer@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Two raid5 arrays are inactive and have changed UUIDs
Date: Fri, 24 Jan 2020 14:10:00 +0000 [thread overview]
Message-ID: <87y2txvtc7.fsf@esperi.org.uk> (raw)
In-Reply-To: <917bd12e-3b76-2f27-8340-686dd71b1408@youngman.org.uk> (Wol's lists's message of "Sun, 19 Jan 2020 21:10:40 +0000")
On 19 Jan 2020, Wol's lists verbalised:
> It would be nice if we had some decent docu on what all these assorted id's and uuid's and all that were, but I haven't managed to
> find any. Probably somewhere in the info pages for grub - given that I really don't like hypertext the fact that grub docu is very
> much hypertext is rather off-putting ...
It's just perfectly ordinary Texinfo. There are lots of non-hypertext
output formats, e.g. plain text:
<https://www.gnu.org/software/grub/manual/grub/grub.txt.gz> or DVI:
<https://www.gnu.org/software/grub/manual/grub/grub.dvi.gz>. (Though the
DVI, like the PDF, contains specials that can implement hyperlinks if
your viewer can render them, I'm fairly sure the plain text version
doesn't.)
--
NULL && (void)
next prev parent reply other threads:[~2020-01-24 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALc6PW4OKR2KVFgzoEbRJ0TRwvqi5EZAdC__HOx+vJKMT0TXYQ@mail.gmail.com>
[not found] ` <959ca414-0c97-2e8d-7715-a7cb75790fcd@youngman.org.uk>
2020-01-10 1:19 ` Two raid5 arrays are inactive and have changed UUIDs William Morgan
2020-01-10 1:55 ` Wols Lists
2020-01-13 22:40 ` William Morgan
2020-01-14 14:47 ` William Morgan
2020-01-14 15:23 ` Wols Lists
2020-01-15 22:12 ` William Morgan
2020-01-15 23:44 ` Wols Lists
2020-01-19 17:02 ` William Morgan
2020-01-19 17:07 ` William Morgan
2020-01-19 17:41 ` Wols Lists
2020-01-19 20:12 ` William Morgan
2020-01-19 21:10 ` Wol's lists
2020-01-24 14:10 ` Nix [this message]
2020-01-20 8:49 ` Robin Hill
2020-01-20 15:00 ` William Morgan
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=87y2txvtc7.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=therealbrewer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.