Here are three golden rules of unpacking a kernel tarball:
1. Make sure that you have sufficient free space on the partition before
unpacking.
Reason: the kernel source is not small. Currently the 2.4.0 kernel is
around 105MB, but once built it will grow to 125MB or more depending on
your configuration.
2. Make sure that there isn't a pre-existing file or directory called 'linux'
Reason: unpacking a new kernel tree over an old kernel tree will give
unpredicatable results, and may end up with it failing to build, or
failing to unpack if 'linux' is a file.
3. Never unpack a kernel tar ball in /usr/src
Reason: some systems still have symlinks from /usr/include/linux into
/usr/src/linux/include/linux. The headers in /usr/include/linux are
supposed to be the ones that your C library was compiled against, not
the current kernel you are running.
Suggestion: create a directory called '/usr/src/v2.4.0' and unpack in
there. If you need any extra patches, or other utilities (eg, modutils)
you have a convienient place to keep them for later reference.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 15 2001 - 21:00:34 EST