On Sat, May 12, 2007 at 08:35:22PM -0400, Albert Cahalan wrote: > > That's wrong too, since it'd still load a default font. > > I had to uninstall this defective package because it insisted > on loading a font at boot. That really screwed me up, as I was > using a kernel-supplied framebuffer font that wasn't available.
You have four options: 1. use the font face "VGA16" of console-setup which is similar to the kernel font. 2. Use a line "FONT=/usr/share/consolefonts/somefont" in /etc/default/console-setup in order to load a non-console-setup font. 3. Remove/deactivate /etc/rcS.d/S49console-setup and leave only S06keyboard-setup 4. Remove console-setup entirely > An 8-pixel-wide font is no good for me. I'm sure other people > have nice 9x16 VGA ROM fonts they'd like to keep. (can you even > handle a 9-pixel-wide VGA font correctly?) If you use a framebuffer, you don't have a 9x16 font. If framebuffer is not used, then 9x16 fonts are handled correctly. > In any case, DO NOT LOAD A FONT BY DEFAULT!!!! While it would be useful to have a configuration option to tell console-setup not to load a font (and maybe I will implement this in some future version), I doubt that most people need such a feature. > The most serious problem is in unicode_start, which should just issue > the command to put the console in UTF-8 mode without touching the > console font. I agree here with you at 100%. Both "kbd" and "console-tools" have a version of unicode_start and any change in this utility has to be coordinated between the two packages. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
