linuxlogo for Debian
--------------------

Old versions of linuxlogo have modified /etc/issue file so that the selected
logo would display at the login prompt. Since this was a policy violation
(/etc/issue belongs to another Debian package) the Debconf selection was
dropped.

1. Instruction for users with sysv init systems (where inittab is present)

(Recommended) Scipt way

A good way is to use install_linux_logo from /usr/share/linuxlogo/ (thanks Barak A. Pearlmutter), and
invoke it install_linux_logo install|uninstall. 

Manual way

Users that want to show the logo in the login files have to manually edit
configuration files for this. You have several options:

  * (Recommended) Manually /etc/inittab:

    Add '-f /etc/issue.linuxlogo' to the getty lines in /etc/inittab for each
    terminal that will display Linuxlogo at the login prompt. For an ASCII logo
    use /etc/issue.linuxlogo.ascii. The line:

	1:2345:respawn:/sbin/getty 38400 tty1

    becomes:

	1:2345:respawn:/sbin/getty -f /etc/issue.linuxlogo 38400 tty1

  * Edit /etc/pam.d/login

    Change the (commented) issue definition:

	# auth	required	pam_issue.so issue=/etc/issue

    to:

	auth	required	pam_issue.so issue=/etc/issue.linuxlog

    Note: In old Debian releases you can also adjust the ISSUE_FILE definition
    in /etc/login.defs

You *can not* make a symlink (or a diversion) from /etc/issue to the
/etc/issue.linuxlogo files, if you do so the /etc/init.d/linuxlogo script will
fail as it uses /etc/issue to update the linuxlogo files.

2. Instructions for users with systemd 

As described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750781

The simplest approach - editing /lib/systemd/system/getty@.service and
adding the "-f /etc/issue.linuxlogo" parameter to the ExecStart line -
gives the right result, but that solution is vulnerable to being
overwritten on upgrade.  (You also need to remember to invoke
"systemctl daemon-reload && getty@tty1 start", making sure you aren't
logged in on TTY1 at the time.)

The next best option - copying the file to /etc/systemd/system and
editing it there - also works, though it still means losing any
improvements in later versions of the packaged service file.




 -- Barak A. Pearlmutter <bap@debian.org>, Fri,  8 Apr 2016 15:51:46 +0100