Hi,
Alex == Alex Kwan [EMAIL PROTECTED] writes:
Alex Dear debian fans,
Alex My system is hamm, and I have downloaded the
Alex kernel source (kernel-source-2.0.34-2.0.34-4.deb)
Alex from ftp.debian.org
Look at /usr/doc/kernel-source-2.0.34/. A copy is attached
below.
manoj
$Id: README,v 1.17 1998/05/11 06:54:38 srivasta Exp $
This is the Debian GNU/Linux prepackaged version of the Linux kernel.
Linux was written by Linus Torvalds [EMAIL PROTECTED] and
others.
This package was put together by Herbert Xu
[EMAIL PROTECTED], from sources retrieved from
directories under ftp.cs.helsinki.fi:/pub/Software/Linux/Kernel/
Linux is copyrighted by Linus Torvalds and others.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; version 2 dated June, 1991.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave., Cambridge, MA 02139, USA.
On Debian GNU/Linux systems, the complete text of the GNU General
Public License can be found in `/usr/doc/copyright/GPL'.
INSTALLATION NOTES:
Before you go any further, please allow me to point out that you need to
have a few other packages installed before you can compile your own kernels
(it is difficult to compile anything without a compiler ;-).
Firstly, you will need gcc, the libc development package (libc5-dev or
libc6-dev at the time of writing), and, on Intel platforms, bin86. [If
you use the menuconfig target of make, you will need ncursesX.X-dev,
and make xconfig also requires tkX.X-dev, and other packages these
depend on]
The packages suggested are:
devel:gcc, libc5-dev/libc6-dev, binutils, make, and, for intel
x86 platforms, bin86 (non-Intel platforms don't need
this).
interpreters: awk, which is contained in either the mawk or gawk packages
base: gzip, shellutils, and grep.
Some of these packages are marked essential, and hence are going to be
present on your machine already. Others you have to check and install.
Of course, pretty gui front ends to kernel configuration require more
packages, but they are not strictly essential (though quite nice really).
Oh, and of course, make-kpkg is part of kernel-package, usually found
in section misc.
For the Brave and the impatient:
1% cd kernel source tree
2% make config # or make menuconfig or make xconfig and configure
3% make-kpkg clean
4% make-kpkg --rootcmd fakeroot --revision=custom.1.0 kernel_image
5% dpkg -i ../kernel-image-X.XXX_1.0_arch.deb
6% shutdown -r now # If and only if LILO worked or you have a means of
# booting the new kernel. YOU HAVE BEEN WARNED!!
With the addition of fakeroot ( a really nice program, I recommend
it) Steps 1 to 4 can be carried out as a non root user. Step 5 does
require root priviledges.
Detailed instructions
Then, remember to change the revision number (using the --revision
option of make-kpkg). It has been suggested that you renumber the
revision number in such a way that a generic kernel image package will
not override the custom package while using dselect (or dpkg
-BOGiE). You may also do this on the fly by setting the
DEBIAN_REVISION environmental variable.
The revision number (the argument supplied after the --revision flag)
has certain constraints:
a) It only has an effect during the configure phase (in other words, if a
file called stamp-configure exists, this option has no effect -- run
make-kpkg clean or manually remove stamp-configure for it to have an
effect).. So, if you re-run make-kpkg with a different revision number,
you have to reconfigure the kernel.
b) It may contain only alphanumerics and the characters + . (full stop,
and plus) and should contain a digit. NOTE: No hyphens allowed. (Look
at Chapter 5 of the Programmers manual for details) Optionally, you
may prepend the revision with a digit followed by a colon (:); this
shall put your revision into a new epoch; (which makes older dpkg very
confused), more on this later.
You should _not_ use a _ in the revision number! As tempting as it may
seem, it actually interferes with the policy.
The revision number is required because dpkg imposes an ordering on
version numbers, so that it can tell whether packages are being up or
downgraded and so that dselect can tell whether a package it finds
available is newer than the one installed on the system. Dselect uses
an option that prevents a package from being downgraded, for example.
Packaged kernel-images in the distribution also have a version number -
