colinux-users — coLinux users mailing list

Re: [coLinux-users] unionfs in colinux?

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

David Kaufman wrote:
> Hi,
> 
> I'd like to use unionfs in colinux:
> http://www.fsl.cs.sunysb.edu/project-unionfs.html
> 
> My goal is to have several colinux instances sharing a large read-only 
> filesystem (like the OS images that ship with colinux) and saving their 
> local changes to smaller writable local "unioned" filesystems.  This would 
> help me to repeatedly test-install large, complicated software packages 
> that we develop (such as http://krang.sf.net), with the ability to quickly 
> roll back the O/S to its pristine state and re-do as many times as needed, 
> and also to make it easy to identify and isolate all changes made to the 
> underlying distro afterwards (by examining the writable directory mounted).
> 
> I read that unionfs was "baked in" to the linux kernel since 2.6.14 and 
> also see that it is supported by my distro (debian etch) so I was 
> disappointed when:
> 
>   mount -t unionfs -o dirs=/Fruits:/Vegetables none /mnt/healthy
> 
> complained that:
> 
>   unknown file system unionfs
> 
> Is unionfs not baked into the colinux kernel, too?  Am I doing something 
> wrong (or not doing something else right?)  Do I need to get the source, 
> compile and load the kernel module for colinux?  I've never done that 
> before, but for this I'd be anxious to give it a try!
> 
> I'm running a recent 0.8.0 snapshot (at the moment) but would be willing to 
> up-, down-, or side-grade to get unionfs running!

Unionfs is not in the vanilla kernel. I have grepped the conmplete tree
for "unionfs". Only found one comemnt, but no code.

You needs to have a kernel 2.6.22(.19) patch from unionfs team [1] and
must patch this over the colinux patched kernel. Than needs to
reconfigure the kernel and test it. Please read the doc/building or [2],
section "4. Building a coLinux kernel".

We have kernel 2.6.22.18, but see, there are no conflicts in patch for
2.6.22.19, think is usable.

[1] http://www.fsl.cs.sunysb.edu/project-unionfs.html
[2] http://colinux.wikia.com/wiki/BuildingColinux0.8.0

-- 
Henry N.

[coLinux-users] unionfs in colinux?

[David K. <da...@gi...>]

Hi,

I'd like to use unionfs in colinux:
http://www.fsl.cs.sunysb.edu/project-unionfs.html

My goal is to have several colinux instances sharing a large read-only 
filesystem (like the OS images that ship with colinux) and saving their 
local changes to smaller writable local "unioned" filesystems.  This would 
help me to repeatedly test-install large, complicated software packages 
that we develop (such as http://krang.sf.net), with the ability to quickly 
roll back the O/S to its pristine state and re-do as many times as needed, 
and also to make it easy to identify and isolate all changes made to the 
underlying distro afterwards (by examining the writable directory mounted).

I read that unionfs was "baked in" to the linux kernel since 2.6.14 and 
also see that it is supported by my distro (debian etch) so I was 
disappointed when:

  mount -t unionfs -o dirs=/Fruits:/Vegetables none /mnt/healthy

complained that:

  unknown file system unionfs

Is unionfs not baked into the colinux kernel, too?  Am I doing something 
wrong (or not doing something else right?)  Do I need to get the source, 
compile and load the kernel module for colinux?  I've never done that 
before, but for this I'd be anxious to give it a try!

I'm running a recent 0.8.0 snapshot (at the moment) but would be willing to 
up-, down-, or side-grade to get unionfs running!

Thanks!

-dave

Re: [coLinux-users] Colinux 0.7.2 hangs on startup XP

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

Paolo Minazzi wrote:
> Hi Henry,
> 
> I checked my old kernel configuration of 0.7.1 that was very very
> stable .... Never an hang of my system !
> 
> I had
> 
> #
> # IO Schedulers
> #
> CONFIG_IOSCHED_NOOP=y
> CONFIG_IOSCHED_AS=y
> CONFIG_IOSCHED_DEADLINE=y
> CONFIG_IOSCHED_CFQ=y

And what is the CONFIG_DEFAULT_IOSCHED="..."?

> CONFIG_PREEMPT=y
> CONFIG_PREEMPT_BKL=y
> 
> as you say.
> 
> This is the real thing. It is not the theory. The old configuration was stable.
> 
> But I cannot understand why  disabling CONFIG_PREEMPT and
> CONFIG_PREEMPT_BKL can produce deadlocks (or have more chances to have
> deadlocks).

Help for "CONFIG_PREEMPT_BKL" from kernel source:
"This option reduces the latency of the kernel by making the
big kernel lock preemptible."

This, I read, that a "big kernel lock" can be interupted. Right? And in
your case the PC hangs without accepting any interrupts (keyboard). A
simple "big kernel lock" is a simple disable all interrupts. Perhaps the
 CONFIG_PREEMPT_BKL helps to not hang in such lock.

CONFIG_PREEMPT needs to have CONFIG_PREEMPT_BKL.

> I decided to disabling these because I am not interested in improving
> the responsivity of my colinux. I am only interested in performance.
> 
> Today I'll reconfigure as you saied me.

I have only checked differences between your and the default config and
listened candidates for problems. A highly candidate is the io scheduler.

After you have enabled all the io schedulers, you can select ones with
the kernel boot option "elevator=deadline", default is
"elevator=anticipatory".

Yes, of curse, perhaps there exist a bug and nobody has seen it. You can
use your scheduler (DEADLINE) and all other configs. But please, then
should enable the CONFIG_DEBUG_KERNEL to find the daedlog, instead
hanging in it.

-- 
Henry N.

[coLinux-users] Colinux 0.7.2 hangs on startup XP

[Paolo M. <pao...@gm...>]

Hi Henry,

I checked my old kernel configuration of 0.7.1 that was very very
stable .... Never an hang of my system !

I had

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y

CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y

as you say.

This is the real thing. It is not the theory. The old configuration was stable.

But I cannot understand why  disabling CONFIG_PREEMPT and
CONFIG_PREEMPT_BKL can produce deadlocks (or have more chances to have
deadlocks).

I decided to disabling these because I am not interested in improving
the responsivity of my colinux. I am only interested in performance.

Today I'll reconfigure as you saied me.

Bye,
Paolo

Re: [coLinux-users] andLinux not working on Windows 2000

[Luco <luc...@gm...>]

Hi all,

I'm still no further in getting this to work. Has anyone had any success 
using andLinux on Windows 2000? No matter what I do I can't get anything 
to happen.

The problem seems to stem from the absence of network bridge support in 
Windows 2000, and the internet connection sharing method produces the 
following error Terminal is run:

Could not launch 'Termnial': could not connect to 192.168.11.150:81

However, currently any changes to the network configuration have no 
effect on this. It is possible that I have missed something in the 
internet connection sharing settings, though if I have, it is not 
documented.

I have had this problem for around two months now, and discussions on 
coLinux IRC have verified that there should not be any problems. The 
problem is identical on both my machines, but andLinux runs first time 
on XP on the same machines.

Does anyone know the sequence of events that occurs when starting an ap 
in andLinux so that I might be able to track what is going wrong?

Thanks

NB: On installation I always get the error 'could not execute file: ss'

* Luco wrote, On 20/02/2008 01:28:
> Hi,
> 
> I actually posted this on the dev list, but this may be a better
> location. Although it is a tough one ;)
> 
> I have installed andLinux and enabled connection sharing on the physical
>  ethernet. The tap adaptor is currently on DHCP. Applications try but
> fail to connect to 192.168.11.150:81. The ethernet is currently static
> at 180.*
> 
> I've tried every possible combination of adjustments to my network
> settings for both adaptors, and disabled the firewall altogether but
> still no luck.
> 
> Of course this is on 2000. On XP everything works immediately and perfectly.
> 
> After the first installation attempt, I received the following message
> on subsequent attempts:
> 
> "Unable to execute file:
> sc
> 
> ShellExecuteEx failed; code 2
> The system cannot find the file specified"
> 
> Running a linux ap, such as Thunar produces the error:
> 
> "could not launch 'Thunar': could not connect to 192.168.11.150:81"
> 
> I've read most of the list archives, wiki, and website, and there isn't
> much more I can think of to do.
> 
> Interestingly (in the bad way), if I set the Tap adapter to DHCP,
> disable it, diable ICS on the ethernet, enable the tap, enable ICS on
> the ethernet, the tap will be set a static IP. Is this the cause of the
> problem?
> 
> Thanks
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: [coLinux-users] colinux 0.7.2 hangs ....

[Paolo M. <pao...@gm...>]

What distro you runs?

Slack12

What is the compiler version, you used for kernel build?

I use gcc 3.4.6
The standard is gcc 4.1.2, but it has problem compile qemu, so I use
this older compiler.
The 3.4.6 is in the contrib directory (old package) of slack 12.

mingw32 4.1.2

Bye!
Paolo

Re: [coLinux-users] Colinux 0.7.2 hangs on startup XP

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

Paolo Minazzi wrote:
> Hi colinux users.
> I have to say that 0.7.2 is not stable as 0.7.1.
> I'm using 0.7.2 (during last month) and today is the 2nd time it hangs my WinXP.
> 
> It hangs always (the 2 times) in the same point, at startup of the system.
> 
> .........
> TCP cubic Registered
> NET Registered protocol family 1
> NET Registered protocol family 17
> Using IPI Shortcut mode
> 
> After this, my XP doesn't respond and I have to power-down and power-on my PC.
> 
> My config is at the end of email.

You have changed some on the kernel configs? On the sheduler!
Please reenable CONFIG_IOSCHED_AS and let the default sheduler as
"anticipatory". All other shedulers have not well tested. I have known
one error from other user about sheduler CFQ in combination with async
block device.

Please enable also CONFIG_PREEMPT and CONFIG_PREEMPT_BKL.

For error tracing reenable CONFIG_DEBUG_KERNEL. Then you should see the
daedlock, instead a hanging pc.

> I'm using a my-compiled version of 0.7.2 with 100x50 console-nt.
> But I think (and I hope) that is not my problem (in adjusting
> console-size in the source) because I use it everyday and it stops
> only two times at the same point.
> What can I do to help to solve the problem ?
> Launch colinux-deamon-debug ?

No. The debug-daemon can not help, if the guest kernel hangs. This is a
symptop of a daedlog. For example waiting for a mutex with disabled
interrupts.

What distro you runs?
What is the compiler version, you used for kernel build?

-- 
Henry N.

[coLinux-users] Colinux 0.7.2 hangs on startup XP

[Paolo M. <pao...@gm...>]

Hi colinux users.
I have to say that 0.7.2 is not stable as 0.7.1.
I'm using 0.7.2 (during last month) and today is the 2nd time it hangs my WinXP.

It hangs always (the 2 times) in the same point, at startup of the system.

.........
TCP cubic Registered
NET Registered protocol family 1
NET Registered protocol family 17
Using IPI Shortcut mode

After this, my XP doesn't respond and I have to power-down and power-on my PC.

My config is at the end of email.

I'm using a my-compiled version of 0.7.2 with 100x50 console-nt.
But I think (and I hope) that is not my problem (in adjusting
console-size in the source) because I use it everyday and it stops
only two times at the same point.
What can I do to help to solve the problem ?
Launch colinux-deamon-debug ?

Regards,
Paolo


#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22
# Tue Mar 25 23:16:10 2008
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set

#
# Block layer
#
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_PARAVIRT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MCORE2 is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_MINIMUM_CPU_MODEL=4
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_COPIC=y
# CONFIG_X86_MCE is not set
CONFIG_VM86=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_NR_QUICK=1
# CONFIG_MATH_EMULATION is not set
# CONFIG_SECCOMP is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_COOPERATIVE=y
CONFIG_COMPAT_VDSO=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set

#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNPACPI is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=1
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_BLK_DEV_COBD=y
CONFIG_BLK_DEV_CLOOP=y
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# Misc devices
#
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_ATA is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_MACINTOSH_DRIVERS is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
CONFIG_COOPERATIVE_CONET=y

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_WAN is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_COOPERATIVE=y
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=y
CONFIG_SERIO_COKBD=y
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_COSERIAL=y

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_R3964 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
# CONFIG_I2C is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
# CONFIG_HWMON is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
# CONFIG_FB is not set

#
# Console display driver support
#
CONFIG_COOPERATIVE_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# HID Devices
#
# CONFIG_HID is not set

#
# USB support
#
# CONFIG_USB_ARCH_HAS_HCD is not set
# CONFIG_USB_ARCH_HAS_OHCI is not set
# CONFIG_USB_ARCH_HAS_EHCI is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set

#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set

#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set

#
# DMA Clients
#

#
# DMA Devices
#

#
# Virtualization
#
# CONFIG_KVM is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_COFUSE_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Distributed Lock Manager
#
# CONFIG_DLM is not set

#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_EARLY_PRINTK=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
# CONFIG_CRC32 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_KTIME_SCALAR=y

Re: [coLinux-users] Private Network and wireless trouble

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

Henry Nestler wrote:
> Mike wrote:
>> OK the scenario would than be: 
>> (for simplicity lets forget the host->guest connection for now)
>>
>> Internet Router: 192.168.2.254
>>
>> Colinux:
>> eth0: (taptun 10.0.1.1 255.255.255.0 10.0.1.255 gw 10.0.1.2)
>>
>> Host:
>> wtap0 (WinTAP 10.0.1.2 255.255.255.0 10.0.1.255 gw 192.168.2.254)
>> phys (Wifi 192.168.2.23 255.255.255.0 192.168.2.255 gw 192.168.2.254)
>>
>>  +---------------------+        +-------------------------+
>>  |   Colinux guest     |        |        WinXP host       |     +-----+
>>  |               eth0  +<------>+ wtap0              phys +<--->+lan
>>  |                     |   ^    |   +------>???<------+   |  ^  +-----+
>>  +---------------------+   |    +-------------------------+  |
>>                            |                                 |
>>                         10.0.1.0                       192.168.2.0
>>                         network                          network
>>
>> Question now is how to make sure the wtap0 forwards all communication to phys
>> and vice versa? 
> 
> This type of forwarding is named "bridge".
> 
> I'm prefer Windows bridge way. That I have tested with cable networks.
> http://colinux.wikia.com/wiki/Network#TAP_with_Windows_Software_Bridge
> 
> The other way is Internet Connection Sharing (ICS).
> This is perhaps the better way for WLAN.
> http://colinux.wikia.com/wiki/Network#Internet_Connection_Sharing_.28ICS.29
> "Networking" in
> http://www.ibm.com/developerworks/library/l-virtualization-colinux/
> 

Think this description for ICS is better:
http://colinux.wikia.com/wiki/Getting_Started_with_coLinux_-_Long_manual#Setting_up_networking_with_TAP-Win32_and_ICS

-- 
Henry N.

Re: [coLinux-users] Private Network and wireless trouble

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

Mike wrote:
> OK the scenario would than be: 
> (for simplicity lets forget the host->guest connection for now)
> 
> Internet Router: 192.168.2.254
> 
> Colinux:
> eth0: (taptun 10.0.1.1 255.255.255.0 10.0.1.255 gw 10.0.1.2)
> 
> Host:
> wtap0 (WinTAP 10.0.1.2 255.255.255.0 10.0.1.255 gw 192.168.2.254)
> phys (Wifi 192.168.2.23 255.255.255.0 192.168.2.255 gw 192.168.2.254)
> 
>  +---------------------+        +-------------------------+
>  |   Colinux guest     |        |        WinXP host       |     +-----+
>  |               eth0  +<------>+ wtap0              phys +<--->+lan
>  |                     |   ^    |   +------>???<------+   |  ^  +-----+
>  +---------------------+   |    +-------------------------+  |
>                            |                                 |
>                         10.0.1.0                       192.168.2.0
>                         network                          network
> 
> Question now is how to make sure the wtap0 forwards all communication to phys
> and vice versa? 

This type of forwarding is named "bridge".

I'm prefer Windows bridge way. That I have tested with cable networks.
http://colinux.wikia.com/wiki/Network#TAP_with_Windows_Software_Bridge

The other way is Internet Connection Sharing (ICS).
This is perhaps the better way for WLAN.
http://colinux.wikia.com/wiki/Network#Internet_Connection_Sharing_.28ICS.29
"Networking" in
http://www.ibm.com/developerworks/library/l-virtualization-colinux/

-- 
Henry N.

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.

Re: [coLinux-users] Creating a development environment

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

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

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.

[coLinux-users] Creating a development environment

[Antony B. <at...@ms...>]

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?
 
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).
 
