colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] Modules?

[Leo A. <le...@ya...>]

For method 2 you might not need a char device.  With
tar you can tar to and from a block device directly.  
I used to this all the time with floppies (that way
you don't have to have the proper module for the
filesystem of the floppy).  I don't have the time to
try it right now, but you might just have to point a
"/dev/cobd" to the "vmlinux-modules.tar.gz" file in
the default.colinux.xml file and just use tar in
linux.  Something like this:

# tar -xzvf /dev/cobd#


--- Jaroslaw Kowalski <ja...@zd...> wrote:
> Hi guys!
> 
> Recently a patch has been introduced that makes
> additional kernel features
> available as modules.
> 
> This is good because we have new functionality
> available in coLinux, some
> very useful (a firewall), but at the same time it
> introduced a dependency
> between the root images and the running kernel.
> 
> You're no longer able to use just any root image -
> you have to use the one
> that has the appropriate modules. I was wondering
> what can be done to
> improve this.
> 
> Here are some ideas:
> 
> 1. Compile everything statically.
> 
> 2. Provide a way to automatically install
> "vmlinux-modules.tar.gz" under
> "/lib/modules/kernel-version". This would require
> some smart script on the
> linux side, but I think it's doable. The only
> problem I see is passing the
> vmlinux-modules.tar.gz down to the linux guest. I
> think we'd need something
> like /dev/cocd (character device as opposed to
> /dev/cobd).
> 
> 3. Provide a mini-partition that would contain the
> modules instead of the
> tar.gz. This can could be mounted in fstab under
> "/lib/modules".
> 
> Out of the above ideas, I find "1" to be the easiest
> to implement and most
> trouble-free. What do you think? Is there anything
> that MUST be installed as
> a module and cannot be compiled-in?
> 
> What do you think?
> 
> Jarek
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
>
https://lists.sourceforge.net/lists/listinfo/colinux-devel

-- 
Leo Amendola

Re: [coLinux-devel] snapshot 20040417

[Vlad D. <vl...@w-...>]

Dan Aloni wrote:

>     * Sizes of raw partition devices are now detected properly. This 
>       means that the resierfs problems should be over, plus cat /dev/cobd* 
>       would work for you.

Cool! It now works with a native partition on my external firewire hard 
drive!

Thanks!

-- vlad

Re: [coLinux-devel] Modules?

[Robert C. <rw...@al...>]

On Saturday, April 17, 2004, at 04:17  PM, peter green wrote:
> atm i see colinux as a work in progress :) ie not really for newbies

Yup.  Working on it.  Run coLinux in just three steps: download, 
extract, install.  See method 1:

   http://cwelug.org/cgi-bin/wiki.cgi?CoLinux

Regards,
- Robert

Re: [coLinux-devel] Modules?

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

On Sun, Apr 18, 2004 at 12:26:45AM +0300, Dan Aloni wrote:
> On Sat, Apr 17, 2004 at 10:17:32PM +0100, peter green wrote:
> 
> > btw the format of the modules tarballs i have seen was horrible there is
> > nowhere in the filesystem where you can simply extract it and have it work
> > you always have to extract and move
> 
> Well, you know who to complain to about that :)

I'll also turn all the file in the tarball to root-owned.

-- 
Dan Aloni
da...@co...

Re: [coLinux-devel] Modules?

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

On Sat, Apr 17, 2004 at 10:17:32PM +0100, peter green wrote:

> btw the format of the modules tarballs i have seen was horrible there is
> nowhere in the filesystem where you can simply extract it and have it work
> you always have to extract and move

Well, you know who to complain to about that :)

-- 
Dan Aloni
da...@co...

Re: [coLinux-devel] Modules?

[Max <ma...@al...>]

Jaroslaw Kowalski wrote:

