Bug#639830: mdadm: alternative md-device names

[Cristian Ionescu-Idbohrn]

On Sat, 26 May 2012, Michael Tokarev wrote:
>
> There's another possibility -- to try to detect such a disparity
> (when one place uses one name and another place uses alternative
> name) and fail if found.

This sound like a good idea: detect the disparity and recommend the proper
alternative?

> But I like this version less, -- it is
> less ugly in case of the device nodes it creates, but it has more
> chances to make the system unbootable...

Well, you're the one with deeper insight ;)

Aren't there (at least) 2 parts involved in this?  The "producers"
joggling with device nodes/symlinks creation and the "consumers" which
expect to find those files in place?  Is there a risk some other package
was not doing what was expected?


Cheers,

-- 
Cristian