Many thanks in advance for any help/suggestions that people may provide,
 
Best Regards,
 
Antony Barton
_________________________________________________________________
Welcome to the next generation of Windows Live
http://www.windowslive.co.uk/get-live

Re: [coLinux-users] Private Network and wireless trouble

[Mike <dis...@bo...>]

Mike <dispose02@...> writes:
The parent of this mail should be disgarded
It was posted before the actual question was added.
Excuse
Mike

Re: [coLinux-users] Private Network and wireless trouble

[Mike <dis...@bo...>]

> > I connect to internet through a router using wep encryption and fixed IP 
> > adresses.
> > 
> > The host has a wifi card (ZyDas zd1211, usb), 
> > -MAC 00:11:E2:00:EA:93
> > -ip 192.168.2.23 (name PhysicalNetwork)
> > -gw 192.168.2.254
> > -pcap-bridge 192.168.2.24 (Colinux-TAP-external-network)
> > -taptun 192.168.100.1 (Colinux-TAP-guest-network)
> > 
> > 
> > The guest (Archlinux, runs squid),has
> > eth0: 192.168.2.25  (name Colinux-TAP-external-network)
> > eth1: 192.168.100.2 (name Colinux-TAP-guest-network)
> > 
> > The connection to the guest through 192.168.100.1-192.168.100.2 works.
> > 
> 
> Hope, we talk about a scene, that was in wiki as
> http://colinux.wikia.com/wiki/Network#TAP_-_Private_Connection_with_Hosting_OS
Yep, that's exactly what I want.

