[Bug-report] [Lunar Linux 0000217]: Escape chars in /etc/issue and /etc/issue.net

[bug-reports at lunar-linux.org]

The following bug has been RESOLVED.
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000217
=======================================================================
Reporter:                   tjacobs
Handler:                    tchan
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000217
Category:                   base
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     resolved
Resolution:                 won't fix
=======================================================================
Date Submitted:             2003-01-29 19:55 GMT
Last Modified:              2003-01-31 02:39 GMT
=======================================================================
Summary:                    Escape chars in /etc/issue and /etc/issue.net
Description: 
Every install produces the following text in the named files:

Lunar Linux 1.2 (Pico)
Kernel \r on an \m
=======================================================================

-----------------------------------------------------------------------
 sofar - 2003-01-29 19:57 GMT 
-----------------------------------------------------------------------
unfortunately not trivial, but known. only occurs on the second? time the
issue gets drawn on screen...

-----------------------------------------------------------------------
 sofar - 2003-01-29 22:17 GMT 
-----------------------------------------------------------------------
Lurch was so kind to tell us:

===========
lo all,

I've just been doing some diggin on this, and this is what I found: it's 
perfectly normal behaviour... :)

on startup /etc/inittab spawns an agetty, which reads /etc/issue, and
expands 
the escape codes... (as explained in the man page)

however, after you enter the username in agetty, control is passed to 
/bin/login (which checks the login/password) until a valid username is 
entered (in other words /bin/login just sits in a loop until a valid
username 
is entered, or a timeout occurred).. If a valid username is entered, you
get 
your shell, if it times out, /bin/login exits, which causes agetty to be 
respawned from /etc/inittab, and the escapes will be handled correctly 
again... :)

if you really wanted to fix it, you could just have /bin/login call
exit(0) in 
/bin/login instead of have it call it's own version of login_prompt (in 
libmisc/loginprompt.c) in src/login.c, in which case it would respawn an 
agetty and read /etc/issue correctly again...

HTH,

Lurch_