From: Phil Dibowitz <phil@ipom.com>
To: linux-hotplug@vger.kernel.org
Subject: udev and mdX where X > 0
Date: Fri, 13 May 2005 08:16:55 +0000 [thread overview]
Message-ID: <42846277.7050507@ipom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
This has been discussed previously on the list:
http://sourceforge.net/mailarchive/message.php?msg_id=8778276
But I'm not really clear on a solution here - how do I get udev to
create /dev/md1 for my second raid array.
I found a page that mentioned adding (in debian) the following to
/etc/udev/links.conf:
M md1 b 9 1
Which appears to work, but given the text at the top of the file:
# This file does not exist. Please do not ask the debian maintainer
about it.
# You may use it to do strange and wonderful things, at your risk.
This is probably not the "right" way to do it - not only is that file
Debian-specific (best I can tell), it's, I'm guessing, interpreted by a
script that writes out proper udev rules.
So what's the "right" way to tell udev "hey, I need md1, always" ?
Thanks,
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2005-05-13 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 8:16 Phil Dibowitz [this message]
2005-05-13 8:18 ` udev and mdX where X > 0 Marco d'Itri
2005-05-13 8:38 ` Phil Dibowitz
2005-05-13 8:55 ` Marco d'Itri
2005-05-14 10:11 ` Phil Dibowitz
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=42846277.7050507@ipom.com \
--to=phil@ipom.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 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.