diff options
author | Dave Reisner <dreisner@archlinux.org> | 2012-02-11 19:53:49 +0100 |
---|---|---|
committer | Dave Reisner <dreisner@archlinux.org> | 2012-02-11 20:51:16 +0100 |
commit | d11ba0046d74b61f14c79c0793e53a99e51395cb (patch) | |
tree | 33ea3d3ac9d9062fb42448c3bc3b1a379c88e43d /01-memdisk.rules | |
parent | 9a2d5f4450d71803aa5013f8f1cdb5d962fb2617 (diff) | |
download | mkinitcpio-d11ba0046d74b61f14c79c0793e53a99e51395cb.tar.gz mkinitcpio-d11ba0046d74b61f14c79c0793e53a99e51395cb.tar.xz |
autodetect: refactor raid device detection
FS#10061 still isn't dead, its just resting:
https://bbs.archlinux.org/viewtopic.php?pid=1056003
An strace from a helpful user shows that our mdadm call is trying to
open a block device and the call never returns:
open("/dev/sdb", O_RDONLY|O_DIRECT|O_LARGEFILE
Fix this by only scanning explicitly the block devices we're interested
in, found via sysfs. This is an all around win for everyone, especially
users who have mdadm installed without any need for it.
This changes some of our assumptions about the environment:
- the mdadm binary exists when we find md devices in /sys
- the user running mkinitcpio isn't any specific UID or part of any
particular group, but merely has read access to the block devices
we're about to scan.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
Diffstat (limited to '01-memdisk.rules')
0 files changed, 0 insertions, 0 deletions