From: Andreas Jellinghaus <aj@leogic.com>
To: linux-hotplug@vger.kernel.org
Subject: udev and mkraid
Date: Tue, 22 Jun 2004 12:37:36 +0000 [thread overview]
Message-ID: <pan.2004.06.22.12.37.36.47922@leogic.com> (raw)
Hi,
how to mkraid on an udev system?
/dev is a tmpfs and has only inodes found via /sys
(created by udevstart).
Now there is no md0, so there is no md0 device in /dev,
so I can't make an md0 with mkraid. But if I could,
udev would create an md0 device.
Oh well.
Either the mkraid tool should know how to create an md
device without /dev/mdX existing, or the kernel md driver
should always export all possible md via sysfs, even if
they don't exist, so mkraid can create them.
Did I miss anything?
As a hack, I'm running mknod before mkraid.
But it would be nice, if some day that would
no longer be necessary. It defeats the whole purpose
of mkraid in my opinion.
So if you know a better way, please let me know.
Regards, Andreas
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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
next reply other threads:[~2004-06-22 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 12:37 Andreas Jellinghaus [this message]
2004-06-22 12:57 ` udev and mkraid Kevin P. Fleming
2004-06-22 22:15 ` John L Fjellstad
2004-06-23 12:59 ` Kevin P. Fleming
2004-06-23 20:46 ` John L Fjellstad
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=pan.2004.06.22.12.37.36.47922@leogic.com \
--to=aj@leogic.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).