colinux-users — coLinux users mailing list

Re: [coLinux-users] colinux 0.6.2 with pcap (snapshot coLinux-20040710)

[Andreas B. <and...@gm...>]

> If I understand your situation correcly, It would seem that the
> partial naming is playing a role here.  It's finding the TAP
> adatper, which is named Local Area  Connection 2, first as it's
> the one it encounters first, and since what you specified partially
> matches it chooses it, before it hits the Local Area Connection
> and sees it.  I suppose we could change the logic to go through
> all partial matches, then go through them again to find one that
> matches exactly, and if one doesn't go with the first one.  
> But You're best bet is to name them something less simliar. 
> I use Local Araa Connection for my REAL NIC, and Virtual Connection
> for the TAP that I have.  That seems to work fine.


Thank you for the answer George. 

I changed the adapters name from "Local Area Connection 2" to something else
and tried to start colinux 0.6.2, well after I hit enter I got the blue
sceen with STOP 0x1111777A and the hard disk and all data has gone :-( I
don't know if this is happened by mischange. I have to wait for a new disk
maybe after that I try again, but I am unsure, it is my office laptop and if
it really would happen a second time I'll get some troubles.

Andreas

-- 
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl

[coLinux-users] Re: Routing problem to coLinux from other computers

[John F. <J.P...@as...>]

I have done some more testing on my routing problem.

The solution on Windows XP has been to swap from Internet 
Connection Sharing to using the Windows XP bridging.

When that is installed and the appropriate settings made for the 
external network, the coLinux "computer" is seen as part of the 
external network.

This means that the IP settings for eth0 in the colinux change to 
those needed for the external network.

e.g. in my case where the external network is 192.168.123.x then 
192.168.123.40 is a valid choice for the colinux.

I had become confused as I had not realised that there are two 
distinct ways of organising what is referred to as "Native Bridging" 
on the wiki page

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

(a) Native bridging using type="bridged" in the colinux 
configuration.
(b) Native bridging using type="tap" in the colinux configuration and 
then using a Windows XP bridge.

When I have set up type (b) and changed the IP number, I have 
been able to access the colinux using both Samba and VNC from 
the second computer on my network, which is what I wanted to do.

Thank you for providing such a useful tool.

Best wishes

John Fletcher


-------------------------------------------------------------------
Dr John P. Fletcher          Tel: (44) 121 359 3611 ext 4625
Chemical Engineering and Applied Chemistry (CEAC),
School of Engineering and Applied Science (SEAS),
Aston University,            Fax: (44) 121 359 4094
Aston Triangle,              Email: J.P...@as...
BIRMINGHAM B4 7ET  U.K.      CEAC Web site 
http://www.ceac.aston.ac.uk/

Re: [coLinux-users] Re: using 2.6 kernels, moving to latest coLinux snapshot, etc.

[gboutwel <gbo...@pr...>]

> (This seems to be the kernel 2.6 replacement for the modutils

> package which is for kernel 2.4. The new Gentoo package

> includes the old modutils so that if module-init-tools is

> installed, then both 2.4 and 2.6 kernels can be used.)



Yes, Exactly.  As I understand it they moved more of the logic
from the Kernel to the userland tools (module-init-tools) code
which made features like versioning and stuff much easier.





> * observe that Firefox dies with a floating point exception:

> I have put the trace output at

>

> http://www.macs.hw.ac.uk/~jbw/firefox-death.trace

> 

> in case it can help anyone figure this out.



  This is interesting cause of the changes made was to make it
so that it passed the fops20 tests, and The Linux Kernel Test
project, also, gives the chagnes passes on the floating point
stuff.



  I'm sorry, but I'm no good with ltrace/strace outputs.  I do
better with gdb's bt back traces.  If you feel like it can you
get an bt of the FPE?  Maybe Dan or someone else can make sense
of the trace and point use in the right direction.



George





What could have changed to cause floating point exceptions? I
checked

that my configuration files could not be causing the problem
by

temporarily moving them out of the way. Is this a Linux kernel
2.6

change or a coLinux change? Any thoughts or suggestions? What

information is needed to debug this?





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

Looking for Great Christian Shopping Ideas?

http://www.praize.com/shopping/

Re: [coLinux-users] colinux 0.6.2 with pcap (snapshot coLinux-20040710)

[gboutwel <gbo...@pr...>]

> "Changed PCAP handling to use Connection Name instead of

> Adapter/Device/Driver name. Name is +now uniform between PCAP
& TAP and

> multiple devices of the same/make/model should be able to be
connected to.

> (George Boutwell)"



> What excatly does that mean for my bridged network configuration?



It means that you don't need to use your Adapter/Driver name,
but the Connection Name as you see it in the Network Connection
Screen to Select which NIC is bound by the bridged network.





> It seams PCAP needs "Local Area Connection", so I tried with



Yes, if Local Area Connection is your NIC that you want PCAP
bound too.  However, It does an 'partial' search so you need
to specify enough to identify it UNIQUELY from any other like
named Connection.





> : Looking for interface "Local Area Connection"

> : Adapter Generic NdisWan adapter doesn't have a connection

> : Checking connection: Local Area Connection 2

> Listening on: tap0801co15 TAP-Win32 Adapter V8 (coLinux)...

> Listening for: (ether dst 00:43:4f:4e:45:30) or (ether broadcast
or

> multicast) or (ip broadcast or multicast)



> Well, as I understand the console, the used interface is "tap0801co15

> TAP-Win32 Adapter V8 (coLinux)" and not "Local Area Connection",
I even got

> an MAC-Address but unfortunately eth0 doesn't work.



> What do I miss?



If I understand your situation correcly, It would seem that the
partial naming is playing a role here.  It's finding the TAP
adatper, which is named Local Area  Connection 2, first as it's
the one it encounters first, and since what you specified partially
matches it chooses it, before it hits the Local Area Connection
and sees it.  I suppose we could change the logic to go through
all partial matches, then go through them again to find one that
matches exactly, and if one doesn't go with the first one.  
But You're best bet is to name them something less simliar. 
I use Local Araa Connection for my REAL NIC, and Virtual Connection
for the TAP that I have.  That seems to work fine.



HTH,



George





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

Looking for Great Christian Shopping Ideas?

http://www.praize.com/shopping/

Re: [coLinux-users] NFS performance and colinux

[gboutwel <gbo...@pr...>]

> I am using colinux 0.6.1 over kernel 2.4.26. The original distribution
=



Only advice I can give is to try the more recent snapshots. 
Especially the 20040710 snapshot.  It will involve and upgrade
to an 2.6 kernel and all that that may entail for the distro
of your your choice.  It probalby take rebulding the kernel with
NFS settings, but it might not.  But network performance has
been something that has been worked and has gotten comments about
it betting better in recent snapshots.



> If somebody has an idea why the NFS service is so slow, please,
do not =

> hesitate to contact me.



If after trying the recent snapshots, you still have problems
we can perhaps look at them to see fi there is more we can do.
 Additionally, If you find that we could enable something more
in the kernels for recent snapshots to make NFS support better,
let us know.



George



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

Love to laugh?

Good Clean Jokes at Praize

http://www.praize.com/jokes/

[coLinux-users] internet sharing problem

[Manuel M. <mar...@ea...>]

Im using the latest build of colinux. on a windows 2k box. I have downloaded and followed the installation process step by step. The only problem I have at this moment is, Internet sharing. every time I try to share the network location, my system crashes and a blue screen come up. Something about module cannot handle an exception. I cant get the full error because it just flashes and the system reboots it self. anybody please help!

[coLinux-users] NFS performance and colinux

[Claude L. (QB/EMC) <cla...@er...>]

Hi,
=20
I am currently trying to build a Solaris jumpstart server using =
colinux. This Linux based jumpstart version already works fine in =
native Linux solutions. The Solaris jumpstart service requires RARP, =
bootparamd, TFTP and NFS services. All those services behave perfectly =
under colinux but the NFS service exhibits an important performance =
problem. The NFS service seems to be a way too slow compared to the =
native solution. The other services run at a very acceptable =
performance. It is diificult for me to measure this problem but using =
the native solution, NFS roughly speeds up at 1000 to 1500 =
packets/second (maybe more) while colinux show a maximum of 10 =
packets/second.
=20
I am using colinux 0.6.1 over kernel 2.4.26. The original distribution =
does not offer the NFS kernel side server. So, I have recompiled the =
vanilla 2.4.26 kernel with the required options to run nfsd from =
colinux. I have simply updated the modules in my Fedora Core 1 =
"virtual" machine and I got the NFS service working fine. I am using =
Windows 2000 SP4 and bridged networking.
=20
If somebody has an idea why the NFS service is so slow, please, do not =
hesitate to contact me.
=20
Thanks,
=20
Claude.

Claude LeFran=E7ois=20
cla...@er... <mailto:cla...@er...>=20

[coLinux-users] Re: Routing problem to coLinux from other computers

[John F. <J.P...@as...>]

To:             	col...@li...
From:           	baldyeti <e_...@ho...>
Organization:   	-
Subject:        	[coLinux-users] Re: Routing problem to coLinux from other computers
Date sent:      	Fri, 13 Aug 2004 17:48:27 +0200

> I'd guess whatever targets anything but 192.168.123.x is
> sent by the win95 box to the gateway. So it's the gateway
> which needs to be told that traffic to 192.168.1.x needs
> to go to the win2k machine. Check your gateway manual on
> how to add a route there. Alternatively, win95 might have
> a route.exe or equivalent command, with which you could
> override the default gateway for a particular IP range.
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save
> 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________ coLinux-users mailing
> list coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

I've done "route print" on the Win95 and even done a "route add" 
on it using examples from 

"Practical TCP/IP" Niall Mansfield.

I am wondering if I am wrong to use ICS at all.  Should I be using 
coLinux bridge instead of TAP?  If so, should I use WinXP's bridge 
as well?

One of the problems is that there is very little I can find on how to 
access RRAS and NAT on the WInXP box.

Thanks

John

-------------------------------------------------------------------
Dr John P. Fletcher          Tel: (44) 121 359 3611 ext 4625
Chemical Engineering and Applied Chemistry (CEAC),
School of Engineering and Applied Science (SEAS),
Aston University,            Fax: (44) 121 359 4094
Aston Triangle,              Email: J.P...@as...
BIRMINGHAM B4 7ET  U.K.      CEAC Web site 
http://www.ceac.aston.ac.uk/

[coLinux-users] Re: Routing problem to coLinux from other computers

[baldyeti <e_...@ho...>]

I'd guess whatever targets anything but 192.168.123.x is
sent by the win95 box to the gateway. So it's the gateway
which needs to be told that traffic to 192.168.1.x needs
to go to the win2k machine. Check your gateway manual on
how to add a route there. Alternatively, win95 might have
a route.exe or equivalent command, with which you could
override the default gateway for a particular IP range.

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[gboutwel <gbo...@pr...>]

> Oh, sorry, coLinux-0.6.2-gpb.tar.bz2 on this server contains
Windows

> EXE-files!

> Because this archive have no installer, you need an installed
version,

> before copy new executable files over an installed version.



Not really.  The only thing I didn't include in the aboe coLinux
archive is the TAP driver.  If he doesn't need the TAP driver,
then the contains everything he'd need to run colinux, except
the images and the configuration file.



> > The remove option must not run from old executable,



> I thought the --remove-driver option *must* be run from the
*old*

> colinux-daemon.exe and the --install-driver option *must* be
run from

> the *new* colinux-daemon.exe. Now I am really confused.



  Either way will work really.  If you use the new executable
to remove the old driver, you MAY get an few warnings/messages
about version mismatches.  I suggested the old executable --remove-driver
order to avoid any unnecessary warnings/messages.



> it's runs also from new executable.

>

> This should do only better testers. Because it's dificould
for newbies.



I don't know about that.  I think we've made it plenty easy.
 Besides it's the only way to run multiple versions.  And if
folks are like me, then they want to try the new one out before
really abbandoning the old one.



George



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

Love to laugh?

Good Clean Jokes at Praize

http://www.praize.com/jokes/

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux

[gboutwel <gbo...@pr...>]

> This version doesn't provide any gettimeofday fixes that aren't

> in 0710. It does include an fix for memory allocation that



It seems I was wrong on this point...  0710 still reports problems
with Linux Test Project on at least 1 gettimeofday test, while
0717 does not.



> Why would I need to install the 2004-07-10 snapshot? Here is
what I



  I'm sorry.  I should have been more clear.  If you are using
TAP as your Network type, then you'll need to 



1) Install 0710 so that the latest TAP driver gets installed
or

2) Get the TAP driver from 0710 and install it yourself.



  The reason for this is cause the TAP driver was upgraded and
an change was made to make it play nice with other TAP programs,
especially OpenVPN.



> What would go wrong with this? Why would I need to have installed
the

> 2004-07-10 snapshot first in order for this to work?



Don't see anything wrong with it, looks basically sound.



HTH,



George



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

Praize? The all-in-one Christian Community

http://www.praize.com/

[coLinux-users] Routing problem to coLinux from other computers

[John F. <J.P...@as...>]

I have set up coLinux using 0.6.1 and the Fedora Core 1 
distribution. I am using Tap and Internet Connection sharing.  All 
this works well on two installations, one Windows XP and one 
Windows 2000. I also run vncserver and samba on the Fedora 
coLinux and can see these on the PC hosting coLinux.

I would like to enable these services on another PC in the same 
workgroup as the host PC, and I have been unable to discover how 
to configure the routing in the host windows XP PC to do this.

Example

Real network
==========
HOST PC: 192.168.123.2   (Windows XP)
Another PC: 192.168.123.1 (Windows 95 OSR 2)
Gateway: 192.168.123.254 

coLinux Network
=====
TAP Gateway 192.168.0.1
coLinux 192.168.0.40

ICS enabled on the Real network on the HOST PC.

coLinux can ping to 192.168.123.1

the other PC cannot ping to 192.168.0.40 or 192.168.0.1

I think that one way to overcome this problem would be to enable a 
NAT service and allocate to the coLinux an IP number in the series 
of the real network. e.g.

192.168.123.40 <=> 192.168.0.40

The problem is that I cannot find out how to do this.  There are a 
number of items in XP e.g. RRAS, netsh, route, which are just not 
intended for ordinary people to know about. We are expected to 
use tools which assume we want to do something different.

I found this web site which suggests modification to the Regstry 
setting for IpEnableRouter and I have applied this to the XP 
computer but it is not the complete solution.

http://www.wown.com/j_helmig/w2kprout.htm

There is also some discussion of the problem at this page on the 
wiki

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

Any help will be appreciated and I'll put the solution to this onto the 
wiki.

John Fletcher
-------------------------------------------------------------------
Dr John P. Fletcher          Tel: (44) 121 359 3611 ext 4625
Chemical Engineering and Applied Chemistry (CEAC),
School of Engineering and Applied Science (SEAS),
Aston University,            Fax: (44) 121 359 4094
Aston Triangle,              Email: J.P...@as...
BIRMINGHAM B4 7ET  U.K.      CEAC Web site 
http://www.ceac.aston.ac.uk/

[coLinux-users] colinux 0.6.2 with pcap (snapshot coLinux-20040710)

[Andreas B. <and...@gm...>]

Hi all,

I would like to use 0.6.2 with bridged network. 

I tried my working configuration from 0.6.1 but I was not able to bring up
the network, in NEWS I found that PCAP-handling changed:

"Changed PCAP handling to use Connection Name instead of
Adapter/Device/Driver name. Name is +now uniform between PCAP & TAP and
multiple devices of the same/make/model should be able to be connected to.
(George Boutwell)"

What excatly does that mean for my bridged network configuration? 

Output with my old network definition:

<network index="0" name="b57w2k0 Broadcom NetXtreme Gigabit Ethernet Driver"
type="bridged" />

Result:

: Calibrating delay loop... Looking for interface "b57w2k0 Broadcom
NetXtreme Gigabit Ethernet Driver"
: Adapter Generic NdisWan adapter doesn't have a connection
: Checking connection: Local Area Connection 2
: 0.00 BogoMIPS
: Checking connection: TAP-Win32
: Checking connection: Local Area Connection
: No matching adapter
: Error initializing winPCap

It seams PCAP needs "Local Area Connection", so I tried with

<network index="0" name="Local Area Connection" type="bridged" />

Result:

: Calibrating delay loop... 0.00 BogoMIPS
: Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
: Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
: CPU:     After generic identify, caps: a7e9f9bf 00000000 00000000 00000000
: CPU:     After vendor identify, caps: a7e9f9bf 00000000 00000000 00000000
: CPU: L1 I cache: 32KLooking for interface "Local Area Connection"
: Adapter Generic NdisWan adapter doesn't have a connection
: Checking connection: Local Area Connection 2
: , L1 D cache: 32K
: CPU: L2 cache: 1024K
: Listening on: tap0801co15 TAP-Win32 Adapter V8 (coLinux)...
: Listening for: (ether dst 00:43:4f:4e:45:30) or (ether broadcast or
multicast) or (ip broadcast or multicast)

Well, as I understand the console, the used interface is "tap0801co15
TAP-Win32 Adapter V8 (coLinux)" and not "Local Area Connection", I even got
an MAC-Address but unfortunately eth0 doesn't work.

What do I miss?

Thanks for your help.

Cheers, 
Andreas

PS: As you see english is not my motherlanguage, hope it doesn't matter ;-)

-- 
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl

[coLinux-users] Re: using 2.6 kernels, moving to latest coLinux snapshot, etc.

[Joe W. <sl...@bl...>]

Okay, here is the story of me moving from coLinux 0.6.1 to a recent
coLinux snapshot.  There is a bug reported at the end of the story
where Firefox is dying with a floating point exception and I'm
wondering if it is due to something wrong in coLinux.

This is what I did:

* prepared for kernel 2.6 modules:
    emerge module-init-tools
      (This seems to be the kernel 2.6 replacement for the modutils
      package which is for kernel 2.4.  The new Gentoo package
      includes the old modutils so that if module-init-tools is
      installed, then both 2.4 and 2.6 kernels can be used.)

* prepared for coLinux snapshot's change in the location of the cobd
  devices (only needed if using devfs (which Gentoo does)):
  * created new cobd names:
      mkdir /dev/cobd
      for i in `seq 0 31`; do
          mknod /dev/cobd/$i b 117 $i
          chmod u=rw,g=r,o= /dev/cobd/$i 
      done
  * changed /dev/cobd{0,1} to /dev/cobd/{0,1} in /etc/fstab

* installed the new TAP driver from the 2004-07-10 coLinux snapshot
  (not sure if this is needed, I actually did this later when trying
  to get the TAP working):
    ./coLinux-20040710.exe
    Next -> "I agree" -> unselect(coLinux, coLinux Bridged Ethernet,
    Root Filesystem image Download) -> Next -> "C:\Program
    Files\coLinux\snapshot-2004-07-10" -> Next -> Next -> "Continue 
    Anyway" -> Finish

* unpack 2004-07-19 monotone build from http://firechief.dyndns.org/colinux/:
    mkdir '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
    cp coLinux-0.6.2-gpb.tar.bz2 '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
    cd '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
    tar xfj coLinux-0.6.2-gpb.tar.bz2

* stop old coLinux

* switch to the new coLinux driver:
    cd ..
    ./colinux-daemon --remove-driver
    cd 0.6.2-gbp-2004-07-19
    ./colinux-daemon --install-driver

* fix the configuration file:
    cp ../gentoo-i686-ext3-4g.colinux.xml .
    emacs gentoo-i686-ext3-4g.colinux.xml:
      change "root=/dev/cobd0" to "root=/dev/cobd/0"
      added 'name="Local Area Connection 3"' to the network setting
        (actually, I only added the 'name' attribute later when I had
        problems with the TAP not being found)

* check that it boots okay:
    ./colinux-daemon -c gentoo-i686-ext3-4g.colinux.xml

* the first time I did this it didn't find my TAP device and I went
  back and did things as described above.

* did lots of screwing around with Windows to get ICF/ICS to work
  with "Local Area Connection 3" instead of "Local Area Connection
  2" as I had it set before.  painful.

* unpack and test the new kernel modules:
    smbmount //MYMACHINE/C$ /c -o username=jbw,uid=jbw,gid=users
    cd /
    tar xvfz '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19/vmlinux-modules.tar.gz'
    modprobe ip_tables

* check that Linux kernel 2.6 detects my CPU correctly:
    cat /proc/cpuinfo

* observe that Firefox dies with a floating point exception:
    /usr/bin/firefox: line 87:  3285 Floating point exception$mozbin "$@"

The last point is the main annoyance.  Firefox dies with a repeatable
floating point exception.  I have run it like this to get a trace:

----------------------------------------------------------------------
#!/bin/sh
export MOZILLA_FIVE_HOME=/usr/lib/MozillaFirefox
export LD_LIBRARY_PATH=/usr/lib/MozillaFirefox:/usr/lib/MozillaFirefox/plugins
strace -o firefox-death.trace /usr/lib/MozillaFirefox/firefox-bin
----------------------------------------------------------------------

I have put the trace output at

  http://www.macs.hw.ac.uk/~jbw/firefox-death.trace

in case it can help anyone figure this out.

What could have changed to cause floating point exceptions?  I checked
that my configuration files could not be causing the problem by
temporarily moving them out of the way.  Is this a Linux kernel 2.6
change or a coLinux change?  Any thoughts or suggestions?  What
information is needed to debug this?

-- 
Joe

Re: [coLinux-users] Re: only half of memory detected

[Dani R. <rid...@ya...>]

Ok, thx all for the explanations.

-Dani-

--- Nuno Lucas <nt...@nl...> wrote:

> Dani Ridhaswana, dando pulos de alegria, escreveu :
> > Hi,
> > 
> > I have Z-pro machine with 4GB RAM installed. On
> > colinux xml file I tried to use 1000MB of memory
> for
> > colinux, but it's detected only ~500MB. Do you
> know
> > why? Is it because I used 1024MB image file for
> swap?
> 
> CoLinux memory is limited by kernel memory.
> Windows (and Linux in some configs) uses 2GB for
> user space and 2GB for 
> kernel space, so you can only use 2GB for all your
> kernel address space.
> 
> Your graphics card AGP memory is also mapped into
> the kernel address 
> space, which will probably give you only the ~500MB
> you say you have 
> left (also, it's not easy to fit all kernel objects
> inside only 1GB of 
> memory - that includes bitmaps (your desktop
> background), as GDI is in 
> kernel space).
> 
> The swap file is not relevant.
> The only fix I know is going for a 64 bits OS. There
> are some hacks for 
> the normal 32 bits Linux to address more memory, but
> the real solution 
> is 64-bit Linux and/or 64-bit Windows as the host OS
> (note that Linux 
> doesn't use as much kernel memory as Windows, so the
> problem is not so big).
> 
> > Another question, can TAP-win32 driver has 100Mbps
> > instead of 10Mbps connection?
> 
> That value is not relevant.
> The network interface is known to be slow, but
> remember colinux is still 
> in an early phase of development ;)
> 
> Regards,
> ~Nuno Lucas
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest
> price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R
> for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping
> and Free Gift.
>
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[Joe W. <sl...@bl...>]

Henry Nestler <Hen...@ar...> writes:

> Joe Wells wrote:
> > Hi, Henry and George!
> > Thank you both very much for your helpful explanations!
> > There was one bit I didn't understand fully:
> >
> >>>I noticed from an earlier message that there is a build of the
> >>>2004-07-19 version from the monotone repository available at
> >>>http://firechief.dyndns.org/colinux/>. Does this version fix
> >>>the problems?
> >>
> >>...  It's just the latest sources
> >>on 07/19 compiled, and archived in to an archive.  It doesn't
> >>even have an installer.  You will probalby want to/need to install
> >>0710 as a pre-requisite to running this version if you wish to
> >>try it.
> >
> > Why would I need to install the 2004-07-10 snapshot?  Here is what I
> > think I need to do:
> >
> >   * mkdir '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
> >   * cp coLinux-0.6.2-gpb.tar.bz2 '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
> >   * cd '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
> >   * tar xfj coLinux-0.6.2-gpb.tar.bz2
> >   * stop coLinux
> >   * cd ..
> >   * colinux-daemon --remove-driver
> >   * cd 0.6.2-gbp-2004-07-19
> >   * colinux-daemon --install-driver
> >   * cp ../gentoo-i686-ext3-4g.colinux.xml .
> >   * ln -s ../gentoo-i686-ext3-4g .
> >   * ln -s ../swap_256Mb .
> >   * colinux-daemon -c gentoo-i686-ext3-4g.colinux.xml
> >   * hope that it boots okay
> >
> > What would go wrong with this?  Why would I need to have installed
> > the 2004-07-10 snapshot first in order for this to work?
> 
> Oh, sorry, coLinux-0.6.2-gpb.tar.bz2 on this server contains Windows
> EXE-files!
> Because this archive have no installer, you need an installed version,
> before copy new executable files over an installed version.

I'm confused.  Why do I need to copy the files over an installed
version?  I plan to put the files in a separate directory.  Is there
anything that will go wrong with my plan (see the steps of my plan
above)?

Why would I need an "installer"?

> And a versions switch under Windoes need
>    colinux-daemon.exe --remove-driver
>    colinux-daemon.exe --install-driver
>    colinux-daemon -c config.xml
> to run run new version.

Yes, all of these steps are listed in my plan above.

> The remove option must not run from old executable,

I thought the --remove-driver option *must* be run from the *old*
colinux-daemon.exe and the --install-driver option *must* be run from
the *new* colinux-daemon.exe.  Now I am really confused.

> it's runs also from new executable.
> 
> This should do only better testers. Because it's dificould for newbies.

Thanks a lot for all of your help.  I hope I will be able to
understand this.

-- 
Joe

[coLinux-users] Re: colinux cannot start working!

[Sam L. <sa...@li...>]

Dustin Webb wrote:
> --- »ª·ã ÁÖ <lh...@ya...> wrote:
> 
>>       When I use the colinux, I meet a strange
>>problem. I have install the colinux and exact the
>>Debian-3.0r0.ext3.1gb to the install  directory. And
>>then I edit the default.colinux.xml(the install
>>directory is f:\colinux):
> 
> 
> As was already pointed out this is because you must
> specify the configuration file when you execute
> colinux-daemon.exe. If you want to be able to start
> coLinux by double clicking an icon then you could add
> the following to a .bat file and then double click the
> icon for that file.
> 
> REM BEGIN COLINUX.BAT
> @echo off
> f:
> cd "f:\colinux"
> colinux-daemon.exe -c default.colinux.xml
> REM END COLINUX.BAT
> 

Or, just right-drag the colinux-daemon.exe and make a shortcut,
then right-click on the shortcut and choose "Properties"
Then add: -c default.colinux.xml
at the end of the "target" field.

Then just double click on the shortcut.

A shortcut can contain a defailt start directory, as well as additional 
arguments.

Sam

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[Henry N. <Hen...@ar...>]

Joe Wells wrote:
> Hi, Henry and George!
> 
> Thank you both very much for your helpful explanations!
> There was one bit I didn't understand fully:
> 
>>>I noticed from an earlier message that there is a build of the
>>>2004-07-19 version from the monotone repository available at
>>>http://firechief.dyndns.org/colinux/>. Does this version fix
>>>the problems?
>>
>>This version doesn't provide any gettimeofday fixes that aren't
>>in 0710.  It does include an fix for memory allocation that
>>reportedly
>>speeds-up boot time, and an fix for situations where starting
>>up sometimes resulted in an cannot connect to pipe errors.  It's
>>an build of monotone's 07/17/2004 changes (which where what was
>>there on 07/19/2004) when I built that version to give to an
>>guy experiencing an odd problem.  Oddly enough the build fixed
>>his problem, so I left it up and have recommended to several
>>people experiencing problems to try it.  It's not an OFFICIAL
>>snapshot/release or otherwise.  It's just the latest sources
>>on 07/19 compiled, and archived in to an archive.  It doesn't
>>even have an installer.  You will probalby want to/need to install
>>0710 as a pre-requisite to running this version if you wish to
>>try it.
> 
> 
> Why would I need to install the 2004-07-10 snapshot?  Here is what I
> think I need to do:
> 
>   * mkdir '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
>   * cp coLinux-0.6.2-gpb.tar.bz2 '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
>   * cd '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
>   * tar xfj coLinux-0.6.2-gpb.tar.bz2
>   * stop coLinux
>   * cd ..
>   * colinux-daemon --remove-driver
>   * cd 0.6.2-gbp-2004-07-19
>   * colinux-daemon --install-driver
>   * cp ../gentoo-i686-ext3-4g.colinux.xml .
>   * ln -s ../gentoo-i686-ext3-4g .
>   * ln -s ../swap_256Mb .
>   * colinux-daemon -c gentoo-i686-ext3-4g.colinux.xml
>   * hope that it boots okay
> 
> What would go wrong with this?  Why would I need to have installed the
> 2004-07-10 snapshot first in order for this to work?

Oh, sorry, coLinux-0.6.2-gpb.tar.bz2 on this server contains Windows 
EXE-files!
Because this archive have no installer, you need an installed version, 
before copy new executable files over an installed version.

And a versions switch under Windoes need
   colinux-daemon.exe --remove-driver
   colinux-daemon.exe --install-driver
   colinux-daemon -c config.xml
to run run new version.

The remove option must not run from old executable, it's runs also from 
new executable.

This should do only better testers. Because it's dificould for newbies.

Henry

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[Joe W. <jb...@ma...>]

Hi, Henry and George!

Thank you both very much for your helpful explanations!

There was one bit I didn't understand fully:

> > I noticed from an earlier message that there is a build of the
> > 2004-07-19 version from the monotone repository available at
> > http://firechief.dyndns.org/colinux/>. Does this version fix
> > the problems?
> 
> This version doesn't provide any gettimeofday fixes that aren't
> in 0710.  It does include an fix for memory allocation that
> reportedly
> speeds-up boot time, and an fix for situations where starting
> up sometimes resulted in an cannot connect to pipe errors.  It's
> an build of monotone's 07/17/2004 changes (which where what was
> there on 07/19/2004) when I built that version to give to an
> guy experiencing an odd problem.  Oddly enough the build fixed
> his problem, so I left it up and have recommended to several
> people experiencing problems to try it.  It's not an OFFICIAL
> snapshot/release or otherwise.  It's just the latest sources
> on 07/19 compiled, and archived in to an archive.  It doesn't
> even have an installer.  You will probalby want to/need to install
> 0710 as a pre-requisite to running this version if you wish to
> try it.

Why would I need to install the 2004-07-10 snapshot?  Here is what I
think I need to do:

  * mkdir '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
  * cp coLinux-0.6.2-gpb.tar.bz2 '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
  * cd '/c/Program Files/coLinux/0.6.2-gbp-2004-07-19'
  * tar xfj coLinux-0.6.2-gpb.tar.bz2
  * stop coLinux
  * cd ..
  * colinux-daemon --remove-driver
  * cd 0.6.2-gbp-2004-07-19
  * colinux-daemon --install-driver
  * cp ../gentoo-i686-ext3-4g.colinux.xml .
  * ln -s ../gentoo-i686-ext3-4g .
  * ln -s ../swap_256Mb .
  * colinux-daemon -c gentoo-i686-ext3-4g.colinux.xml
  * hope that it boots okay

What would go wrong with this?  Why would I need to have installed the
2004-07-10 snapshot first in order for this to work?

> After that, you'd back-up or make an copy of the 0710
> install directory, and unarchive this archive over the top of
> the existing files.


> > Is there any good prediction on when there will be an official
> > coLinux 0.6.2 release? If it is in the next 2 weeks, then I am
> > better waiting for it, but otherwise I want to consider using a
> > development snapshot.
> 
> I'm not sure when Dan's going to release another snapshot or
> release.  I'd say it's a pretty safe bet that it'd be in the
> next 2 weeks,

Sounds great!

> but I maybe wrong.

I hope you're right.

> I've been running the 07/17
> code with other patches (namely UML's SKAS3 patch) applied since
> 7/28 with very little issues.  I'd say the 07/17 code is fairly
> stable and worth moving to TODAY, if it solves your problems.

Okay, this sounds good.

> Even if it doesn't solve your all your problems, it will help
> us deteremine which ones we have solved and which ones still
> need some work.

Okay, I will report back (assuming I try it).

I will reply more later to the other points.  I have to go now.

-- 
Thanks,

Joe

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[gboutwel <gbo...@pr...>]

> Does the 2004-07-10 snapshot fix all of the known problems
with

> microseconds returned by gettimeofday (especially on Windows
XP

> SP1, which I am using)?



In a nutshell..  0.6.1 was 2.4 kernel, just moving to 2.6 kernel
helped tremendously with the gettimeofday problems, but there
where still some.  I believe an patch that went into the 0710
snapshot helped some more.  I still experience clock skew on
XP SP1 on Gentoo when doing make sometimes.  But it's probably
the best it's been in a long time.



> I noticed from an earlier message that there is a build of
the

> 2004-07-19 version from the monotone repository available at

> http://firechief.dyndns.org/colinux/>. Does this version fix

> the problems?



This version doesn't provide any gettimeofday fixes that aren't
in 0710.  It does include an fix for memory allocation that reportedly
speeds-up boot time, and an fix for situations where starting
up sometimes resulted in an cannot connect to pipe errors.  It's
an build of monotone's 07/17/2004 changes (which where what was
there on 07/19/2004) when I built that version to give to an
guy experiencing an odd problem.  Oddly enough the build fixed
his problem, so I left it up and have recommended to several
people experiencing problems to try it.  It's not an OFFICIAL
snapshot/release or otherwise.  It's just the latest sources
on 07/19 compiled, and archived in to an archive.  It doesn't
even have an installer.  You will probalby want to/need to install
0710 as a pre-requisite to running this version if you wish to
try it.  After that, you'd back-up or make an copy of the 0710
install directory, and unarchive this archive over the top of
the existing files.



> Is there any good prediction on when there will be an official

> coLinux 0.6.2 release? If it is in the next 2 weeks, then I
am

> better waiting for it, but otherwise I want to consider using
a

> development snapshot.



I'm not sure when Dan's going to release another snapshot or
release.  I'd say it's a pretty safe bet that it'd be in the
next 2 weeks, but I maybe wrong.  I've been running the 07/17
code with other patches (namely UML's SKAS3 patch) applied since
7/28 with very little issues.  I'd say the 07/17 code is fairly
stable and worth moving to TODAY, if it solves your problems.
 Even if it doesn't solve your all your problems, it will help
us deteremine which ones we have solved and which ones still
need some work.



> * Can I run both the old and new coLinux at the same time so
that I

> don't have to shut down my working coLinux to test out the
new one?

> I think this doesn't work because I can't have both versions
of the

> Windows driver for coLinux installed at the same time. Am I
right?



  Yes and No.  Yes you can have both installed (in different
directories) and run them interchangably, but No you can't leave
your current one running, install the new one and test with it.



  When running interchangably, you'd need to run a sequence of
commands similiar to the following:



1) stop all colinux instances

2) in directory of verison you where just running, run colinux-daemon
--remove-driver

3) cd to directory of version you want to run

4) run colinux-daemon --install-driver

5) start any colinux instance you want to run under this version.



  The main reason for this is that until the coLinux 'API' has
been solidified it's still changing and has changed pretty much
every version/snapshot.  As long as the API changes the Windows
side kernel-mode driver can not be used with different versions,
doing so causes reboots.  The API especially changed in the switch
from 2.4 to 2.6.





> Is this enough? Will the new coLinux with the new kernel just

> simply work?



Pretty much, you'll also want to modify your /etc/fstab to point
to /dev/cobd/0, or create an symbolic link between /dev/cobd0
and /dev/cobd/0



> Why do the new /dev/cobd/X files need to exist? What software

> depends on them being in that location vs. the old location?
As far

> as I can understand, the coLinux-adapted kernel just knows
about the

> major number 117 and couldn't care less what names the devices
have

> in the file system. The only place that I know of that cares
about

> the names is /etc/fstab. So why can't I just continue using
the old

> names? The advice on the wiki does not explain this.



Because the 2.6 flavor has devfs enabled, not sure why the 2.4
didn't or why the behavior under 2.4 was different than 2.6.
 devfs is what causes the change from /dev/cobd0 to /dev/cobd/0
and /etc/fstab is the only thing that needs changed.  Not changing
/etc/fstab results in gentoo not liking the / partition, putting
it into RO mode, and booting into a single/rescue mode (every
time you boot, until you've fixed the /etc/fstab). Gentoo is
pretty much the only distro that had this problem of booting
into single/rescue mode on the switch-over.  The other distros
(namely debian) just worked, so it may be somehting in Gentoo's
handling of 2.6 kernels.  Sorry I didn't make that clearer when
I wrote those instructions on the wiki.  You're welcome to go
fix it. :)



> * What is relationship between the files in /lib/modules/2.4.24-co
in

> the pre-built 2GB Gentoo root partition and the contents of

> vmlinux-modules.tar.gz that comes with coLinux 0.6.1? There
are

> only two .o files with names in common and they differ. Otherwise,

> the modules in vmlinux-modules.tar.gz seem to be a nearly completely

> different set from the modules in /lib/modules/2.4.24-co.



the vmlinux-modules.tar.gz that ships with colinux installs,
are the modules built at the same time the vmlinux is built,
put into an archive, which extracts to an path of /lib/modules/<kernelversion>,
so in your move to 2.6, you should transfer the vmlinux-modules.tar.gz
file from the colinux directory to your image and unarchive it
while in the / directory, that is if you want/need modules which
aren't built into the kernel.  If that's not the case for you
(you don't need anything that's not bult-in to the kernel) then
you can pretty much not care about the modules or the vmlinux-modules.tar.gz.
 The difference between vmlinux-modules.tar.gz in 2.4 and vmlinux-modules.tar.gz
in 2.6 is the difference in the kernel and the kernels handling
of modules in 2.6, which changed pretty dramatically.  There's
an great document called the 2.6 Halloween document that talks
about what's invovled in moving from 2.4 to 2.6, probably well
worth the read (sorry I don't have an URL for you).  BTW, the
changes in the 2.6 kernel module handling, are also there reason
you have to install module-init-tools.



> Are the ones in vmlinux-modules.tar.gz supposed to be loaded
at boot

> time (perhaps via initrd?) and the others are for later? Also,
why

> are the Linux files in /lib/modules/2.4.24-co and not

> /lib/modules/2.4.24-co-0.6.1 (which would seem to be the place
they

> should be based on a page on the wiki).



No, Everything that's need for a typical boot is pretty much
built-in to the kernel.  The vmlinux-modules.tar.gz is provided
to give folks who want/need the additional modules the abililty
to insmod them, without having to d/l the kernel source, patch
it, and build them on their own.



> * When I emerged module-init-tools, it did not create an

> /etc/modprobe.conf file from my existing /etc/modules.conf
file. Am

> I supposed to run generate-modprobe.conf or

> modules.conf2modprobe.conf?



Hmm... Not sure on that. The 2.6 Halloween doc covers the modules.conf
to modprobe.conf changes, but I'm not sure how Gentoo specifically
handles this.



> Do I need to run depmod at some point? Or will this happen

> automatically?



Most distros run depmod automaticlally, pretty sure Gentoo does
too.



I hope that answers most your questions.  Feel free to question
further on any or the repsonse I've given if I didn't make it
clear enough.



Also, the next snapshot and/or release should include an initrd
image which will 'automagically' install the vmlinux-modules.tar.gz
files into the file image.  I just wrapped up working on that
earlier this week.



George



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

Looking for that favorite verse?

Search for it in Praize Bible

http://www.praize.com/bible/

[coLinux-users] Re: Fedora bare bones: where is crontab?

[Chris D. <da...@ya...>]

--- Chris Dahl <da...@ya...> wrote:
> Soooo... this may be a silly question, but how do I install cron?  I have
> tried
> "yum installing" cron, crond and crontab with no matching packages found. 
> Hehe... I feel pretty bad that I don't even know what it is really called so
> that I can install it.

To answer my own question... the crond use by fedora is vixie-cron.
so "yum install vixie-cron" seems to have done the job.

--Chris

=====
There is a very fine line between "hobby" and "mental illness." --Dave Barry
Linux DVDs: http://www.LinuxDVDs.com
beginners robotics: http://www.robots101.com
personal pages: http://www.dahlweb.net

Re: [coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[Henry N. <Hen...@ar...>]

Hello Joe!

Joe Wells wrote:
[...]
>   Does the 2004-07-10 snapshot fix all of the known problems with
>   microseconds returned by gettimeofday (especially on Windows XP
>   SP1, which I am using)?
> 
>   I noticed from an earlier message that there is a build of the
>   2004-07-19 version from the monotone repository available at
>   <URL:>.  Does this version fix
>   the problems?

Perhaps Yes. Please download the file
http://firechief.dyndns.org/colinux/coLinux-0.6.2-gpb.tar.bz2
This version is from source date 2004-07-18, with many modifications on 
timers.

Please check this.

>   Is there any good prediction on when there will be an official
>   coLinux 0.6.2 release?  If it is in the next 2 weeks, then I am
>   better waiting for it, but otherwise I want to consider using a
>   development snapshot.
> 
> * Can I run both the old and new coLinux at the same time so that I
>   don't have to shut down my working coLinux to test out the new one?
>   I think this doesn't work because I can't have both versions of the
>   Windows driver for coLinux installed at the same time.  Am I right?

You must relinstall driver before run various versions of colinux-daemon 
on (in different directories).
  colinux-deamon --remove-driver
  colinux-deamon --install-driver

> 
[...]
>

PS: Sorry, than I not answer all Questions yust in this time. Later more.

Henry

[coLinux-users] Bridged Networking

[Greg B. <da...@na...>]

Hello,
	Is there some easy, fullproof way to get the Device ID used for 
bridged network connections? I've read through the wiki and tried on 
several machines, and the description in the "Connect Using" field just 
doesn't do it for me. For example, my one box has "3Com 3C950B PCI 
Ethernet Adapter (10/100)", but I have to put "3Com PCI Ethernet" in the 
XML file to get CoLinux to use it. Another machine has a Davicom network 
adapter and NOTHING works for it.

Am I missing some easy, simple way to get this done? :)

-- 
    Vice President of N2Net, a New Age Consulting Service, Inc. Company
         http://www.n2net.net Where everything clicks into place!
                             KP-216-121-ST

[coLinux-users] Fedora bare bones: where is crontab?

[Chris D. <da...@ya...>]

Hi,

I am using the minimal fedora core 1 image.  I have been slowly yum-ing
packages as I need them.  Today I wanted to set up some cron jobs and
discovered that cron doesn't appear to be installed yet.  At least I can't see
a crond process and the crontab command is nowhere to be found.

Soooo... this may be a silly question, but how do I install cron?  I have tried
"yum installing" cron, crond and crontab with no matching packages found. 
Hehe... I feel pretty bad that I don't even know what it is really called so
that I can install it.

Thanks!
--Chris



=====
There is a very fine line between "hobby" and "mental illness." --Dave Barry
Linux DVDs: http://www.LinuxDVDs.com
beginners robotics: http://www.robots101.com
personal pages: http://www.dahlweb.net

[coLinux-users] using 2.6 kernels, moving to latest coLinux snapshot, etc.

[Joe W. <sl...@bl...>]

Dear fellow coLinux users,

I have a few questions regarding using 2.6 kernels and moving to the
latest coLinux snapshots.  I'm using coLinux 0.6.1 right now.

* I am considering upgrading before the next official release to solve
  the various problems with the microseconds returned by gettimeofday.

  Sometimes gettimeofday seems to just work, but at other times the
  microseconds are not a number from 0 to 999999.  Needless to say,
  this causes trouble for some software.  "make" complains a lot when
  I am installing software (I use Gentoo), although this problem seems
  innocuous when compiling software from distributions.  Emacs is
  fairly badly hit by the bad microseconds, with frequent errors while
  waiting for input.  The TRAMP Emacs subsystem (for remote file
  access) is crippled by bad microseconds although I was able to work
  around this by putting a wrapper around Emacs's current-time
  function that replaced the microseconds by 0.  Firefox starts
  spinning and using all the CPU when the microseconds go below -21
  minutes.

  I've seen a number of different bad behaviors of the microseconds.
  Sometimes, the sum of the microseconds and the seconds seems to be
  the correct time, although the microseconds are wildly out of the
  allowed range and hover around some very negative number.
  Sometimes, the seconds field seems to be correct but the
  microseconds fail to wrap properly, going up to perhaps 1 or 2
  minutes and then when they wrap starting from about -1 or -2
  minutes.  Sometimes the gettimeofday results seem to return to
  normal for extended periods.

  Does the 2004-07-10 snapshot fix all of the known problems with
  microseconds returned by gettimeofday (especially on Windows XP
  SP1, which I am using)?

  I noticed from an earlier message that there is a build of the
  2004-07-19 version from the monotone repository available at
  <URL:http://firechief.dyndns.org/colinux/>.  Does this version fix
  the problems?

  Is there any good prediction on when there will be an official
  coLinux 0.6.2 release?  If it is in the next 2 weeks, then I am
  better waiting for it, but otherwise I want to consider using a
  development snapshot.

* Can I run both the old and new coLinux at the same time so that I
  don't have to shut down my working coLinux to test out the new one?
  I think this doesn't work because I can't have both versions of the
  Windows driver for coLinux installed at the same time.  Am I right?

* I am having trouble understanding just what I need to do to upgrade
  my current coLinux root partition to be usable with the post-0.6.1
  coLinux and 2.6 Linux kernel.  I found the instructions on the
  coLinux wiki to be confusing.

  I'm running Gentoo based on the pre-built 2GB Gentoo root partition
  available from the coLinux web site.  I have done "emerge
  module-init-tools".  I have done "mknod /dev/codb/X b 117 X" for X
  from 0 through 31.

  Is this enough?  Will the new coLinux with the new kernel just
  simply work?

  Why do the new /dev/cobd/X files need to exist?  What software
  depends on them being in that location vs. the old location?  As far
  as I can understand, the coLinux-adapted kernel just knows about the
  major number 117 and couldn't care less what names the devices have
  in the file system.  The only place that I know of that cares about
  the names is /etc/fstab.  So why can't I just continue using the old
  names?  The advice on the wiki does not explain this.

* What is relationship between the files in /lib/modules/2.4.24-co in
  the pre-built 2GB Gentoo root partition and the contents of
  vmlinux-modules.tar.gz that comes with coLinux 0.6.1?  There are
  only two .o files with names in common and they differ.  Otherwise,
  the modules in vmlinux-modules.tar.gz seem to be a nearly completely
  different set from the modules in /lib/modules/2.4.24-co.

  Are the ones in vmlinux-modules.tar.gz supposed to be loaded at boot
  time (perhaps via initrd?) and the others are for later?  Also, why
  are the Linux files in /lib/modules/2.4.24-co and not
  /lib/modules/2.4.24-co-0.6.1 (which would seem to be the place they
  should be based on a page on the wiki).

* When I emerged module-init-tools, it did not create an
  /etc/modprobe.conf file from my existing /etc/modules.conf file.  Am
  I supposed to run generate-modprobe.conf or
  modules.conf2modprobe.conf?

  Do I need to run depmod at some point?  Or will this happen
  automatically?

* At gmane.org, the coLinux mailing lists are archived and they have
  inadequate concealment of addresses.  It is too easy for spammers to
  automatically harvest addresses of the form "<MBOX <at> DOMAIN>".
  So I am sending this message using an obfuscated address for myself.
  I had to create an extra mailing address for myself and subscribe it
  to the mailing list just for this purpose because the sourceforge
  mailing list system rejected my message when I just used a bogus
  return address.  It would be nice if the archivers at gmane.org
  didn't make this necessary.

Thanks for any helpful information any of you can give me!

-- 
Joe Wells