colinux-devel

[coLinux-devel] colinux-daemon debug info? or kernel sizes?

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

Hello,

  2.4.24+openMosix+FreeSWAN compiles (once you've jiggied
FreeSWAN's Makefile around to remove its enforced "make 
bzImage").  However, when I go to run colniux-daemon.exe
I get;

  Cooperative Linux daemon
  Installing kernel driver
  Creating monitor
  Monitor is running
  <network interface comes up>
  <1 second pause>
  <network interface goes down>
  Monitor is shutting down
  Closing monitor
  Removing kernel driver
  Stopping driver service
  Removing driver service

This is repeatable (so no bad mojo from the colinux-daemon 
process).  Is there any way to have colinux-daemon produce
more or debugging output, to help me see where the new
kernel falls apart?  (I can see the irony of this request after
asking to have the window removed altogether - but that was
for production usage ;-)

My initial thought for the kernel issue is probably its size.  As the
kernels can't be compressed they're going to be pretty big.  The
one I've just built is 2,288,062 bytes -- is there an upper limit for
the kernel size? (have I gone over it?).


A second thought is that my prioritisation for the conflicting patch
with oM is wrong .. I'll build a version without openMosix and see
where I get.


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/

Re: [coLinux-devel] colinux-daemon debug info? or kernel sizes?

[Dan A. <da...@gm...>]

On Tue, Feb 03, 2004 at 08:06:53PM +1000, Ian Latter wrote:
> Hello,
> 
>   2.4.24+openMosix+FreeSWAN compiles (once you've jiggied
> FreeSWAN's Makefile around to remove its enforced "make 
> bzImage").  However, when I go to run colniux-daemon.exe
> I get;
> 
>   Cooperative Linux daemon
>   Installing kernel driver
>   Creating monitor
>   Monitor is running
>   <network interface comes up>
>   <1 second pause>
>   <network interface goes down>
>   Monitor is shutting down
>   Closing monitor
>   Removing kernel driver
>   Stopping driver service
>   Removing driver service
> 
> This is repeatable (so no bad mojo from the colinux-daemon 
> process).  Is there any way to have colinux-daemon produce
> more or debugging output, to help me see where the new
> kernel falls apart?  (I can see the irony of this request after
> asking to have the window removed altogether - but that was
> for production usage ;-)
> 
> My initial thought for the kernel issue is probably its size.  As the
> kernels can't be compressed they're going to be pretty big.  The
> one I've just built is 2,288,062 bytes -- is there an upper limit for
> the kernel size? (have I gone over it?).
> 
> A second thought is that my prioritisation for the conflicting patch
> with oM is wrong .. I'll build a version without openMosix and see
> where I get.

What happens here is probably that Linux boots, and then exists for
some reason from one of the co_terminate() calls, maybe due to a panic.

At this stage, you can trying writing a script that attaches the console
just when the daemon starts booting Linux in order to catch it. My initial
intention was that the daemon itself would be given a switch that would
instruct it to launch a console when the boot starts.

-- 
Dan Aloni
da...@gm...