[coLinux-devel] vmlinux

[Ian L. <Ian...@mq...>]

Hello,

  I feel like a total noob.  I haven't needed this much support building 
linux kernels ever .. even when I was a noob the first time round I
did it better than this.

  Appologies, too, for missing the "vmlinux vs bzImage" problem,
as you've got that clearly doc'd in the doc/building file (I've been
back through all of your docs this evening)..

  I forwarded and reversed all of my software until I came back to
where I started.  I am currently using the default (colinux supplied)
.config, a fresh/clean/virgin 2.4.24 kernel source and a I'm
 producing a kernel, that is neither the same size as the orginal [1]
nor is it working as a direct drop-in replacement for the precompiled 
version that you've shipped in your binary release.

  Each of the kernels I've built have compiled fine, but failed to leave
the daemon running for more than a second.  I wondered if I was
missing a map file, or some other include/supporting file, but I don't
see the binary distribution using any such thing.  Once you've
made the vmlinux file, you just copy it over to the Windows host,
right?  No need to set any of its boot options or anything?

[1] - I wouldn't have expected them to be identical in size, but 
each time I compile it on this system it comes out to the same size;
            Mine;               1,646,244 vmlinux
            coLinux-bin;    1,624,545 vmlinux


  I have diff'd the config files and they are identical .. the patch is
clean .. but its doesn't patch cleanly (I feel this is odd - but 
acceptable - depending on the line that I'm missing).

patching file CREDITS
patching file Documentation/devices.txt
patching file Makefile
Hunk #1 succeeded at 27 (offset -1 lines).
Hunk #3 succeeded at 289 (offset -1 lines).
patching file arch/i386/config.in
patching file arch/i386/kernel/Makefile
patching file arch/i386/kernel/cooperative.c
patching file arch/i386/kernel/entry.S
patching file arch/i386/kernel/head.S
patching file arch/i386/kernel/i8259.c
patching file arch/i386/kernel/process.c
patching file arch/i386/kernel/setup.c
patching file arch/i386/kernel/time.c
patching file arch/i386/kernel/traps.c
patching file arch/i386/mm/fault.c
patching file arch/i386/mm/init.c
patching file arch/i386/vmlinux.lds
patching file drivers/block/Config.in
patching file drivers/block/Makefile
patching file drivers/block/cobd.c
patching file drivers/block/ll_rw_blk.c
patching file drivers/char/Makefile
patching file drivers/char/colx_keyb.c
patching file drivers/char/vt.c
patching file drivers/net/Config.in
patching file drivers/net/Makefile
patching file drivers/net/conet.c
patching file drivers/video/Makefile
patching file drivers/video/cocon.c
patching file include/asm-i386/cooperative.h
patching file include/asm-i386/desc.h
patching file include/asm-i386/dma.h
patching file include/asm-i386/io.h
patching file include/asm-i386/irq.h
patching file include/asm-i386/mmu_context.h
patching file include/asm-i386/page.h
patching file include/asm-i386/pgalloc.h
patching file include/asm-i386/pgtable-2level.h
patching file include/asm-i386/pgtable.h
patching file include/asm-i386/processor.h
patching file include/asm-i386/segment.h
patching file include/linux/console.h
patching file include/linux/cooperative.h
patching file include/linux/major.h
patching file init/do_mounts.c
patching file init/main.c
patching file kernel/Makefile
patching file kernel/cooperative.c
patching file kernel/import.c
patching file kernel/panic.c
patching file kernel/printk.c
patching file mm/page_alloc.c
patching file mm/vmalloc.c

The kernel verifies under gpg .. I have md5sum'd the tar.gz
version that I have - if anyone can verify this it would rule out
an odd-kernel;  
  fc365a4d55826c605ff25f6227036dbb  linux-2.4.24.tar.gz
  647e29c582965987219859097ffdc7f8  linux-2.4.24.tar.gz.sign


I'm still not using the same compiler as Dan .. but I am using a GCC 
v3 compiler (per previous thread).

Is there anything else that I could be doing wrong?  Happy to
provide any additional info required to diagnose this problem.


Thanks,



--
Ian Latter
Internet and Networking Security Officer
Macquarie University

 Meet me at the Australian Unix and open systems
   User Group (AUUG) Security Symposium; 2004
  http://www.auug.org.au/events/2004/security/