-snip- 
> eth0 should not bridge to any "TAP". The "pcap-bridge 192.168.2.24"
> should configure to your real LAN "(name PhysicalNetwork)" or the name
> of WiFI card. But, I'm afraid pcap-bridge does not work for your card.
> Some times helps to disable CRC checksum in this card. Some Access
> points don't allow to injecting different MAC on same air channel. In
> that case pcap-bridge would never work.
I cannot find where to disable CRC checksum in this ZyDas adapter. Also tried
another USB adapter (Netgear) same problem, so I've given up trying to inject
straight into the Wifi adapter. Pity that it does not work, in my other PC
(wired) it works perfect.

-snip
> 
> An other way would better work: Let windows bridge the WiFi with you
> second TAP (Colinux-TAP-external-network), hope this is the name. You
> needs to have 2 Win32-TAP drivers for that scenario and you must give
> the right names in the colinux config, autodetection does not work with
> more as one TAP-Win32.

OK the scenario would than be: 
(for simplicity lets forget the host->guest connection for now)

Internet Router: 192.168.2.254

Colinux:
eth0: (taptun 10.0.1.1 255.255.255.0 10.0.1.255 gw 10.0.1.2)

Host:
wtap0 (WinTAP 10.0.1.2 255.255.255.0 10.0.1.255 gw 192.168.2.254)
phys (Wifi 192.168.2.23 255.255.255.0 192.168.2.255 gw 192.168.2.254)

 +---------------------+        +-------------------------+
 |   Colinux guest     |        |        WinXP host       |     +-----+
 |               eth0  +<------>+ wtap0              phys +<--->+lan
 |                     |   ^    |   +------>???<------+   |  ^  +-----+
 +---------------------+   |    +-------------------------+  |
                           |                                 |
                        10.0.1.0                       192.168.2.0
                        network                          network

Question now is how to make sure the wtap0 forwards all communication to phys
and vice versa? 


> Don't use the same MAC more as ones, this would never work.
OK that's clear

> 
> iwconfig is not usable inside coLinux. The client does not know the
> external hardware (wifi, ethernet cable, or DSL modem).
OK.

Mike

Re: [coLinux-users] Private Network and wireless trouble

[Mike <dis...@bo...>]

> > I connect to internet through a router using wep encryption and fixed IP 
> > adresses.
> > 
> > The host has a wifi card (ZyDas zd1211, usb), 
> > -MAC 00:11:E2:00:EA:93
> > -ip 192.168.2.23 (name PhysicalNetwork)
> > -gw 192.168.2.254
> > -pcap-bridge 192.168.2.24 (Colinux-TAP-external-network)
> > -taptun 192.168.100.1 (Colinux-TAP-guest-network)
> > 
> > 
> > The guest (Archlinux, runs squid),has
> > eth0: 192.168.2.25  (name Colinux-TAP-external-network)
> > eth1: 192.168.100.2 (name Colinux-TAP-guest-network)
> > 
> > The connection to the guest through 192.168.100.1-192.168.100.2 works.
> > 
> 
> Hope, we talk about a scene, that was in wiki as
> http://colinux.wikia.com/wiki/Network#TAP_-_Private_Connection_with_Hosting_OS
Yep, that's exactly what I want.

-snip- 
> eth0 should not bridge to any "TAP". The "pcap-bridge 192.168.2.24"
> should configure to your real LAN "(name PhysicalNetwork)" or the name
> of WiFI card. But, I'm afraid pcap-bridge does not work for your card.
> Some times helps to disable CRC checksum in this card. Some Access
> points don't allow to injecting different MAC on same air channel. In
> that case pcap-bridge would never work.
I cannot find where to disable CRC checksum in this ZyDas adapter. Also tried
another USB adapter (Netgear) same problem, so I've given up trying to inject
straight into the Wifi adapter. Pity that it does not work, in my other PC
(wired) it works perfect.

-snip
> 
> An other way would better work: Let windows bridge the WiFi with you
> second TAP (Colinux-TAP-external-network), hope this is the name. You
> needs to have 2 Win32-TAP drivers for that scenario and you must give
> the right names in the colinux config, autodetection does not work with
> more as one TAP-Win32.

OK the scenario would than be: 
(for simplicity lets forget the host->guest connection for now)

Internet Router: 192.168.2.254

Colinux:
eth0: (taptun 10.0.1.1 255.255.255.0 10.0.1.255 gw 10.0.1.2)

Host:
wtap0 (WinTAP 10.0.1.2 255.255.255.0 10.0.1.255 gw 192.168.2.254)
phys (Wifi 192.168.2.23 255.255.255.0 192.168.2.255 gw 192.168.2.254)


 +---------------------+        +-------------------------+
 |   Colinux guest     |        |        WinXP host       |     +-----+
 |               eth0  +<------>+ wtap0              phys +<--->+lan
 |                     |   ^    |   +------>???<------+   |  ^  +-----+
 +---------------------+   |    +-------------------------+  |
                           |                                 |
                        10.0.1.0                       192.168.2.0
                        network                          network
 


> Don't use the same MAC more as ones, this would never work.
OK that's clear

> 
> iwconfig is not usable inside coLinux. The client does not know the
> external hardware (wifi, ethernet cable, or DSL modem).
OK.

Mike

[coLinux-users] &#191; La inflaci&#243; n y los cursos de las divisas afectan sus econom&#237; as? Sabemos como luchar contra eso.

[colip <co...@co...>]

xbjil"

Re: [coLinux-users] Running a NAS Server with CoLinux

[<Use...@zo...>]

bri...@gm...(Brian Weeden)  26.03.08 19:19


>Hi all.  New member here, hopefully with not a dumb question.  

Not html please, bcause it's palin for digst readers.

>I've done some searching around the mailing list archives and haven't seen
>anything about running a NAS server from within CoLinux.  

installin "samba" should work.
webmin, ladap, tinySQL for user management?



