From: Florian Lohoff <flo@rfc822.org>
To: George Gensure <werkt@csh.rit.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: 2.4.3 kernel
Date: Tue, 8 May 2001 17:19:08 +0200 [thread overview]
Message-ID: <20010508171908.B8522@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.SOL.4.31.0105061221330.1956-100000@fury.csh.rit.edu>; from werkt@csh.rit.edu on Sun, May 06, 2001 at 12:25:12PM -0400
On Sun, May 06, 2001 at 12:25:12PM -0400, George Gensure wrote:
> Can anyone explain to me how the 2.4.3 kernel available on ftp.rfc822.org was
> built? I've been working for about a month and a half on getting that to
> compile with no success. The only reason I need it is to get input core
> support, since linux doesn't like to recognize any device nodes that I create
> using mknod. If anyone could shed some light on either of these problems...
> the kernel or getting linux to recognize my mouse on (10,1) please contact me.
Whats your exact problem ? I made the kernel and i dont think i had
greater problems. Everything needed should be in the tar (config etc)
except some patches which should be in the cvs by now.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-05-08 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 16:25 2.4.3 kernel George Gensure
2001-05-06 16:25 ` George Gensure
2001-05-06 19:47 ` DELETE CPMSA
2001-05-06 19:47 ` DELETE CPMSA
2001-05-06 23:26 ` install in the first hard disk Yoshi.-K
2001-05-06 23:26 ` Yoshi.-K
2001-05-06 23:36 ` Keith M Wesolowski
2001-05-08 15:19 ` Florian Lohoff [this message]
2001-08-17 2:17 ` Upgrade kernel from release 2.2.1 to 2.4.? Hua Wen
2001-08-17 2:17 ` Hua Wen
2001-08-17 17:32 ` Upgrade kernel from release 2.2 " Hua Wen
2001-08-17 17:32 ` Hua Wen
2001-08-17 17:44 ` Jun Sun
2001-08-17 19:20 ` Hua Wen
2001-08-17 21:26 ` Jun Sun
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=20010508171908.B8522@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=werkt@csh.rit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.