[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#250789: termwrap unloads the charset mapping in second-stage installation



* Joey Hess [2004-05-25 13:52:28-0300]
> Recai Oktas wrote:
> > When I retested it, I modified the termwrap code so as to immediately 
> > exit after calling the base-config, that is:
> > 
> > 	[...]
> > 
> > 	$@
> > 
> > 	exit $?
> > 
> > 	case $ENCODING in
> > 
> > and I found the console as it should be.
> 
> This would give you one usable console, until you rebooted, and nothing
> else. 

No, this is not correct.  Please note that console keyboard is already 
configured in prebasecoonfig and console screen is also set by an init 
script (console-screen.sh) before reaching the base-config.  'termwrap' 
does the _final touch_ by generating the required locale and runs the 
base-config in user's language.  That is, the patch I sent for this bug, 
provides a correct and _permanent_ Turkish console, though it does not 
conform to the whole picture by treating Turkish as a special case.  I 
rather prefer a more natural solution.  I guess the same problems may 
also true for other ISO encodings (asian encodings are different and 
cyrillic consoles have their own settings).

> That's why base-config doesn't do it, it's out of its scope to set
> up properly configured terminals after the initial system 
> installation.

Yes, this is a reasonable argument, but isn't it be good to find a 
correctly localized console after finishing the whole installation?

Regards,

-- 
roktas

Attachment: signature.asc
Description: Digital signature


Reply to: