colinux-devel — Cooperative Linux development mailing list

[coLinux-devel] Re: BSOD, kd> !analyze -v

[ePAc <ep...@ko...>]

> I have some output from the kernel debugger, but i don't have the symbols
> files (gotta hunt those suckers down on the MS website), and no linux.pdb
> to trace either.

this is the output (minus the big useless boxes).
it loads in the windbg, and gives me some "disassembly". Dan, is you want
to have a look at it, i'd be more than happy to give you more info.. :o)

--------------------------------------------------------------------------

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: eea5e000, Virtual address for the attempted write.
Arg2: 81ec1b38, PTE contents.
Arg3: eebe0aa8, (reserved)
Arg4: 0000000e, (reserved)

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xBE

LAST_CONTROL_TRANSFER:  from 80511b47 to 804f4103

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
eebe0a44 80511b47 000000be eea5e000 81ec1b38 nt!KeBugCheckEx+0x19
eebe0a90 80530140 00000001 eea5e000 00000000 nt!MmTrimAllSystemPagableMemory+0x50f1
eebe0aa8 00000000 c03ba778 eebe0ad4 eeda621d nt!Kei386EoiHelper+0x2388


FOLLOWUP_IP:
nt!MmTrimAllSystemPagableMemory+50f1
80511b47 833dbc30548000 cmp dword ptr [nt!LpcPortObjectType+0x114
(805430bc)],0x0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!MmTrimAllSystemPagableMemory+50f1

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

BUCKET_ID:  WRONG_SYMBOLS

MODULE_NAME:  Unknown_Module

Followup: MachineOwner
---------

I hope this makes more sense to some of you than to me...

this the the bugcheck i got after a clean boot, running it once, and got a
error -15 (as mentioned in other posts), and on the second try, a couple
of minutes later, this BSOD.

---
Nothing is foolproof to a sufficiently talented fool...
  oo
,(..)\
  ~~

Re: [coLinux-devel] Re: BSOD, DDK dependency

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

On Mon, Feb 02, 2004 at 04:48:32PM -0600, Richard Goodwin wrote:
> Dan, here is a register dump for the original "50" bugcheck.
> kd> r
> eax=ebab5000 ebx=eb3b6000 ecx=00000000 edx=0003fc00 esi=00000000 edi=00000000
                                             ^^^^^^^^
edx=0003fc00. 

Is there 1GB of RAM in that machine?

It crashed because the pa_to_host_va was allocated too short because of 
the PAGE_SHIFT bug, that was triggered because 1MB is not enough to 
round GlobalMemoryStatus's result. Aiee, Aiee, Aiee!

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

Re: [coLinux-devel] Re: BSOD, DDK dependency

[ePAc <ep...@ko...>]

I have some output from the kernel debugger, but i don't have the symbols
files (gotta hunt those suckers down on the MS website), and no linux.pdb
to trace either.

