On Tue, 27 Apr 1999, Stefan Troeger wrote:
>
> Hi,
>
> On Mon, Apr 26, 1999 at 22:54 -0400, Steve Pauly wrote:
>
> > Hanspeter wondered if the the placement of System.map in /boot was a 2.2.x
> > kernel issue. I don't know, but man lilo.conf says you can specify where
> > the map file is located in lilo.conf, for example, by:
> >
> > image = /boot/vmlinuz
> > root = /dev/hda4
> > label = linux
> > map = /boot/map_place/System.map
> >
> > The default location is /boot/System.map, though you can specify an
> > alternative location.
> >
> > Someone also pointed out that the function of the .map file is (only)to
> > aid kernel crash diagnosis.
> >
> > Pls correct me if wrong. HTH
>
> You asked for it ;-) The System.map and the map file the
> lilo.conf manpage is talking about are two different things. If
I believe you are right. This redhat box has a System.map and a map file
in /boot/. Course I can't cat it since I'm not root. :-( Plus, I saw the
ref in man klogd you were talking about.
I was confused because another poster, Kim C. Callis, on Jan-8-1999,
indicated that lilo map= was used to point to the System.map. Just goes to
show that shooting ones mouth off without testing is not a good idea.
Thanks very much for setting me straight!
Steve.
(Linux is cool)
> you want to change the location of the System.map file to
> something other than /, /boot or /usr/src/linux, you have to use
> the -k option when starting klogd (this is done in
> /sbin/init.d/syslog.
>
> Ciao,
> Stefan
> --
> To get out of this list, please send email to [EMAIL PROTECTED] with
> this text in its body: unsubscribe suse-linux-e
> Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
> archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
>
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
