On Tue, 18 May, 1999, Michael Stone wrote: > On Tue, May 18, 1999 at 02:26:09PM -0700, Chris Waters wrote: > > Michael Stone <[EMAIL PROTECTED]> writes: > > > Because too many people don't use debian kernel images. > > > > If people don't use the tools, then they don't get the benefits of the > > tools, which is hardly our fault. This is like saying that we > > shouldn't have dependencies on libgtk, because some people might > > compile their own, without using dpkg-source. As long as it works > > with make-kpkg, and doesn't require one of the *official* kernel > > images, I'm all for it; there's no valid excuses for not using > > make-kpkg that I've ever seen. > > Except that it's a fairly common thing to have to do, and most of the > howto's out there don't mention anything about make-kpkg. It's also IMHO > not immediately obvious to a new user that he can/should make a kernel > package.
From /usr/doc/debian/FAQ/debian-faq.txt.gz:
-----
11.1. What tools does Debian provide to build custom kernels?
Users who wish to (or must) build a custom kernel are encouraged to
download the package kernel-package_VVV_all.deb (it is stored in
section misc at the Debian FTP archives). This package contains the
script to build the kernel package, and provides the capability to
create a Debian kernel-image package just by running the command make-
kpkg kernel_image in the top-level kernel source directory. Help is
available by executing the command make-kpkg --help, and through the
manual page for make-kpkg(8).
Users must separately download the source code for the most recent
kernel (or the kernel of their choice) from their favorite Linux
archive site.
To build a custom kernel, users must have these packages installed:
gcc, libc6-dev, bin86, binutils, and make.
Executing the command dpkg --install kernel-package_VVV_all.deb sets
up the directory /usr/src/linux-VVV/, and sets up the link
/usr/src/linux to point to the directory /usr/src/linux-VVV/
containing the kernel sources.
Detailed instructions for using the package are given in the file
/usr/doc/kernel-package/README. Briefly, one should:
o Unpack the kernel sources, and cd to the newly created directory.
o Modify the kernel configuration using one of these commands:
o make config (for a tty one-line-at-a-time-interface).
o make menuconfig (for an ncurses-based menu driven interface).
Note that to use this option, the ncurses3.0-dev package must be
installed.
o make xconfig (for an X11 interface). Using this option requires
that relevant X packages be installed.
Any of the above steps generates a new .config in the top-level
kernel source directory.
o Execute the command: make-kpkg -r Custom.N kernel_image, where N is
a revision number assigned by the user. The new Debian archive
thus formed would have revision Custom.1, e.g., kernel-
image-2.0.36-Custom.1.deb for the Linux kernel 2.0.36.
o Install the package created.
o Run dpkg --install /usr/src/kernel-image_VVV-Custom.N.deb to
install the kernel itself. The installation script will:
o run the boot loader, LILO (if it is installed),
o install the custom kernel in /boot/vmlinuz_VVV-Custom.N, and set up
appropriate symbolic links to the most recent kernel version.
o prompt the user to make a boot floppy. This boot floppy will
contain the raw kernel only. See additional notes for making a
``custom boot floppy''.
o To employ a secondary boot loaders (e.g., loadlin), copy this image
to other locations (e.g., an MS-DOS partition).
-----
Users will read the documentary. If you were wondering how to complie a kernel
in Debian GNU/Linux, the first place you would look would be the Debian FAQ.
--
I consume, therefore I am
pgp8OXPJLyKt5.pgp
Description: PGP signature
