From: "Holmes, Steve" <SAHolmes@ahcccs.state.az.us>
To: "'speakup@braille.uwo.ca'" <speakup@braille.uwo.ca>
Subject: RE: Error while compiling kernel
Date: Mon, 22 Jan 2001 07:08:39 -0700 [thread overview]
Message-ID: <D3033FFE34DAD41196B200508BAE8CDA0A11A8@NTEXCH02> (raw)
I installed kbd from the A8 disk series and loadkeys was placed in one of
the bin directories; I verified that with "which loadkeys". I've since been
able to compile the kernel all the way through now without errors. One
thing to note though, after installing kbd, I had to start over again with
the kernel recompile as the dependencies apparently changed. Now, I'm in
the midst of just getting the new kernel to boot! My last attempt failed.
I've compiled kernels in the past without much trouble but this time, I
guess I got the wrong combinations of configs or something but the machine
won't boot up at all with that kernel so on to more trial/error <sigh>.
-----Original Message-----
From: Charles Hallenbeck [mailto:chuckh@mhonline.net]
Sent: Saturday, January 20, 2001 4:53 AM
To: speakup e-mail list
Subject: Re: Error while compiling kernel
Hmmm... after sending my comment I checked for my loadkey program and
could not find it on my Slackware 7.1 system either, although I have
installed kbd as I suggested. However my 2.2.18 compile did not seem to
mind its absence. In an earlier upgrade I solved the missing loadkey
problem by installing kbd, but apparently the co;ntext has now changed in
Slackware 7.1. I will be interested to hear how you solve your problem.
Regards - Chuck
On Sat, 20 Jan 2001, Charles Hallenbeck wrote:
>
> Make sure you have included the package 'kbd' with your installation. The
> loadkey program comes with that package.
>
> On Fri, 19 Jan 2001, Steve Holmes wrote:
>
> > Hey, I was attempting to compile a 2.2.18 kernel tonight and ran into an
> > error: loadkeys not found. Everything compiled good except it cannot
find
> > the loadkeys command anywhere. I tried the find command to see if it
got
> > left somewhere else or what but no go.
> >
> > This is Slackware 7.1 with Kernel 2.2.18 and Speakup-0.10A.
> >
> > Any ideas?
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> My web site is http://www.mhonline.net/~chuckh
> The Moon is Waning Crescent (14% of Full)
>
>
My web site is http://www.mhonline.net/~chuckh
The Moon is Waning Crescent (14% of Full)
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Holmes, Steve [this message]
-- strict thread matches above, loose matches on Subject: below --
Steve Holmes
` Charles Hallenbeck
` Charles Hallenbeck
` Jacob Schmude
` Matthew Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D3033FFE34DAD41196B200508BAE8CDA0A11A8@NTEXCH02 \
--to=saholmes@ahcccs.state.az.us \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).