Hallo Laurent! >> The best way would be to evolve tovards using data formats >> and command-line options which are compatible with relevant >> standard tools. > There is no standard as far as keyboard tables go. Every Unix flavour > has its own utility. For instance, OpenBSD has 'wsconsctl'. > 'loadkeys' is just a well-known tool that manages keyboard tables > under Linux, and it is only widely used because nobody ever bothered to > design another one. That hardly makes it a standard. True, in the sense of Unix standard. As you tell "loadkeys" is the de-facto standard in Linux. As Busybox is mainly a Linux tool (or started at least as this), I assumed Denys talks about that de-facto standard.
> Having the same interface as "loadkeys" offers one benefit: busybox can then > be used as a drop-in replacement for original loadkeys. > This benefit should be compared to the benefit of designing and using > a leaner interface, that will not require including a full table parser > into the busybox binary. That is true, but blows up the complexity and resource requirements of keyboard table loading in Busybox a lot. Especially in init RAM file systems this would consume a lot of unnecessary space (and some extra startup time too). IMHO keyboard table definitions are not that often changed that they really need to be stored in an ASCII table and loaded from that table on every system startup. Creating a binary key table from it's source definition is in my eyes like compiling a program. We do not include the source of every program in a startup system neither do we install a compiler on every such system. That is, why I would like to stay with "pre-compiled" binary key tables (not including the full blown keyboard table "compiler" on every startup system). -- Harald Special note to Laurent: This message is created using "Reply all" ... Thunderbird honors your "Mail-Followup-To" (just for your information). _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
