Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Dan A. <da...@co...> - 2004-04-06 21:37:08
|
On Tue, Apr 06, 2004 at 01:11:04PM -0500, Gregory M. Turner wrote: > Looks like I may have been wrong anyhow; the latest snapshots claim 2.6 > support; looking into it... I have to correct you; The latest snapshot can run *under* Linux 2.6.x as the host operating system, not *run* Linux 2.6.x as guest. -- Dan Aloni da...@co... |
|
From: Dan A. <da...@co...> - 2004-04-06 21:35:06
|
On Tue, Apr 06, 2004 at 07:41:20PM +0200, Jaroslaw Kowalski wrote: > Sorry about the "guest os" term. I think I know how colinux works. > > Question to Dan: do you plan to port colinux to 2.6? That port is just waiting to be done by either me or anyone who volunteer. -- Dan Aloni da...@co... |
|
From: Eric S. J. <es...@ha...> - 2004-04-06 21:17:06
|
I am very intrigued by cooperative Linux at and I would like to try it if I can have the same machine dual boot into Linux for Windows and if I am running on windows, run cooperative Linux off of the dual boot partition. it seems to me that in order to do this, you would need two kernels and the boot loaders would be configured to load either one or the other depending a context. I will admit that my original thought was to try and install gentoo on the system via a cooperative Linux installed base. From what I've learned so far, I would say it is possible but not advisable. in any case, the two OS/triple boot model is intriguing for variety of reasons and I'm wondering just how practical is it? ---eric |
|
From: gboutwel <gbo...@pr...> - 2004-04-06 20:59:56
|
Jarek, > Sorry about the "guest os" term. I think I know how colinux works. > > Question to Dan: do you plan to port colinux to 2.6? I'm looking into this (on the hopes that Dan can continue more productive work doing other things, and then improve on my initial patch, when I send it his way.) It doesn't appear to be easy (at least not for me). They changed the 'make system' around, and changed files/directories around a bit between the two versions. The current coLinux patch does not apply cleanly to an 2.6 (not that that's surprising), it has rejects, and even can't find files, etc. If someone beats me to the punch, please by all means send what you have this way. Thanks. George ---------------------------- Love to laugh? Good Clean Jokes at Praize http://www.praize.com/jokes/ |
|
From: Gregory M. T. <gmt...@am...> - 2004-04-06 18:11:12
|
Looks like I may have been wrong anyhow; the latest snapshots claim 2.6 support; looking into it... On Tuesday 06 April 2004 12:41 pm, Jaroslaw Kowalski wrote: > Sorry about the "guest os" term. I think I know how colinux works. > > Question to Dan: do you plan to port colinux to 2.6? > > Jarek > ----- Original Message ----- > From: "Gregory M. Turner" <gmt...@am...> > To: <col...@li...> > Cc: "Jaroslaw Kowalski" <ja...@zd...> > Sent: Tuesday, April 06, 2004 7:38 PM > Subject: Re: [coLinux-devel] 2.6 kernel ? > > > On Tuesday 06 April 2004 09:36 am, Jaroslaw Kowalski wrote: > > > Hi guys! > > > > > > Does coLinux support 2.6 kernel as a guest OS ? Is there a patch > > available > > > > for 2.6.5? I'd like to use NTPL and it seems non-obvious with 2.4 > > > kernels... > > > > > > Jarek > > > > Nope -- colinux is not an emulator like VMWare, but (in part), a linux > > kernel > > > that has been modified to run under Windows (and now Linux) using some > > "trickery" analagous to User-Mode Linux. That's why it's faster than > > VMWare > > > -- look Ma, no emulation! The upshot is: to achieve this, one has to > > port the coLinux kernel patch forward to 2.6. Presumably this is > > nontrivial, > > or > > > Dan would have done it already. > > > > -- > > gmt > > ------------------------------------------------------- > 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 -- gmt |
|
From: Robert P. <rob...@ho...> - 2004-04-06 18:07:16
|
Hi all Just an update. I downloaded and built "pump" in FC1 in coLinux. With pump, I can now set up FC1 to talk DHCP. It looks like the kernel that comes with 0.6.0 either wasn't compiled with packet filtering that dhclient needs (dhclient is what FC1 uses for DHCP), or there is a bug somewhere. Thanks. Rob ----- Original Message ----- From: "Robert Pang" <rob...@ho...> To: <col...@li...> Sent: Monday, April 05, 2004 11:05 AM Subject: Two networking issues > Hi folks, > > coLinux is great. I am able to set up and run Fedora Core 1 with the 0.6.0 > build on Windows 2000. However, I run into 2 issues. > > First, I cannot use DHCP with FC1. I get the same error as described in > http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no pump > binary package for FC1, I haven't tried pump to see if will resolve the > issue. FC1 uses dhclient for DHCP and I am not sure how to set it up to use pump. |
|
From: Jaroslaw K. <ja...@zd...> - 2004-04-06 17:41:28
|
Sorry about the "guest os" term. I think I know how colinux works. Question to Dan: do you plan to port colinux to 2.6? Jarek ----- Original Message ----- From: "Gregory M. Turner" <gmt...@am...> To: <col...@li...> Cc: "Jaroslaw Kowalski" <ja...@zd...> Sent: Tuesday, April 06, 2004 7:38 PM Subject: Re: [coLinux-devel] 2.6 kernel ? > On Tuesday 06 April 2004 09:36 am, Jaroslaw Kowalski wrote: > > Hi guys! > > > > Does coLinux support 2.6 kernel as a guest OS ? Is there a patch available > > for 2.6.5? I'd like to use NTPL and it seems non-obvious with 2.4 > > kernels... > > > > Jarek > > Nope -- colinux is not an emulator like VMWare, but (in part), a linux kernel > that has been modified to run under Windows (and now Linux) using some > "trickery" analagous to User-Mode Linux. That's why it's faster than VMWare > -- look Ma, no emulation! The upshot is: to achieve this, one has to port > the coLinux kernel patch forward to 2.6. Presumably this is nontrivial, or > Dan would have done it already. > > -- > gmt > |
|
From: Gregory M. T. <gmt...@am...> - 2004-04-06 17:39:03
|
On Tuesday 06 April 2004 09:36 am, Jaroslaw Kowalski wrote: > Hi guys! > > Does coLinux support 2.6 kernel as a guest OS ? Is there a patch available > for 2.6.5? I'd like to use NTPL and it seems non-obvious with 2.4 > kernels... > > Jarek Nope -- colinux is not an emulator like VMWare, but (in part), a linux kernel that has been modified to run under Windows (and now Linux) using some "trickery" analagous to User-Mode Linux. That's why it's faster than VMWare -- look Ma, no emulation! The upshot is: to achieve this, one has to port the coLinux kernel patch forward to 2.6. Presumably this is nontrivial, or Dan would have done it already. -- gmt |
|
From: Jaroslaw K. <ja...@zd...> - 2004-04-06 17:36:08
|
It "works-for-me(tm)" on Windows 2003 Enterprise Edition. Perhaps there's
some difference between the two systems. I'll investigate it and provide
more-debuggish version of coLinuxService so that you can test it.
Jarek
----- Original Message -----
From: <ch...@to...>
To: <ch...@to...>
Cc: "Jaroslaw Kowalski" <ja...@zd...>;
<col...@li...>
Sent: Tuesday, April 06, 2004 5:16 PM
Subject: Re: [coLinux-devel] ANN: CoLinuxService v0.1 released
> I did some testing yesterday for 2 below I added a
> date >> colog
> to the shutdown_colinux script to see if it was running when shutting down
> windows. It was not run. I double checked that the colog was generated
> when doing a
> net stop colinux
> it was.
>
> I was thinking could coLinuxService.exe attach itself as a console and
> then just send the scan codes for the three finger salute. Most inittab
> files that I have seen are set to do a clean shutdown with this and you do
> not have to be loged in at that console. It works when the login prompt is
> up.
>
>
> chris
>
>
> > 2 bugs I found
> >
> > 1) Not really a bug but when using telnet to test the shutdown linux
> > configuration the telnet that comes with windows 2k sends cr/lf the read
> > statement in the script leaves the cr as part of $REPLY . I was able to
> > filter this off with
> > if [ ${REPLY:0:6} = 'KILLME' ]; then
> > and this still works fine when using it. The 6 would need to be changed
> > for a different length password
> >
> >
> > 2) I am not getting clean shutdowns when shuting down windows while
> > service is running both when starting the service manualy or
automaticly.
> > net stop colinux
> > works great. I'm not shure if the problem is that windows is not waiting
> > till the service gives the ok or if the message is not getting sent.
(It's
> > just fscking due to unclean shutdown) I could do further tests to see on
> > monday or tuesday if you can not reproduce this.
> > I'm using an up to date win2k
> >
> > chris
> >
> >
> >> I'm proud to announce that CoLinuxService v0.1 has been released.
> >>
> >> It allows you to run colinux as a Windows service and supports clean
> >> shutdown procedure with elementary authentication.
> >
> >> Any feedback is welcome. Feel free to send patches and I'll include
them
> >> in
> >> future versions.
> >>
> >> 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
> >
>
|
|
From: gboutwel <gbo...@pr...> - 2004-04-06 16:02:42
|
tf...@no... wrote: > I also added support to build the bridged net daemon (really a > hack ;-( )and to collect the build binary-files in a 'binary' directory. :). I like that. :) > My current problem is that I don't have a windows box here to verify > if the compiled bin's actually work. Can someone check this out? > > If this is verified I would like to upload cobuild.sh to the wiki-page > to document the build process. Not a problem at all. I'll give this a try and let you konw if the resulting binraries work. George ------------------------------------------ Praize? The all-in-one Christian Community http://www.praize.com/ |
|
From: <ch...@to...> - 2004-04-06 15:19:55
|
Would it be possible to add a send ctrl alt delete to the Monitor menu of the fltk console? I noticed that terminate is a dirty shutdown. Most distro's have a ctrl alt delete handler in inittab. chris |
|
From: <ch...@to...> - 2004-04-06 15:16:11
|
I did some testing yesterday for 2 below I added a
date >> colog
to the shutdown_colinux script to see if it was running when shutting down
windows. It was not run. I double checked that the colog was generated
when doing a
net stop colinux
it was.
I was thinking could coLinuxService.exe attach itself as a console and
then just send the scan codes for the three finger salute. Most inittab
files that I have seen are set to do a clean shutdown with this and you do
not have to be loged in at that console. It works when the login prompt is
up.
chris
> 2 bugs I found
>
> 1) Not really a bug but when using telnet to test the shutdown linux
> configuration the telnet that comes with windows 2k sends cr/lf the read
> statement in the script leaves the cr as part of $REPLY . I was able to
> filter this off with
> if [ ${REPLY:0:6} = 'KILLME' ]; then
> and this still works fine when using it. The 6 would need to be changed
> for a different length password
>
>
> 2) I am not getting clean shutdowns when shuting down windows while
> service is running both when starting the service manualy or automaticly.
> net stop colinux
> works great. I'm not shure if the problem is that windows is not waiting
> till the service gives the ok or if the message is not getting sent. (It's
> just fscking due to unclean shutdown) I could do further tests to see on
> monday or tuesday if you can not reproduce this.
> I'm using an up to date win2k
>
> chris
>
>
>> I'm proud to announce that CoLinuxService v0.1 has been released.
>>
>> It allows you to run colinux as a Windows service and supports clean
>> shutdown procedure with elementary authentication.
>
>> Any feedback is welcome. Feel free to send patches and I'll include them
>> in
>> future versions.
>>
>> 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
>
|
|
From: <ch...@to...> - 2004-04-06 15:04:33
|
you can start the colinux daemon with a -c to use a config file other than the default. colinux-daemon.exe -c c:\colinux\other.colinux.xml you can create a .bat file for each config file. as far as I know -c is undocumented so I'll go add it to the wiki faq chris > > It would be nice if this tool would have an option to be simular to a > 'bootloader' (lilo eg) too - so it creates XML files and gives an option > to "boot" coLinux based on a dynamic/statically created XML, this would > enable to start with different kernels and network/disk configs from > within ONE cL folder. > > |
|
From: Jaroslaw K. <ja...@zd...> - 2004-04-06 14:36:13
|
Hi guys! Does coLinux support 2.6 kernel as a guest OS ? Is there a patch = available for 2.6.5? I'd like to use NTPL and it seems non-obvious with = 2.4 kernels... Jarek |
|
From: Bart K. <Bar...@su...> - 2004-04-06 14:27:39
|
Digital Infra, Inc. wrote: > Umm.. Nobody wants to do it? Okay, It is easy. I will do it. It would be nice if this tool would have an option to be simular to a 'bootloader' (lilo eg) too - so it creates XML files and gives an option to "boot" coLinux based on a dynamic/statically created XML, this would enable to start with different kernels and network/disk configs from within ONE cL folder. Bart >>Would anyone like to volunteer and create a GUI-based .colinux.xml >>generator/editor ? It could help new users of coLinux and It doesn't >>require any kernel programming experience in order to be developed. >> >>I'd prefer if you use the FLTK toolkit. We can later merge it into >>the FLTK console so it would appear more like VMware from the aspect >>of editing the currently used configuration. >> >>I'd also thank anyone who can send a patch for the colinux.nsi script >>that points the users to the rootfs image download location and >>Wiki site. |
|
From: Dan A. <da...@co...> - 2004-04-06 14:06:41
|
On Tue, Apr 06, 2004 at 09:45:49AM -0400, Ian C. Blenke wrote: > On Tue, Apr 06, 2004 at 12:22:56AM +0200, Dan Aloni wrote: > > On Mon, Apr 05, 2004 at 01:11:39PM -0700, Eyal Lotem wrote: > > > > > I think the reason may be that Windows is using the > > > disks better and making access faster. Perhaps DMA > > > acceleration or some other feature is turned off on > > > the Linux host side, making disk access slower on the > > > Linux side. > > > > No Windows was involved with these benchmarks in any way. I ran > > coLinux on Linux. > > You ran coLinux on a Linux host? Perhaps I've missed something on the list.. > is there a native Linux kernel port now? An alternative to User Mode Linux > is a rather big thing for me. Yes, it's an alternative to User Mode Linux, thought it's a bit early and doesn't have all the wide range of support tools and nifty stuff that UML has. -- Dan Aloni da...@co... |
|
From: Ian C. B. <ia...@bl...> - 2004-04-06 13:46:09
|
On Tue, Apr 06, 2004 at 12:22:56AM +0200, Dan Aloni wrote: > On Mon, Apr 05, 2004 at 01:11:39PM -0700, Eyal Lotem wrote: > > > I think the reason may be that Windows is using the > > disks better and making access faster. Perhaps DMA > > acceleration or some other feature is turned off on > > the Linux host side, making disk access slower on the > > Linux side. > > No Windows was involved with these benchmarks in any way. I ran > coLinux on Linux. You ran coLinux on a Linux host? Perhaps I've missed something on the list.. is there a native Linux kernel port now? An alternative to User Mode Linux is a rather big thing for me. - Ian C. Blenke <ia...@bl...> |
|
From: Dan A. <da...@co...> - 2004-04-06 13:24:48
|
On Tue, Apr 06, 2004 at 01:02:55AM -0000, Thomas Fritzsche wrote: > The simplest way would we if Dan could include the patches in colinux or > upload them to the colinux-homepage. All patches necessary to build coLinux should be in the source tarball patch/ directory. I have no problem to have the cobuild.sh script depend on the patches in that directory. In fact, I've already started maintaining the patches there, starting from the next snapshot. % ls -l total 148 -rw-r--r-- 1 karrde karrde 1043 Apr 4 10:58 fltk-1.1.4-linux-patch.diff -rw-r--r-- 1 karrde karrde 14274 Apr 4 11:01 fltk-1.1.4-winnt.patch.diff -rw-r--r-- 1 karrde karrde 123673 Apr 6 15:21 linux > If this is verified I would like to upload cobuild.sh to the wiki-page to > document the build process. No need to upload files to the Wiki, just send me a patch. -- Dan Aloni da...@co... |
|
From: Dan A. <da...@co...> - 2004-04-06 13:15:44
|
Hello all, Many of you who noticed that for cobd* devices which are mapped to raw partitions or CDROMs, the reported size is 0. Well, turns out that the Windows ZwQueryInformationFile function wasn't behaving as you might expect. Anyway, I got this fixed today, so expect the next snapshot to include this fix. No need to patch resierfs anymore. I also changed cobd so that mounts and opens of these block devices invalidate the caches, so if the media is replaced, no corruption occurs. -- Dan Aloni da...@co... |
|
From: Thomas F. <tf...@no...> - 2004-04-06 01:00:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi gboutwel, thanks for updating cobuild.sh! I used you prev. patch and uploaded the w32api patch to my web-page so it's not neccessary to include this in the build script. Looks like your patch works without problems, just a few fuzzy searchs because you applied the old gcc patch to a new gcc version, but the compiler runs through. The simplest way would we if Dan could include the patches in colinux or upload them to the colinux-homepage. I also added support to build the bridged net daemon (really a hack ;-( )and to collect the build binary-files in a 'binary' directory. My current problem is that I don't have a windows box here to verify if the compiled bin's actually work. Can someone check this out? If this is verified I would like to upload cobuild.sh to the wiki-page to document the build process. Thanks and regards, Thomas > Updated per comments to include the w32api.diff file in the patch > itself. In addition I did some clean-up this time that I didn't > do last time. Removing any commented out old stuff that might > have been left in there, etc. > > > > See attached file. > > > > -------------------------------- > > Looking for that favorite verse? > > Search for it in Praize Bible > > http://www.praize.com/bible/ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAcgG+nwJBIFTVIqwRAg4zAJ4zK2PZ15GhTSIeyagh7q8DX5rMDgCgvPNb gcRTjYkYEmtUzjRE/y3olrw= =SgnZ -----END PGP SIGNATURE----- |
|
From: Steven E. <ste...@ya...> - 2004-04-05 23:22:02
|
Hello All, If you want to run Linux and have your Windows device drivers then this message is for you. I just wanted to give all of you a update on our work to get CoLinux working on ReactOS. Where it stands right now it looks like ReactOS will be able to run CoLinux quite soon. We still have some issues with running Cygwin applications so we need some help either fixing that or we need to see if the CoLinux deamon can be built linking to msvcrt rather than cygwin. Other than this the only show stopper we have atm is our TCP/IP stack is still under heavy development and will not be ready to run the Xserver and Linux network applications for another few months. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Robert P. <rob...@ho...> - 2004-04-05 23:21:30
|
Thanks. I downloaded your vmlinux binary and tried it twice and each time result in an adrupt reboot of W2k (not even a blue screen). I have reverted to the old kernel for now. Thanks. Rob ----- Original Message ----- From: "Alejandro R. Sedeno" <as...@MI...> To: "Robert Pang" <rob...@ho...> Cc: <col...@li...> Sent: Monday, April 05, 2004 1:24 PM Subject: [coLinux-devel] Re: Two networking issues > You shouldn't need to turn off the Rx checksum offloading, just Tx, but > it probably won't hurt to have it off. > > I built a new 2.4.25 kernel using the 0.6.0 config file + socket > filtering. If you want to try it and see if that fixes dhcp, it's > available at: > > http://web.mit.edu/asedeno/www/coLinux/my_0.6.0_kernel > > Be sure to keep your old kernel around just in case. > > -Alejandro > > On Mon, 2004-04-05 at 15:11, Robert Pang wrote: > > Alejandro > > > > Yes. That's it. My NIC have "Rx Checksum Offload" and "Tx Checksum Offload" > > options. After disabling them, I am able to TCP to and from my W2k host with > > coLinux. I still get dup ping replies though. Not sure if it matters or not. > > > > As for the kernel, I am just using the kernel that comes with 0.6.0 install. > > Don't know if it is compiled with packet filtering or not. It looks like it > > takes quite a bit of effort to setup the env to build coLinux and I doubt if > > I have the bandwidth to try building the kernel myself. > > > > Thanks for your help in any case. > > > > Rob > > > > ----- Original Message ----- > > From: "Alejandro R. Sedeno" <as...@MI...> > > To: "Robert Pang" <rob...@ho...> > > Cc: <col...@li...> > > Sent: Monday, April 05, 2004 11:36 AM > > Subject: Re: [coLinux-devel] Two networking issues > > > > > > > With the caveat that I've not used your particular NIC, nor have I used > > > Fedora: > > > > > > DHCP - Does your kernel have Socket Filtering? I'm not sure if this is > > > compiled into the coLinux kernel yet, but it caused some issues with > > > dhcp for me. > > > > > > As far as host<->coLinux communications, I recently had issues with an > > > integrated network card that offloaded TCP and IP checksums to the NIC. > > > Check the NIC's configuration from the device manager and look under > > > advanced to see if there are any options resembling "Offload Transmit IP > > > Checksum". Disable checksum offloading for transmit on both TCP and IP > > > if the options are there. > > > > > > Good luck! > > > > > > -Alejandro > > > > > > > > > On Mon, 2004-04-05 at 14:05, Robert Pang wrote: > > > > Hi folks, > > > > > > > > coLinux is great. I am able to set up and run Fedora Core 1 with the > > 0.6.0 > > > > build on Windows 2000. However, I run into 2 issues. > > > > > > > > First, I cannot use DHCP with FC1. I get the same error as described in > > > > http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no > > pump > > > > binary package for FC1, I haven't tried pump to see if will resolve the > > > > issue. FC1 uses dhclient for DHCP and I am not how to set it up to use > > pump. > > > > > > > > Second, using static IP, I cannot make a TCP connection from the W2k > > host to > > > > coLinux or vice versa. ping works but I got duplicate replies if I ping > > the > > > > W2k host (rpang-pc2) from coLinux: > > > > > > > > [rpang@colinux rpang]$ ping rpang-pc2 > > > > PING rpang-pc2 (130.35.168.159) 56(84) bytes of data. > > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=4.96 > > ms > > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=6.25 > > ms > > > > (DUP!) > > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.11 > > ms > > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.91 > > ms > > > > (DUP!) > > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.13 > > ms > > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.72 > > ms > > > > (DUP!) > > > > .. > > > > > > > > ping from W2k to coLinux seems to be okay though: > > > > > > > > C:\Documents and Settings\rpang>ping lvbcheng-pc > > > > > > > > Pinging lvbcheng-pc.us.oracle.com [130.35.168.148] with 32 bytes of > > data: > > > > > > > > Reply from 130.35.168.148: bytes=32 time=30ms TTL=64 > > > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > > Reply from 130.35.168.148: bytes=32 time<10ms TTL=64 > > > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > > > > > > Ping statistics for 130.35.168.148: > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > > > Approximate round trip times in milli-seconds: > > > > Minimum = 0ms, Maximum = 30ms, Average = 12ms > > > > > > > > Because of this problem, I cannot make X connection from coLinux to my > > > > cygwin/XFree86 running on my W2k host. Neither can I ssh from my W2k > > host > > > > back to coLinux. TCP connection to and from another machine on the > > network > > > > with coLinux is fine though. > > > > > > > > Here is my coLinux network setup: > > > > > > > > [rpang@colinux rpang]# ifconfig > > > > eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > > > > inet addr:130.35.168.148 Bcast:130.35.171.255 > > Mask:255.255.252.0 > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > RX packets:1523574 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:4726 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > RX bytes:104822082 (99.9 Mb) TX bytes:3234903 (3.0 Mb) > > > > Interrupt:2 > > > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:0 > > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > > > My W2k network setup: > > > > > > > > Windows 2000 IP Configuration > > > > > > > > Host Name . . . . . . . . . . . . : rpang-pc2 > > > > Node Type . . . . . . . . . . . . : Hybrid > > > > IP Routing Enabled. . . . . . . . : No > > > > WINS Proxy Enabled. . . . . . . . : No > > > > > > > > Ethernet adapter Local Area Connection: > > > > > > > > Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast > > > > Ethernet > > > > Controller (3C905B-TX Compatible) > > > > Physical Address. . . . . . . . . : 00-C0-4F-5E-C2-DA > > > > DHCP Enabled. . . . . . . . . . . : No > > > > IP Address. . . . . . . . . . . . : 130.35.168.159 > > > > Subnet Mask . . . . . . . . . . . : 255.255.252.0 > > > > Default Gateway . . . . . . . . . : 130.35.168.1 > > > > DNS Servers . . . . . . . . . . . : 130.35.249.41 > > > > 138.2.202.15 > > > > Primary WINS Server . . . . . . . : 138.2.202.14 > > > > Secondary WINS Server . . . . . . : 130.35.62.34 > > > > > > > > And my default.colinux.xml: > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > <colinux> > > > > <block_device index="0" path="\DosDevices\e:\fedora_root" > > > > enabled="true"> > > > > </block_device> > > > > <block_device index="1" path="\DosDevices\e:\colinux_swap" > > > > enabled="true"> > > > > </block_device> > > > > <bootparams>ro root=/dev/cobd0</bootparams> > > > > <image path="vmlinux"></image> > > > > <memory size="64"></memory> > > > > <network index="0" type="bridged" name="3Com 3C918 Integrated Fast > > > > Ethernet Controller (3C905B-TX Compatible)"></network> > > > > </colinux> > > > > > > > > BTW, I am using the bridged network. I failed to setup NAT with W2k ICS. > > > > Enabling W2k ICS always results with an error. It turns out that ICS > > uses > > > > DHCP implicitly and there is another DHCP server running in my network > > so > > > > ICS cannot be used (see the first common problem under > > > > http://is-it-true.org/nt/nt2000/utips/utips11.shtml). > > > > > > > > Any take on these two issues? > > > > > > > > Thanks. > > > > > > > > Rob > > > > > > > > > > > > ------------------------------------------------------- > > > > 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 > > > > > > > > > > > > > > > > ------------------------------------------------------- > 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 > |
|
From: Dan A. <da...@co...> - 2004-04-05 22:34:25
|
On Mon, Apr 05, 2004 at 01:11:39PM -0700, Eyal Lotem wrote: > I think the reason may be that Windows is using the > disks better and making access faster. Perhaps DMA > acceleration or some other feature is turned off on > the Linux host side, making disk access slower on the > Linux side. No Windows was involved with these benchmarks in any way. I ran coLinux on Linux. -- Dan Aloni da...@co... |
|
From: keksov <ke...@gm...> - 2004-04-05 21:03:30
|
Hi, try to use hdparam under "real" Linux to tune HDD performance. Something like hdparam -X66 -d1 -u1 -m16 -c3 /dev/hda First run hdparam /dev/hda, may be it's already tweaked. Use hdparam -tT /dev/hda for roughly testing disk's I/O. Be warned! hdparam may... well, crash your system... Switch to single user mode first and put right string into rc.d/* after all. Sure, don't forget to man hdparam ;) Regards, Dim |
|
From: Jeff W. <Kaz...@ce...> - 2004-04-05 20:53:17
|
>I think the reason may be that Windows is using the disks better and >making access faster. Perhaps DMA acceleration or some other feature is >turned off on the Linux host side, making disk access slower on the Linux side. What does Windows have to do with it? He's running Linux on Linux. -- Jeff Woods <kaz...@ce...> |
81 messages has been excluded from this view by a project administrator.
