On Wednesday 16 September 2009 20:25:57 Samuel Thibault wrote: > ATM, if one runs cat from a VT with a UTF-8 locale, type a non-ascii > character, backspace, enter, the first byte of the utf-8 encoding > non-ascii will remain in the stream. This is because the iutf8 flag is > not set. getty clears it because it is not supposed to know anything > beyond ascii. login, however, is responsible for loading the initial > environment through the pam_env.so PAM module, and then knows which > locale is configured on the system. There should be a PAM module (could > be named pam_tty for instance) which basically does
except that the locale is rarely configured through pam_env, and this doesnt work with a non-pam environment. and throwing another pam module into the mix sounds like throwing crap onto the pile rather than addressing it at the right place. this is why the `unicode_start` and `unicode_stop` programs exist -- for people to dynamically change the console input mode. and why the keyboard/console font init scripts exist -- to set the defaults. and why the kernel now defaults all consoles to iutf8 on by default. perhaps you meant to file a bug about agetty not preserving the IUTF8 flag. certainly nothing needs to be changed in the shadow package. -mike
signature.asc
Description: This is a digitally signed message part.
