Bret Hughes wrote:
>
> Cool Should I compile my own for use on these chips then? What is the
> difference? I guess of the binary files that redhat produces the 386's
> are the ones to use? Please tell me I didn't dream up the suggestion to
> use 386.
>
> Bret
I would be inclined to compile my own. The steps are really quite simple
and are explained in the /usr/doc/linux source. If you want to be really
safe just do a make menuconifg and leave everything at default except
the CPU type.
If you want to get more adventurous here's some things you can do:
1) Edit the /usr/src/linux/Makefile and change the -O2 to something
higher
There are two places it appears, so make sure you get them both. GCC
says -O3 is the highest "safe" they recommend although I compile mine at
-O5.
2) Edit the /usr/src/linux/arc/i386/Makefile and change the -m stuff
around
Work out which set of commands you are using (by looking at the CPU type
you've selected and the name of the object in the Makefile) and change
the -mcpu=586 to -march=pentium. Mcpu is only an alignment on bytes
change...basically you still end up with a super fast 386. -march
introduces changes that are specific to the pentium or whatever you tell
it.
3) Then make the kernel as you normally would
So the steps ARE:
make clean; make mrproper
[change the Makefiles now]
make menuconfig
[change any configuration options you want]
make bzImage
make modules
make modules_install
mv /boot/System.map /boot/.System.map
cp /usr/src/linux/System.map /boot/System.map
cp /usr/src/linux/arch/i386/boot/bzImage /boot/
cd /etc
vi lilo.conf
[add the entries needed in lilo.conf...man lilo.conf....the new kernel
is called /boot/bzImage]
lilo
reboot
DAVID
--
The Linux C Mailing Lists Have Moved
mailto:[EMAIL PROTECTED]?subject=subscribe
The Linux C++ Mailing Lists Have Moved
mailto:[EMAIL PROTECTED]?subject=subscribe
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
