[systemd-devel] Have custom agetty behaviour even after upgadres
Wulf C. Krueger
philantrop at exherbo.org
Tue May 15 08:47:25 PDT 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Lennart,
On 14.05.2012 23:34, Lennart Poettering wrote:
>> I'll bring this closer to home. Why does "make
>> DESTDIR=%{buildroot} install" write to $(sysconfdir) when you've
>> always proclaimed that it's admin territory? Why not write this
>> link as: $(systemunitdir)/getty.target.wants/getty at tty1.service?
> Since this is just about enabling, not about shipping
> configuration. People will frequently not enable the getty on tty1,
> on servers with serial gettys and on containers for example.
I'd say, leave the entire enabling part to the distro/packager and
don't do the linking at all.
It's up to the distro to decide about a sane default installation with
respect to about every other part of systemd already - why make this
an exception?
- --
Best regards, Wulf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+yeo0ACgkQnuVXRcSi+5pffwCeN4nbBuJAu2OmwqA1di3m43d8
db8An0hy4mfbgGsfj6/kbAcdU+WfmkQp
=3lBX
-----END PGP SIGNATURE-----
More information about the systemd-devel
mailing list