search for: ktl

On Thu, 06 Jun, at 01:11:53AM, poma wrote: > > Standalone directive 'kbdmap <kbd>.ktl' doesn't work within series 5. > Tested via 5.00, 5.01 and 5.10. > It works within series 4 - tested via 4.05 and 4.06. > Is it a bug, or is it a feature? Could you provide me with your .ktl file? -- Matt Fleming, Intel Open Source Technology Center

On 12.06.2013 14:41, Matt Fleming wrote: > On Thu, 06 Jun, at 01:11:53AM, poma wrote: >> >> Standalone directive 'kbdmap <kbd>.ktl' doesn't work within series 5. >> Tested via 5.00, 5.01 and 5.10. >> It works within series 4 - tested via 4.05 and 4.06. >> Is it a bug, or is it a feature? > > Could you provide me with your .ktl file? [1] manual mode within "boot:" prompt *do* work:...

On Thu, 13 Jun, at 12:40:48PM, poma wrote: > Regarding [1], [2], and [3], I somehow doubt that this is a '*.ktl' i.e. > "Keyboard Table for Lilo" problem. > Which ones of these[4] produced by the 'keytab-lilo' you need? > All of them[4] were tested. ;) Any one will do. I just want to reproduce this bug. -- Matt Fleming, Intel Open Source Technology Center

On 13.06.2013 13:04, Matt Fleming wrote: > On Thu, 13 Jun, at 12:40:48PM, poma wrote: >> Regarding [1], [2], and [3], I somehow doubt that this is a '*.ktl' i.e. >> "Keyboard Table for Lilo" problem. >> Which ones of these[4] produced by the 'keytab-lilo' you need? >> All of them[4] were tested. ;) > > Any one will do. I just want to reproduce this bug. http://goo.gl/O9UwH poma -------------- next...

...; > > > keytab-lilo - out of service > http://bugzilla.syslinux.org/show_bug.cgi?id=68 > keytab-lilo is just a Perl script invoking the "loadkeys" program. Generic example (as root): # keytab-lilo.pl /path/to/us.kmap.gz /path/to/dvorak.kmap.gz > /path/to/dvorak.ktl or: # keytab-lilo.pl /path/to/us.map.gz /path/to/dvorak.map.gz > /path/to/dvorak.ktl or: # keytab-lilo.pl /path/to/us.map /path/to/dvorak.map > /path/to/dvorak.ktl Then copy the resulting "dvorak.ktl" file to "/boot/syslinux/" (or to the relevant location for Syslinu...

...syslinux.org/show_bug.cgi?id=68 >>> >> >> >> keytab-lilo is just a Perl script invoking the "loadkeys" program. >> >> Generic example (as root): >> # keytab-lilo.pl /path/to/us.kmap.gz /path/to/dvorak.kmap.gz > >> /path/to/dvorak.ktl >> >> or: >> # keytab-lilo.pl /path/to/us.map.gz /path/to/dvorak.map.gz > >> /path/to/dvorak.ktl >> >> or: >> # keytab-lilo.pl /path/to/us.map /path/to/dvorak.map > >> /path/to/dvorak.ktl >> >> Then copy the resulting "dvorak....

Hello, Long story short, example config: ### cut UI vesamenu.c32 MENU TITLE Multiboot USB MENU BACKGROUND #00000000 MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all MENU COLOR unsel 37;44 #50ffffff #a0000000 std MENU COLOR tabmsg 31;40 #30ffffff #00000000 std MENU BEGIN MENU TITLE System Rescue CD 2.4.1 INCLUDE sysrcd-2.4.1.conf MENU END MENU BEGIN MENU TITLE

...4.1 scandelay=1 setkmap=uk vga=791 docache dostartx LABEL fd64 MENU HIDE LINUX /sysrcd-2.4.1/rescue64 INITRD /sysrcd-2.4.1/initram.igz APPEND subdir=sysrcd-2.4.1 scandelay=1 setkmap=uk vga=791 docache dostartx LABEL azerty MENU HIDE KERNEL kbdmap.c32 APPEND /sysrcd-2.4.1/maps/azerty.ktl LABEL be MENU HIDE KERNEL kbdmap.c32 APPEND /sysrcd-2.4.1/maps/be.ktl LABEL bg MENU HIDE KERNEL kbdmap.c32 APPEND /sysrcd-2.4.1/maps/bg.ktl LABEL by MENU HIDE KERNEL kbdmap.c32 APPEND /sysrcd-2.4.1/maps/by.ktl LABEL cf MENU HIDE KERNEL kbdmap.c32 APPEND /sysrcd-2.4.1/maps/cf...

...d to complicate the matter, we're often logged on to Citrix and into some sort of remote java gui console. All of these complicate the issue (or at least do not improve it). Now, somehow I hoped the solution would be fairly simple. Take the us.map, take the be-latin1.map, create a be_latin.ktl out of it by running: /usr/lib/syslinux/keytab-lilo.pl us.map be-latin1.map >be_latin1.ktl Beware that I had to modify the default path inside the perl script and unzip the maps that usually are zipped on my system. Also beware that the file be-latin1.ktl will end up being be_latin1.ktl. N...

