Re: Cset 1.1490.4.201 - dasd naming

[Martin Schwidefsky]

Hi Pete,

> Martin, it is your architecture to break as you wish, but my gut feeling
> is that you'd never get away with this if you did it on anything using
> common use peripherals. This is a return to times of UNIX v6 and /dev/rk1a.
> The chief penguin repeatedly stated that he wanted to see /dev/diskN
> or similar (defined by a userland policy).
The idea was to get rid of the dasdxyz names which are not intuitive.

> Considering Fedora Core 2, I do not know if we have time to repair the
> damage. For the moment, I am patching a reverse patch.
Ok.

> Is there a story of a real world deployment where the 2.4 scheme was
> a hindrance which you could share? Honestly, I'm surprised you bring
> the matter of "persistent names" instead of, say, exhaustion of
> address range and majors.
That is probably the main argument to go back to the old names. After
udev and friends are in place it is not important how the disk is named
internally. The only place where it would surface is on the root=
parameter.

I'll discuss this with the Horst again to see if we really need the
dasd_<busid>_ names or if we can live with the old style names on the
root= parameter.

blue skies,
   Martin

Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@xxxxxxxxxx



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/