On Thu, 2015-03-05 at 22:10 +0100, Christoph Anton Mitterer wrote: > Hey. > > I'm a bit disturbed by seeing such a regression added so shortly before > release. > > AFAIU the NEWS entry: > >* If the /usr filesystem is on a RAID device and the INITRDSTART > > setting in /etc/default/mdadm is not 'all', you will need to change > > it to include that device. > > the value (which defaults to "none") needs now to be changed on all > systems whose /usr is on a MD device.
Note that this actually describes a change made in 0.117, not in 0.119. > But so far, this situation (at least mine, where *everything* is on one > single MD device) has been detected just perfectly well. Reconfiguration is only required if /usr is on a RAID device and / is not on that same device. Can you suggest a better way to word this? > I understand that one tries to make "more exotic" setups (e.g. /root not > on MD but /usr on it) working,... in fact I've already wrote > https://wiki.debian.org/AdvancedStartupShutdownWithMultilayeredBlockDevices > years ago about the whole unfortunate situation in Debian. > > But the above seems to go just one further step away from > things-working-out-of-the-box™ and making another place mandatory to > have boot device information configured. [...] The default is INITRDSTART=all and this continues to work. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein
signature.asc
Description: This is a digitally signed message part
