On Mon, 6 Nov 2006, Neil Brown wrote:
> This creates a deep disconnect between udev and md.
> udev expects a device to appear first, then it created the
> device-special-file in /dev.
> md expect the device-special-file to exist first, and then created the
> device on the first open.
could you create a special /dev/mdx device which is used to
assemble/create arrays only? i mean literally "mdx" not "mdX" where X is
a number. mdx would always be there if md module is loaded... so udev
would see the driver appear and then create the /dev/mdx. then mdadm
would use /dev/mdx to do assemble/creates/whatever and cause other devices
to appear/disappear in a manner which udev is happy with.
(much like how /dev/ptmx is used to create /dev/pts/N entries.)
doesn't help legacy mdadm binaries... but seems like it fits the New World
Order.
or hm i suppose the New World Order is to eschew binary interfaces and
suggest a /sys/class/md/ hierarchy with a bunch of files you have to splat
ascii data into to cause an array to be created/assembled.
-dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
