🚀 go-pugleaf

Matt Bottrell (mattb@Deakin.Edu.Au) wrote:
: In article <5bicmv$3qv@minkirri.apana.org.au> abo@minkirri.apana.org.au (Donovan Baarda) writes:
: >motk@powerup.com.au wrote:
: >: Mike Lord (lordm@ix.netcom.com) wrote:

[snip]

: 	Nope what is happening here is that vmlinuz is unable to find your
: 	System.map file.

: 	You can setup in your lilo.conf file for you HD boot to read something
: 	like:

: 	map=/boot/System.map

: 	A word of warning though, you'll get the above message you you cannot 
: 	locate the System.map file or you are pointing to the wrong one 
: 	(ie: another Kernel build).

: 	Also to build a floppy that boots:

: 	dd if=/usr/src/linux/arch/i386/boot/zImage of=/dev/fd0
: 	rdev /dev/fd0 /dev/hda1

: 	(Where /dev/hda1 is the partition of your / partition for Linux!).

: 	Hope this helps...

Actualy, it raises more questions than it answers. I am talking about a
boot/root disk pair used to install a distribution to a virgin HDD. In my
case it was slackware, and several different releases have been tried,
none have ever worked, all produced the same error message. These same
boot/root disks worked perfectly on two other computers.

I cannot see how the "System.map" file can have anything to do with it.
Actualy, I hadn't even heard of the System.map file before. What does it
do?

ABO