similar to: Help me, where to find layout/language settings

Displaying 20 results from an estimated 6000 matches similar to: "Help me, where to find layout/language settings"

2016 Mar 07
2
keytab-lilo: update to support kbd 2.0.3 format
On 29.12.2015 22:51, poma wrote: > On 29.12.2015 22:20, Ady via Syslinux wrote: >> >>> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote: >>>> 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
2013 Jun 12
2
KBDMAP - extlinux 5.xx
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
2016 Mar 07
2
keytab-lilo: update to support kbd 2.0.3 format
On 07.03.2016 19:24, Ady via Syslinux wrote: >> doc: keytab-lilo example on Fedora >> >> --- >> doc/keytab-lilo.txt | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> 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 @@
2020 Jun 24
1
Blog article about the state of CentOS
On 6/24/20 12:27 PM, Lamar Owen wrote: > ... You can look in the %{BUILDTIME} query tag for build order; use > the following command to get the order: > rpm -qa --queryformat "%{BUILDTIME} %{NAME} %{EPOCH} %{VERSION} > %{RELEASE}\n" | sort So, replying to my own post here, as build order is only part of the story.? Determining the contents of what was in the actual
2009 Feb 08
2
keytab-lilo included with SYSLINUX is not up to date
Hi, I just noticed that the keytab-lilo utility included with SYSLINUX isn't up to date. It *is* a problem since the old version isn't compatible with current distributions like Debian ou Ubuntu (for example). Two options are offered to those who would like to use keytab-lilo in order to generate a file compatible with the KBDMAP directive : - use an up to date version of keytab-lilo
2002 Oct 16
5
kbdmap & ASCII > 128
Hi, I've just played around with kbdmap in pxelinux. I always wondered why there was no translation for "AltGr"-Keys (the right 'Alt'-Key) (AltGr-Q generates "@" on a german keyboard e.g.), and I found in conio.inc (syslinux 1.76): getchar: [..] .kbd: xor ax,ax ; Get keyboard input int 16h and al,al jz .func_key mov bx,KbdMap ; Convert character sets
2015 Dec 29
2
keytab-lilo: update to support kbd 2.0.3 format
> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote: > > 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
2002 Oct 21
2
strange problem with pxelinux - Config file size limit?
Hi, I have some strange problem with pxelinux. I have a quite big config file (>8K), with much labels (29), long append's and some texts on the F-Keys (F1-F5). This works as expected, pxelinux loads all labels without a peep. Now I added 'kbdmap kbd-de' to this config file - and I get strange errors all over. pxelinux reports several times 'Unknown keyword in config file.'
2006 Mar 23
1
Syslinux keyboard mappings
Hi, I finally want to end the fights we have had in the past with keyboard mappings. I already curse the person who is responsible for this keyboard mess (and even more the persons who could have create a 'detect keyboard' kind of functionality in modern PCs :)) But the general problem is this, BIOSes are US qwerty, Belgium uses be-latin1 (azerty with lots of custom keys). And to
2015 Dec 27
2
keytab-lilo: update to support kbd 2.0.3 format
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
2013 Jun 13
2
KBDMAP - extlinux 5.xx
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
2015 Dec 27
2
[PATCH] keytab-lilo: update to support kbd 2.0.3 format
Since kbd 2.0.3 (commit 6ff47cf2) the format generated by 'loadkeys -m' has changed slightly, using "unsigned short" instead of "u_short" Signed-off-by: Olivier Brunel <jjk at jjacky.com> --- utils/keytab-lilo | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/utils/keytab-lilo b/utils/keytab-lilo index 9e34160..337a869 100755 ---
2020 Jun 20
3
Blog article about the state of CentOS
On 20/06/20 3:50 am, Johnny Hughes wrote: > Your dates are significantly off > Wikipedia has a delay listed in a table: > > It is, for CentOS-7, For example: > > 7.0 27 > 7.1 26 > 7.2 25 > 7.3 39 > 7.4 43 > 7.5 31 > 7.6 34 > 7.7 42 > 7.8 28 > > > For 6 .. since 6.2, it has bee3n between 10 and 18 days. > > For 8: > > 8.0
2013 Jun 05
1
KBDMAP - extlinux 5.xx
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
2009 May 22
0
[LLVMdev] Arm port
Samuel Crow wrote: > > > > > ----- Original Message ---- >> From: Chuck Robey <chuckr at telenix.org> >> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >> Sent: Friday, May 22, 2009 9:22:53 AM >> Subject: Re: [LLVMdev] Arm port >> >> OK, I've got enough to go on with, and I'm getting ready right now to begin
2013 Sep 04
5
5.10 regression (from 5.01) MENU INCLUDE broken.
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
2020 Jun 24
0
Blog article about the state of CentOS
On 6/20/20 6:50 AM, Peter wrote: > On 20/06/20 3:50 am, Johnny Hughes wrote: > >> And EL8 is exponentially harder with an entirely new build system and >> the requirement to build modules. > > But it seems like every major release has had reasons to be > exponentially harder than the last.? With 7 it was the shift to using > the git sources instead of the SRPMS that
2008 Aug 30
1
booting w98 bootdisk via memdisk
Hallo, I try to boot the windows 98 bootdisk via memdisk. It doesn't work completely. Booting a freedos FD image works, booting the windows 98 image works too. But the windows 98 boot disk then should extract the file "ebd.cab" with the file "extract.com", and that step fails. Is that a syslinux problem or a windows problem? Viele Gruesse! Helmut
2003 Jun 20
1
Remapping Serial Keyboard Input with SYSLINUX
I have a system with a Matrix Orbital keypad (only) on ttyS0 which generates it own strange bytes when keys are pressed. Is there something similar to the KBDMAP directive but for serial input? This is a serious problem for us (i.e. we have to remap the 'L' character to be interpreted the same as an "Enter" (i.e. <cr>)) and so if there isn't a way of doing this
2017 Feb 03
2
KBDMAP and chainloading supported by syslinux.efi?
Hallo List, Maybe someone on the list can answer these questions for everyone concerning the more or less experimental syslinux.efi for UEFI boot: 1. Is the KBDMAP directive supported by syslinux.efi? In my tests with a german keymap generated as documented in http://www.syslinux.org/wiki/index.php?title=Config#KBDMAP only the BIOS version of syslinux loads and sets the correct keymap, while the