this looks like it can work (i say that, but i have no idea what i'm
tlaking about, other than the fact it seems that the system is trying to
write to something it shouldn't be writing to :o)

and one studpid question, but why round it up ? and not down ?

Jok

On Tue, 3 Feb 2004, Dan Aloni wrote:

> Date: Tue, 3 Feb 2004 00:48:03 +0200
> From: Dan Aloni <da...@gm...>
> To: Richard Goodwin <ric...@ri...>
> Cc: Cooperative Linux Development <col...@li...>,
>      Shachar Shemesh <win...@sh...>,
>      Steven Edwards <ste...@ya...>
> Subject: Re: [coLinux-devel] Re: BSOD, DDK dependency
>
> On Mon, Feb 02, 2004 at 04:35:36PM -0600, Richard Goodwin wrote:
> > I think it works! :) So far no crash!! What did you change?
>
> Cool.
>
> This might take care of those BSODs for now.
>
> --- colinux-20040131/src/colinux/kernel/monitor.c	2004-01-31 18:57:06.000000000 +0200
> +++ colinux-20040131-patch/src/colinux/kernel/monitor.c	2004-02-03 00:19:25.000000000 +0200
> @@ -114,9 +114,9 @@
>  	co_rc_t rc;
>
>  	cmon->page_tables_size = cmon->physical_frames * sizeof(unsigned long *);
> -	cmon->page_tables_pages = (cmon->page_tables_size + PAGE_SHIFT-1) >> PAGE_SHIFT;
> +	cmon->page_tables_pages = (cmon->page_tables_size + PAGE_SIZE-1) >> PAGE_SHIFT;
>  	cmon->pa_maps_size = cmon->manager->host_memory_pages * sizeof(unsigned long);
> -	cmon->pa_maps_pages = (cmon->pa_maps_size + PAGE_SHIFT-1) >> PAGE_SHIFT;
> +	cmon->pa_maps_pages = (cmon->pa_maps_size + PAGE_SIZE-1) >> PAGE_SHIFT;
>
>  	rc = co_monitor_alloc_pages(cmon, cmon->page_tables_pages, (void **)&cmon->page_tables);
>  	if (!CO_OK(rc)) {
>
> An obvious bug-o.
>
> But I don't think it's the end of the fix. The problem is that the
> amount of physical RAM reported from userspace is not divided
> by 16MB, which means that something went wrong in its calculation.
>
> Look at this:
>
> unsigned long co_os_get_physical_ram_size()
> {
> 	MEMORYSTATUS memstat;
>
> 	GlobalMemoryStatus(&memstat);
>
> 	/* Round up in MBs: */
>
> 	return (memstat.dwTotalPhys + 0xFFFFF) & 0xFFF00000;
> }
>
> It's BAD.
>
> Does anyone know a better way to get this information?
>
> --
> Dan Aloni
> da...@gm...
>
>
> -------------------------------------------------------
> 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
>

---
Nothing is foolproof to a sufficiently talented fool...
  oo
,(..)\
  ~~

Re: Re:[coLinux-devel] file/dir in use

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

Yeah, I built a package last night .. its the CHAOS minix file system, ported
across to an ext2 file system, mounted under the coLinux kernel.  I did a
few things when I bundled it last night;

  - Build a "Power-On" pif/lnk file to get the pwd right before exec, and to
      run the process minimised
  - Built a "Console" pif/lnk to match the pair.
  - Installer checks for XP
  - Installs to c:galileo with the files required to run it
  - Installs to c:galileonet with the TAP drivers
  - Adds start menu guff .. includes Power-On and Console .. link to site 
    and uninstall

  You can check it out at http://itsecurity.mq.edu.au/chaos/isos/beta/

Beware, if you're going to run this image that CHAOS comes with "certaintyd"
that checksums the file system every 2 seconds ... kill it if you want to change
anything.

  All I need now is a method of detecting/installing TAP and detecting/installing
the Bridge.  And from last night, I now have a couple of minor feature requests
to post back.


  There's a whole 'nutha world to this installer land isn't there?  Just be nice
to get some of this fiddly time-consuming bits out of the way while the rest
of the project does its bit.






----- Original Message -----
>From: "Ballard Jonathan" <sac...@ho...>
>To: "Ian Latter" <Ian...@mq...>, <col...@li...>
>Subject:  Re: Re:[coLinux-devel] file/dir in use
>Date: Mon, 02 Feb 2004 08:08:12 -0800
>
> 
> From: "Ian Latter" <Ian...@mq...>
> > On the up-side .. I was clearing some screen space to try out
> > this little installshield clone;
> >
> >   http://www.jrsoftware.org/isdl.php
> >
> > Looks very handy for those who may be looking to bundle
> > coLinux in a user-digestable format.
> 
> 
> I thought about an install script with NSIS: http://nsis.sourceforge.net
> 
> I have not read enough of the documentation to figure out how to register
> the TAP-Win32 device automatically.
> 
> Jonathan
> 

--
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] Re: BSOD, DDK dependency

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

On Mon, Feb 02, 2004 at 04:35:36PM -0600, Richard Goodwin wrote:
> I think it works! :) So far no crash!! What did you change?

Cool.

This might take care of those BSODs for now.

--- colinux-20040131/src/colinux/kernel/monitor.c	2004-01-31 18:57:06.000000000 +0200
+++ colinux-20040131-patch/src/colinux/kernel/monitor.c	2004-02-03 00:19:25.000000000 +0200
@@ -114,9 +114,9 @@
 	co_rc_t rc;
 
 	cmon->page_tables_size = cmon->physical_frames * sizeof(unsigned long *);
-	cmon->page_tables_pages = (cmon->page_tables_size + PAGE_SHIFT-1) >> PAGE_SHIFT;
+	cmon->page_tables_pages = (cmon->page_tables_size + PAGE_SIZE-1) >> PAGE_SHIFT;
 	cmon->pa_maps_size = cmon->manager->host_memory_pages * sizeof(unsigned long);
