bug#44347: closed (mingetty --no-clear is hard-coded)

[GNU bug Tracking System]

Your message dated Thu, 03 Dec 2020 18:12:14 +0100
with message-id <87lfeebyq9.fsf@gnu.org>
and subject line Re: bug#44347: mingetty --no-clear is hard-coded
has caused the debbugs.gnu.org bug report #44347,
regarding mingetty --no-clear is hard-coded
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44347: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44347
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> mingetty --no-clear is hard-coded
>
>
>
>
> Date: 
>
> Sat, 31 Oct 2020 09:16:19 -0600
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Icedove/78.4.0
>
>
>
>
> The --no-clear option is hard-coded for mingetty, with no documentation 
> about why. The mingetty page says,
>        --noclear
>               Do not clear the screen before prompting for the login 
> name (the
>               screen is normally cleared).
>
> I do not think I am alone in preferring the screen cleared after logout. 
> I also think it could be a security issue. For now my workaround is to 
> include a call to "tput reset" or "clear" in my .bash_logout script, but 
> that has to be configured for every user and requires more packages 
> installed either at the system level or per-user.
>
> I think this is an "easy for beginners" issue. I would fix it myself, 
> but I have a lot of other stuff to do.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#44347: mingetty --no-clear is hard-coded
>
>
>
>
> Date: 
>
> Thu, 03 Dec 2020 18:12:14 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
>
>
>
>
> This was fixed by commit e3ae31347882b25e1513e4475616fb6e4497e280.
>
> Closing!
>
>
> --- End Message ---