Menu
▾
▴
colinux-users — coLinux users mailing list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
| 2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
| 2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
| 2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
| 2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
| 2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
| 2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Martin K. <ka...@po...> - 2004-07-13 18:23:36
|
you should newer access one partition/file with two different programs, that doesn't know what the other does. so if you can't access partition, because colinux use it and locks, you're lucky to not lost some of data. Regards, Martin > I found the problem. I did not realize that my vmfile are in that partition, > therefore I am not able to access the whole partition as colinux locks it. > Perhaps I have to use samba -- Is this the right way to access any windows > partition? > > Thanks > > "Sarah Tanembaum" <sar...@ya...> > wrote in message news:ccvhid$ugm$1...@se...... > >>I'm having probs mounting FAT32 partition(in a extended partition) within >>coLinux but FAT16 partition(in primary partition) is okay. Is there >>restriction? >> >>THanks >> >> >> >> >> >> >> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com |
|
From: <joe...@ce...> - 2004-07-13 17:09:35
|
Group,
Is there any reason why crossover office wouldn't install on my
debian colinux instance? Not neccisarily for full-time productivity, but
just for the high furstration and learning that is likely to occur with the
install and maintenance.
Thanks,
Joe
|
|
From: <joc...@ho...> - 2004-07-13 16:51:46
|
As they are the steps to install the Traditional Desktop of Linux = (without vncserver) Javier Osvaldo Ch=E9rcoles --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05/07/2004 |
|
From: Sarah T. <sar...@ya...> - 2004-07-13 16:42:38
|
I found the problem. I did not realize that my vmfile are in that partition, therefore I am not able to access the whole partition as colinux locks it. Perhaps I have to use samba -- Is this the right way to access any windows partition? Thanks "Sarah Tanembaum" <sar...@ya...> wrote in message news:ccvhid$ugm$1...@se...... > I'm having probs mounting FAT32 partition(in a extended partition) within > coLinux but FAT16 partition(in primary partition) is okay. Is there > restriction? > > THanks > > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com |
|
From: Ishwar R. <is...@pa...> - 2004-07-13 15:23:47
|
I tried again to get networking going but no success. 1. I followed the steps (exactly) from wiki-site-->coLinux Networking-> Native network Bridged (Windows 2000 or Windows XP) 2. Disabled TCP/IP checksums in LAC (3Com configuration) 3. Added the option mac="00:ff:40:a9:20:60" for 'TAP VPN Adapter' 4. Booted and rebooted coLinux but no success with ping 191.168.0.1 All I see is error in command window: --- ... Freeing unused kernel memory: 52k freed EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117,0), internal journal bridged-net-daemon: Checking adapter: Generic NdisWan adapter bridged-net-daemon: Checking adapter: 3Com EtherLink PCI (Microsoft's Packet Scheduler) bridged-net-daemon: Checking adapter: VMware Virtual Ethernet Adapter bridged-net-daemon: Checking adapter: TAP VPN Adapter. (Microsoft's Packet Scheduler) bridged-net-daemon: Listening on: TAP VPN Adapter. (Microsoft's Packet Scheduler) ... bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30) or (ether broadcast or multicast) o r (ip broadcast or multicast) pipe client 0/8: Connecting to daemon... pipe client 0/8: Connection established daemon: module connected: conet0 co_message_switch: setting callback rule for 8 packet tx: pcap - FAILED packet tx: pcap - FAILED packet tx: pcap - FAILED -- Any ideas? -ishwar On Mon, 12 Jul 2004, Ishwar Rattan wrote: > > Host: Windows XP/Pro > NIC : 3Com Etherlink > > Box is connected to dept LAN with static IP (a DHCP sever is > also available). I installed coLinux-0.6.1 (with winPcap-3.1beta > and Debian-3.0r0??.1gb (root_fs) and swap_256Mb files. > > I have had no success with neworking part. > > The 'TAP-Win32 Adapter' device is visible twice (Control Panel-> > Network connections) as Local Area Connection (LAC) #2 and LAC #3 > where 3Com is visible as LAC (itsef). > > I tried bridging (want coLinux to have its own IP on deptLAN) between > LAC and LAC #2:: > > the real 3Com intreface also disappears no response with message > destination network not reachable) > > [last line in default.colinux.xml: > <network index="0" type="bridged" name="TAP VPN Adapter" /> > ] > > Help will be appreciated. > > -ishwar > > |
|
From: Sarah T. <sar...@ya...> - 2004-07-13 03:54:54
|
Dan, I tried to play with this snapshot but none of the gentoo distribution works. It seems that it does not work with 2.4 kernel. Where can I get the 2.6 gentoo distribution? Thanks "Dan Aloni" <da...@co...> wrote in message news:200...@ca...... > Good evening, > > I've just uploaded a new snapshot - 20040710. It brings forth a bunch > of changes, and hopefully solves some reported bugs (I'd be glad to > receive confirmation mails). > > Changes since 20040622: > > * Added a coserial deamon, that allows one to open a serial terminal > to the guest machine (You can run /sbin/mgetty ttyS0 in the guest > and then run the daemon in the host and get a login prompt :). > Porting this daemon to Windows should be relatively easy, though I > can't promise that the Windows Win32 console can handle the terminal > properties of the Linux end, but it would be interesting to find out. > * Improved debugging - we now have a debug messages "collector" > deamon named colinux-debug-deamon, which collects debug messages > from all the coLinux components. This also changes the way things > are printed when you run the daemon (it is now easier to see > what belongs to what). All debug messages are off by default, > so things may go a little faster. > * An API version number was added to make sure that you use the > right vmlinux and user-space executables with the right coLinux > driver (previously it caused crashes if the APIs changed). > * Bug fix: A tiny memory leak when coLinux is shutting down. > * Bug fix: Proper reference counting of the driver in the Linux > port. > * Bug fix: The network driver (conet) now verifies checksums (as > network packets that are received by PCAP can indeed be bad). > * Added block device aliasing, e.g alias="hda2". You can specify > such an alias in the <block_device> element in the configuration > XML and expect coLinux to mount it, even when passed with root=. > NOTE: The cobdX device and its alias are mutual exclusive, which > means that you can't mount both of them at the same time. > * Bug fix: Proper floating point state preservation in the Linux > guest. coLinux now passes the flops20 test program. > * Implemented a new timer for the Linux guest, this should fix > time-going-back issues. > * Improved message passing, which may boost networking a bit. > * Win32-TAP driver upgraded to version 8.1. This version doesn't > bring any changes to the actual driver code. However it was > released in order to notify the other projects that bundle the > TAP driver along with their software, to modify the name > identifer of the driver so that multiple TAP driver users can > coexist (e.g, OpenVPN with coLinux). Therefore, coLinux now > installs its TAP driver as TAPxxxxco (where xxxx is the > driver version). > After installing it, you will notice " (coLinux)" appended to > the device name in the Network Connections manager. The old > driver will remain until it is uninstalled. > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com |
|
From: Sarah T. <sar...@ya...> - 2004-07-13 03:00:48
|
Hi, now that I manage to run my native fedora 2 within coLinux, I need some
help how do I build the 2.6.7 kernel.
So far I have:
gcc-3.3.2 and rest of gnu utilities
kernel-2.6.7
How unfortunate, I can't even pass the 'make menuconfig'.
Do I need to patch the virgin linux-2.6.7 to be able to compile within
coLinux? If yes, where can I get those patch?
Thanks
Here's the errors:
HOSTCC scripts/basic/fixdep
scripts/basic/fixdep.c:97:23: sys/types.h: No such file or directory
scripts/basic/fixdep.c:98:22: sys/stat.h: No such file or directory
scripts/basic/fixdep.c:99:22: sys/mman.h: No such file or directory
scripts/basic/fixdep.c:100:20: unistd.h: No such file or directory
scripts/basic/fixdep.c:101:19: fcntl.h: No such file or directory
scripts/basic/fixdep.c:102:20: string.h: No such file or directory
scripts/basic/fixdep.c:103:20: stdlib.h: No such file or directory
scripts/basic/fixdep.c:104:19: stdio.h: No such file or directory
In file included from
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/syslimits.h:7,
from
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/limits.h:11,
from scripts/basic/fixdep.c:105:
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/limits.h:122:75:
limits.h: No such file or directory
scripts/basic/fixdep.c:106:19: ctype.h: No such file or directory
scripts/basic/fixdep.c:107:24: netinet/in.h: No such file or directory
scripts/basic/fixdep.c: In function `usage':
scripts/basic/fixdep.c:121: warning: implicit declaration of function
`fprintf'
scripts/basic/fixdep.c:121: error: `stderr' undeclared (first use in this
function)
scripts/basic/fixdep.c:121: error: (Each undeclared identifier is reported
only once
scripts/basic/fixdep.c:121: error: for each function it appears in.)
scripts/basic/fixdep.c:122: warning: implicit declaration of function `exit'
scripts/basic/fixdep.c: In function `print_cmdline':
scripts/basic/fixdep.c:127: warning: implicit declaration of function
`printf'
scripts/basic/fixdep.c: At top level:
scripts/basic/fixdep.c:130: error: `NULL' undeclared here (not in a
function)
scripts/basic/fixdep.c: In function `grow_config':
scripts/basic/fixdep.c:143: warning: implicit declaration of function
`realloc'
scripts/basic/fixdep.c:143: warning: assignment makes pointer from integer
without a cast
scripts/basic/fixdep.c:144: error: `NULL' undeclared (first use in this
function)
scripts/basic/fixdep.c:145: warning: implicit declaration of function
`perror'
scripts/basic/fixdep.c: In function `is_defined_config':
scripts/basic/fixdep.c:161: warning: implicit declaration of function
`memcmp'
scripts/basic/fixdep.c: In function `define_config':
scripts/basic/fixdep.c:174: warning: implicit declaration of function
`memcpy'
scripts/basic/fixdep.c: In function `use_config':
scripts/basic/fixdep.c:193: error: `PATH_MAX' undeclared (first use in this
function)
scripts/basic/fixdep.c:207: warning: implicit declaration of function
`tolower'
scripts/basic/fixdep.c:193: warning: unused variable `s'
scripts/basic/fixdep.c: At top level:
scripts/basic/fixdep.c:212: error: parse error before "size_t"
scripts/basic/fixdep.c:213: warning: function declaration isn't a prototype
scripts/basic/fixdep.c: In function `parse_config_file':
scripts/basic/fixdep.c:214: error: `map' undeclared (first use in this
function)
scripts/basic/fixdep.c:214: error: `len' undeclared (first use in this
function)
scripts/basic/fixdep.c:220: warning: implicit declaration of function
`ntohl'
scripts/basic/fixdep.c:231: warning: implicit declaration of function
`isalnum'
scripts/basic/fixdep.c: In function `strrcmp':
scripts/basic/fixdep.c:244: warning: implicit declaration of function
`strlen'
scripts/basic/fixdep.c: In function `do_config_file':
scripts/basic/fixdep.c:255: error: storage size of `st' isn't known
scripts/basic/fixdep.c:259: warning: implicit declaration of function `open'
scripts/basic/fixdep.c:259: error: `O_RDONLY' undeclared (first use in this
function)
scripts/basic/fixdep.c:261: error: `stderr' undeclared (first use in this
function)
scripts/basic/fixdep.c:265: warning: implicit declaration of function
`fstat'
scripts/basic/fixdep.c:267: warning: implicit declaration of function
`close'
scripts/basic/fixdep.c:270: warning: implicit declaration of function `mmap'
scripts/basic/fixdep.c:270: error: `NULL' undeclared (first use in this
function)
scripts/basic/fixdep.c:270: error: `PROT_READ' undeclared (first use in this
function)
scripts/basic/fixdep.c:270: error: `MAP_PRIVATE' undeclared (first use in
this function)
scripts/basic/fixdep.c:270: warning: assignment makes pointer from integer
without a cast
scripts/basic/fixdep.c:279: warning: implicit declaration of function
`munmap'
scripts/basic/fixdep.c:255: warning: unused variable `st'
scripts/basic/fixdep.c: At top level:
scripts/basic/fixdep.c:284: error: parse error before "size_t"
scripts/basic/fixdep.c:285: warning: function declaration isn't a prototype
scripts/basic/fixdep.c: In function `parse_dep_file':
scripts/basic/fixdep.c:286: error: `map' undeclared (first use in this
function)
scripts/basic/fixdep.c:287: error: `len' undeclared (first use in this
function)
scripts/basic/fixdep.c:289: error: `PATH_MAX' undeclared (first use in this
function)
scripts/basic/fixdep.c:291: warning: implicit declaration of function
`strchr'
scripts/basic/fixdep.c:293: error: `stderr' undeclared (first use in this
function)
scripts/basic/fixdep.c:289: warning: unused variable `s'
scripts/basic/fixdep.c: In function `print_deps':
scripts/basic/fixdep.c:325: error: storage size of `st' isn't known
scripts/basic/fixdep.c:329: error: `O_RDONLY' undeclared (first use in this
function)
scripts/basic/fixdep.c:331: error: `stderr' undeclared (first use in this
function)
scripts/basic/fixdep.c:341: error: `NULL' undeclared (first use in this
function)
scripts/basic/fixdep.c:341: error: `PROT_READ' undeclared (first use in this
function)
scripts/basic/fixdep.c:341: error: `MAP_PRIVATE' undeclared (first use in
this function)
scripts/basic/fixdep.c:341: warning: assignment makes pointer from integer
without a cast
scripts/basic/fixdep.c:325: warning: unused variable `st'
scripts/basic/fixdep.c: In function `traps':
scripts/basic/fixdep.c:360: error: `stderr' undeclared (first use in this
function)
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2
|
|
From: Sarah T. <sar...@ya...> - 2004-07-13 02:31:47
|
I'm having probs mounting FAT32 partition(in a extended partition) within coLinux but FAT16 partition(in primary partition) is okay. Is there restriction? THanks |
|
From: Ishwar R. <is...@pa...> - 2004-07-12 19:33:09
|
Host: Windows XP/Pro NIC : 3Com Etherlink Box is connected to dept LAN with static IP (a DHCP sever is also available). I installed coLinux-0.6.1 (with winPcap-3.1beta and Debian-3.0r0??.1gb (root_fs) and swap_256Mb files. I have had no success with neworking part. The 'TAP-Win32 Adapter' device is visible twice (Control Panel-> Network connections) as Local Area Connection (LAC) #2 and LAC #3 where 3Com is visible as LAC (itsef). I tried bridging (want coLinux to have its own IP on deptLAN) between LAC and LAC #2:: the real 3Com intreface also disappears no response with message destination network not reachable) [last line in default.colinux.xml: <network index="0" type="bridged" name="TAP VPN Adapter" /> ] Help will be appreciated. -ishwar |
|
From: Blake <pb...@ta...> - 2004-07-11 19:20:32
|
You should test further. I tried to reproduce your results and found = that initially things look this way. But if I ssh into the colinux = instance and try the tests, then the colinux' netperf network = performance is actually better than loopback. =20 Even when I then switch back to using the default CoLinux console after = this, the netperf network results are as they were in the ssh session. =20 So maybe you need at least 1 open TCP session to achieve acceptable = performance on this test. Try ssh-ing from one instance to the other = and then run the test from that one to the first. And then reverse this = procedure. I'm using the TAP bridging scheme in XP. How are you setup? --=20 --Blake pb...@ta... "Taisuke Yamada" <tya...@li...> wrote in message = news:nqt...@ho...... > Hi. >=20 > I've set up 2 coLinux instances with NFS client-server > configuration to save diskspace, but performance is way > slower than I expected. >=20 > To quantify my experience, I dis some benchmarking with > netperf. In following data, "co00" is the NFS server > and "co01" is the client. They both use TAP driver bridged > by Windows "Network Bridge" for network connection. >=20 > co00:/root# netperf > TCP STREAM TEST to localhost > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > =20 > 87380 16384 16384 10.00 8599.03 > co00:/root# >=20 > co01:/root# netperf -H 192.168.100.100 > TCP STREAM TEST to 192.168.100.100 > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > =20 > 87380 16384 16384 10.02 23.39 > co01:/root# >=20 > As you can see, TCP thoughput between 2 colinux instances > is about 400 times slower than loopback. >=20 > Is this a current limitation, or am I doing something wrong? > Since there's no physical device between these two, I'm > wondering if there's any coLinux parameter to increase > network performance. >=20 > Thanks in advance. >=20 |
|
From: Blake <pb...@ta...> - 2004-07-11 19:19:06
|
You should test further. I tried to reproduce your results and found = that initially things look this way. But if I ssh into the colinux = instance and try the tests, then the colinux' netperf network = performance is actually better than loopback. =20 Even when I then switch back to using the default CoLinux console after = this, the netperf network results are as they were in the ssh session. =20 So maybe you need at least 1 open TCP session to achieve acceptable = performance on this test. Try ssh-ing from one instance to the other = and then run the test from that one to the first. And then reverse this = procedure. I'm using the TAP bridging scheme in XP. How are you setup? --=20 --Blake pb...@ta... "Taisuke Yamada" <tya...@li...> wrote in message = news:nqt...@ho...... > Hi. >=20 > I've set up 2 coLinux instances with NFS client-server > configuration to save diskspace, but performance is way > slower than I expected. >=20 > To quantify my experience, I dis some benchmarking with > netperf. In following data, "co00" is the NFS server > and "co01" is the client. They both use TAP driver bridged > by Windows "Network Bridge" for network connection. >=20 > co00:/root# netperf > TCP STREAM TEST to localhost > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > =20 > 87380 16384 16384 10.00 8599.03 > co00:/root# >=20 > co01:/root# netperf -H 192.168.100.100 > TCP STREAM TEST to 192.168.100.100 > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > =20 > 87380 16384 16384 10.02 23.39 > co01:/root# >=20 > As you can see, TCP thoughput between 2 colinux instances > is about 400 times slower than loopback. >=20 > Is this a current limitation, or am I doing something wrong? > Since there's no physical device between these two, I'm > wondering if there's any coLinux parameter to increase > network performance. >=20 > Thanks in advance. >=20 |
|
From: Taisuke Y. <tya...@li...> - 2004-07-11 17:57:45
|
Hi. I've set up 2 coLinux instances with NFS client-server configuration to save diskspace, but performance is way slower than I expected. To quantify my experience, I dis some benchmarking with netperf. In following data, "co00" is the NFS server and "co01" is the client. They both use TAP driver bridged by Windows "Network Bridge" for network connection. co00:/root# netperf TCP STREAM TEST to localhost Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 87380 16384 16384 10.00 8599.03 co00:/root# co01:/root# netperf -H 192.168.100.100 TCP STREAM TEST to 192.168.100.100 Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 87380 16384 16384 10.02 23.39 co01:/root# As you can see, TCP thoughput between 2 colinux instances is about 400 times slower than loopback. Is this a current limitation, or am I doing something wrong? Since there's no physical device between these two, I'm wondering if there's any coLinux parameter to increase network performance. Thanks in advance. -- 012345678901234567890123456789012345678901234567890123456789012345678901234 Taisuke Yamada <<tya...@sp...>> Message to my public address may not be handled in a timely manner. Message to my "SPAM honeypot" address will be registered as a SPAM. For a direct contact, please use my private address on my namecard. |
|
From: Dan A. <da...@co...> - 2004-07-10 17:24:43
|
Good evening,
I've just uploaded a new snapshot - 20040710. It brings forth a bunch
of changes, and hopefully solves some reported bugs (I'd be glad to
receive confirmation mails).
Changes since 20040622:
* Added a coserial deamon, that allows one to open a serial terminal
to the guest machine (You can run /sbin/mgetty ttyS0 in the guest
and then run the daemon in the host and get a login prompt :).
Porting this daemon to Windows should be relatively easy, though I
can't promise that the Windows Win32 console can handle the terminal
properties of the Linux end, but it would be interesting to find out.
* Improved debugging - we now have a debug messages "collector"
deamon named colinux-debug-deamon, which collects debug messages
from all the coLinux components. This also changes the way things
are printed when you run the daemon (it is now easier to see
what belongs to what). All debug messages are off by default,
so things may go a little faster.
* An API version number was added to make sure that you use the
right vmlinux and user-space executables with the right coLinux
driver (previously it caused crashes if the APIs changed).
* Bug fix: A tiny memory leak when coLinux is shutting down.
* Bug fix: Proper reference counting of the driver in the Linux
port.
* Bug fix: The network driver (conet) now verifies checksums (as
network packets that are received by PCAP can indeed be bad).
* Added block device aliasing, e.g alias="hda2". You can specify
such an alias in the <block_device> element in the configuration
XML and expect coLinux to mount it, even when passed with root=.
NOTE: The cobdX device and its alias are mutual exclusive, which
means that you can't mount both of them at the same time.
* Bug fix: Proper floating point state preservation in the Linux
guest. coLinux now passes the flops20 test program.
* Implemented a new timer for the Linux guest, this should fix
time-going-back issues.
* Improved message passing, which may boost networking a bit.
* Win32-TAP driver upgraded to version 8.1. This version doesn't
bring any changes to the actual driver code. However it was
released in order to notify the other projects that bundle the
TAP driver along with their software, to modify the name
identifer of the driver so that multiple TAP driver users can
coexist (e.g, OpenVPN with coLinux). Therefore, coLinux now
installs its TAP driver as TAPxxxxco (where xxxx is the
driver version).
After installing it, you will notice " (coLinux)" appended to
the device name in the Network Connections manager. The old
driver will remain until it is uninstalled.
--
Dan Aloni
da...@co...
|
|
From: David S. <Dav...@by...> - 2004-07-10 12:48:31
|
<quote who="Sam Liddicott"> > David Smith wrote: >> I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and >> boots >> extremely fast! Now I'm messing with my config.xml to try to get CoLinux >> to mount my 120Gb IDE ext3-formatted drive. This is a separate drive >> than >> the one Windows XP is installed on, and it has a single ext3 partition. >> According to the CoLinux docs, CoLinux relies on the host OS to provide >> logical access to block devices. But if my host OS (Windows) doesn't >> understand ext3, how can it provide logical access? Here's what I've >> tried >> to no avail in config.xml: >> >> <block_device index="1" >> path="\Device\HarddiskVolume1" >> enabled="true" /> >> >> <block_device index="1" >> path="\Device\Harddisk1\Partition1" >> enabled="true" /> >> >> <block_device index="1" >> path="\Device\Harddisk1" >> enabled="true" /> >> >> According to the Windows management console, my drive is "Disk 1", and >> it >> appears as "Healthy (Unknown Partition)". >> >> Can anyone shed any light on how I could get CoLinux to recognize my >> ext3 >> drive? > > I've got rhis to work with removable USB hard drives; it would help if > you said why you thought it wasn't working. > > By using: index="1" it would make the coLinux block device that > represents the disk be /dev/cobd1 > > What happens when you try and mount /dev/cobd1 ? > > Can you do: less -f /dev/cobd1 > to see if the partition can even be read from coLinux? > > Sam See my previous post. I've already solved the problem. But to answer your question: mount told me that there was no valid superblock, and 'fdisk -l /dev/cobd1' output nothing. But no worries, I've got it working now. It mounts properly and fdisk -l gives valid output. All is well! --Dave |
|
From: Sam L. <sa...@li...> - 2004-07-09 21:02:44
|
David Smith wrote: > I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and boots > extremely fast! Now I'm messing with my config.xml to try to get CoLinux > to mount my 120Gb IDE ext3-formatted drive. This is a separate drive than > the one Windows XP is installed on, and it has a single ext3 partition. > According to the CoLinux docs, CoLinux relies on the host OS to provide > logical access to block devices. But if my host OS (Windows) doesn't > understand ext3, how can it provide logical access? Here's what I've tried > to no avail in config.xml: > > <block_device index="1" > path="\Device\HarddiskVolume1" > enabled="true" /> > > <block_device index="1" > path="\Device\Harddisk1\Partition1" > enabled="true" /> > > <block_device index="1" > path="\Device\Harddisk1" > enabled="true" /> > > According to the Windows management console, my drive is "Disk 1", and it > appears as "Healthy (Unknown Partition)". > > Can anyone shed any light on how I could get CoLinux to recognize my ext3 > drive? I've got rhis to work with removable USB hard drives; it would help if you said why you thought it wasn't working. By using: index="1" it would make the coLinux block device that represents the disk be /dev/cobd1 What happens when you try and mount /dev/cobd1 ? Can you do: less -f /dev/cobd1 to see if the partition can even be read from coLinux? Sam |
|
From: <mar...@mu...> - 2004-07-09 13:22:34
|
Oh, sorry. I used the wrong button to reply :\ I think I have fixed it: I reinstalled the TAP driver and everythin= g worked again. Thanks for you help. Anyway, I'll find out more about non-ICS networking, it seem= s interesting... LvdT> Please keep replies to the forum, not just to private e-mail... LvdT> In my experience, even if Gentoo can't bring up it's LvdT> network interface the device is now at least 'connected' at the LvdT> windows end, so it's possible to configure it in all sorts of LvdT> manners. LvdT> There are btw. several ways to achieve networking LvdT> connectivity without using ICS; I don't use ICS myself either. --------------------------------------- Mart=EDn Melado - youk [en] mundo-r.com 43=BA 21' 11" N, 8=BA 24' 45" W --------------------------------------- |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-07-09 13:01:19
|
Please keep replies to the forum, not just to private e-mail... In my experience, even if Gentoo can't bring up it's network interface = the device is now at least 'connected' at the windows end, so it's = possible to configure it in all sorts of manners. There are btw. several ways to achieve networking connectivity without = using ICS; I don't use ICS myself either. regards, --Tim -----Original Message----- From: Mart=EDn Melado [mailto:mar...@mu...] Sent: vrijdag 9 juli 2004 15:00 To: Leeuw van der, Tim Subject: Re: [coLinux-users] coLinux and Gentoo LvdT> Look at the wiki-pages for networking-configuration... Er.. that's my problem. I can't enable ICS in Windows since coLinux doesn't activate its network device. --------------------------------------- Mart=EDn Melado - youk [en] mundo-r.com 43=BA 21' 11" N, 8=BA 24' 45" W --------------------------------------- |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-07-09 12:14:34
|
Hi,
Look at the wiki-pages for networking-configuration...
--Tim
-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Mart=EDn
Melado
Sent: vrijdag 9 juli 2004 14:08
To: col...@li...
Subject: [coLinux-users] coLinux and Gentoo
Hi,
I have installed coLinux 0.6.1 and downloaded the Gentoo Deluxe
image (gentoo-i586-ext3-2g-deluxe.bz2). When I run colinux-daemon,
Gentoo boots, but it shows this error:
* Bringing eth0 up...
* Failed to bring eth0 up =
[ !! ]
* ERROR: Problem starting needed services.
* "netmount" was not started.
* Starting vixie-cron... =
[ ok ]
* Starting local... =
[ ok ]
The network device of coLinux in Windows isn't working, so I guess
it's because Gentoo can't activate eth0.
What I'm doing wrong? This is my config:
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<colinux>
<block_device index=3D"0" =
path=3D"\DosDevices\c:\coLinux\gentoo-i586-ext3-2g-deluxe" =
enabled=3D"true" />
<block_device index=3D"1" path=3D"\DosDevices\c:\coLinux\swap_512Mb" =
enabled=3D"true" />
<bootparams>root=3D/dev/cobd0</bootparams>
<image path=3D"vmlinux" />
<memory size=3D"64" />
<network index=3D"0" type=3D"tap" />
</colinux>
Thanks :)
---------------------------------------
Mart=EDn Melado - youk [en] mundo-r.com
43=BA 21' 11" N, 8=BA 24' 45" W
---------------------------------------
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
digital self defense, top technical experts, no vendor pitches,=20
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users
|
|
From: <mar...@mu...> - 2004-07-09 12:05:57
|
Hi,
I have installed coLinux 0.6.1 and downloaded the Gentoo Delux=
e
image (gentoo-i586-ext3-2g-deluxe.bz2). When I run colinux-daemon=
,
Gentoo boots, but it shows this error:
* Bringing eth0 up...
* Failed to bring eth0 up =
[ !! ]
* ERROR: Problem starting needed services.
* "netmount" was not started.
* Starting vixie-cron... =
[ ok ]
* Starting local... =
[ ok ]
The network device of coLinux in Windows isn't working, so I gues=
s
it's because Gentoo can't activate eth0.
What I'm doing wrong? This is my config:
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<colinux>
<block_device index=3D"0" path=3D"\DosDevices\c:\coLinux\gentoo-i=
586-ext3-2g-deluxe" enabled=3D"true" />
<block_device index=3D"1" path=3D"\DosDevices\c:\coLinux\swap_512=
Mb" enabled=3D"true" />
<bootparams>root=3D/dev/cobd0</bootparams>
<image path=3D"vmlinux" />
<memory size=3D"64" />
<network index=3D"0" type=3D"tap" />
</colinux>
Thanks :)
---------------------------------------
Mart=EDn Melado - youk [en] mundo-r.com
43=BA 21' 11" N, 8=BA 24' 45" W
---------------------------------------
|
|
From: A. A. A. <alp...@tt...> - 2004-07-09 08:59:08
|
On Thu, Jul 08, 2004 at 08:17:20PM -0600, Ryan Krauss wrote: > I actually had a similar question and got my partitions to mount in > coLinux with the following lines in my config.xml: > > <block_device index="2" path="\Device\Harddisk0\Partition3" > enabled="true" /> > <block_device index="3" path="\Device\Harddisk0\Partition4" > enabled="true" /> > > For my dual boot system, Partition0 is the NTFS, Partition1 is the linux There is no Partition0, partition numbers start from 1 (as stated in wiki). The rule of thumb is to start numbering primary part.s, then logical and always skip extended in diskpart output. -- A. Alper ATICI OpenPGP key-id: 0xB824F550 fpr(S) = DFA9 6619 70C7 400C 1DA8 7BFB 2C56 F3AF B824 F550 |
|
From: Dembskey, E. (Evan) <Ev...@ne...> - 2004-07-09 06:26:54
|
Hi, Can someone put a copy of coLinux on a FTP server somewhere for me in .zip format? Our firewall blocks .exe and .gz, but not .zips. Regards, Evan ******************** This email and any accompanying attachments may contain confidential and proprietary information. This information is private and protected by law and, accordingly, if you are not the intended recipient, you are requested to delete this entire communication immediately and are notified that any disclosure, copying or distribution of or taking any action based on this information is prohibited. Emails cannot be guaranteed to be secure or free of errors or viruses. The sender does not accept any liability or responsibility for any interception, corruption, destruction, loss, late arrival or incompleteness of or tampering or interference with any of the information contained in this email or for its incorrect delivery or non-delivery for whatsoever reason or for its effect on any electronic device of the recipient. If verification of this email or any attachment is required, please request a hard-copy version. ******************** |
|
From: Ryan K. <rya...@co...> - 2004-07-09 02:17:31
|
I actually had a similar question and got my partitions to mount in coLinux with the following lines in my config.xml: <block_device index="2" path="\Device\Harddisk0\Partition3" enabled="true" /> <block_device index="3" path="\Device\Harddisk0\Partition4" enabled="true" /> For my dual boot system, Partition0 is the NTFS, Partition1 is the linux boot partition, Partition2 is a FAT32 partition, and Partition4 is the linux root. It took some messing around to figure out the partition numbers, but once I had them it worked like a charm. Ryan -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of David Smith Sent: Thursday, July 08, 2004 2:39 PM To: col...@li... Subject: Re: Fw: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro I actually got it to work by using \DosDevices\z: since evidently Windows recognized the drive (and I had given it a drive letter previously). That worked, and it mounted wondefully! Thank you! CoLinux r0x0rz! <quote who="Blake"> > Sourceforge didn't like the included .exe file. dmdiag can be found at > http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/dmdi ag-o.asp > > --Blake > pb...@ta... > ----- Original Message ----- > From: "Blake" <pb...@ta...> > To: "David Smith" <Dav...@by...> > Sent: Thursday, July 08, 2004 3:20 PM > Subject: Re: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > > >> Try >> >> <block_device >> index=N+2 >> path=\Device\HarddiskVolumeN >> enabled="true"> >> </block_device> >> >> N = 1 to 30 >> >> And try to access each cobd device in colinux in some way (mount is > probably >> the easiest way in this case). >> >> Or I found the Win2000 SDK utility "dmdiag" helpful. >> >> Or the Diskpart utility could help: >> >> diskpart >> >list disk >> >select disk N >> >list volume >> >list partition >> >> I've attached dmdiag.exe in case you can't find it on windows' site. >> >> --Blake >> pb...@ta... >> ----- Original Message ----- >> From: "David Smith" <Dav...@by...> >> To: <col...@li...> >> Sent: Thursday, July 08, 2004 10:02 AM >> Subject: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro >> >> >> > I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and > boots >> > extremely fast! Now I'm messing with my config.xml to try to get >> CoLinux >> > to mount my 120Gb IDE ext3-formatted drive. This is a separate drive > than >> > the one Windows XP is installed on, and it has a single ext3 >> partition. >> > According to the CoLinux docs, CoLinux relies on the host OS to >> provide >> > logical access to block devices. But if my host OS (Windows) doesn't >> > understand ext3, how can it provide logical access? Here's what I've > tried >> > to no avail in config.xml: >> > >> > <block_device index="1" >> > path="\Device\HarddiskVolume1" >> > enabled="true" /> >> > >> > <block_device index="1" >> > path="\Device\Harddisk1\Partition1" >> > enabled="true" /> >> > >> > <block_device index="1" >> > path="\Device\Harddisk1" >> > enabled="true" /> >> > >> > According to the Windows management console, my drive is "Disk 1", and > it >> > appears as "Healthy (Unknown Partition)". >> > >> > Can anyone shed any light on how I could get CoLinux to recognize my > ext3 >> > drive? >> > >> > --Dave ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Blake <pb...@ta...> - 2004-07-08 21:34:41
|
It's probably better to access it at a lower level of abstraction than "z:". Who knows how long that will stick? --Blake pb...@ta... ----- Original Message ----- From: "David Smith" <Dav...@by...> To: <col...@li...> Sent: Thursday, July 08, 2004 4:38 PM Subject: Re: Fw: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > I actually got it to work by using \DosDevices\z: since evidently Windows > recognized the drive (and I had given it a drive letter previously). That > worked, and it mounted wondefully! Thank you! CoLinux r0x0rz! > > <quote who="Blake"> > > Sourceforge didn't like the included .exe file. dmdiag can be found at > > http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/dmdiag-o.asp > > > > --Blake > > pb...@ta... > > ----- Original Message ----- > > From: "Blake" <pb...@ta...> > > To: "David Smith" <Dav...@by...> > > Sent: Thursday, July 08, 2004 3:20 PM > > Subject: Re: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > > > > > >> Try > >> > >> <block_device > >> index=N+2 > >> path=\Device\HarddiskVolumeN > >> enabled="true"> > >> </block_device> > >> > >> N = 1 to 30 > >> > >> And try to access each cobd device in colinux in some way (mount is > > probably > >> the easiest way in this case). > >> > >> Or I found the Win2000 SDK utility "dmdiag" helpful. > >> > >> Or the Diskpart utility could help: > >> > >> diskpart > >> >list disk > >> >select disk N > >> >list volume > >> >list partition > >> > >> I've attached dmdiag.exe in case you can't find it on windows' site. > >> > >> --Blake > >> pb...@ta... > >> ----- Original Message ----- > >> From: "David Smith" <Dav...@by...> > >> To: <col...@li...> > >> Sent: Thursday, July 08, 2004 10:02 AM > >> Subject: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > >> > >> > >> > I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and > > boots > >> > extremely fast! Now I'm messing with my config.xml to try to get > >> CoLinux > >> > to mount my 120Gb IDE ext3-formatted drive. This is a separate drive > > than > >> > the one Windows XP is installed on, and it has a single ext3 > >> partition. > >> > According to the CoLinux docs, CoLinux relies on the host OS to > >> provide > >> > logical access to block devices. But if my host OS (Windows) doesn't > >> > understand ext3, how can it provide logical access? Here's what I've > > tried > >> > to no avail in config.xml: > >> > > >> > <block_device index="1" > >> > path="\Device\HarddiskVolume1" > >> > enabled="true" /> > >> > > >> > <block_device index="1" > >> > path="\Device\Harddisk1\Partition1" > >> > enabled="true" /> > >> > > >> > <block_device index="1" > >> > path="\Device\Harddisk1" > >> > enabled="true" /> > >> > > >> > According to the Windows management console, my drive is "Disk 1", and > > it > >> > appears as "Healthy (Unknown Partition)". > >> > > >> > Can anyone shed any light on how I could get CoLinux to recognize my > > ext3 > >> > drive? > >> > > >> > --Dave > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: David S. <Dav...@by...> - 2004-07-08 20:39:35
|
I actually got it to work by using \DosDevices\z: since evidently Windows recognized the drive (and I had given it a drive letter previously). That worked, and it mounted wondefully! Thank you! CoLinux r0x0rz! <quote who="Blake"> > Sourceforge didn't like the included .exe file. dmdiag can be found at > http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/dmdiag-o.asp > > --Blake > pb...@ta... > ----- Original Message ----- > From: "Blake" <pb...@ta...> > To: "David Smith" <Dav...@by...> > Sent: Thursday, July 08, 2004 3:20 PM > Subject: Re: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > > >> Try >> >> <block_device >> index=N+2 >> path=\Device\HarddiskVolumeN >> enabled="true"> >> </block_device> >> >> N = 1 to 30 >> >> And try to access each cobd device in colinux in some way (mount is > probably >> the easiest way in this case). >> >> Or I found the Win2000 SDK utility "dmdiag" helpful. >> >> Or the Diskpart utility could help: >> >> diskpart >> >list disk >> >select disk N >> >list volume >> >list partition >> >> I've attached dmdiag.exe in case you can't find it on windows' site. >> >> --Blake >> pb...@ta... >> ----- Original Message ----- >> From: "David Smith" <Dav...@by...> >> To: <col...@li...> >> Sent: Thursday, July 08, 2004 10:02 AM >> Subject: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro >> >> >> > I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and > boots >> > extremely fast! Now I'm messing with my config.xml to try to get >> CoLinux >> > to mount my 120Gb IDE ext3-formatted drive. This is a separate drive > than >> > the one Windows XP is installed on, and it has a single ext3 >> partition. >> > According to the CoLinux docs, CoLinux relies on the host OS to >> provide >> > logical access to block devices. But if my host OS (Windows) doesn't >> > understand ext3, how can it provide logical access? Here's what I've > tried >> > to no avail in config.xml: >> > >> > <block_device index="1" >> > path="\Device\HarddiskVolume1" >> > enabled="true" /> >> > >> > <block_device index="1" >> > path="\Device\Harddisk1\Partition1" >> > enabled="true" /> >> > >> > <block_device index="1" >> > path="\Device\Harddisk1" >> > enabled="true" /> >> > >> > According to the Windows management console, my drive is "Disk 1", and > it >> > appears as "Healthy (Unknown Partition)". >> > >> > Can anyone shed any light on how I could get CoLinux to recognize my > ext3 >> > drive? >> > >> > --Dave |
|
From: Blake <pb...@ta...> - 2004-07-08 19:33:02
|
Sourceforge didn't like the included .exe file. dmdiag can be found at http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/dmdiag-o.asp --Blake pb...@ta... ----- Original Message ----- From: "Blake" <pb...@ta...> To: "David Smith" <Dav...@by...> Sent: Thursday, July 08, 2004 3:20 PM Subject: Re: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > Try > > <block_device > index=N+2 > path=\Device\HarddiskVolumeN > enabled="true"> > </block_device> > > N = 1 to 30 > > And try to access each cobd device in colinux in some way (mount is probably > the easiest way in this case). > > Or I found the Win2000 SDK utility "dmdiag" helpful. > > Or the Diskpart utility could help: > > diskpart > >list disk > >select disk N > >list volume > >list partition > > I've attached dmdiag.exe in case you can't find it on windows' site. > > --Blake > pb...@ta... > ----- Original Message ----- > From: "David Smith" <Dav...@by...> > To: <col...@li...> > Sent: Thursday, July 08, 2004 10:02 AM > Subject: [coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro > > > > I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and boots > > extremely fast! Now I'm messing with my config.xml to try to get CoLinux > > to mount my 120Gb IDE ext3-formatted drive. This is a separate drive than > > the one Windows XP is installed on, and it has a single ext3 partition. > > According to the CoLinux docs, CoLinux relies on the host OS to provide > > logical access to block devices. But if my host OS (Windows) doesn't > > understand ext3, how can it provide logical access? Here's what I've tried > > to no avail in config.xml: > > > > <block_device index="1" > > path="\Device\HarddiskVolume1" > > enabled="true" /> > > > > <block_device index="1" > > path="\Device\Harddisk1\Partition1" > > enabled="true" /> > > > > <block_device index="1" > > path="\Device\Harddisk1" > > enabled="true" /> > > > > According to the Windows management console, my drive is "Disk 1", and it > > appears as "Healthy (Unknown Partition)". > > > > Can anyone shed any light on how I could get CoLinux to recognize my ext3 > > drive? > > > > --Dave > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
119 messages has been excluded from this view by a project administrator.
