All of lore.kernel.org
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.15: mdrun, udev -- who creates nodes?
Date: Mon, 30 Jan 2006 20:47:43 +0000	[thread overview]
Message-ID: <20060130204743.GA13902@wonderland.linux.it> (raw)
In-Reply-To: <43DCA9CA.5020505@bl.com>

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

On Jan 30, linas <linas@austin.ibm.com> wrote:

> -- kernel scans /dev/hda1, looking for md superblock
> -- kernel assembles devices according to info found in the superblocks
> -- udev creates /dev/md0, etc. 
The problem is that some users and distributions build the drivers as
modules and/or disable in-kernel auto-assembly.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-01-30 20:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 11:40 2.6.15: mdrun, udev -- who creates nodes? Moshe Yudkowsky
2006-01-29 12:35 ` Marco d'Itri
2006-01-29 14:49 ` Moshe Yudkowsky
2006-01-30 20:42 ` linas
2006-01-30 20:47 ` Marco d'Itri [this message]
2006-01-31 16:40 ` Jason Lunz
2006-01-31 19:26   ` linas
2006-01-31 19:26     ` linas
2006-01-31 20:19     ` Molle Bestefich
2006-01-31 20:19       ` Molle Bestefich
2006-01-31 20:52       ` Jason Lunz
2006-01-31 20:52         ` Jason Lunz
2006-01-31 21:13         ` linas
2006-01-31 21:13           ` linas
2006-01-31 21:58           ` Molle Bestefich
2006-01-31 21:58             ` Molle Bestefich
2006-02-01  9:27             ` Andy Smith
2006-02-01 19:44               ` Luca Berra
2006-02-01 22:14                 ` Andy Smith
2006-02-02  1:27               ` Neil Brown
2006-01-31 21:44     ` Luca Berra
2006-01-31 21:44       ` Luca Berra
2006-02-10 22:46     ` Bill Davidsen
2006-02-10 22:46       ` Bill Davidsen

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=20060130204743.GA13902@wonderland.linux.it \
    --to=md@linux.it \
    --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 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.