Update-grub Doesn't Find/Install New Linux-Image

[NoOp]

On 06/19/2008 08:06 PM, Leonard Chatagnier wrote:
> --- NoOp <glgxg at sbcglobal.net> wrote:
> 
>> On 06/18/2008 10:49 AM, Leonard Chatagnier wrote:
>> > Just installed vmlinux-debug-2.6.22-14-generic and
>> ran
>> > update-grub which didn't find or add it to
>> menu/lst.
>> > May have something to do with same kernel version
>> as
>> > mentioned the menu.lst but how do I get it to boot
>> > without adding it manually.  It is listed in boot
>> > along with the regular generic kernel. Appreciate
>> any
>> > suggestions,
>> > 
>> 
>>
> http://packages.ubuntu.com/gutsy/linux-image-debug-2.6.22-14-generic
>> [The kernel image contained in this package is NOT
>> meant to boot from.
>> It is uncompressed, and unstripped.]
> Thanks NoOp.  Read the links which didn't tell me
> anything about what the package is for, how to use it
> or even if I should be using it.  I expected the
> paackage would somehow be useful in debuggung the
> kernel, and maybe it is, but I haven't a clue about
> that. I suppose this is another case of "if you don't
> know what it's for then you don't need it".  However,
> that doesn't help me progress and learn.

:-)

I install new stuff all the time on my "test" system to see what happens
& for learning purposes. On occassion I end up breaking things - but
usually not too seriously.

One has to wonder why you installed the debug package if not debuging
something though... :-)

Anyway, to answer your question from a non-expert laymans view (and I am
very certain that someone with coding/debugging experience will come
along & fix this as soon as I post):

The dbg and debug packages are for assistance in debuging the
application/package. For instance if someone asks me to provide an
strace/dump/etc to check for a crash or memory leak, loading the
dbg/debug package generally helps provide additional symbols/debug
information for the developer. Example: I try to find a memory leak in
SeaMonkey, so I use a symbolic debugger (gdb - see:
http://dirac.org/linux/gdb/01-Introduction.php#whatisadebugger and
http://www.gnu.org/software/gdb/gdb.html) to provide additional
information to the developers.

However in order to do so, I may need to add the debug symbols for the
package if not included in the original package. These provide
additional information about variables and routines used in the source,
and may not be included in the binary in order to keep the binary
small(er). For example, your file; note that the install size on i386 is
58284 kB (58MB) and on amd64 is 41348 kB. That's additional Mbytes that
don't need to go into the base binary and is not needed by users like
you and I unless requested for additional debugging info by the developers.

That's pretty much my (very basic) understanding of the dbg/debug
packages. So unless you actually want to fill up an additional 58MB of
your disk space, I'd uninstall what you installed.

And I guarantee that _now_ someone will come along in the words of Paul
Harvey & provide "the  rest of the story" :-)

Gary