REG) See the Kernel HOWTO for some information. Also, there are people at http://www.kernelnewbies.org/ who are usually willing to help. William Stearns) The Buildkernel script walks you through an entire kernel build, including downloading the necessary files, patching the source, building the kernel and modules, installing the lot into lilo, and optionally building pcmcia-cs, cipe, and freeswan code for that kernel.

REG) First make sure you have the latest version of that kernel series. Perhaps a pre-patch already has a fix. If not, search the list archives for a fix. Don't contribute to noise on the list by asking a question that may already have been answered. If the problem has not yet been fixed, try digging into the code yourself and post a fix to the mailing list.

In order for you to do any major work of any kind, you'll probably have to have the source and be able to do things with it. (Unless you just happen to be a super ResEdit/Macsbugs hacker that can play with the assembly. :) ) If you just want to test the things that others have done, you won't need to.

Compiling a kernel for the ARM architecture is very similar to any other architecture. Russell King maintains a document detailing the process.

Remember that when you apply a patch to the kernel, you must use the -p0 or -p1 option: otherwise, the patch may be misapplied. See the patch manual page for details. ld: unrecognized option -qmagic means that you should get a newer linker, from ftp://tsx-11.mit.edu/pub/linux/packages/GCC/, in the file binutils-2.8.1.0.1.bin.tar.gz.

use: # make [modules|zImage|bzImages] MAKE="make -jX" where X=max number of processes. WARNING: This won't work for "make dep". With a 2.1.x like kernel, see also the file /usr/src/linux/Documentation/smp for specific instruction. BTW, since running multiple compilers allows a machine with sufficient memory to use use the otherwise wasted CPU time during I/O caused delays make MAKE="make -j 2" -j 2 actually even helps on uniprocessor boxes (from Ralf B?chle). In the 2.

You are not using the new make buildkernel and make installkernel targets, and your source tree is different from the one used to build the currently running system (e.g., you are compiling 4.3-RELEASE on a 4.0-RELEASE system). If you are attempting an upgrade, please read the /usr/src/UPDATING file, paying particular attention to the ''COMMON ITEMS'' section at the end.

Please ensure this is not caused by using a broken toolchain, binutils or third party patch. A quick look at the Kautobuild for kernel you are trying to build should give some idea if the error is expected. Once all these things have been checked the issue should be reported to the community mailing list. When reporting these problems, always include as much information as possible as a minimum the full build line. This can be obtained by re-running the make with an additional argument: V=1

Use the CONCURRENCY_LEVEL environment variable eg make-kpkg kernel_image CONCURRENCY_LEVEL=4 after installing distcc into a masquerade directory.

ADB) Production or stable kernels have a well defined feature set, a low number of known bugs, and tried and proven drivers. They are released less frequently than the experimental kernels, but even so some "vintages" are considered better than others. GNU/Linux distributions are usually based on chosen stable kernel versions, not necessarily the latest production version.

ADB) These are intermediate pre-release versions of version f.g.hh. Note that usually i < 5, but e.g. 2.0.34prei was available with i = 1 to 16. Sometimes "pre" is replaced by the initials of the developer putting together the kernel revision, e.g. 2.1.105ac4 means the 4th intermediate release of kernel version 2.1.105 by Alan Cox.

RRR) Depending on your patch there are several ways to get it into the kernel. The first thing is to determine under which maintainer does your code fall into (look in the MAINTAINERS file). If your patch is only a small bugfix and you're sure that it is 'obviously correct', then by all means send it to the appropriate maintainer and post it to the list. If there is urgency to the bugfix (i.e.

REG) Originally, Linus Torvalds maintained the kernel. As the kernel has matured, he has delegated maintenance for older stable versions to others, while he continues development of the latest "bleeding edge" release. As of 27-MAY-2002, the following kernel versions are maintained by these people:

These files are OEM versions of Ontrack. They have got a big bug: an error occures when you want to rename a file. The IBM*.COM files nativly support the new partition type 0Fh (LBA). It's not recommended to use these files if you don't know what you do. The COMMAND.COM file seems to be okay, but I didn't notice any changes.

brings a new and exciting answer to this question: PAR, a "Cross-Platform Packaging and Deployment tool", originally developed by Autrijus Tang. Before PAR, the only public support for Perl/Tk "compilation" was in the Dr.

Edit the code and remove the arguments to setpgrp. Or upgrade to Expect 5.31 (or later) which adapts automatically.

Check this out: Cobalt Raq2 - Building expect causes Fatal signal 11 in gcc [Kernel 2.0.34 MIPS , Redhat/Cobalt Release 4.0] Seems libieee.a is built oddly and gcc doesn't like it, neither expect nor tcl seem to actully need it, removing -lieee from the makefile allows it to compile, no undefined references, expect passes make test... (Maybe the needed functions are really in libm?) ps: tcl 8.2.1 needs the same fix to compile

You need Visual C++ 6 and Sleepycat db 3.1.17 (which you can get from here). If the compiler complains about missing db.h, then you don't have Sleepycat in a place where the compiler expects to find it. The project files for Outport are set up such that it expects the Sleepycat db zip file to be expanded in a directory called db-3.1.17, as in the diagram to the right. When you compile it, the binaries are created in win32/bin and win32/bind (release and debug respectively).