>Hi guys!
>
>Here are some ideas:
>
>1. Compile everything statically.
>
>2. Provide a way to automatically install "vmlinux-modules.tar.gz" under
>"/lib/modules/kernel-version". This would require some smart script on the
>linux side, but I think it's doable. The only problem I see is passing the
>vmlinux-modules.tar.gz down to the linux guest. I think we'd need something
>like /dev/cocd (character device as opposed to /dev/cobd).
>
>3. Provide a mini-partition that would contain the modules instead of the
>tar.gz. This can could be mounted in fstab under "/lib/modules".
>
>What do you think?
>  
>
I like solutions 1 and 3.

However, I think long term, it might be better to boot the kernel out of 
the image, using some grub-like magic to read the file system.  I 
realize this would be a pain right now since the kernel changes daily.   
However, this would also allow us to patch and compile the kernel within 
linux and just leave it there.  Eg, more like grub than loadlin.  Or we 
can give up on modules.  Since the hardware in the guest is pretty much 
always the same, there's no need for modules.

>Jarek
>  
>
Max

RE: [coLinux-devel] Modules?

[peter g. <plu...@p1...>]

atm i see colinux as a work in progress :) ie not really for newbies

provided smbfs (or better hostfs when/if it appears) are compiled in it is
not too hard for a techie to install the modules file.

btw the format of the modules tarballs i have seen was horrible there is
nowhere in the filesystem where you can simply extract it and have it work
you always have to extract and move



-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Jaroslaw
Kowalski
Sent: 17 April 2004 21:58
To: col...@li...
Subject: [coLinux-devel] Modules?


Hi guys!

Recently a patch has been introduced that makes additional kernel features
available as modules.

This is good because we have new functionality available in coLinux, some
very useful (a firewall), but at the same time it introduced a dependency
between the root images and the running kernel.

You're no longer able to use just any root image - you have to use the one
that has the appropriate modules. I was wondering what can be done to
improve this.

Here are some ideas:

1. Compile everything statically.

2. Provide a way to automatically install "vmlinux-modules.tar.gz" under
"/lib/modules/kernel-version". This would require some smart script on the
linux side, but I think it's doable. The only problem I see is passing the
vmlinux-modules.tar.gz down to the linux guest. I think we'd need something
like /dev/cocd (character device as opposed to /dev/cobd).

3. Provide a mini-partition that would contain the modules instead of the
tar.gz. This can could be mounted in fstab under "/lib/modules".

Out of the above ideas, I find "1" to be the easiest to implement and most
trouble-free. What do you think? Is there anything that MUST be installed as
a module and cannot be compiled-in?

What do you think?

Jarek



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004

[coLinux-devel] Modules?

[Jaroslaw K. <ja...@zd...>]

Hi guys!

Recently a patch has been introduced that makes additional kernel features
available as modules.

This is good because we have new functionality available in coLinux, some
very useful (a firewall), but at the same time it introduced a dependency
between the root images and the running kernel.

You're no longer able to use just any root image - you have to use the one
that has the appropriate modules. I was wondering what can be done to
improve this.

Here are some ideas:

1. Compile everything statically.

2. Provide a way to automatically install "vmlinux-modules.tar.gz" under
"/lib/modules/kernel-version". This would require some smart script on the
linux side, but I think it's doable. The only problem I see is passing the
vmlinux-modules.tar.gz down to the linux guest. I think we'd need something
like /dev/cocd (character device as opposed to /dev/cobd).

3. Provide a mini-partition that would contain the modules instead of the
tar.gz. This can could be mounted in fstab under "/lib/modules".

Out of the above ideas, I find "1" to be the easiest to implement and most
trouble-free. What do you think? Is there anything that MUST be installed as
a module and cannot be compiled-in?

What do you think?

Jarek

RE: [coLinux-devel] snapshot 20040417

[Daniel R. S. <dan...@ya...>]

I believe what he means is that when colinux is installed as a service and
it receives the service stop message, it will send a ctrl-alt-delete message
to the linux machine so it shuts down cleanly before stopping the service.


