Re: [coLinux-users] Networking and run-as-service user account issues

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

Jason Alonso schrieb:
> Hello,
> 
> I'm running 0.8.0 with a custom genkernel-built kernel, upgraded from
> 0.7.3 (actually the first snapshot that didn't require XML
> configuration), upgraded from a version number I've since forgotten.
> (This image has been running for a while).  The host is WinXP Pro.
> 
> I'm now experiencing a phenomenon in that I need to have
> colinux-daemon run as my personal account in order to have network
> access (tuntap).  When launched from the command line, the network
> devices connect just fine.  When launched as a service, all of the
> relevant daemons appear to be present and running as SYSTEM, but the
> coLinux system doesn't detect the network devices, though it otherwise
> boots the image.  I reconfigured the service from the Windows
> management console to run under my account instead of SYSTEM, and it
> boots fine, though I haven't gone the extra step of trying to get the
> service to start on system boot, whereupon I expect I still need to
> add NPF and PCAP service dependencies.
> 
> I'd like to get this running as SYSTEM again... what am I doing wrong?

You would see your network ethX with command "cat /proc/net/dev".

Please read the section "Upgrading from coLinux 0.7.2 and before"
carefully on http://www.colinux.org/snapshots/devel-RUNNING

You needs to remove all entries from
/etc/udev/rules.d/z25_persistent-net.rules
Than reboot to have eth0 again.

It is a badly because 0.8.0 has udev working and an other network
adapter stays in the persistend file as eth0. Then udev renames it to
next network for example eth1 or more.

-- 
Henry N.