RE: [coLinux-devel] FW: switching to snapshots, TAP device gone?

[Anders E. C (KI/EAB) <and...@er...>]

I'd be happy to provide details on recreating this effect, if I could
find out what that triggering step would be. To that end, I'll uninstall
colinux, and reinstall (0.6.1, move to latest snap), noting the steps 
and see what happens. Anything in particular one should observe to
ensure ALL of it is uninstalled?

This is on a "2000 Professional version 5.0 Service Pack 4 (Build 2195)"
if that is relevant.

I'll be back tonight (.se time) with details.

Thanks,

/Anders
PS: In my first investigation, I read the source for the TAP finding,
and discovered its registry walkink routines. I _guess_ there might be
differences in this machines registry setup and my old (now gone) one (where
snapshots worked). Any ideas how I can share relevant parts of the registry
with you folks?

/Anders

> 
> slirp is the name of it, don't think anything major happened with it
> (ported from qemu or sth)
> 
> slirp is known to have bugs in coLinux (missing byte issue), you could
> try and play with that and see how you go there.
> 
> as for the snapshots, i'm not quite sure what i have myself, let alone
> what would be on the web.
> 
> could u perhaps give us a method to recreate your situation, i
> wouldn't seeing if I could recreate and have a look for you ;)
> 
> sam
> 
> On Thu, 20 Jan 2005 13:36:09 +0100, Anders Eriksson C (KI/EAB)
> <and...@er...> wrote:
> > Hi Sam,
> > >
> > > colinux is testing out 'different' methods of connecting 
> from windows
> > > and linux, checkout the devel archives online for some information
> > >
> > >
> > 
> > I know of the bridged method (cannot use it, I use a whole slew of
> > different interfaces to get the net which cange _after_ 
> colinux is started),
> > and the recent cofs effort which seems promising. Are these the ones
> > you refer to? I've been on the -user and -devel lists since 11 Aug
> > and I have not seen any other report indicating that the TAP support
> > is changing. Can you point at anything particular?
> > 
> > I tried to with explicit naming of the TAP device:
> >         <network index="0" type="tap" name="colinux tap"/>
> >        (and carefully renaming the "TAP win32 adapter" net 
> to "colinux tap")
> > to no avail:
> >        searching TAP device named "colinux tap"
> >        TAP device not found
> > 
> > The strange thing is that it works like a charm with the 
> 0.6.1 release,
> > so things should not be that far off with my base 
> installation. Do you
> > have any pointers to snapshots between 0.6.1 and 20041029? 
> I'd like to
> > binary search for the problem spot, but dont have the 
> facilities to compile
> > the thing myself :-((
> > 
> > Thanks,
> > 
> > /Anders
> >
>