-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of andre
Sent: Saturday, April 17, 2004 1:28 PM
To: col...@li...
Subject: Re: [coLinux-devel] snapshot 20040417

On Saturday 17 April 2004 16:12, Dan Aloni wrote:
>   * Added the ability to send Ctrl-Alt-Del to the Linux machine.

What do you mean with this. Do you want to claim that if you press 
Ctrl-Alt-Del that colinux will restart and not windows?


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel

Re: [coLinux-devel] ANN: Minimal Fedora Core 1 - new image

[Jaroslaw K. <ja...@zd...>]

Since Dan has uploaded a new snapshot that fixes the modules, I've prepared
an update to "minimal fedora core 1" image that uses the modules and
contains no custom kernel.

Image is available for download at:

http://jaak.sav.net/colinux/

Jarek
----- Original Message ----- 
From: "Jaroslaw Kowalski" <ja...@zd...>
To: <col...@li...>
Sent: Saturday, April 17, 2004 8:20 PM
Subject: [coLinux-devel] ANN: Minimal Fedora Core 1 - new image


>
> Hi colinuxers!
>
> After more-or-less 1 terabyte of generated root images, I'm pleased to
> annouce the availability of a new version of "minimal fedora core 1" root
> image.
>
> It is available along with installation instructions at:
>
> http://jaak.sav.net/colinux/newimage.html
>
> The server bandwidth is 2Mbit/s so please be patient.
>
> Changes:
>
> 1. Initial image size is 35 MB (was 80 MB). The rest is downloaded from
> freshrpms.net or another RedHat mirror.
>
> 2. Tasks-like feature (similar to what Debian has) is provided. You can
now
> write:
>
> # apt-get task-gnome-full
>
> (Note that there are some bugs in redhat dependencies which may require
you
> to do manually install some packages)
>
> 3. iptables works (Note that this requires a custom kernel + images since
> 20040417 image is broken. As soon as Dan releases a new snapshot
containing
> fixed modules I'll remove the kernel + modules from my release).
>
> 4. Some basic GUI configuration is provided for setting up network and
> firewall (redhat-config-network-tui and redhat-config-securitylevel-tui)
>
> 5. The initial image is already patched with the latest redhat updates (as
> of Apr 17th).
>
> Jarek
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

[coLinux-devel] debugging linux.sys

[Daniel S. <dan...@au...>]

Can someone tell me how you are kernel debugging linux.sys? Since it is
built with gcc, I don't see how you generate symbols that WinDbg or KDB
can read and as far as I am know, gdb is not capable of kernel debugging
windows.

=20

Dan

=20

Updated with SMP stability workaround (Was: Re: [coLinux-devel] Modules broken?)

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

On Sat, Apr 17, 2004 at 06:20:37PM +0200, Jaroslaw Kowalski wrote:
> Hi Dan,
> 
> I just downloaded today's snapshot and (as I reported on IRC) "depmod -ae"
> failed for me on Fedora Core 1 image. I got errors about some missing
> symbols.

My release script was the fault. 

I have updated the snapshot with one addition:

  * The daemon process is pinned to the first processor until
    we get the SMP stability issue fixed.	 

With this change it runs without any problem on my HT machine (Linux as 
host, though).
 
-- 
Dan Aloni
da...@co...

[coLinux-devel] ANN: Minimal Fedora Core 1 - new image

[Jaroslaw K. <ja...@zd...>]

Hi colinuxers!

After more-or-less 1 terabyte of generated root images, I'm pleased to
annouce the availability of a new version of "minimal fedora core 1" root
image.

It is available along with installation instructions at:

http://jaak.sav.net/colinux/newimage.html

The server bandwidth is 2Mbit/s so please be patient.

Changes:

1. Initial image size is 35 MB (was 80 MB). The rest is downloaded from
freshrpms.net or another RedHat mirror.

2. Tasks-like feature (similar to what Debian has) is provided. You can now
write:

# apt-get task-gnome-full

(Note that there are some bugs in redhat dependencies which may require you
to do manually install some packages)

3. iptables works (Note that this requires a custom kernel + images since
20040417 image is broken. As soon as Dan releases a new snapshot containing
fixed modules I'll remove the kernel + modules from my release).

4. Some basic GUI configuration is provided for setting up network and
firewall (redhat-config-network-tui and redhat-config-securitylevel-tui)

5. The initial image is already patched with the latest redhat updates (as
of Apr 17th).

Jarek

RE: [coLinux-devel] Using VNC/X ->Win32 Link Off-Network

[Michael S. <msi...@ya...>]

Peter,

You're right - when Win2k detects no cable it shuts down all routes to
and from that adapter.  I might be able to turn off the media detect on
my network adpater (MSDN Q239924), but for me it's easier to point
coLinux at my wireless card which is always "connected."  It won't work
to get to the Internet that way, but it allows Win2k and coLinux to see
each other now when I'm not near an Ethernet jack.

Thanks for the help!

Michael

--- peter green <plu...@p1...> wrote:
> i don't think that is the problem
> i think the problem is that winpcap can't work on an interface that
> is down
> and windows automatically downs interfaces that are unplugged
> 
> if win2k supports it (i dunno if the feature was in 2K or wasn new in
> XP)
> you could use the tap driver and then use windows bridegeing to
> attach it to
> your nic
> 
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of
> Michael
> Sisolak
> Sent: 17 April 2004 16:47
> To: col...@li...
> Subject: [coLinux-devel] Using VNC/X ->Win32 Link Off-Network
> 
> 
> I have coLinux running on my Windows 2000 laptop with a native
> network
> configuration (started with the Debian image and added X, VNCserver,
> and KDE 3.2.1).  As long as my laptop is plugged into the network I
> can
> use a Win32 VNC client to hook into the X system in the coLinux
> instance.  As soon as I unhook from the network, however, the coLinux
> instance and the Win32 instance can no longer communicate with each
> other.
> 
> It appears that in a native networking configuration coLinux can only
> talk to Win32 programs by first passing the packets out to my router
> and then having the router pass them back to the laptop.  Thus with
> the
> laptop off the network the two instances have no way to communicate.
> 
> Is there some way to get off-network usage in a native network
> configuration to work?  Thanks for all your work on CoLinux - it's
> quite an impressive trick.
> 
> Michael Sisolak
> msi...@ya...



	
		
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash

Re[2]: [coLinux-devel] snapshot 20040417

[keksov <ke...@gm...>]

Danke sehr :)



Saturday, April 17, 2004, 5:56:07 PM, you wrote:

TF> -----BEGIN PGP SIGNED MESSAGE-----
TF> Hash: SHA1

TF> Hi Dim,


TF> http://www.colinux.org/snapshots/

TF> Cheers, Thomas

Re: [coLinux-devel] snapshot 20040417

[andre <avb...@gm...>]

On Saturday 17 April 2004 16:12, Dan Aloni wrote:
>   * Added the ability to send Ctrl-Alt-Del to the Linux machine.

What do you mean with this. Do you want to claim that if you press 
Ctrl-Alt-Del that colinux will restart and not windows?

Re: [coLinux-devel] Modules broken?

[Jaroslaw K. <ja...@zd...>]

BTW. With coLinux-20040415.exe it was ok.

Jarek

----- Original Message ----- 
From: "Jaroslaw Kowalski" <ja...@zd...>
To: "Dan Aloni" <da...@co...>
Cc: <col...@li...>
Sent: Saturday, April 17, 2004 6:20 PM
Subject: [coLinux-devel] Modules broken?


> Hi Dan,
>
> I just downloaded today's snapshot and (as I reported on IRC) "depmod -ae"
> failed for me on Fedora Core 1 image. I got errors about some missing
> symbols.
>
> I attempted to rebuild kernel + modules myself:
>
> 1. I got FRESH kernel-2.4.26.tar.bz2 - extracted and applied patch
> There wass some error saying that one of the chunks is already applied
> (strange, but doesn't look harmful - it's just a printk(), so I ignored
it)
>
> 2. I copied today's config file to .config
>
> 3. make oldconfig && make dep && make vmlinux && make modules && make
> modules_install
>
> After this I copied the kernel and modules into appropriate places and IT
> WORKED.
>
> This suggests that there's a mismatch between today's kernel and modules.
> Can you confirm/fix this?
>
> Jarek
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

[coLinux-devel] Modules broken?

[Jaroslaw K. <ja...@zd...>]

Hi Dan,

I just downloaded today's snapshot and (as I reported on IRC) "depmod -ae"
failed for me on Fedora Core 1 image. I got errors about some missing
symbols.

I attempted to rebuild kernel + modules myself:

1. I got FRESH kernel-2.4.26.tar.bz2 - extracted and applied patch
There wass some error saying that one of the chunks is already applied
(strange, but doesn't look harmful - it's just a printk(), so I ignored it)

2. I copied today's config file to .config

3. make oldconfig && make dep && make vmlinux && make modules && make
modules_install

After this I copied the kernel and modules into appropriate places and IT
WORKED.

This suggests that there's a mismatch between today's kernel and modules.
Can you confirm/fix this?

Jarek

Re: [coLinux-devel] snapshot 20040417

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dim,


http://www.colinux.org/snapshots/

Cheers, Thomas

> I'm really sorry about that, but where is the place from which it could be
> downloaded?
>
> Thank you,
> Dim
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAgVOXnwJBIFTVIqwRAsCYAJ4ps/4/KpwAWnKUSZvz72GnwBu2sQCgxvMK
KwalsuKWI2DeZJDzmS7l+Dw=
=Iu1P
-----END PGP SIGNATURE-----

[coLinux-devel] Using VNC/X ->Win32 Link Off-Network

[Michael S. <msi...@ya...>]

I have coLinux running on my Windows 2000 laptop with a native network
configuration (started with the Debian image and added X, VNCserver,
and KDE 3.2.1).  As long as my laptop is plugged into the network I can
use a Win32 VNC client to hook into the X system in the coLinux
instance.  As soon as I unhook from the network, however, the coLinux
instance and the Win32 instance can no longer communicate with each
other.

It appears that in a native networking configuration coLinux can only
talk to Win32 programs by first passing the packets out to my router
and then having the router pass them back to the laptop.  Thus with the
laptop off the network the two instances have no way to communicate.

Is there some way to get off-network usage in a native network
configuration to work?  Thanks for all your work on CoLinux - it's
quite an impressive trick.

Michael Sisolak
msi...@ya...


	
		
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html

Re: [coLinux-devel] IRC server & channel?

[Robert C. <rw...@al...>]

On Saturday, April 17, 2004, at 09:45  AM, Dan Aloni wrote:
> On Sat, Apr 17, 2004 at 09:39:58AM -0500, Robert Citek wrote:
>>
>> Does coLinux have a preferred server & channel on IRC?  Found nicks 
>> but
>> little else:
>>
>>   http://www.colinux.org/wiki/index.php/nicksandnames
>
> The official coLinux channel is #colinux at irc.oftc.net.

Thanks, Dan and others.  Wiki updated. - Robert

Re: [coLinux-devel] snapshot 20040417

[keksov <ke...@gm...>]

I'm really sorry about that, but where is the place from which it could be
downloaded?

Thank you,
Dim



Saturday, April 17, 2004, 4:12:23 PM, you wrote:

DA> Hello,

DA> Note about the swapoff fix (actually flush_tlb_all()). I've also 
DA> included more modules -- of course you'd have to extract that big 
DA> (600KB) vmlinux-modules.tar.gz to your filesystem images.

DA> Current list of changes since 0.6.0:

DA>   * Added the ability to send Ctrl-Alt-Del to the Linux machine.
DA>   * Linux patch updated to 2.4.26	
DA>   * Linux port (for systems running kernel 2.6.x)
DA>   * Fixed a crash that could happen on swapoff().
DA>   * Initmem is freed (no more 'missing implementation')
DA>   * The number of maximum cobd block devices was increased to 32.
DA>   * Windows: 
DA>     * Sizes of raw partition devices are now detected properly. This 
DA>       means that the resierfs problems should be over, plus cat /dev/cobd* 
DA>       would work for you.
DA>     * Suspension of the host machine won't cause colinux-daemon problems like
DA>       memory leaks.
DA>     * The daemon can install itself as a service (Jaroslaw Kowalski). 
DA>       Stopping the service sends Ctrl-Alt-Del to let the Linux VM
DA>       shutdown cleanly.
DA>     * coLinux now builds using MingW32 and no longer depends on cygwin1.dll.
DA>     * Added scripts for building the MingW32 cross compiler on Linux,
DA>       plus scripts that download, compile, and install the libraries
DA>       coLinux depends on.
DA>   * Linux port:
DA>     * Sending SIGHUP to the daemon causes it to issue Ctrl-Alt-Del on the
DA>       Linux VM.
DA>   * Consoles: 
DA>     * Fixed a bug in the clear operation: let it clear with the right video 
DA>       erase character so that ncurses apps would appear properly.
DA>     * Fixed virtual console switching (alt-f1, alt-f2, etc.) so it will
DA>       save/redraw the screen like it should.
DA>     * FLTK: The cursor is visible again.

Re: [coLinux-devel] IRC server & channel?

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

On Sat, Apr 17, 2004 at 09:39:58AM -0500, Robert Citek wrote:
> 
> Does coLinux have a preferred server & channel on IRC?  Found nicks but 
> little else:
> 
>   http://www.colinux.org/wiki/index.php/nicksandnames

The official coLinux channel is #colinux at irc.oftc.net.

-- 
Dan Aloni
da...@co...

[coLinux-devel] IRC server & channel?

[Robert C. <rw...@al...>]

Does coLinux have a preferred server & channel on IRC?  Found nicks but 
little else:

   http://www.colinux.org/wiki/index.php/nicksandnames

Regards,
- Robert

[coLinux-devel] snapshot 20040417

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

Hello,

Note about the swapoff fix (actually flush_tlb_all()). I've also 
included more modules -- of course you'd have to extract that big 
(600KB) vmlinux-modules.tar.gz to your filesystem images.

Current list of changes since 0.6.0:

  * Added the ability to send Ctrl-Alt-Del to the Linux machine.
  * Linux patch updated to 2.4.26	
  * Linux port (for systems running kernel 2.6.x)
  * Fixed a crash that could happen on swapoff().
  * Initmem is freed (no more 'missing implementation')
  * The number of maximum cobd block devices was increased to 32.
  * Windows: 
    * Sizes of raw partition devices are now detected properly. This 
      means that the resierfs problems should be over, plus cat /dev/cobd* 
      would work for you.
    * Suspension of the host machine won't cause colinux-daemon problems like 
      memory leaks.
    * The daemon can install itself as a service (Jaroslaw Kowalski). 
      Stopping the service sends Ctrl-Alt-Del to let the Linux VM
      shutdown cleanly.
    * coLinux now builds using MingW32 and no longer depends on cygwin1.dll.
    * Added scripts for building the MingW32 cross compiler on Linux,
      plus scripts that download, compile, and install the libraries
      coLinux depends on.
  * Linux port:
    * Sending SIGHUP to the daemon causes it to issue Ctrl-Alt-Del on the
      Linux VM.
  * Consoles: 
    * Fixed a bug in the clear operation: let it clear with the right video 
      erase character so that ncurses apps would appear properly.
    * Fixed virtual console switching (alt-f1, alt-f2, etc.) so it will
      save/redraw the screen like it should.
    * FLTK: The cursor is visible again.

-- 
Dan Aloni
da...@co...