From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Compiling a new kernel?
Date: Mon, 5 Nov 2001 23:20:44 -0500 [thread overview]
Message-ID: <005601c1667a$6800a300$0100a8c0@enterprise> (raw)
In-Reply-To: <5.1.0.14.0.20011105233517.02e0bb30@pop-server.roadrunner.nf.net>
Hi, Doug. Well, I know of two documents that will help. One is sort of
general. It is the kernel howto.You can see a copy at:
www.redhat.com/support/
Also there is the Linux kernel hackers guide, but I can't remember where I
read it at.
Ok, I saw some errors in your post below. So here is the correct sequence.
First type make config or make menuconfig.This will create the configuration
file needed for building your kernel.
Basically, a kernel requires at minimum your processor type, drivers for
all your hardware, file system support, keyboard types, ppp, and so on. To
make your kernel smaller include most of the stuff as modules. However, your
hard drive, floppy, file system, and crytical stuff must be built into the
kernel.
At last you can use the following command to build your kernel, and get an
output file.
make dep; make clean; make bzImage; make install; make modules_install >
/usr/src/output.txt
Note, don't forget the cemmi to seperate the commands if you want to enter
them as one command I've got a shell script that does this part for me.
.Other wise you can enter them one by one.
the grader sign redirects the output, and puts it in the file I named
/usr/src/output.txt
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Doug Lawlor
` Jason
` Thomas Ward [this message]
` Gregory Nowak
` Charles Hallenbeck
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='005601c1667a$6800a300$0100a8c0@enterprise' \
--to=tward@bright.net \
--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).