-	cmon->pa_maps_pages = (cmon->pa_maps_size + PAGE_SHIFT-1) >> PAGE_SHIFT;
+	cmon->pa_maps_pages = (cmon->pa_maps_size + PAGE_SIZE-1) >> PAGE_SHIFT;
 
 	rc = co_monitor_alloc_pages(cmon, cmon->page_tables_pages, (void **)&cmon->page_tables);
 	if (!CO_OK(rc)) {

An obvious bug-o.

But I don't think it's the end of the fix. The problem is that the 
amount of physical RAM reported from userspace is not divided 
by 16MB, which means that something went wrong in its calculation.

Look at this:

unsigned long co_os_get_physical_ram_size()
{
	MEMORYSTATUS memstat;
	
	GlobalMemoryStatus(&memstat);

	/* Round up in MBs: */

	return (memstat.dwTotalPhys + 0xFFFFF) & 0xFFF00000;
}

It's BAD.

Does anyone know a better way to get this information?

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

Re: [coLinux-devel] file/dir in use

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

Cool - now that I have a choice .. I can ask about features;  I want
to be able to script the automated installation of the TAP driver, and
the assembly of the Bridge (Mini MAC).  The best I can do on the
TAP driver so far, is pop up the "Add new hardware wizard" 
(hdwwiz.cpl) .. and I can't drive it, so far.  Looking at the TAP driver,
it's really just a sys file, a couple of registry entries and a service.  So,
I'm considering pulling it appart to add it to the installer ... but I'd prefer
not to ... have you seen a way around this?

Also, I found "netsh" that comes with XP, so I'm hoping (tho I haven't
found it yet) that I can script the addition of the bridge via that interface.

Suggestions are welcome.



----- Original Message -----
>From: "Ian C. Blenke" <ia...@bl...>
>To: "Ian Latter" <Ian...@mq...>
>Subject:  Re: [coLinux-devel] file/dir in use
>Date: Mon, 02 Feb 2004 10:00:03 -0500
>
> On Mon, Feb 02, 2004 at 09:14:14PM +1000, Ian Latter wrote:
> > Looks very handy for those who may be looking to bundle 
> > coLinux in a user-digestable format.
> 
> I've had great luck with the free win32 installer NSIS.
> 
> 	http://nsis.sf.net
> 
> With a minor bit of scripting, even cygwin packages neatly for
> installs/upgrades to windows boxen in the field.
> 
> - Ian
> 

--
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/

[coLinux-devel] file system error

[Gregor M. <mi...@ra...>]

Hi,

I installed coLinux (version from Jan. 31st) on WindowsXP Home edition.

Double clicking on colinux-daemon.exe yields:

Cooperative Linux daemon
Installing kernel driver
Creating monitor
Monitor is running

The coLinux console says:

  [...]
  Checking root file system...
  fsck 1.27 (8-Mar-2002)
  /dev/cobd0: The filesystem size (according to the superblok) is
  262144 blocks
  The physical size of the device is 30448 blocks
  Either the superblock or the partition table is likely to be corrupt!

  /dev/cobd0: UNEXPECTED INCONSISTENCY; [...]

  [...]

  (none):~#

I tried to fix the filesystem using fsck and e2fsck but the error
message does not disappear.

I then ran the bootscripts manually but I couldn't establish a network
connection. E. g. ping fails on every IP address.

What can I do?

Regards,

Gregor

-- 
   |          Gregor Mitsch  |
   |  www.gmdsoft.de/mitsch  |

Re: [coLinux-devel] BSOD, DDK dependency

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

On Mon, Feb 02, 2004 at 09:26:01PM +0000, Tim Larson wrote:
> On Mon, Feb 02, 2004 at 04:15:17PM -0500, Ian C. Blenke wrote:
> > You know, a colinux-users list might be in order here at some point. I
> > hate spamming *-devel lists with user support traffic.
> 
> Please wait till the project is bigger to split out a users list.
> I have watched some projects die because they split the community before
> they reached critical mass.  I would not want to risk that on a project
> this important.

I agree with Tim. The project's maturity is the reason why I didn't open 
a user mailing list yet.

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

Re: [coLinux-devel] BSOD, DDK dependency

[Tim L. <ti...@ke...>]

On Mon, Feb 02, 2004 at 04:15:17PM -0500, Ian C. Blenke wrote:
> You know, a colinux-users list might be in order here at some point. I
> hate spamming *-devel lists with user support traffic.

Please wait till the project is bigger to split out a users list.
I have watched some projects die because they split the community before
they reached critical mass.  I would not want to risk that on a project
this important.

--Tim Larson

Re: [coLinux-devel] BSOD, DDK dependency

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

On Mon, Feb 02, 2004 at 03:27:20PM -0500, Remy Porter wrote:
> ICS isn't working, nor is bridging. Bridging however, completely knocks 
> my computer off of the Internet (though not the local network, I fail to 
> understand this). With ICS, I give TAP the .0.1 IP, then when I activate 
> ICS, I'm told that my external connection will be set to .0.1 (is this 
> intentional, or is it some slight change in instructions between 2k and 
> XP?) I run ifup eth0, then try and ping and nothing. Any other thoughts?

Win2k doesn't have ICS, that I'm aware of. It's an XP thing.

You enabled ICS on your external interface, right? Not the Tap
interface.

You should not be setting your "external" connection to 192.168.0.1.
ICS only NATs IPs in the 192.168.0.x netblock, with the ICS gateway
itself at 192.168.0.1 on the "internal" connection.

   External Interface (Local Area Connection 1 - Ethernet)
   (24.164.164.210)
   WindowsXP w/ICS NAT
   (192.168.0.1)
   Tap Interface (Local Area Connection 2 - Tap interface)
   (192.168.0.40)
   Linux Image
   
When you enable bridging, you need to assign the bridge interface the
"external" IP of your PC (or use DHCP, as per default).

   Bridged Interface
   (24.164.154.210)
   	Local Area Connection 1 (Ethernet)
	Local Area Connection 2 (Tap interface)

   	(24.164.154.211)
   	Linux Image

Both your host's Bridge Interface *and* the Linux Image have IP adresses
on the same external public segment, with the same default gateway. 
All packets that your Windows host sees will also be seen by the Linux 
image, and vice-versa.

A Tap interface has two sides: the host side and the guest side.
- With ICS, the host side needs to be assigned an IP address. The guest
  must be given an IP address on that same virtual ethernet segment
  (think of it as a crossover cable). The ICS host acts as the default 
  gateway for the guest to route through. 
- With a bridge, you add the host side to the bridge - no IP is needed 
  on the host side for layer-2 bridging. The guest side may take any IP
  on that external network, just as the host itself would (think of it
  as a hub to which both the host and the guest are plugged into on the
  outside). The host side, however DOES need to assign an IP address 
  to the bridge interface itself (think of it as a virtual interface on
  that same segment that the host uses to talk to that network).

I hope that didn't confuse you more than it helped.

You know, a colinux-users list might be in order here at some point. I
hate spamming *-devel lists with user support traffic.

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

Re: [coLinux-devel] Strange problem with Win-TAP and coLinux

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

On Tue, Feb 03, 2004 at 12:07:48AM +0300, Vlad Doubrov wrote:
> Hi!
> 
> I've just installed the recent version (0.5.2) of coLinux binaries.
> Everething worked fine, including network drivers.

Good to hear :)

> But when I tried to transfer large files from the host OS (win XP pro)
> to the virtual linux box, I got this error:
> 
> C:\SFU\usr\src>scp mysql-3.23.58.tar.gz vlad@192.168.0.2:
> vlad@192.168.0.2's password:
> mysql-3.23.58.tar.gz           10% 1216KB 321.3KB/s   00:32 ETA
> Received disconnect from 192.168.0.2: 2: Corrupted MAC on input.
> lost connection
> 
> The same happens when I try to transfer that file via SMB (smbd and
> smbclient is installed on coLinux) - except that the file is getting
> corrupted after "successful" download.
> 
> Small files (less than 1 MB in size) get transferred very well.
> 
> So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible?
> Or may be it's my misunderstood?

My guess is to try to using ifconfig to change eth0's MAC address.

I didn't give much thought about the MAC address when I wrote the conet 
driver.

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

[coLinux-devel] Strange problem with Win-TAP and coLinux

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

Hi!

I've just installed the recent version (0.5.2) of coLinux binaries.
Everething worked fine, including network drivers.

But when I tried to transfer large files from the host OS (win XP pro)
to the virtual linux box, I got this error:

C:\SFU\usr\src>scp mysql-3.23.58.tar.gz vlad@192.168.0.2:
vlad@192.168.0.2's password:
mysql-3.23.58.tar.gz           10% 1216KB 321.3KB/s   00:32 ETA
Received disconnect from 192.168.0.2: 2: Corrupted MAC on input.
lost connection

The same happens when I try to transfer that file via SMB (smbd and
smbclient is installed on coLinux) - except that the file is getting
corrupted after "successful" download.

Small files (less than 1 MB in size) get transferred very well.

So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible?
Or may be it's my misunderstood?

Thanks!

-- vlad

Re: [coLinux-devel] linux kernel; array size missing in `data'

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

>   - 20040131 .config (from coLinux download site @ sourceforge)
>   - 20040131 linux patch (from same download).
> 
> 
> At this stage the kernel build fails in the very last stage of the
> build process (see below).
> 
> The build process is very simple ... patch it .. make mrproper .. cp in
> the .config .. make oldconfig .. make dep .. make bzImage .. nothing
> fancy at all (no openMosix, no IPSec, no other drivers, etc).

There's no need to 'make bzImage'. 

'make vmlinux' does the job without causing the problem you mentioned.


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

[coLinux-devel] Different Machines, Same XP Install, one BSODs

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

I got all the debug files and tried several setups.

I have an older Gateway with a P3 that I only use as a network server.  =
I thought that would be a good canidate for coLinux tests.   That system =
boots coLinux just fine except the fsck notice.

I have a newer P4 on a 845 chipset and that system crashes with the =
colinux-daemon.  I have the debug tools, but the system has not wanted =
to produce the kernel dump which is enabled.  The P4 is not HT but the =
845 board supports it.

Re: [coLinux-devel] BSOD Ahoy!

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

Well, disabling both HT and SMP via BIOS didn't help; however I still can't
help but think that it's SMP related. Anyone else having problems/success on
SMP/Hyperthreading machines? My OS'es are at standard revs, etc, so I'm not
sure where else to look.

----- Original Message ----- 
From: "Richard Goodwin" <ric...@ri...>
To: "Cooperative Linux Development" <col...@li...>
Sent: Monday, February 02, 2004 10:48 AM
Subject: Re: [coLinux-devel] BSOD Ahoy!


> Just realized what the common thread is in the failing machines...SMP! And
> of course both machines have Hyperthreading as well. I'll try disabling
the
> hyperthreading and see what happens, but unfortunately I can't remove the
> extra CPU to test that either.
>
> I installed the newer (seems like much newer) TAP driver from OpenVPN to
no
> avail, btw.
>
>
> ----- Original Message ----- 
> From: "Ian C. Blenke" <ia...@bl...>
> To: "Richard Goodwin" <rgo...@nu...>
> Cc: "Cooperative Linux Development" <col...@li...>
> Sent: Monday, February 02, 2004 10:08 AM
> Subject: Re: [coLinux-devel] BSOD Ahoy!
>
>
> > On Mon, Feb 02, 2004 at 10:02:26AM -0600, Richard Goodwin wrote:
> > > Is it possible there's a problem with the TAP driver or something? I'm
> using
> > > the same exact downloaded files, etc, on all three machines with
> obviously
> > > varied results.
> >
> > I'm running the Tap driver bundled as part of the openvpn project:
> >
> > http://openvpn.sf.net
> >
> > It was already installed, I didn't need to run the one bundled with the
> > coLinux project.
> >
> > Is there a difference in these versions perhaps?
> >
> > - Ian C. Blenke <ia...@bl...>
> >
> >
> >
>
>
>
> -------------------------------------------------------
> 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
>
>

[coLinux-devel] coLinux+XEN=WindowsXP on WindowsXP

[Digital I. Inc. <ok...@di...>]

Hello Everyone.

You know XEN?
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/

They run hacked Linux(XenoLinux)/NetBSD/WindowsXP on
hacked Linux(XEN Hypervisor). How about combining these
two project. I mean, adding Hypervisor patch to coLinux.
Then you can use XenoLinux/NetBSD/WindowsXP on coLinux.

One problem is, Running XP on coLinux needs hacked
WindowsXP that only Cambridge Univ can use.
But the development team claims that they are under
negotiation with MS to publicize hacked binary of XP.
I think the possibility of success is very low. but 
just seeing a screenshot of XP on XP taken by Cambridge
Univ is enough fun, dont you?

At least, by this, we get yet another way to run NetBSD on Windows.
And probably this way is the fastest.

          --- Okajima.

Re: [coLinux-devel] BSOD Ahoy!

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

Just realized what the common thread is in the failing machines...SMP! And
of course both machines have Hyperthreading as well. I'll try disabling the
hyperthreading and see what happens, but unfortunately I can't remove the
extra CPU to test that either.

I installed the newer (seems like much newer) TAP driver from OpenVPN to no
avail, btw.


----- Original Message ----- 
From: "Ian C. Blenke" <ia...@bl...>
To: "Richard Goodwin" <rgo...@nu...>
Cc: "Cooperative Linux Development" <col...@li...>
Sent: Monday, February 02, 2004 10:08 AM
Subject: Re: [coLinux-devel] BSOD Ahoy!


> On Mon, Feb 02, 2004 at 10:02:26AM -0600, Richard Goodwin wrote:
> > Is it possible there's a problem with the TAP driver or something? I'm
using
> > the same exact downloaded files, etc, on all three machines with
obviously
> > varied results.
>
> I'm running the Tap driver bundled as part of the openvpn project:
>
> http://openvpn.sf.net
>
> It was already installed, I didn't need to run the one bundled with the
> coLinux project.
>
> Is there a difference in these versions perhaps?
>
> - Ian C. Blenke <ia...@bl...>
>
>
>

Re: [coLinux-devel] BSOD Ahoy!

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

On Mon, Feb 02, 2004 at 10:02:26AM -0600, Richard Goodwin wrote:
> Is it possible there's a problem with the TAP driver or something? I'm using
> the same exact downloaded files, etc, on all three machines with obviously
> varied results.

I'm running the Tap driver bundled as part of the openvpn project:

	http://openvpn.sf.net

It was already installed, I didn't need to run the one bundled with the
coLinux project.

Is there a difference in these versions perhaps?

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

[coLinux-devel] BSOD Ahoy!

[Richard G. <rgo...@nu...>]

Ok, so far here's my experiences:

Machine A, laptop, W2k3: everything works fine
Machine B, workstation, W2k3: BSOD (including 8E and 50) upon starting (and
stopping?) cL
Machine C, workstation, XP Pro SP1: BSOD (including 8E, 50, and BE when I
switched to the replacement daemon) upon starting cL

Is it possible there's a problem with the TAP driver or something? I'm using
the same exact downloaded files, etc, on all three machines with obviously
varied results.

Here are the full stop codes from Machine C:
Stop 8E ( C0000005, 8050B62F, B9807948, 0000000)
Stop BE(EB733000,84932B38, EBABEAB4,0000000E), with some additional info
"Address EBA18926 base of EBA17000, Date Stamp 401becfb".

Thoughts?

[coLinux-devel] SP1 required?

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

I have XP Pro on my computer without SP1, and I still have not got =
coLinux to not crash on startup.  I see individuals with XP Home and XP =
Pro that state they installed SP1 and have coLinux work.  Is SP1 =
required?

I have a tablet with SP1 but I do not want to test coLinux on that =
machine.

[ I know I could install SP1 but that does not answer the requirement =
question. ]

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: Re:[coLinux-devel] file/dir in use

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

From: "Ian Latter" <Ian...@mq...>
> On the up-side .. I was clearing some screen space to try out
> this little installshield clone;
>
>   http://www.jrsoftware.org/isdl.php
>
> Looks very handy for those who may be looking to bundle
> coLinux in a user-digestable format.


I thought about an install script with NSIS: http://nsis.sourceforge.net

I have not read enough of the documentation to figure out how to register
the TAP-Win32 device automatically.

Jonathan

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] file/dir in use

[Tony H. <tm...@no...>]

Ian C. Blenke wrote:

> On Mon, Feb 02, 2004 at 09:14:14PM +1000, Ian Latter wrote:
> 
>>Looks very handy for those who may be looking to bundle 
>>coLinux in a user-digestable format.
> 
> 
> I've had great luck with the free win32 installer NSIS.
> 
> 	http://nsis.sf.net
> 
> With a minor bit of scripting, even cygwin packages neatly for
> installs/upgrades to windows boxen in the field.
> 
...and of course no list of installers would be complete without 
mentioning Innosetup :)

http://www.jrsoftware.org/isinfo.php

Tony

Re: [coLinux-devel] file/dir in use

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

On Mon, Feb 02, 2004 at 09:14:14PM +1000, Ian Latter wrote:
> Looks very handy for those who may be looking to bundle 
> coLinux in a user-digestable format.

I've had great luck with the free win32 installer NSIS.

	http://nsis.sf.net

With a minor bit of scripting, even cygwin packages neatly for
installs/upgrades to windows boxen in the field.

- Ian