On Fri, 16.11.12 11:14, Karel Zak (kzak@xxxxxxxxxx) wrote: > > On Wed, Nov 14, 2012 at 03:27:20PM +0100, Dr. Werner Fink wrote: > > Indeed this is a good solution ... but in the case of systemd and its > > getty generator we may think about a /etc/agettytab with a similar > > syntax scheme as the old /etc/inittab to be able to provide agetty > > options based on the used tty line. Clearly this /etc/agettytab should > > be parsed by agetty and options for the specified tty are found: > > > > 1:tty1:--noclear %p > > 2:tty2:%p > > 3:tty3:%p > > 4:tty4:%p > > 5:tty5:%p > > 6:tty6:%p > > S0:ttyS0:--erase-chars # --kill-chars @ -mt 60 %p 9600,2400,1200 > > S1:ttyS0:-L 9600 %p 9600 vt102 > > Hmm, I guess it's still possible to create tty line specific config > file on systems with systemd. I'd like to avoid another place where > will be configuration. Please do not add such a configuration file. In systemd, if people want to configure line-specific getty configuration they should just copy /usr/lib/systemd/system/getty@.service to /etc/systemd/system/getty@ttyS0.service and edit it there. Since systemd will first look for instantiated unit files, and only then fall back to generic template this should do the right thing. Lennart -- Lennart Poettering - Red Hat, Inc. -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
