From: "Rick A. Hohensee" <rickh@Capaccess.org>
To: linux-kernel@vger.kernel.org
Subject: report from left field
Date: Mon, 12 Aug 2002 03:23:18 -0400 [thread overview]
Message-ID: <fc.0010c7b20054c5020010c7b20054c502.54c557@Capaccess.org> (raw)
I just built a simple 2.4.19 with gcc 3.0, and am writing from a warm boot
to it. The bletcherization of the kernel still hasn't completely killed
cLIeNUX. I do now have to run my pathname mungler on the kernel sources
themselves, which I didn't used to have to do, and make dep doesn't work
anyway, but make bzImage is almost hitch-free.
You get a lot of questions about modules in make config after telling it
no modules.
As usual I have a lot of drivers for things not on this box and all seems
rosy. It's big though. 900k without my usual "everything that doesn't kill
it", and of course, I boot an image with the System.map and .config
appended to the bzImage itself.
Rick Hohensee
:; cLIeNUX /dev/tty4 02:48:45 /
:;d -d */
Ha3sm/ command/ device/ help/ owner/ suite/
Linux/ configure/ floppy/ log/ source/ temp/
boot/ dev/ guest/ mount/ subroutine/
:; cLIeNUX /dev/tty4 02:48:49 /
:;
o
reply other threads:[~2002-08-12 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fc.0010c7b20054c5020010c7b20054c502.54c557@Capaccess.org \
--to=rickh@capaccess.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®