- Original Message -
From: "Bruce Dubbs"
To: "LFS Developers Mailinglist"
Sent: Friday, February 19, 2010 6:39 PM
Subject: Re: klogd and System.map
> linux fan wrote:
> > On 2/19/10, Bruce Dubbs wrote:
> >> My first choice right now is the
linux fan wrote:
> On 2/19/10, Bruce Dubbs wrote:
>> My first choice right now is the script with the unconditional -x as a
>> second choice.
>
> It seems script effectively does unconditional -x because
> it greps for Version_ which is what they removed
> which triggered this whole business.
Wi
Bruce Dubbs wrote:
> Bryan Kadzban wrote:
>> David Jensen wrote:
>>> from slackware rc.syslog
>>> # '-c 3' = display level 'error' or higher messages on console
>> Starting to get off topic now, but after reading the klogd manpage, this
>> is exactly what the current LFS bootscripts do when you
On 2/19/10, Bruce Dubbs wrote:
> My first choice right now is the script with the unconditional -x as a
> second choice.
It seems script effectively does unconditional -x because
it greps for Version_ which is what they removed
which triggered this whole business.
Does -x cause loss of informati
Bryan Kadzban wrote:
> David Jensen wrote:
>> Bryan Kadzban wrote:
>>> Bruce Dubbs wrote:
>>>
To stop klogd from trying to read System.map, it requires passing -x
in the command line. We can do that easily in the boot scripts.
>>> Which I would suggest if we want to silence
David Jensen wrote:
> Bryan Kadzban wrote:
>> Bruce Dubbs wrote:
>>
>>> To stop klogd from trying to read System.map, it requires passing -x
>>> in the command line. We can do that easily in the boot scripts.
>>>
>> Which I would suggest if we want to silence the warning. Given the
>> (to
Bryan Kadzban wrote:
> Bruce Dubbs wrote:
>
>> To stop klogd from trying to read System.map, it requires passing -x
>> in the command line. We can do that easily in the boot scripts.
>>
>
> Which I would suggest if we want to silence the warning. Given the
> (total lack of) need for Syste
Bruce Dubbs wrote:
> I've noticed an irritating message when klogd starts up. It says:
>
> Cannot find map file.
Meh. I've been skipping the System.map copy (as part of the kernel
install) *forever* -- or at least ever since I moved to kernel 2.6, I
believe -- and never cared enough to fix this
On 2/18/10, Bruce Dubbs wrote:
> I saw that when I was researching last night. I don't think it is a
> feature. It implies something is wrong. When something is right in
> Linux/Unix, the application should stay silent.
I fussed a lot over this and the warning happen in ksym.c in sysklogd sour
linux fan wrote:
> On 2/18/10, Bruce Dubbs wrote:
>> My understanding is that klogd reads the symbols to translate kernel
>> oops to symbols. I think I saw that the kernel is now doing that
>> internally. In that case, there is no need for klogd to read System.map
>> at all.
>
> That is what L
On 2/18/10, Bruce Dubbs wrote:
> My understanding is that klogd reads the symbols to translate kernel
> oops to symbols. I think I saw that the kernel is now doing that
> internally. In that case, there is no need for klogd to read System.map
> at all.
That is what Linus said in reply to an e
Andrew Benton wrote:
> On 18/02/10 20:57, Bruce Dubbs wrote:
>> I've noticed an irritating message when klogd starts up. It says:
>>
>>Cannot find map file.
>>
>> I traced the cause of this message. System.map is a dump of the kernel
>> symbols using nm. klogd finds the System.map, but rejec
On 18/02/10 20:57, Bruce Dubbs wrote:
> I've noticed an irritating message when klogd starts up. It says:
>
>Cannot find map file.
>
> I traced the cause of this message. System.map is a dump of the kernel
> symbols using nm. klogd finds the System.map, but rejects it because
> there is no s
I've noticed an irritating message when klogd starts up. It says:
Cannot find map file.
I traced the cause of this message. System.map is a dump of the kernel
symbols using nm. klogd finds the System.map, but rejects it because
there is no symbol with the name "Version_xx" where xx
14 matches
Mail list logo
