Re: [coLinux-users] Creating a development environment

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

Henry Nestler wrote:
> Antony Barton wrote:
>> Hi everyone,
>>  
>> I'm fairly new to this endeavour so please forgive me for any ignorance.
>>  
>> As I'm sure you are aware colinux provides huge potential for providing
>> an easily transferrable development environment for any team, and I have
>> been set with the task of investigating colinux as an option.
>>  
>> I have successfully installed it and run it using the fedora image
>> included with it but i am still stuck on two issues.
>>  
>> First of all, the development board i am working on uses a kernel 2.4
>> system and will be for the foreseeable future, and so i require to be
>> able to cross-compile the toolchain for its linux dist. Does anybody
>> have any suggestions as the best way to achieve this?
> 
> This is not the right forum here. After you have coLinux Fedora runnin,
> it is a question for Fedora or your Cross target depent on that Name.
> 
>> Secondly I am struggling to set up any form of network sharing to be
>> able to transfer any data from the host OS to colinux and vice-versa - I
>> have read through various FAQ and tutorials and have unfortunately found
>> them more confusing than helpful. Can anybody outline the most simple
>> and effective means of setting up a shared drive (or simply getting the
>> network configuration to the stage where one can be set up), starting
>> from the .bat file included with the fedora image (i choose fedora as it
>> is the linux dist of choice for the development team).
> 
> Yeha, you needs to know some about networking, to made it runable.
> 
> Simplest way to have a shared folder between coLinux and Windows is "cofs".
> 
> You needs to have coLinux 0.7.2 or later.
> Edit your config file and add a shared folder, for example C:\TEMP
>   cofs0=C:\TEMP
> 
> Inside coLinux you can mount this as
>   mkdir /windows
>   mount -t cofs cofs0 /windows
> 
> You can also create such fstab entry:
> cofs0:/  /windows  cofs  user,noexec,uid=hn,gid=users  0 0
> 
> Helps for cofs you will find in cofs.txt in your coLinux installation
> directory and in the wiki: http://colinux.wikia.com/wiki/Cofs_device
> 
> 
> Installig networking is complicated, because you have to many ways. The
> simples way is to use "eth0=slirp" in colinux config file and enable
> DHCP inside the linux. If DHCP is not usable, use the static way:
> http://colinux.wikia.com/wiki/Network#SLiRP_with_Static_IP_Address

This article sems me better for you:
http://colinux.wikia.com/wiki/Getting_Started_with_coLinux_-_Long_manual#Setting_up_networking_with_SLiRP

> All other network types are for special cases.
> TAP is a closed network between host and coLinux only. You needt to know
> what network is free in your environment and you needs to setup it right
> on windows and linux side.
> pcap-bridges is for inserting your coLinux as public PC into a LAN, but
> works not in all cases (WLAN problem). For this you needs a self made
> MAC and a free ipaddress from your network to configure it inside coLinux.
> 
> More about networking details finds under "Choose networking method(s)
> to install" in the file README.txt from your installation. And details
> about parameters in the file colinux-daemon.txt

-- 
Henry N.