From: Jason <unleet@qwest.net>
To: speakup@braille.uwo.ca
Subject: Re: Compiling a new kernel?
Date: Mon, 5 Nov 2001 20:52:55 -0700 [thread overview]
Message-ID: <01110520525500.26726@lightstar> (raw)
In-Reply-To: <5.1.0.14.0.20011105233517.02e0bb30@pop-server.roadrunner.nf.net>
> 1. place the 'linux-2.4.13.tar.gz' file in my '/usr/src' directory.
>
> 2. 'tar zxvf linux-2.4.13.tar.gz'. A directory 'linux' is created and the
> files and directories from the tar ball are placed in this directory.
Correct
> 3. Place 'speakup-1.00.tar.gz' in my '/usr/src' directory.
>
> 4. 'tar zxvf speakup-1.00.tar.gz' A directory 'speakup-1.00' is created
> and the files and directories are placed in this directory.
>
> 5. 'cd /usr/src/speakup-1.00'
>
> 6. './install' All of the patch hunks apply successfully.
I have no idea how speakup is installed, so I'll assume you did that right
> 7. 'cd /usr/src/linux'
>
> 8. 'make dep >/home/dlawlor/makedep' The output is directed into
> '/home/dlawlor/makedep'.
>
> 9. 'make menuconfig' I go through the configuration process and save my
> configuration in '/home/dlawlor/kernel-config.cfg'.
>
> 10. I press the 'esc' key until I am asked if I want to save my
> configuration. I say yes and end up with a '.config' file in my
> '/usr/src/linux' directory.
OK... it should be "make menuconfig" then "make dep"
> 11. 'make >/home/dlawlor/kernel-make' All the output from make is placed
> into '/home/dlawlor/kernel-make'.
that should be "make modules" then "make modules_install" then "make bzImage"
feel free to redirect the output wherever you want, just remember to check
the end of each file for error messages.
your new kernel will be in /usr/src/linux/arch/i386/boot
the file will be called bzImage
obviously, everything's case sensitive, and you don't type the quotes
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Doug Lawlor
` Jason [this message]
` Thomas Ward
` 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=01110520525500.26726@lightstar \
--to=unleet@qwest.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).