Re: Installation in russian
> At 5 Jan 04 15:22:02 GMT,
> Nikita V. Youshchenko wrote:
>> > I think installed packages at 1st stage should be smallest.
>> > I'm planning to use jfbterm for 2nd stage.
>>
>> Jfbterm and unifont also cost some space...
>
> Yes, but it can handle all of major language.
>
>> I'm not really familar with current DI status. Is debootstrap the only
>> tool used to install packages at the first stage? Seems not - at least
>> kernel package seems to be installed in another way.
>>
>> So maybe it is possible to install console-cyrillic at the first stage
>> only in cases when it is needed? And install jfbterm in other cases ...
>
> This needs to modify 1st stage frequently.
> We go to freeze 1st stage, so we may be refused such a thing.
> Sorry.
>
>> I believe that tools that require framebuffer should be used only when
>> really required. Linux framebuffer is not only slow, it does not always
>> work. Recently we had some problems with a recent NVidia video card -
>> linux text console worked, linux framebuffer console did not.
>> Also experience shows that X is more stable when framebuffer console is
>> disabled.
>>
>> > Could you test jfbterm whether fits Russian or not?
>> > 1. apt-get install jfbterm unifont
>> > 2. Enable your kernel Framebuffer driver
>> > 3. Run "jfbterm -c other,KOI8-R,iconv,UTF-8" (Does KOI8-R match for
>> > Russian?)
>> > 4. Check some debconf packages, apt-get messages, and so on.
>>
>> I just tried to start mc under jfbterm.
>> Immidiate problem is that pseudographics characters are displayed
>> incorrectly (letters are displayed instead).
>
> - jfbterm/unifont is used temporary for support multi languages on 2nd
> stage. After installation completed, terminal will come back old
> console (or run xdm).
But you can't disable framebuffer (and return to vga text console) without a
reboot, can you?
And even with reboot, this requires playing with kernel boot parameters,
which may be too difficult for non-technical user.
> - My code trys vesafb and vga16fb as same as 1st stage. Does these
> break nVidia? How about 1st stage?
One person here has had big problems with installing Debian at home because
installator (boot-floppies in that case) required framebuffer, and
framebuffer just didn't work on his system.
We could solve that problem only by putting his harddrive into another
computer and doing installation there.
I don't know how often such things happen, but if we take a look at current
policies of NVidia, ATI and other video chip vendors, we will see that they
prefer to close specifications of newer chips, and to be not strict at
following "old" standarts such as vesa. So probablythe situation when
framebuffer does not work on brand-new user's PC will be not uncommon in
foreseeable future.
Reply to: