On Sunday, May 16, 2004, at 09:40 US/Central, Robert Citek wrote:
> http://prdownloads.sourceforge.net/openvpn/
Has anyone build the TAP driver from source? If so, could you share
how you did it?
I've downloaded the 1.6 version and tried to build it under Libranet:
$ ./configure --disable-lzo --disable-crypto
$ make
unfortunately, only one of the three files could be found:
$ find . -type f -iname OemWin2k.inf -o -iname tapdrvr.sys -o -iname
devcon.exe
./tap-win32/i386/OemWin2k.inf
I've looked in the INSTALL-win32.txt file which mentions I need a bunch
of stuff, including a DDK package from Microsoft (couldn't figure out
how to get this. Looks like I need to subscribe to the MSDN, or am I
missing something?) Besides, I don't really want to build openvpn. I
just want to build the TAP driver. Some questions:
- can the driver be built under Linux (even coLinux) using the MinGW
environment that coLinux sets up with the build-* scripts?
- does anyone have simplified instructions of any kind for building
the TAP driver for use in colinux?
A full text search on the wiki pages for tapdrvr.sys didn't find
anything.
Thanks in advance for any pointers in the right direction.
Regards,
- Robert

On Sunday, May 16, 2004, at 08:59 US/Central, ePAc wrote:
> the TAP driver is part of the OpenVPN implementation.
> http://openvpn.sf.net
>
> sourcecode and all are available there.
Thanks. Which version of OpenVPN did coLinux get it's TAP from?
There's everything from openvpn-1.0 to openvpn-2.0-beta. 1.6 is the
latest stable version, but was release just a few days ago: May 9th.
http://prdownloads.sourceforge.net/openvpn/
Or does it not matter?
Regards,
- Robert

>
> Hello all,
>
> Where does one get the source code for the TAP binaries that come with
> colinux?
>
the TAP driver is part of the OpenVPN implementation.
http://openvpn.sf.net
sourcecode and all are available there.
Jok
---
Nothing is foolproof to a sufficiently talented fool...
oo
,(..)\
~~

Hello all,
Where does one get the source code for the TAP binaries that come with
colinux?
From reading the .nsi file, coLinux.exe needs three files for TAP:
OemWin2k.inf, tapdrvr.sys, and devcon.exe (see below for the complete
.nsi section). They come from the ./premaid folder which I could not
find in the colinux-20040509 (nor any other snapshot) source tree.
Anyone know where they are from, how to get them, and how to
compile/create them?
Regards,
- Robert
-----
Section "coLinux Virtual Ethernet Driver (TAP-Win32)" SeccoLinuxNet
;---------------------------------------------------------------FILES--
;----------------------------------------------------------------------
; Our Files . If you adds something here, Remember to delete it in
; the uninstall section
SetOutPath "$INSTDIR\netdriver"
File "premaid\netdriver\OemWin2k.inf"
File "premaid\netdriver\tapdrvr.sys"
File "premaid\netdriver\devcon.exe"
;--------------------------------------------------------------/FILES--
;----------------------------------------------------------------------
SectionEnd

I posited the question about how to handle both native and colinux
gentoo installations on the same machine and I got this interesting
reply. The last one is the most interesting but I'm leaving the context
so folks have a chance to understand how we got there.
-------- Original Message --------
Subject: Re: [gentoo-user] an interesting configuration problem
Date: Thu, 13 May 2004 13:56:36 -0400
From: Araemo <araemo@...>
Reply-To: gentoo-user@...
To: gentoo-user@...
References: <40A23782.1060102@...>
<1084377710.2539.66.camel@...>
<40A2B24F.7020207@...> <40A2E8ED.8020200@...>
<20040513041723.GD8317@...>
Sami Samhuri wrote:
>* It was Wed, May 12, 2004 at 11:18:05PM -0400 when Araemo said:
>
>
>>Eric S. Johansson wrote:
>>
>>
>>
>>>John Nilsson wrote:
>>>
>>>
>>>
><snip>
>
>
>>>one would think. Unfortunately, is still doesn't solve this problem.
>>>Let's say you create /etc as a separate and different partition on
>>>both "machines". When you emerge a package, it changes /etc on the
>>>machine you do the emerge. What happens to the second machine which
>>>is identical in all but the /etc directory. How do you bring it up to
>>>date?
>>>
>>>I'm sure there are other places other than /etc that will vary between
>>>a colinux and native boot systems. it's just the worst.
>>>
>>>this problem smells like what is needed is some form of filesystem
>>>proxy. A layer which will redirect file system requests in different
>>>directions based on system context. I've been told openBSD has
>>>something similar to what I'm thinking of. It would be useful lots of
>>>contexts.
>>>
>>>
>>>
>>Perhaps it would minimize trouble to change your $PORTDIR to something
>>on this loopback FS, and always build packages when you run emerge -u?
>>that at least cuts down the compile time to once per package that needs
>>updated. That way you emerge sync once, emerge -uvb world (I think
>>those are the right flags, and I'm too lazy to look atm, since I'm in
>>windows), and go through the compile once, and just 'emerge -uvk world'
>>when in native gentoo, to pull the previously built packages from
>>$PORTDIR. This doesn't solve config file headaches, but I don't know
>>if theres a clean solution to that(Yet).
>>
>>
>
>Except that after the first 'emerge -ub world' updates the system, the
>subsequent 'emerge -uk world' won't find updates to apply. (At least,
>this is what seems like should happen)
>
>
>
$PORTDIR only contains the portage tree, downloaded sources, and built
packages. not the information about locally installed packages.
That goes into /var/edb/world or something like that, under /var. That
way, as long as /var is seperate between the two systems, you can avoid
a lot of extra compile time.
Of course, this is assuming that your cflags on whichever system builds
the binary packages, will run under the other(I really don't know how
colinux handles CPU/hardware access.. would it 'dumb-down' some CPU
features, or is it pretty much like running linux natively?)
--
gentoo-user@... mailing list
-----------------
so, it looks like if we build the system totally common except for
differences in /var, and /etc(maybe??) it might work. I will continue
the conversation with them and report back on the progress
---eric

Wow. That's impressive. Congratulations to the coLinux development team!
Rob
----- Original Message -----
From: "Olivier Souiry" <colinux@...>
To: <colinux-devel@...>
Sent: Saturday, May 15, 2004 10:35 PM
Subject: [coLinux-devel] just ran Oracle in coLinux...
> so, I had Oracle 9i R1 on a Mandrake 8.2 partition on a disk I forgot
> about almost 2 years ago. I mounted it with coLinux snapshot 20040509.
>
> I had to mknod a few /dev/cobd nodes, edit /etc/inittab to run at level 3
> and not 5, and that was basically all. next thing I booted the Mandrake
> image with the following block device entry :
>
> <block_device index="0" path="\Device\Harddisk2\Partition2"
> enabled="true"></block_device>
>
> I started the database, had one or two connections to it, ran a few
selects
> like SELECT TABLE_NAME FROM USER_TABLES and sat down.
>
> the coLinux image was allocated 128 Mb of RAM, and 100 Mb of swap were in
> use, of 512 available. those are fairly typical numbers of the times when
I
> was testing Oracle on the native Mandrake installation, so no big surprise
> there, either.
>
> I tried later with 256 Mb of RAM allocated, and Oracle started really
fast,
> as in, not slower that on a real Linux system.
>
>
> you can see a screeshot here :
http://gniarf.nerim.net/colinux/colinux26.gif
>
> not very impressive or informative, unfortunately.
>
>
> ok, so thats just another testimony to the overall quality and stability
of
> coLinux.
>
> coLinux allows Linux distributions to run various applications from
apt-get
> and ssh to X, KDE and Gnome, including Mozilla and OpenOffice, heavy-duty
> compilation efforts including emerge and building coLinux itself, and now
> they can run Oracle itself, a 1,000-pound gorilla of software.
>
>
> this is truly impressive.
>
>
> Olivier Souiry.
>
>
>
>
>
>
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> coLinux-devel mailing list
> coLinux-devel@...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

so, I had Oracle 9i R1 on a Mandrake 8.2 partition on a disk I forgot
about almost 2 years ago. I mounted it with coLinux snapshot 20040509.
I had to mknod a few /dev/cobd nodes, edit /etc/inittab to run at level 3
and not 5, and that was basically all. next thing I booted the Mandrake
image with the following block device entry :
<block_device index="0" path="\Device\Harddisk2\Partition2"
enabled="true"></block_device>
I started the database, had one or two connections to it, ran a few selects
like SELECT TABLE_NAME FROM USER_TABLES and sat down.
the coLinux image was allocated 128 Mb of RAM, and 100 Mb of swap were in
use, of 512 available. those are fairly typical numbers of the times when I
was testing Oracle on the native Mandrake installation, so no big surprise
there, either.
I tried later with 256 Mb of RAM allocated, and Oracle started really fast,
as in, not slower that on a real Linux system.
you can see a screeshot here : http://gniarf.nerim.net/colinux/colinux26.gif
not very impressive or informative, unfortunately.
ok, so thats just another testimony to the overall quality and stability of
coLinux.
coLinux allows Linux distributions to run various applications from apt-get
and ssh to X, KDE and Gnome, including Mozilla and OpenOffice, heavy-duty
compilation efforts including emerge and building coLinux itself, and now
they can run Oracle itself, a 1,000-pound gorilla of software.
this is truly impressive.
Olivier Souiry.

On Saturday, May 15, 2004, at 19:28 US/Central, Antelio I. Abe wrote:
> I've tried with gdm and console.
>
> All returns wrong password.
>
> I'm using WinXP sp1.
> I'm using Debian 3.0 rc1
And which colinux version/snapshot?
Add 'init=3D/bin/bash' to the bootparams. To do so, edit your=20
default.colinux.xml and change this line:
<bootparams>root=3D/dev/cobd0</bootparams>
to this
<bootparams>init=3D/bin/bash root=3D/dev/cobd0</bootparams>=00
Then start colinux-daemon.exe. You should be dropped into a bash shell=20=
at start up. What output do you get if you type this:
# grep root /etc/passwd
Regards,
- Robert