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. See similar questions...

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. See similar questions...

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

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. See similar questions...

No, but you need to know how basic firewalling and networking theory, in order to exploit FIAIF to the fullest. See similar questions...

Answer: Use the shorewall[-lite] show capabilities command at a root prompt.gateway:~# shorewall show capabilities Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules.. See similar questions...

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. See similar questions...

Building a new kernel was originally pretty much a required step in a FreeBSD installation, but more recent releases have benefited from the introduction of a much friendlier kernel configuration tool. When at the FreeBSD boot prompt (boot:), use the -c flag and you will be dropped into a visual configuration screen which allows you to configure the kernel's settings for most common ISA cards. See similar questions...

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. See similar questions...

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 See similar questions...

First, you need a suitable toolchain. What this means is that basically you need versions of GCC and GNU binutils (but watch out - some old revisions of binutils are buggy and will build non-working kernels!) that are capable of building and linking m68k ELF object files. You will probably also need GNU make. See similar questions...

Linuxha.net uses a kernel module called "drbd". If the version of the kernel changes it is likely that the software will not be able to load the available "drbd" module. In such circumstances a suitable error will be given along with instructions on how the drbd can be recompiled and re-installed. For version 1.2 this process is automated when the cluster daemons start. For older versions based on 1.0 only the warning stated above will be given - intervention by the administrator is required. See similar questions...

You need a kernel 2.6 or 2.4 plus cpufreq patch, Alan Cox already included it in the -ac branch. If you use kernel 2.6.0 or higher, everything is already in the kernel, check you have selected the right cpufreq drivers, see also #3. If you own a PowerPC (i.e. Apple) computer, and you use kernel 2.4 and have problems, then upgrade to benh kernel, cpudynd does work very well with his kernel. See similar questions...

A recent 2.4 or 2.6 kernel should be fine - pre 2.4.9 are not supported. This requirement is mainly based on the version of the block replication device used, DRBD, but also impacts the networking code as well. See similar questions...

That depends on which kernel series you're using. If you're using the 2.4.x kernels, then you've already got the latest RAID code that's available. If you're running 2.2.x, see the following instructions on how to find out. The easiest way is to check what's in /proc/mdstat. Here's a sample from a 2.2.x kernel, with the RAID patches applied. If the contents of /proc/mdstat looks like the above, then you don't need to patch your kernel. See similar questions...

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