According to Pollywog: While burning my CPU.
>
>
> On 07-Feb-99 Tom Savage wrote:
> > My questions are:
> > 1. Was the "Cannot find map file" a problem that should have been fixed or
> > just
> > ignored?
> >
> > 2. Should I have created the above link to solve this problem?
> >
> > 3. Is this a Red Hat/Linux feature or bug?
>
> I think it is a bug, one that I had problems with in Caldera OpenLinux 1.1 but
> not in 1.3. Have you recompiled your kernel? Make sure that when you do
> this, you copy /usr/src/linux/System.map to /
> There should be a System.map in the root directory ( / directory, not /root
> directory).
Not all distributions place System.map into the "/" (root) directory.
Redhat has its default as /boot when its being installed.
People using Redhat have possably seen this and ask, why is it then that when
i make a new kernel it gets automaticly copied to "/". The answer to that is
change /usr/src/linux/Makefile from;
#INSTALL_PATH=/boot
to
INSTALL_PATH=/boot
Bug no, there's no need to copy the System.map from /usr/src/linux to /boot
as the syslog daemon looks into /usr/src/linux if it cant find it in /boot
or "/"
An example from my messages file;
Feb 2 13:23:42 pa3gcu syslogd 1.3-3: restart.
Feb 2 13:23:43 pa3gcu kernel: klogd 1.3-3, log source = /proc/kmsg started.
Feb 2 13:23:43 pa3gcu kernel: Loaded 3192 symbols from
/usr/src/linux/System.map.
The origanal message suggested that the user had deleted the symbolic link
or the System.map file which was installed when the distribution was loaded,
furhter more it suggests that he has no System.map in /usr/src/linux which
also suggests that he has not compiled a kernel, or he deleted that file as
well.
>
>
> --
> Andrew
>
--
Regards Richard.
[EMAIL PROTECTED]
