lkml.org 
[lkml]   [2000]   [Sep]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Given an image, how can show its config?

On Sat, 23 Sep 2000, David Ford wrote:

> Keith Owens wrote:
>
> > That would take my 2.4.0 bzImage to 893864, it does not leave much room
> > out of a 1.4Mb floppy for LILO files. We could have multiple make
> > targets, with and without appended config/map but that just complicates
> > the build environment.
>
> I normally occupy over a meg with my image and I frequently build a LILO boot
> disk for safekeeping. I strip my config down to only enabled options and
> further strip the CONFIG_ from it, then bzip2 -s -9 the both of config and
> system map and it comes out to about 122K
>
>
> > This is all to protect those few poor 'administrators' who cannot keep
> > track of three separate files. We should not coddle such idiots, if
> > they cannot track 3 files they should not be configuring Linux.
> > Anybody who loses their config and System.map will learn from their
> > mistake and only do it once or they will never learn, in which case
> > they are better off running Windows.
>
> The same idiots who have multiple patch trees that haven't been merged and
> different builds of a kernel to test effects? I.e. those who really do the
> work on LKML?
>
>
> > "Think of it as evolution in action".
>
> After you're looking down the ladder of evolution, think to look up the
> ladder.
>
> Personally, /proc/ksyms has what I need for symbols but 1.3K for a .config is
> trivial enough to add to the image.

Some people want this, and some people dont.

Make it configurable (as people already told) and the discussion is over.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.143 / U:1.288 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site