[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0611060030320.20361@twinlark.arctic.org>
Date: Mon, 6 Nov 2006 00:38:32 -0800 (PST)
From: dean gaudet <dean@...tic.org>
To: Neil Brown <neilb@...e.de>
cc: Kay Sievers <kay.sievers@...y.org>, Greg KH <gregkh@...e.de>,
Andrew Morton <akpm@...l.org>, linux-raid@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 001 of 6] md: Send online/offline uevents when an md
array starts/stops.
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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists