[systemd-devel] getty at .service.m4 and serial-getty at .service.m4

[Kay Sievers]

On Thu, Nov 11, 2010 at 12:39, Andrew Edmunds
<Andrew.Edmunds at yahoo.com.au> wrote:
> Kay Sievers wrote:
>> Michael, any chance to check if it's possible to avoid the mangling of
>> common util-linux tool names, and get a symlink in Debian package?
>> After that we can drop the ifdef stuff here.
>
> We can ask, but it has been that way for at least a decade so I'm
> guessing it's unlikely to be changed now. See this Debian bug from
> 2001, marked wontfix.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117596
>
> The Debian position actually seems quite logical to me.  Why do Fedora
> (and SUSE?) need to ship two different versions of getty and hence
> call one of them "alternate getty"?  Other people seem to manage quite
> well with only one.

We have only agetty from util-linux, there is no getty here.

>>> Is there a reason why this applies only to Fedora and Arch?  It seems
>>> > appropriate for all users as far as I can see.
>>
>> Only Fedora and Arch have rc.local. If you ask me rc.local is something
>> that should just die, hence I am very reluctant to support it on any
>> more distros than we currently support it on.

/etc/rc.local should not be in the default setup, it's legacy only
some distros did, and it does not make much sense in the systemd
context, especially not to run an empty shell script. :)

> Anyway, the point of this was only to have getty start late(ish) in
> the boot process, after most of the other services that are pulled in
> by multi-user.target. Maybe there is a better way to specify this, if
> not everyone has rc.local?

Yeah, others asked for that too. So far, we don't really have a
concept of 'late' or 'last' in systemd.

Kay