Bug#773173: Bug#757298: Please add fallback boot entry for sysvinit when systemd is the active init

[Colin Watson]

On Sat, Jan 10, 2015 at 05:46:04PM +0100, I. Schrey wrote:
> So, before the 2.02~beta2-20 update "1>6" was
> 'Debian GNU/Linux, with Linux 3.12.0-svs-amd64'
> 
> After the update "1>6" would be
> 'Debian GNU/Linux, with Linux 3.14.0-svsi-amd64'
> because of the extra 'menuentry' lines, so I had to change the
> default entry to "1>9" to get the old behaviour back.
> 
> (that 3.14.0-svsi kernel package was missing some modules, so the
> system was unreachable after reboot. Now I guess you could say that was
> partly my fault for installing unsuitable kernels on a headless system,
> but still.. the new default boot took me by surprise)
> 
> 
> I guess if
> GRUB_DEFAULT="0" or
> GRUB_DEFAULT="<menuentry name>"
> I wouldn't have noticed?

Oh, right, there's absolutely no guarantee that menu entry numbers won't
change.  This is exactly why the ability to set the default to a name
was introduced; you need to use that if you want predictable behaviour
across upgrades.

(In this case, of course, you'd need to use two names separated by ">"
to account for the submenu.)

-- 
Colin Watson                                       [cjwatson at debian.org]