On Mon, Mar 11, 2002 at 04:51:03AM -0500, Roland McGrath wrote: > That is a wacky notion, but it might just make sense. Certainly using the > xkb utilities from X directly is an attractive idea. Not only is the > configuration based on a compatible format, it's actually the very same > commands to do the configuration to a pseudo-X server that is a virtual > console.
Indeed. > I wouldn't want the console server talking to xfs the way the X > server does, though. For loadfont, you still want a user program that gets > font data from whereever (including from an xfs, or all manner of format > conversions it might do) and loads the data into the console server. Maybe I don't know enough about the xfs protocol. But it seems to me a very good thing if the console server can copletely configure itself from the passive translator setting, without requiring to run a loadfont program or anything. This works either by specifying a filename, or maybe by setting a font server and an X font name (or a directory search list plus an X font name). The general notion here is getting rid of scripts to run at boot time. But I also see your point about uploading a font that isn't a file or a font in a font dir or font server anywhere at all, so we should have both (although if you have an helper program, you can probably always write the font into a temporary file, too). Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
