HOME
-> LINUX-PMAC
-> KERNEL
rsync -avz linuxcare.com.au::linux-pmac-stable /src/linux
(when /src/linux is empty) you can get a copy of the source tree. Executing the same command later will update the directory when files in the distribution have changed. Besides linux-pmac-stable, which is based on the most recent 2.2.x kernel, there is linux-pmac-devel, which is based on 2.3.x. If you preferred to use the standard kernel, you could get it from www.kerneli.org together with the crypto patches.
As you see, I suppose the kernel source is located in /src/linux
and therefore
also prepared the necessary links in /usr/include
to point there:
rm /usr/include/asm
ln -s /src/linux/include/asm /usr/include/asm
rm /usr/include/linux
ln -s /src/linux/include/linux /usr/include/linux
As rsync transfers the unpacked files, you don't need these steps which would be necessary, had you fetched the standard source:
cd /src
tar xzvf linux-2.2.13.tar.gz
cd linux
gzip -dc ../patch-2.2.13.1.gz | patch -p 1
rm asm
ln -s asm-ppc asm
The steps to produce the kernel are pretty straightforward. Using the standard kernel it took me nevertheless several trials, until I had a working kernel. This, because the README file was written for PC Linux, and did not tell everything I needed to know. A great help was the Guy de Riencourt's page on how to build a kernel on a PowerBook. Here the successful steps, with the indication if they are always needed, or only when using the standard kernel:
make mrproper
make pmac_config
make config
.config
.
If you want to build a kernel using the configuration as you got it
from the rsync archive you would use the command make
oldconfig
. The .config
file may be
overwritten by rsync. Thus if you made any changes to the
standard configuration, store the resulting .config
file
in some safe place outside the linux source directory. Then, after
your next update from the rsync archive, you would copy back your
config file over .config
.
make dep
make vmlinux
make modules
make modules_install
/lib/modules/version
As result of the last step I had a new kernel named
vmlinux
, which I copied to my mounted Mac partition, so
that BootX could use it.
Benjamin Herrenschmidt's web page contains the newest version of BootX and MountX. The first is the system extension, which let's you choose to boot Linux or MacOS. MountX allows you to mount your Linux partition under MacOS, but it didn't work for me.