Hi, In /usr/src/<linux_directory>/drivers/char/keyboard.c, find the lines that say static struct kbd_struct * kbd = kbd_table; static struct tty_struct * tty; Presently, they're on lines 101 and 102. Remove the word static and the space after it from the beginning of each line. This is after the checkout program attempts to patch the file. I have no idea what the next line does. That appears to be the one that RH adds. HTH. -- Bill in Denver On Thu, 8 May 2003, Jacob Schmude wrote: > Anyhow, what would I have > to do to patch keyboard.c? > just out of curiosity: what has rh done to keyboard.c that requires it to > be patched by hand? I was going to suggest making a patch file, but with > CVS, that just might not be an option since it changes so rapidly. Maybe > there's a way for a rh-specific patch to be put into cvs and the install or > checkout script could decide which one to apply based on a condition, > possibly the condition of a build number after the kernel version (rh and > mandrake are the only distros I know of that do this). I mean something > such as 2.4.20 and 2.4.20-9. Perhaps if the script could determine the > difference, it could know to apply the 2.4.20 redhat patch to 2.4.20-9, for > example. Would such a thing be possible? > For now, though, can you send me some instructions on how to hand-patch it, > what line numbers, what I need to change, etc? > At 22:41 5/7/2003 -0600, you wrote: > > >Hi, > > > > I don't know of a program for verifying a kickstart file. If your IP > >address is routable, I'd be happy to help you with a telnet installation > >over the phone. The Speakup keymaps are available in RH9, although there > >a little old. They'll be fine for an initial installation. I do > >recommend that you upgrade the kbd package along with the kernel. Use the > >clean kernel-source-2.4.20-9.i386.rpm from RH to add the CVS version of > >Speakup to. You'll have to hand patch keyboard.c, Janina or I can help > >with that. >