colinux-devel

[coLinux-devel] Re: coLinux-devel digest, Vol 1 #9 - 11 msgs

[Jamie A. <jar...@ro...>]

First off, thanks to Dan Aloni for creating this, I think it'll be 
really useful in getting people like myself to get into using Linux, and 
thanks to Ian Blenke for telling how to get past the FSCK issue (though 
I'm sure it seems obvious to the others on this list).

I'm also experiencing some issues with bluescreens, they seem to happen 
most when the console screen is updated.  Another issue is that the 
daemon sometimes freezes if I alt-tab back to the console from another 
application; not much of an issue by itself but additionally, I can't 
kill the daemon through the Windows process list or through any other 
method I can think of.  I think some sort of tag on the daemon to force 
any existing daemons to terminate (such as colinux-daemon.exe -u) would 
be useful (I'd do it myself but kernel programming is a bit beyond me).  
Or is there another method of forcibly terminating the daemon if it 
crashes / hangs?

Jamie Arseneault

[coLinux-devel] Re: coLinux-devel digest, Vol 1 #9 - 11 msgs

[Jamie A. <jar...@ro...>]

Of course, the fact that I missed Monitor -> Terminate just made my 
whole message useless... Don't mind me, I'm tired -_-

> First off, thanks to Dan Aloni for creating this, I think it'll be 
> really useful in getting people like myself to get into using Linux, 
> and thanks to Ian Blenke for telling how to get past the FSCK issue 
> (though I'm sure it seems obvious to the others on this list).
>
> I'm also experiencing some issues with bluescreens, they seem to 
> happen most when the console screen is updated.  Another issue is that 
> the daemon sometimes freezes if I alt-tab back to the console from 
> another application; not much of an issue by itself but additionally, 
> I can't kill the daemon through the Windows process list or through 
> any other method I can think of.  I think some sort of tag on the 
> daemon to force any existing daemons to terminate (such as 
> colinux-daemon.exe -u) would be useful (I'd do it myself but kernel 
> programming is a bit beyond me).  Or is there another method of 
> forcibly terminating the daemon if it crashes / hangs?
>
> Jamie Arseneault
>

Re: [coLinux-devel] Re: coLinux-devel digest, Vol 1 #9 - 11 msgs

[Richard G. <ric...@ri...>]

I actually removed the fsck check at startup from rcS.d/S10checkroot.sh. Now
I can start coLinux as a service with NtLauncherService (NTLSVC) and it
comes up to network readiness :-)

One thing I haven't figured out with bridging or ICS.. Will I be able to
send incoming packets to the bridge connection?

Example: Windows 2003, "real" NIC has ip of 192.168.123.100; TAP has an IP
of [0.1 for ICS, or 123.101(?) for bridged?]. If I ran an sshd in coLinux,
would I be able to connect to it from another box? Which IP would I need to
connect to?

Couple of other questions:
1) Any way to resize the Debian image? Or can someone put up an image that
is like a 2gb or 4gb compressed filesystem?
2) I really need a kernel with smbfs (to interop with Windows) at this
point. Given that I don't nkow if I can find a clean build system and setup
any cross compilation, what are my options?

Thanks! I'm spreading the coLInux religion to my cohorts at work (Dell)
today :-)


----- Original Message ----- 
From: "Jamie Arseneault" <jar...@ro...>
To: <col...@li...>
Sent: Monday, February 02, 2004 8:06 AM
Subject: [coLinux-devel] Re: coLinux-devel digest, Vol 1 #9 - 11 msgs


> Of course, the fact that I missed Monitor -> Terminate just made my
> whole message useless... Don't mind me, I'm tired -_-
>
> > First off, thanks to Dan Aloni for creating this, I think it'll be
> > really useful in getting people like myself to get into using Linux,
> > and thanks to Ian Blenke for telling how to get past the FSCK issue
> > (though I'm sure it seems obvious to the others on this list).
> >
> > I'm also experiencing some issues with bluescreens, they seem to
> > happen most when the console screen is updated.  Another issue is that
> > the daemon sometimes freezes if I alt-tab back to the console from
> > another application; not much of an issue by itself but additionally,
> > I can't kill the daemon through the Windows process list or through
> > any other method I can think of.  I think some sort of tag on the
> > daemon to force any existing daemons to terminate (such as
> > colinux-daemon.exe -u) would be useful (I'd do it myself but kernel
> > programming is a bit beyond me).  Or is there another method of
> > forcibly terminating the daemon if it crashes / hangs?
> >
> > Jamie Arseneault
> >
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
>

Re: [coLinux-devel] Re: coLinux-devel digest, Vol 1 #9 - 11 msgs

[Ian C. B. <ia...@bl...>]

On Mon, Feb 02, 2004 at 09:16:06AM -0600, Richard Goodwin wrote:
> 
> Example: Windows 2003, "real" NIC has ip of 192.168.123.100; TAP has an IP
> of [0.1 for ICS, or 123.101(?) for bridged?]. If I ran an sshd in coLinux,
> would I be able to connect to it from another box? Which IP would I need to
> connect to?

You would connect to the IP of the image (192.168.1.40 by default - just
edit the /etc/network/interfaces file).

> Couple of other questions:
> 1) Any way to resize the Debian image? Or can someone put up an image that
> is like a 2gb or 4gb compressed filesystem?

Using Unix tools, this is easy:

	$ dd if=/dev/zero of=Debian-3.0r0.ext3.1gb bs=0 seek=4G

This will grow the file to 4G by seeking into the file and writing
nothing. Moreover, on a true Unix filesystem, this file would be a
"sparse file" taking up no disk space until the coLinux image writes a
block to the cobd device. AFAIK, NTFS does not support sparse files in
this way.

The bs=0 trick really means "write 0 bytes, but treat seeks/reads as 1".

Then you must resize the filesystem. With ext2/ext3 it's simple:

	$ resize2fs Debian-3.0r0.ext3.1gb `du Debian-3.0r0.ext3.1gb | awk '{print $1}'`

Other filesystems, like Reiserfs and XFS, support other methods of
growing the filesystem (resize_reiserfs, xfs_growfs).

Here's an old post of mine to the User-Mode-Linux list that might help
(note, I was not aware of the bs=0 seek trick at the time)

http://smtp.linux-sxs.org/pipermail/linux-users/2002-November/010762.html

> 2) I really need a kernel with smbfs (to interop with Windows) at this
> point. Given that I don't nkow if I can find a clean build system and setup
> any cross compilation, what are my options?

SMBFS is slow for production use. Painfully so. I would recommend 
running Samba 3.0 and mapping the other direction if at all possible. 
Alternatively, try Microsoft's now free Services For Unix and NFS 
if you really wish to mount the other way.

> Thanks! I'm spreading the coLInux religion to my cohorts at work (Dell)
> today :-)

And so it begins.

- Ian C. Blenke <ia...@bl...>

Re: [coLinux-devel] Re: coLinux-devel digest, Vol 1 #9 - 11 msgs

[Ballard J. <sac...@ho...>]

From: "Richard Goodwin" <ric...@ri...>
[...]
> One thing I haven't figured out with bridging or ICS.. Will I be able to
> send incoming packets to the bridge connection?
[...]

The ICS connection can be directed to the network bridge with all the
devices on bridge.  The ICS normally does not display the option to select
the bridge until the bridge is created.