----- Original Message ----- From: "Bruce Dubbs" <bruce.du...@gmail.com> To: "LFS Developers Mailinglist" <lfs-dev@linuxfromscratch.org> Sent: Friday, February 19, 2010 6:39 PM Subject: Re: klogd and System.map
> linux fan wrote: > > On 2/19/10, Bruce Dubbs <bruce.du...@gmail.com> 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. > > With certain kernel configurations that are fairly rare, the Version_ > symbol can be generated when building the kernel. This would generate > the old behavior making System.map relevant. > >From a recent topic on busybox mailing list, you would need to use CONFIG_EMBEDDED to be allowed to disable CONFIG_KALLSYMS http://lists.busybox.net/pipermail/busybox/2010-February/071579.html (and next message) > > Does -x cause loss of information reported when needed? > No when CONFIG_KALLSYMS is enabled I have used System.map in the last days when in a chroot to run depmod using depmod -ae -F /boot/System.map-2.6.27-3 2.6.27-3 Maybe that's the last usage of System.map? If you want depmod possibly to report the symbol in error using -e, you need System.map Gilles -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
