Matthew Miller (mattdm(a)mattdm.org) said:
How about:
- If /etc/inittab exists and contains an initdefault line, the default
target will be set accordingly.
- any other non-comment, non-blank lines in /etc/inittab will be logged as
warnings.
This leaves a migration path (ditch the file completely) while maintaining
some backwards compatibility. For a number of releases, the file can
continue to exist with a warning in the comments and the release notes, and
then eventually it can go away.
As stated in the bug, this would lead to a situation where you could
have both a initdefault line, and a default.target symlnk, that select
different things. How would you arbitrate?
Bill