From: Moshe Yudkowsky <moshe@pobox.com>
To: maximilian attems <max@stro.at>
Cc: linux-raid@vger.kernel.org
Subject: Re: Documentation? failure to update-initramfs causes Infinite md loop on boot
Date: Wed, 30 Jan 2008 18:44:31 -0600 [thread overview]
Message-ID: <47A119EF.70509@pobox.com> (raw)
In-Reply-To: <20080130224200.GF1446@baikonur.stro.at>
maximilian attems wrote:
> pretty simple, you change mdadm.conf put it also on initramfs:
> update-initramfs -u -k all
Sure, that's what I did after boot on rescue, chroot, etc. However, I
wonder if the *documentation* -- Wiki, or even the man page discussion
on boot -- should mention that changes in the mdadm.conf have to be
propogated to /boot?
In fact, that's an interesting question: which changes have to propagate
to /boot? I'd think any change that affects md devices with /etc/fstab
entries set to "auto" would have to be followed by update-initramfs.
That's quite some bit of hidden knowledge if true.
--
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
"All friends have real and imaginary components."
-- Moshe Yudkowsky
prev parent reply other threads:[~2008-01-31 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 22:32 Documentation? failure to update-initramfs causes Infinite md loop on boot Moshe Yudkowsky
2008-01-30 22:42 ` maximilian attems
2008-01-31 0:44 ` Moshe Yudkowsky [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=47A119EF.70509@pobox.com \
--to=moshe@pobox.com \
--cc=linux-raid@vger.kernel.org \
--cc=max@stro.at \
/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.