[syslinux] Keyboard stops working

[Jim Cromie]

Samuel Clements wrote:

>> Yes, it will be fun. You will feel being a newbie again.
>>
>
:-D

one way to narrow your investigations; see what changed !
most of these you can skip for any particular item in Changelog.

[jimc at harpo syslinux]$ diff -ru syslinux-3.08 syslinux-3.09-pre2 | grep +++
+++ syslinux-3.09-pre2/com32/lib/Makefile       2005-05-19 
15:30:50.000000000 -0600
+++ syslinux-3.09-pre2/config.inc       2005-06-15 23:52:44.000000000 -0600
+++ syslinux-3.09-pre2/conio.inc        2005-06-15 22:39:19.000000000 -0600
+++ syslinux-3.09-pre2/NEWS     2005-06-15 23:52:44.000000000 -0600
+++ syslinux-3.09-pre2/README.menu      2005-01-20 18:35:33.000000000 -0700
+++ syslinux-3.09-pre2/runkernel.inc    2005-06-15 23:52:44.000000000 -0600
+++ syslinux-3.09-pre2/syslinux.doc     2005-06-15 22:39:19.000000000 -0600
    ++++ COMMAND LINE KEYSTROKES ++++
+++ syslinux-3.09-pre2/syslinux.spec    2005-06-15 23:53:15.000000000 -0600
+++ syslinux-3.09-pre2/version  2005-05-19 15:30:50.000000000 -0600
+++ syslinux-3.09-pre2/version.gen      2005-06-15 23:53:18.000000000 -0600
+++ syslinux-3.09-pre2/version.h        2005-06-15 23:53:18.000000000 -0600
[jimc at harpo syslinux]$


> Well okay! Here goes:
>
> n00b situation two:
>   how do I compile in my changes? I'm used to a 'gmake clean' and all 
> the usable binaries go away, edit code, gmake (or gmake pxelinux.0) 
> and usable binaries come back. When I gmake clean, pxelinux.0 still 
> exists. Once I edit files and re-compile them, how do I make sure my 
> changed pxelinux.0 file contains the changes I just made?


$ grep nasm *
Makefile:NASM    = nasm -O99
README:SYSLINUX now builds in a Linux environment, using nasm.  You need 
nasm
README:http://nasm.sf.net/ for information about nasm.
syslinux.spec:BuildPrereq: nasm >= 0.98.38, perl
[jimc at harpo syslinux-3.09-pre2]$