On Wed, 06.02.13 09:47, Colin Guthrie (co...@mageia.org) wrote: > The getty@.service used to specifically enable a getty@tty1.service > under getty.target when enabled. > > Modern versions of systemd allow commands such as: > systemctl enable getty@tty2.service > which automatically create the correct symlink if the > Install rule permits it. > > This changes the default getty@.service to follow this > now standard convension. > > Note: Packagers may need to change their initial install > rules due to this change (e.g. in rpm %post etc)
Hmm, but what happens then if people do run systemctl enable getty@.service? We really need to get the story right on this, I guess, so that something useful happens in both cases? > --- > units/getty@.service.m4 | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/units/getty@.service.m4 b/units/getty@.service.m4 > index 083eb97..bd89a47 100644 > --- a/units/getty@.service.m4 > +++ b/units/getty@.service.m4 > @@ -48,4 +48,4 @@ Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= > LC_COLLATE= LC_MONETA > KillSignal=SIGHUP > > [Install] > -Alias=getty.target.wants/getty@tty1.service > +WantedBy=getty.target Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
