Archives
Archives
| From: | Nikos Chantziaras <realnc@×××××.de> | ||
|---|---|---|---|
| To: | gentoo-user@l.g.o | ||
| Subject: | [gentoo-user] Re: Kernel update messed up console encoding | ||
| Date: | Sun, 01 Mar 2009 12:48:47 | ||
| Message-Id: | goe06g$7d6$1@ger.gmane.org | ||
| In Reply to: | Re: [gentoo-user] Re: Kernel update messed up console encoding by "Florian v. Savigny" |
||
| 1 | Florian v. Savigny wrote: |
| 2 | > [...] |
| 3 | > But still, I am wondering how to get the new kernel to behave as I |
| 4 | > want out of the box. My best guess is now that this console behaviour |
| 5 | > has become the default at some point between kernels 2.6.17 and |
| 6 | > 2.6.27, and that you now have to switch it off explicitely. But how? |
| 7 | |
| 8 | Maybe the commands "unicode_start" and "unicode_stop" might help. |
| Subject | Author |
|---|---|
| Re: [gentoo-user] Re: Kernel update messed up console encoding | "Florian v. Savigny" <lorian@××××××××.de> |