From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Victor Lowther <victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] Final fixups to make the full testsuite work.
Date: Tue, 26 May 2009 11:26:54 +0200 [thread overview]
Message-ID: <4A1BB5DE.3090206@redhat.com> (raw)
In-Reply-To: <151d32e89583815962af8d721b17d0b320f80a2f.1243306326.git.victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 05/26/2009 04:57 AM, Victor Lowther wrote:
> test-10 now completes sucessfully. What has changed:
hmm, it completed sucessfully on Fedora 11 without any problems..
>
> Added some logging functionality. All info, warning, and error messages
> are logged to a logfile, which is cleared on every dracut run.
>
> We no longer try to incrementally assemble mdraid arrays. It did not
> work using Ubuntu 9.04 x86_64. It is probably a bug in mdadm, but for
> now just fall back to auto assembly. A better fix would be appreciated, as
> long as it does not break the test suite and does not remove mdraid testing
> from the test suite.
worked on Fedora 11
$ rpm -qf /sbin/mdadm
mdadm-3.0-0.devel3.6.fc11.x86_64
>
> create-root.sh mounts the root filesystem straight away.
>
> It takes forever (or, at least 30 seconds) to actually unlock the LUKS device.
> This did not happen when the unlock was not done in a udev rule.
> It is either cryptseup behaving badly when called from udev, or demons.
huh? works instantly on Fedora 11
$ rpm -qf /sbin/cryptsetup
cryptsetup-luks-1.0.6-7.fc11.x86_64
>
> We should really not add all the network modules to the initramfs, at least for
> testing. Doing so really bloats things.
>
> Anyways, I am throwing this out there for discussion and ideas on better
> ways of fixing these warts.
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-26 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 2:57 [PATCH 1/1] Final fixups to make the full testsuite work Victor Lowther
[not found] ` <151d32e89583815962af8d721b17d0b320f80a2f.1243306326.git.victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-05-26 9:26 ` Harald Hoyer [this message]
[not found] ` <4A1BB5DE.3090206-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-05-26 12:15 ` Victor Lowther
[not found] ` <1243340142.4005.8.camel-76q0VzFBGGqhmyxYjSZgiRL4W9x8LtSr@public.gmane.org>
2009-05-26 13:27 ` Harald Hoyer
2009-05-29 11:02 ` Seewer Philippe
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=4A1BB5DE.3090206@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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