>I have a
>quad core system I just finished and was thinking of running the NAS
>server on it instead of having a whole extra box running.  

Typically a NAS is requred for "shared" data and for data reduncy.

>Do you
>think it would be possible?  I would love to be able to find a way to
>use the FreeNAS distro for this.  

FreeNAS is based ion FreeBSD, that's not yet another linux distro.
So a non linux geuast depened VM would be easier see vmware,virtual box, xen.

>I do have some experience with Linux
>(run Ubuntu on my laptop) but not much re-compiling kernels.

do 
aptitude install samba  pureftp

see Webmin,SysCP, AHCS, ISPConfig,ispCP,CpVES for User mangement

[coLinux-users] Running a NAS Server with CoLinux

[Brian W. <bri...@gm...>]

Hi all.  New member here, hopefully with not a dumb question.  I've done
some searching around the mailing list archives and haven't seen anything
about running a NAS server from within CoLinux.  I have a quad core system I
just finished and was thinking of running the NAS server on it instead of
having a whole extra box running.  Do you think it would be possible?  I
would love to be able to find a way to use the FreeNAS distro for this.  I
do have some experience with Linux (run Ubuntu on my laptop) but not much
re-compiling kernels.

Thanks!

-----
Brian Weeden
Technical Consultant
Secure World Foundation

Re: [coLinux-users] Problems on Vista Home Edition

[Paolo M. <pao...@gm...>]

Paolo Minazzi wrote:
> At home I have Vista Home Edition.
> I have some problems with colinux.
> Both 0.7.2 and 0.8.0 doesn't exit to console after "poweroff" and
> "halt" command. This happens only rarely, but almost everytime my
> colinux stops on "System halted" message, then I have to close
> manually the console.

Have you set the environment in batch?
 set COLINUX_CONSOLE_EXIT_ON_DETACH=1

	No ! In XP I don't have this variable setted but it works.
	I will try! I can try only at home. At work I have only XP, at home I
have Vista.

Is the FLTK-console Attached or Detached?

	I use only CONSOLE-NT. I don't use FLTK !
	I think (I'm sure 90% :=) ) that it is deteach. I would like to
verify it, but I'm almost sure.

Have you the last lines from the output of colinux-daemon.exe? (after
the power off), for example
 EXT3 FS on cobd0, internal journal
 System halted.
 colinux: Linux VM terminated
 colinux: halted, exiting.


	darkstar login: root
	Linux 2.6.22.18-co-0.8.0.
	Last login: Sun Mar 23 16:13:14 +0100 2008 on tty1.
	You have mail.
	root@darkstar:~# poweroff

	Broadcast message from root (tty1) (Sun Mar 23 16:14:28 2008):
	INIT: Switching to runlevel: 0
	INIT: Sending processes the TERM signal
	root@darkstar:~#
	The system is going down for system halt NOW!
	INIT: Sending processes the KILL signal
	Running shutdown script /etc/rc.d/rc.0:
	Saving system time to the hardware clock (localtime).
	hwclock is unable to get I/O port access:  the iopl(3) call failed.
	smbd: no process killed
	nmbd: no process killed
	Unmounting remote filesystems.
	Saving random seed from /dev/urandom in /etc/random-seed.
	Turning off swap.
	Unmounting local file systems.
	Remounting root filesystem read-only.
	System halted.

Have you tryed the menu in fltk console: Monitor - Shudown?
The same as you run the command: "shutdown -h now"

	I have tried poweroff and halt commands.
	I don't use FLTK.

> An other small problem is this.
> I have installed the driver (linux.sys).
> Then I use colinux and all is ok (I have only the problem of exit that
> I have explained before).
> When I restart the system and I launch the BAT that starts colinux,
> appears a message that tell to check the driver status.
> The driver is installed ! If I remove the driver and reinstall it, all works.
> But If I restarted the system there is the same problem. The daemon
> tell to check the driver status .....

Hm. First check the driver status with Windows tools. Open your hardware
manager, enable "see all hidden devices" and say is the coLinux driver
in running mode? If not, try to start it. Stays the "Start type" on
"automatic"? Any errors in the driver properties?
(German howto find coLinux driver in Windows Device Manager:
http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.png,
http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.png)

What is the output of "colinux-daemon --status-driver" in the line
"current state:..." if the driver is not usable?


	This is he output
	
	C:\coLinux-0.8.0>colinux-daemon.exe -t nt @norm
	Cooperative Linux Daemon, 0.8.0
	Daemon compiled on Fri Mar 21 18:14:03 2008

	colinux: manager open: Impossibile trovare il file specificato. (in
englishlanguage, "Impossible to find the specified file");
	daemon: exit code 82c7400e
	daemon: can't access CoLinuxDriver, please check status driver!



	===========================================
	norm
	===========================================
	kernel=vmlinux
	mem=128
	cobd0=c:\users\paolo\colinux-7.1\_base.img
	cobd1=\Device\CdRom0
	cobd2=\Device\Harddisk0\Partition4
	ro
	root=/dev/cobd0
	cofs0=c:\

Sorry, have no Vista running.

	I'm sorry I had not attached exact logs in my previous email.
	In the next emails I will try to be more precise. ;=)

	Thanks,
	Paolo Minazzi

Re: [coLinux-users] Problems on Vista Home Edition

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

Paolo Minazzi wrote:
> At home I have Vista Home Edition.
> I have some problems with colinux.
> Both 0.7.2 and 0.8.0 doesn't exit to console after "poweroff" and
> "halt" command. This happens only rarely, but almost everytime my
> colinux stops on "System halted" message, then I have to close
> manually the console.

Have you set the environment in batch?
  set COLINUX_CONSOLE_EXIT_ON_DETACH=1

Is the FLTK-console Attached or Detached?

Have you the last lines from the output of colinux-daemon.exe? (after
the power off), for example
  EXT3 FS on cobd0, internal journal
  System halted.
  colinux: Linux VM terminated
  colinux: halted, exiting.

Have you tryed the menu in fltk console: Monitor - Shudown?
The same as you run the command: "shutdown -h now"

> An other small problem is this.
> I have installed the driver (linux.sys).
> Then I use colinux and all is ok (I have only the problem of exit that
> I have explained before).
> When I restart the system and I launch the BAT that starts colinux,
> appears a message that tell to check the driver status.
> The driver is installed ! If I remove the driver and reinstall it, all works.
> But If I restarted the system there is the same problem. The daemon
> tell to check the driver status .....

Hm. First check the driver status with Windows tools. Open your hardware
manager, enable "see all hidden devices" and say is the coLinux driver
in running mode? If not, try to start it. Stays the "Start type" on
"automatic"? Any errors in the driver properties?
(German howto find coLinux driver in Windows Device Manager:
http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.png,
http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.png)

What is the output of "colinux-daemon --status-driver" in the line
"current state:..." if the driver is not usable?

Sorry, have no Vista running.

-- 
Henry N.

Re: [coLinux-users] Private Network and wireless trouble

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

Hello Mike,

Mike schrieb:
> Hi,
> I've been trying to get the 'private network' design, as shown in the Network
> Howto (section 'Keep Windows off the network -- surf via Linux') to work. On my
> pc with wired internet connection it works like a charm, but now I'm trying to
> set it up on a pc with a wireless connection. Tried all kind of variants (w/wo
> loopback, taptun/pcap-bridge, various IP configurations, w/wo promisc) but did
> not succeed to get it to work. 
> 
> OS: WinXP pro and Archlinux on Colinux (0.7.2)
> 
> I connect to internet through a router using wep encryption and fixed IP 
> adresses.
> 
> The host has a wifi card (ZyDas zd1211, usb), 
> -MAC 00:11:E2:00:EA:93
> -ip 192.168.2.23 (name PhysicalNetwork)
> -gw 192.168.2.254
> -pcap-bridge 192.168.2.24 (Colinux-TAP-external-network)
> -taptun 192.168.100.1 (Colinux-TAP-guest-network)
> 
> 
> The guest (Archlinux, runs squid),has
> eth0: 192.168.2.25  (name Colinux-TAP-external-network)
> eth1: 192.168.100.2 (name Colinux-TAP-guest-network)
> 
> The connection to the guest through 192.168.100.1-192.168.100.2 works.
> 
> Now the simple question is: how do I get it to work?
> More precise:
> -When I use a loopback adapter in windows, what would the design look like (e.g.
> which IP addresses and gw's I should use ). What type of bridge I should use
> (the ICS or bridge) between PhysicalNetwork and Colinux-TAP-host?
> 
> -Can I also use pcap-bridge adapter on the client, to inject directly into the
> PhysicalNetwork adapter, should I, in that case, install the wireless extensions
> (iwconfig, etc) in the guest, or would the connection use the wireless-settings
> of the host? Should I provide a MAC address for Colinux-TAP-host (a unique one
> or a copy of the PhysicalNetwork adapter)
> 
> Lots of questions, but I would love to get this to work...

true lot of. :-)

Hope, we talk about a scene, that was in wiki as
http://colinux.wikia.com/wiki/Network#TAP_-_Private_Connection_with_Hosting_OS

First you should configure the networks separately. I see, eth1 is
working for you - the connection between host and guest. Disable eth1
while you configure the eth0. After both of network works separately,
you can enable both at same time.

eth0 should not bridge to any "TAP". The "pcap-bridge 192.168.2.24"
should configure to your real LAN "(name PhysicalNetwork)" or the name
of WiFI card. But, I'm afraid pcap-bridge does not work for your card.
Some times helps to disable CRC checksum in this card. Some Access
points don't allow to injecting different MAC on same air channel. In
that case pcap-bridge would never work.

Check the outgoing and response of network with
http://www.wireshark.org/ on your WiFi. Test to send a Ping to your
router, and watch the answer from your router. I currently not know the
state of wireshark. Have it a option to inject (send) ping packets? If
yes, try it with this tool. It uses also the WinPcap, the same coLinux
use for pcap-bridge.

An other way would better work: Let windows bridge the WiFi with you
second TAP (Colinux-TAP-external-network), hope this is the name. You
needs to have 2 Win32-TAP drivers for that scenario and you must give
the right names in the colinux config, autodetection does not work with
more as one TAP-Win32.

Don't use the same MAC more as ones, this would never work.

iwconfig is not usable inside coLinux. The client does not know the
external hardware (wifi, ethernet cable, or DSL modem).

-- 
Henry N.

Re: [coLinux-users] DamnSmallLinux on colinux

[Mike <dis...@bo...>]

> > Meanwhile I've tried to setup archlinux, but for some reason I cannot
> > use pacman to install anything. On every soruce I get an 'directory not
> > found' or 'file not found', or so. Still the internet connection does work.
> > E.g. in the the Debian fs, I can use apt-get to install apps. Any
> > suggestions?
> 
> You use coLinux ArchLinux image? Or self made from scratch?
> 
> Here is a ready to use image:
> http://sourceforge.net/project/shownotes.php?release_id=436233&group_id=98788
> 
> This is a step by step howto create a new ArchLinux:
> http://wiki.archlinux.org/index.php/CoLinux
> 
> Some older docs, I'm afraid outdated:
> http://colinux.wikia.com/wiki/Howto:_ArchLinux_install_from_iso_with_rescue_fs
> 
> Hope, you will find sugestions there.
> 
Finally I got Archlinux to work, problem was in the TAP adapter naming. That is
solved now. Updated the Archlinux packages, installed squid and webmin. All work
perfect now. Can use Colinux as proxy without noticable performance reduction!
I've given up installing DSL for now, I may try that later, my experience is
that DSL is extremely fast and small.
Thanks again
Mike

[coLinux-users] Private Network and wireless trouble

[Mike <dis...@bo...>]

Hi,
I've been trying to get the 'private network' design, as shown in the Network
Howto (section 'Keep Windows off the network -- surf via Linux') to work. On my
pc with wired internet connection it works like a charm, but now I'm trying to
set it up on a pc with a wireless connection. Tried all kind of variants (w/wo
loopback, taptun/pcap-bridge, various IP configurations, w/wo promisc) but did
not succeed to get it to work. 

OS: WinXP pro and Archlinux on Colinux (0.7.2)

I connect to internet through a router using wep encryption and fixed IP 
adresses.

The host has a wifi card (ZyDas zd1211, usb), 
-MAC 00:11:E2:00:EA:93
-ip 192.168.2.23 (name PhysicalNetwork)
-gw 192.168.2.254
-pcap-bridge 192.168.2.24 (Colinux-TAP-external-network)
-taptun 192.168.100.1 (Colinux-TAP-guest-network)


The guest (Archlinux, runs squid),has
eth0: 192.168.2.25  (name Colinux-TAP-external-network)
eth1: 192.168.100.2 (name Colinux-TAP-guest-network)

The connection to the guest through 192.168.100.1-192.168.100.2 works.

Now the simple question is: how do I get it to work?
More precise:
-When I use a loopback adapter in windows, what would the design look like (e.g.
which IP addresses and gw's I should use ). What type of bridge I should use
(the ICS or bridge) between PhysicalNetwork and Colinux-TAP-host?

-Can I also use pcap-bridge adapter on the client, to inject directly into the
PhysicalNetwork adapter, should I, in that case, install the wireless extensions
(iwconfig, etc) in the guest, or would the connection use the wireless-settings
of the host? Should I provide a MAC address for Colinux-TAP-host (a unique one
or a copy of the PhysicalNetwork adapter)

Lots of questions, but I would love to get this to work...
Thanks 
Mike

[coLinux-users] Problems on Vista Home Edition

[Paolo M. <pao...@gm...>]

Hi,
At home I have Vista Home Edition.
I have some problems with colinux.
Both 0.7.2 and 0.8.0 doesn't exit to console after "poweroff" and
"halt" command. This happens only rarely, but almost everytime my
colinux stops on "System halted" message, then I have to close
manually the console.

An other small problem is this.
I have installed the driver (linux.sys).
Then I use colinux and all is ok (I have only the problem of exit that
I have explained before).
When I restart the system and I launch the BAT that starts colinux,
appears a message that tell to check the driver status.
The driver is installed ! If I remove the driver and reinstall it, all works.
But If I restarted the system there is the same problem. The daemon
tell to check the driver status .....

I don't know if these problems depends on my system.
Under XP I don't have these problems.

Any ideas ?

Regards
Paolo