...rvice >> http://bugzilla.syslinux.org/show_bug.cgi?id=68 >> > > > keytab-lilo is just a Perl script invoking the "loadkeys" program. > > Generic example (as root): > # keytab-lilo.pl /path/to/us.kmap.gz /path/to/dvorak.kmap.gz > > /path/to/dvorak.ktl > > or: > # keytab-lilo.pl /path/to/us.map.gz /path/to/dvorak.map.gz > > /path/to/dvorak.ktl > > or: > # keytab-lilo.pl /path/to/us.map /path/to/dvorak.map > > /path/to/dvorak.ktl > > Then copy the resulting "dvorak.ktl" file to "/boot/syslinu...

Hello, First of all, thanks very much for this piece of software, it's working like a charm. I'm using it to boot a Linux distro I'm working on. What I want to deal with is the display of accented characters in ISOLINUX. First, I set EXTLINUX up to boot an ext2-formatted USB stick. No problem so far. I wrote a config file ordering to load a font (lat-9w) to display french

On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote: > How this change would affect users with older versions of kbd / > loadkeys / or in older OSes? I mean, let's assume a user using a newer > version of Syslinux (containing this proposed change in its keytab-lilo > perl script) but with an older OS / older version of kbd / loadkeys / > map files. The changed

.../doc/keytab-lilo.txt b/doc/keytab-lilo.txt >> index cdbea0f..f35b3e8 100644 >> --- a/doc/keytab-lilo.txt >> +++ b/doc/keytab-lilo.txt >> @@ -83,3 +83,7 @@ where <kbd> is the name of the keyboard layout. >> Example: >> >> keytab-lilo.pl de >/boot/de.ktl >> + >> +on Fedora: >> +keytab-lilo /usr/lib/kbd/keymaps/legacy/i386/qwerty/us.map.gz /usr/lib/kbd/keymaps/legacy/i386/qwertz/cz.map.gz > cz.ktl >> + >> -- >> 2.4.3 >> > > > The doc/keytab-lilo.txt file (and its wikified equivalent) is a co...

...(+) > > diff --git a/doc/keytab-lilo.txt b/doc/keytab-lilo.txt > index cdbea0f..f35b3e8 100644 > --- a/doc/keytab-lilo.txt > +++ b/doc/keytab-lilo.txt > @@ -83,3 +83,7 @@ where <kbd> is the name of the keyboard layout. > Example: > > keytab-lilo.pl de >/boot/de.ktl > + > +on Fedora: > +keytab-lilo /usr/lib/kbd/keymaps/legacy/i386/qwerty/us.map.gz /usr/lib/kbd/keymaps/legacy/i386/qwertz/cz.map.gz > cz.ktl > + > -- > 2.4.3 > The doc/keytab-lilo.txt file (and its wikified equivalent) is a copy of the original file from LILO; it act...

Hi, I was excited to find the kbdmap module, but have some problems making it work with keyboard mapping files that works fine with syslinux. I tried by using both: label be menu label ^Belgian (be) kernel kbdmap.c32 maps/be.ktl as well as: label be menu label p Belgian (be) kernel kbdmap.c32 append maps/be.ktl but I always get the error: Keyboard map file format error According to the sourcecode this is related to a file length issue. However the file works fine with syslinux and the files are e...

Standalone directive 'kbdmap <kbd>.ktl' doesn't work within series 5. Tested via 5.00, 5.01 and 5.10. It works within series 4 - tested via 4.05 and 4.06. Is it a bug, or is it a feature? poma

...KERNEL chain.c32 APPEND hd0 1 # Sous-menu pour les choix de claviers : MENU SEPARATOR LABEL - MENU LABEL Passer en ligne de commande MENU DISABLE MENU SEPARATOR LABEL be MENU LABEL Charger le clavier belge MENU INDENT 1 KERNEL kbdmap.c32 APPEND claviers/be.ktl LABEL cf MENU LABEL Charger le clavier canadien MENU INDENT 1 KERNEL kbdmap.c32 APPEND claviers/cf.ktl LABEL ch MENU LABEL Charger le clavier suisse MENU INDENT 1 KERNEL kbdmap.c32 APPEND claviers/ch.ktl LABEL fr MENU LABEL Charger le clavier fran?ais...

...o editing the original doc). Editing the original document should mean to actually re-write it for Syslinux with relevant and current info. > > BTW, we should find some way to support changing the keyboard map for > > UEFI too. > > > > I do not know whether the "ktl" file / method can be effectively used > > in UEFI. If it can, then it would be desirable for the kbdmap directive > > to be available for UEFI too, and it would be desirable for the > > kbdmap.c32 module to be improved so to support UEFI too. > > > > You can...

Hi I'm trying to read SAS-data on VAX/VMS to Windows R using foreign pakage read.xport and experience some problems. Following lines are used in SAS to create XPORT file LIBNAME a ''xxx; LIBNAME b XPORT ''; PROC COPY IN=a OUT=b; RUN; and I succeed in getting file that looks like correct xport file.However when typing in R following

Dear all, Has anybody tried numerical solving of ODE's and/or transport equations in R? (Don't ask how we ended up in using R for this job, in the first place!) More precisely, does anybody know any technical issue that could make the work insecure in the sense of propagation of errors? Is there any track of evidence that R is, in this kind of task, less reliable than e.g. MatLab?