From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.14, 2.6.15 md mystery partially solved (was: 2.6.15: mdrun,
Date: Mon, 06 Mar 2006 17:00:59 +0000 [thread overview]
Message-ID: <440C6ACB.8010701@bl.com> (raw)
In-Reply-To: <440BB623.30507@bl.com>
If anyone is interested, the reason I couldn't boot 2.6.15 wasn't udev
-- it was initramfs-tools. Several separate bugs!
* the md module wasn't being loaded because it'd been renamed to md-mod,
and even when that was fixed md-mod wasn't being loaded because modprobe
doesn't put out the insmod line we'd expect from the modprobe documentation.
* mdrun attempts to create an /dev/md/0. I gave up and replaced mdrun
with "mkdir /dev/md; mdadm --scan --auto".
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug55580> for full details.
And I'm pleased to report that udev properly creates the symlinks from
/dev/mdN to /dev/md/N -- mdrun's symlinking is not required.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-03-06 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 4:10 2.6.14, 2.6.15 md mystery partially solved (was: 2.6.15: mdrun, udev Moshe Yudkowsky
2006-03-06 17:00 ` 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=440C6ACB.8010701@bl.com \
--to=msha5_17@bl.com \
--cc=linux-hotplug@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).