files that grow like topsy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It just stops the kernel and syslog/klog from beeing able to
dump symbol names instead of hex numbers.
It isn't fatal; but ps in the olden days used to rely on system.map to seek
in /dev/kmem

Regards, Kerry.
On Thu, Feb 14, 2002 at 03:35:55PM -0500, Charles Hallenbeck wrote:
> I guess that is right, and I do not mind, but it would be nice to
> be warned about it. I wonder what else ought to try to
> anticipate. Here is another one I found while poking around in my
> syslog messages...
> 
> When rebuilding the kernel I have been using the "make install"
> command as the final step. It guarantees I will not forget about
> running lilo. However, in Slackware the new kernel and the new
> System.map are placed directly under "/", which turns out not to
> be such a cool thing to do. During the bootup process the new
> kernel looks for its symbol table in /boot/System.map and not in
> /System.map, so after upgrading to a new kernel version I have
> been operating with the wrong symbol table. When I manually
> copied /System.map to /boot/System.map I eliminated some bootup
> error messages about an incorrect version number in the symbol
> table. I wonder what kind of problems I have created for myself
> in running a kernel with the incorrect System.map?
> 
> Chuck
> 
> 
> On Thu, 14 Feb 2002, Gregory Nowak wrote:
> 
> > Isn't that after all the philosophy behind slackware?
> > Greg
> >
> >
> > On Thu, Feb 14, 2002 at 11:29:28AM -0500, Charles Hallenbeck wrote:
> > > Thanks, Kirk,
> > > I guess I have to do that sort of thing by hand in Slackware.
> > > Pity.
> > > Chuck
> > >
> > > On Thu, 14 Feb 2002, Kirk Wood wrote:
> > >
> > > > Charles,
> > > >
> > > > I checked arround on my system. In my monthly cron job file there is a
> > > > comment that the rotation of wtmp has been taken over by logrotate. (I
> > > > have debian if it matters.) Also, I noticed that I have a wtmp.1 last
> > > > modified on Jan 31, and a wtmp. From this information I would think that
> > > > it would be fine to move the file and let the system create a new one
> > > > automatically. If you wanted to be sure, you could touch the file just
> > > > after moving to put a new one in place.
> > > >
> > > > =======
> > > > Kirk Wood
> > > > Cpt.Kirk at 1tree.net
> > > >
> > > > Nowlan's Theory:
> > > >         He who hesitates is not only lost, but several miles from
> > > >         the next freeway exit.
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup at braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > > Visit me now at http://www.valstar.net/~hallenbeck
> > > The Moon is Waxing Crescent (5% of Full)
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup at braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> Visit me now at http://www.valstar.net/~hallenbeck
> The Moon is Waxing Crescent (6% of Full)
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Kerry Hoath:  kerry at gotss.net kerry at gotss.eu.org or  kerry at gotss.spice.net.au




[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux