On Tue, Mar 06, 2018 at 10:40:14AM +0100, Ludwig Nussel wrote: > I just noticed that agetty gained support for /etc/issue.d. Very cool! Thanks, according this feedback https://github.com/karelzak/util-linux/commit/1fc82a1360305f696dc1be6105c9c56a9ea03f52#commitcomment-27947668 it seems that /etc/issue.d may conflict with already existing solutions in OpenSUSE. Is it true? I'll probably add --disable-agetty-issued to make it fully backwardly compatible. > Are there any plans to extend the way it reads those files to a systemd > style layering ie with read only parts in /usr, potentially generated > ones in /run etc? Good idea. > Especially the read only part would be interesting. That way distros > wouldn't need to ship /etc/isse at all and packages would put their > extension in /usr. Ie no interference with admin space. What is expected semantic (order)? Note that agetty requires the /etc/issue file, the directory is an extension to the file. The file may be empty or symlink. This is because "rm /etc/issue" is a way how some admins disable agetty output at all. with layering: - verify /etc/issue (access F_OK -- required) - read /etc/issue.d/*.issue - read /run/agetty/issue.d/*.issue - read /usr/lib/agetty/issue.d/*.issue use-case: - /etc = system specific files - /run = generated files - /usr = installed 3rd party files right? IMHO it's too late to implement it for v2.32. (CC: to our list) Karel -- Karel Zak <kzak@xxxxxxxxxx> http://karelzak.blogspot.com -- 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
