Re: Writing a kernel building walkthrough - proofreaders wanted
On Fri, Sep 13, 2002 at 10:47:35AM -0500, Manoj Srivastava wrote:
> 1. Run "dselect".
ick. I got the impression that dselect really wasn't a favor'd tool any
more. I know I've never had success with it and avoided it like the
plague since. Why not suggest the use of something else? Perhaps
"apt-cache search" or possibly aptitude? This is after all intended for
people that are in need of guidance with the process, right?
> 2. "cd /usr/local/src"
Looking at the path of 3, perhaps this should be "cd /usr/src" instead?
> 5. "ln -s kernel-source-2.4.18 linux". This will create a symbolic
> link ("alias" in Mac-speak; "shortcut" in Windows-speak, but more
> powerful than either) to the directory "kernel-source-2.4.18"; the
> symlink is named "linux". This step is not absolutely necessary, but
> it's the usual way of doing things. "ls -l" will show you that "linux"
> is a "pointer" to "/etc/src/kernel-source-2.4.18".
uhmm, the symlink will point to "/usr/src/kernel-source-2.4.18".
> 7. "make menuconfig". This will start a curses-based (text-based)
> menu-driven application.
Why not combine 7 and 8 ala:
make-kpkg --revision $REV --us --uc --config menuconfig kernel_headers \
kernel_image modules_image
I find it very useful to create a kernel headers package when I create
the kernel image (less headache that way) and the modules_image is very
handy if you use alsa, nvidia, or any other module package.
Might also be a good idea for someone new to kernel compiling to use one
of the config files from an existing kernel-image package as a starting
point. However, you'll want to add --initrd to the make-kpkg invocation
then.
--
Jamin W. Collins
Reply to: