colinux-users — coLinux users mailing list

Re: [coLinux-users] Starting sub-processes at higher priority

[Anshul <ans...@gm...>]

SSB0aG91Z2h0IG9mIHRoYXQgYnV0IHRoZXJlIGlzIG5vIHN0YXJ0LmV4ZSBpbiB3aW5kb3dzIFhQ
LgoKU3RhcnRpbmcgaXQgdmlhIGEgYmF0Y2ggc2NyaXB0IGRpZG4ndCB3b3JrIHRvbyBiZWNhdXNl
IHhtaW5nIGRpZG4ndApleGl0IHdpdGggY29MaW51eC4gIENhbiBJIHB1dCB0aGlzIHVwIGFzIGEg
ZmVhdHVyZSByZXF1ZXN0PyAgUGxlYXNlCmFsbG93IHByb2Nlc3MgcHJpb3JpdHkgdG8gYmUgc3Bl
Y2lmaWVkIGluIGV4ZWNYIGxpbmVzLiAgVGhhdCB3b3VsZApyZWFsbHkgaGVscCBiZWNhdXNlIHF1
aXRlIGEgbG90IG9mIHBlb3BsZSB3b3VsZCB3YW50IHRvIHJ1biB0aGVpciBYCnNlcnZlcnMgYW5k
IHNvdW5kIHNlcnZlcnMgYXQgaGlnaCBwcmlvcml0aWVzLgoKSSBydW4gcHVsc2VhdWRpbyBpbiBy
ZWFsdGltZSBhbmQgeG1pbmcgaW4gYWJvdmVub3JtYWwgIGFuZCBoYXZlIHRvCm1hbnVhbGx5IGVs
ZXZhdGUgdGhlaXIgcHJpb3JpdHkgYXQgZXZlcnkgY29MaW51eCBib290LgoKVGhhbmtzIQoKQW5z
aHVsCgpPbiAxMS8xLzA3LCBIZW5yeSBOZXN0bGVyIDxIZW5yeS5OZUBhcmNvci5kZT4gd3JvdGU6
Cj4gQW5zaHVsIHdyb3RlOgo+ID4gSXMgdGhlcmUgYSB3YXkgdG8gc3BlY2lmeSBwcm9jZXNzIHBy
aW9yaXR5IG9uIHRoZSBleGVjMCBsaW5lPyAgSSB3YW50Cj4gPiB0byBzdGFydCB4bWluZyB3aXRo
IGhpZ2hlciBwcmlvcml0eS4gIFJpZ2h0IG5vdywgSSBkbyB0aGF0IG1hbnVhbGx5IGF0Cj4gPiBl
YWNoIHN0YXJ0Lgo+Cj4gTm8uIGV4ZWMwIGhhcyBubyBvcHRpb25zLiBJIHRoaW5rLCB5b3UgY2Fu
IHVzZSB0aGUgIlNUQVJULkVYRSIgYXMKPiBjb21tYW5kIHdpdGggcHJpb3JpdHkgYW5kIHhtaW5n
IGFzIHBhcmFtZXRlci4KPgo+IC0tCj4gSGVucnkgTi4KPgoKCi0tIApJIGhhdmUgbm8gc3BlY2lh
bCB0YWxlbnRzLiBJIGFtIG9ubHkgcGFzc2lvbmF0ZWx5IGN1cmlvdXMuCiAgIC0tQWxiZXJ0IEVp
bnN0ZWluCi0tCmh0dHA6Ly93d3cuY21pLmFjLmluL35hbnNodWwvCmh0dHA6Ly9iYWJvb25sb2dp
Yy5jb20KLS0K4KSF4KSC4KS24KWB4KSyICDgpJbgpILgpKHgpYfgpLLgpLXgpL7gpLIK

Re: [coLinux-users] Starting sub-processes at higher priority

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

Anshul wrote:
> Is there a way to specify process priority on the exec0 line?  I want
> to start xming with higher priority.  Right now, I do that manually at
> each start.

No. exec0 has no options. I think, you can use the "START.EXE" as 
command with priority and xming as parameter.

-- 
Henry N.

[coLinux-users] Starting sub-processes at higher priority

[Anshul <ans...@gm...>]

Hi!

Is there a way to specify process priority on the exec0 line?  I want
to start xming with higher priority.  Right now, I do that manually at
each start.

Thanks,

Anshul

[coLinux-users] 87% de la gente de su edad no est&#225; n satisfechas con su salario. &#191; C&#243; mo cambiar eso?

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

axdbqntv."|"ikafuo

Re: [coLinux-users] telnet problem

[Armin K. <arm...@lo...>]

Thanks for your help.

1. The file
    /use/lib/pt_chown
    exits

2. Enabling pty support in the kernel
    How could i do this without recompiling the kernel?
    Which kernel module do i have to load?
	
Thanks for you help.
Armin
	


Rainer Zocholl schrieb:
> arm...@lo...(Armin Kurz)  09.10.07 08:04
> 
> Once upon a time "Armin Kurz " shaped the electrons to say...
> 
>> Hi there.
> 
>> I use coLinux on Windows XP SP2.
>> I installed coLinux-0.7.1-20070326.exe and 
>> Ubuntu-6.06.1.ext3.1gb.
>> Everything works fine.
> 
>> I installed telnetd (yes, it is not save, i know!).
> 
> How did you it install it?
> 
> Why not use sshd?
> 
> 
>> After:
> 
>> telnet localhost
> 
>> This message is on the console:
> 
>> Trying 127.0.0.1...
>> Connected to localhost.localdomain.
>> Escape character is '^]'.
>> telnetd: getpty: No such file or directory
>> .
>> Connection closed by foreign host.
> 
>> The devpts fs seems to be mounted (mount -l says it is).
> 
>> So, what is the problem?
> 
> I tried it with debian 4.0:
> package "harden" etc.  was removed, but after a
> #apitude reinstall telnetd
> telnetd it works.
> So a problem of ubuntu or the kernel?
> 
> colinux:~# uname -a
> Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Wed Sep 12 11:35:56 CEST 2007 i686 GNU/Linux
> 
> If not:
> googel says after asking for "telnetd: getpty: No such file or directory":
> 
> http://lists.arm.linux.org.uk/pipermail/linux-arm/2004-July/008045.html
> 
>  I got this error message in the past and it turned out to be a missing
>  file, /usr/libexec/pt_chown, which comes with glibc. Simply install it
>  on your target. 
>  Enabling pty support in the kernel might also be useful.
> 
> 
> 
> 
> colinux:~# ll /dev/pts/0
> crw------- 1 root tty 136, 0 2007-10-09 19:52 /dev/pts/0
> 
> 
> and did i already mention:
> [You shouldn't be using telnetd]
> 
> 
> 
> 
> HTH
> Rainer
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 

-- 
Armin Kurz
Entwicklung

Lobster GmbH
Hauptstr. 67
82327 Tutzing

Tel: +49 (8158) 9 0766 - 0
Fax: +49 (8158) 9 0766 - 99

arm...@lo...
http://www.lobster.de
-------------------------------

HRB 167720
Amtsgericht München
Geschäftsführung: Dr. Martin Fischer

[coLinux-users] =?utf-8?b?15DXldeo15kg15DXldeoID4g15DXqteoINeQ?= =?utf-8?b?15nXoNeY16jXoNeYINeR157Xl9eZ16gg157XqteV16c=?=

[<or...@gm...>]

This is a text part of the message.
It is shown for the users of old-style e-mail clients

Re: [coLinux-users] telnet problem

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

arm...@lo...(Armin Kurz)  09.10.07 08:04

Once upon a time "Armin Kurz " shaped the electrons to say...

>Hi there.

>I use coLinux on Windows XP SP2.
>I installed coLinux-0.7.1-20070326.exe and 
>Ubuntu-6.06.1.ext3.1gb.
>Everything works fine.

>I installed telnetd (yes, it is not save, i know!).

How did you it install it?

Why not use sshd?


>After:

>telnet localhost

>This message is on the console:

>Trying 127.0.0.1...
>Connected to localhost.localdomain.
>Escape character is '^]'.
>telnetd: getpty: No such file or directory
>.
>Connection closed by foreign host.

>The devpts fs seems to be mounted (mount -l says it is).

>So, what is the problem?

I tried it with debian 4.0:
package "harden" etc.  was removed, but after a
#apitude reinstall telnetd
telnetd it works.
So a problem of ubuntu or the kernel?

colinux:~# uname -a
Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Wed Sep 12 11:35:56 CEST 2007 i686 GNU/Linux

If not:
googel says after asking for "telnetd: getpty: No such file or directory":

http://lists.arm.linux.org.uk/pipermail/linux-arm/2004-July/008045.html

 I got this error message in the past and it turned out to be a missing
 file, /usr/libexec/pt_chown, which comes with glibc. Simply install it
 on your target. 
 Enabling pty support in the kernel might also be useful.




colinux:~# ll /dev/pts/0
crw------- 1 root tty 136, 0 2007-10-09 19:52 /dev/pts/0


and did i already mention:
[You shouldn't be using telnetd]




HTH
Rainer

[coLinux-users] telnet problem

[Armin K. <arm...@lo...>]

Hi there.

I use coLinux on Windows XP SP2.
I installed coLinux-0.7.1-20070326.exe and Ubuntu-6.06.1.ext3.1gb.
Everything works fine.

I installed telnetd (yes, it is not save, i know!).

After:

telnet localhost

This message is on the console:

Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
telnetd: getpty: No such file or directory
.
Connection closed by foreign host.

The devpts fs seems to be mounted (mount -l says it is).

So, what is the problem?

Thanks for your help.
Armin

Re: [coLinux-users] slirp nameserver problem - can not resolve name

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

Ken Perl wrote:
> I configured slirp network that works fine before, but today maybe our
> company's network is changed but I'm not sure what is changed. now I
> can not connect to other machines within our company anymore, I can
> before.
> 
> the colinux(debian) ip is 10.0.2.15, the netstat -r output says the
> default route is 10.0.2.2, the dns namserver is 10.0.2.3, I can ping
> the route 10.0.2.2, and I can ping the 200.10.2.83 but can't ping its
> hostname. ping from my XP to the hostname is ok.
> 
> any idea what's wrong with the nameserver 10.0.2.3?
> 

Inside coLinux check the DNS configuration with
   host -v name
This give informations what your gets from dns sever for the host with 
'name'.

10.0.2.3 is mapped inside slirp to the first dns server from your 
windows side. Perhaps you have more dns servers and the first is not 
usable? In this case, setup the second dns server from windows (ipconfig 
/all) also as secondary dns inside your coLinux, by adding it to 
/etc/resolve.conf.

PS: Ping from coLinux Slirp to outside is not supported for all hosts. 
You can ping to the router 10.0.2.2 alltimes. To other hosts only, if 
thre runs an UDP ECHO server (port 7/udp).

-- 
Henry

[coLinux-users] slirp nameserver problem - can not resolve name

[Ken P. <ke...@gm...>]

I configured slirp network that works fine before, but today maybe our
company's network is changed but I'm not sure what is changed. now I
can not connect to other machines within our company anymore, I can
before.

the colinux(debian) ip is 10.0.2.15, the netstat -r output says the
default route is 10.0.2.2, the dns namserver is 10.0.2.3, I can ping
the route 10.0.2.2, and I can ping the 200.10.2.83 but can't ping its
hostname. ping from my XP to the hostname is ok.

any idea what's wrong with the nameserver 10.0.2.3?

-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'

[coLinux-users] Can't connect to the internet anymore... very strange

[Andrew B. <bah...@ya...>]

I've been using CoLinux (0.6.4) for quite a while, and
ever since I ran the Network Setup Wizard (for an
unrelated purpose), I
can't access the internet anymore. I had it up (via
slirp) without
problem until a few days ago. The TAP connection I use
to connect to
Windows is unaffected (it works fine), and Windows can
connect to the internet. I'm
using dialup (if that makes a difference). I tried
uninstalling 0.6.4 and installing 0.7.1, but that
didn't make a difference.





      ____________________________________________________________________________________
Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more!
http://tv.yahoo.com/collections/3658 

Re: [coLinux-users] how to determine driver status/version

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

Hen...@Ar...(Henry Nestler)  11.09.07 21:11

>>
>> API version: Ok, but is that really the new "linux.sys"

>true, an interesting question. ;-) Would add the build date next
>times.

I assume that would help a lot to avoid those problems using
out-of-date drivers.
There might be problems in the driver not caused by a changed API.
So it would be easier to make a "status quo".

>> I would like to make a batch that compares the version running with
>> that in the current directory.

>You can oly unpack from ZIP to other location and compair it. (or
>perhaps directly compair with zip).

Then i know that the one on the disk right or wrong, but don't know
if it is actually running!

>We would change the colinux API, after the driver interface was
>changed. This avoids you from starting colinux with old driver and new
>daemons. Think, you no need extra batch tests.

I would like to warn the user and give him a chance to invoke the new
driver from inside of the batch.

Rainer

Re: [coLinux-users] how to determine driver status/version

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

Rainer Zocholl wrote:
> C:\coLinux>colinux-daemon.exe --remove-driver
> Cooperative Linux Daemon, 0.8.0
> Compiled on Sep 10 2007 09:00:06
> 
> 
> Thinking loud:
> 
>   How that?
>   I would have expect here an older date.
> 
>   Or is that just the date of the colinux-daemon.exe not 
>   of the driver been removed?

is the build date of colinux-daemon.exe you used for remove or status.

> checking if the driver is installed
> current state: 4 (fully initialized)
> current number of monitors: 0
> current linux api version: 10
> current periphery api version: 20
> 
> API version: Ok, but is that really the new "linux.sys" 

true, an interesting question. ;-) Would add the build date next times.

> Is there a way to test the current running version of 
> the linux.sys from command line?

no.

> I would like to make a batch that compares the version running with
> that in the current directory.

You can oly unpack from ZIP to other location and compair it. (or 
perhaps directly compair with zip).

> But linkx.sys does not seem to have a version.rc?
> But i assume file date would be sufficient too.

Right. linux.sys has no windows-versions informations. Think, this would 
also no help, because we do not add the build date to any rc file. 
Typicaly users would no have problems because two releases would mostly 
no have the same API. And anyboda would unpack all files from ZIP to 
same place (driver and daemon).

We would change the colinux API, after the driver interface was changed. 
This avoids you from starting colinux with old driver and new daemons. 
Think, you no need extra batch tests.

-- 
Henry

Re: [coLinux-users] Install colinux on Linux?

[Samir K. <sam...@gm...>]

Thanks Henry. Will try it out tonight.

~Samir

On 9/11/07, Henry Nestler <Hen...@ar...> wrote:
>
> Samir,
>
> host kernel 2.6.20 and later uses hard coded regparms.
> You need to patch and recompile the host kernel, before you can run
> colinux there, see attachment.
>
> Disable regparms makes the host a lidle slower.
>
> But currently no other way is usabable to run coLinux with Linux as host
> there. The problem are the prelinked components for the module
> colinux.ko . Problems comes from coLinux build system. If all kernel
> files (for colinux.ko) would build with the host-kernel build system,
> then regparms can enable...
>
> --
> Henry
>
>

Re: [coLinux-users] Install colinux on Linux?

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

Samir,

host kernel 2.6.20 and later uses hard coded regparms.
You need to patch and recompile the host kernel, before you can run 
colinux there, see attachment.

Disable regparms makes the host a lidle slower.

But currently no other way is usabable to run coLinux with Linux as host 
there. The problem are the prelinked components for the module 
colinux.ko . Problems comes from coLinux build system. If all kernel 
files (for colinux.ko) would build with the host-kernel build system, 
then regparms can enable...

-- 
Henry

[coLinux-users] how to determine driver status/version

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

Hello

downladed new auto build
Overwrite old binaries

did:

C:\coLinux>colinux-daemon.exe --remove-driver
Cooperative Linux Daemon, 0.8.0
Compiled on Sep 10 2007 09:00:06


Thinking loud:

  How that?
  I would have expect here an older date.

  Or is that just the date of the colinux-daemon.exe not 
  of the driver been removed?

C:\coLinux>colinux-daemon.exe --status-driver
Cooperative Linux Daemon, 0.8.0
Compiled on Sep 10 2007 09:00:06

checking if the driver is installed
current state: 4 (fully initialized)
current number of monitors: 0
current linux api version: 10
current periphery api version: 20

API version: Ok, but is that really the new "linux.sys" 

Is there a way to test the current running version of 
the linux.sys from command line?
I would like to make a batch that compares the version running with
that in the current directory.
If the version do not match it should issue a warning and reinstall
the new driver.

But linkx.sys does not seem to have a version.rc?
But i assume file date would be sufficient too.


Rainer---<=====>                         Vertraulich
             //  
           //                              
         <=====>--------------ocholl, Kiel, Germany ------------

Re: [coLinux-users] Install colinux on Linux?

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

Samir Kuthiala wrote:
> I am having some trouble following the guide. I installed fltk-1.1.6 
> from source into ~/i686-pc-linux-local. After that I ran the following 
> commands:
> 
>>  export PATH=$HOME/i686-linux-local/bin:$PATH
>>  ./configure --target=i686-pc-linux-local 
> --targetkerneldir=~/Downloads/devel-colinux-20070819 
> --hostkerneldir=/lib/modules/2.6.20-16-generic/build

'targetkerneldir' should point to patched and configured kernel source 
for colinux guest (kernel 2.6.22 for snapshot 20070819)

Check that there exist the file
$HOME/Downloads/devel-colinux-20070819/include/linux/cooperative.h
(and mutch more kernel headers)

Replace the '~' with '$HOME', im not shure working with '~'.

After give configure a new (empty) path to targetkerneldir, you can get 
the patched kernel source by:
   "make kernel"
in source of coLinux. You can break (CTRL-C) the build after you see the 
message "Configuring Kernel 2.6.22" - if you not need the kernel build 
self. But in normal case, you need the kernel for running coLinux later. 
So, let the kernel build, before build the daemons for linux host.

Kernel build and damons build use the same config. So, it should work.

>>  export COLINUX_TARGET_KERNEL_PATH=~/Downloads/devel-colinux-20070819
>>  export COLINUX_HOST_KERNEL_DIR=/lib/modules/2.6.20-16-generic/build
>>  export COLINUX_HOST_OS=linux
>>  export COLINUX_CFLAGS="-I$HOME/i686-pc-linux-local/include"
>>  export COLINUX_LFLAGS="-L$HOME/i686-pc-linux-local/lib"
>>  make HOSTOS=linux colinux

You stay in the directory where Makefile.linux exist? If yes, you not 
need the follows: COLINUX_TARGET_KERNEL_PATH, COLINUX_HOST_KERNEL_DIR, 
COLINUX_HOST_OS. This all comes from config file, you find in 
bin/user-build.cfg (created by coLinux 'configure').

This lines should be enouth:
export COLINUX_CFLAGS="-I$HOME/i686-pc-linux-local/include"
export COLINUX_LFLAGS="-L$HOME/i686-pc-linux-local/lib"
make HOSTOS=linux colinux


> [...]
> In file included from src/colinux/common/config.h:13,
>                  from src/colinux/user/daemon.h:14,
>                  from src/colinux/os/linux/user/daemon/main.c:18:
> src/colinux/common/common.h:28:31: error: linux/cooperative.h: No such 

The daemon don't find the colinux kernel headers.

PS:
I'm not know your gcc version from your distro. The snapshot you use, 
only works with gcc 4.1.x - If your local gcc is not 4.1.x, you need to 
use the more complicated parameter '--gcc-guest-build'. Or use latest 
source, there have opened for more gcc versions. 
http://www.henrynestler.com/colinux/autobuild/devel-20070909/colinux-0.8.0-20070909.src.tgz

-- 
Henry

Re: [coLinux-users] Install colinux on Linux?

[Samir K. <sam...@gm...>]

Hi Henry,

I am having some trouble following the guide. I installed fltk-1.1.6 from
source into ~/i686-pc-linux-local. After that I ran the following commands:

====================================================================================
>  export PATH=$HOME/i686-linux-local/bin:$PATH
> ./configure --target=i686-pc-linux-local
--targetkerneldir=~/Downloads/devel-colinux-20070819
--hostkerneldir=/lib/modules/2.6.20-16-generic/build
> export COLINUX_TARGET_KERNEL_PATH=~/Downloads/devel-colinux-20070819
> export COLINUX_HOST_KERNEL_DIR=/lib/modules/2.6.20-16-generic/build
> export COLINUX_HOST_OS=linux
> export COLINUX_CFLAGS="-I$HOME/i686-pc-linux-local/include"
> export COLINUX_LFLAGS="-L$HOME/i686-pc-linux-local/lib"
> make HOSTOS=linux colinux

====================================================================================

I have attached the error I get. Do you have any ideas as to what I am doing
wrong? I am running ubuntu 7.0.4 as my host system. Thanks.

================================================================================================================
make[2]: Entering directory
`/home/samir/Downloads/devel-colinux-20070819/src'
python ../bin/make.py colinux
/home/samir/Downloads/devel-colinux-20070819/bin/comake/lib.py:1:
DeprecationWarning: The sre module is deprecated, please import re.
  import sre, os
Analyzing target tree...
Target architecture not specified, defaulting to i386
Starting build
[colinux]
  [src/build]
    [src/colinux/os/linux/build/executables]
      [src/colinux/os/linux/build/colinux-daemon]
        [src/colinux/os/linux/user/daemon/daemon.o]
          [src/colinux/os/linux/user/daemon/main.o]
          Building: target requires creation
          gcc -Isrc -I~/Downloads/devel-colinux-20070819/include
-I~/Downloads/devel-colinux-20070819/include2
-I~/Downloads/devel-colinux-20070819/include -Wno-trigraphs
-fno-strict-aliasing -Wall -I/home/samir/i686-pc-linux-local/include -O2
-DCOLINUX -DCOLINUX_ARCH=linux -DCOLINUX_DEBUG -DCOLINUX_FILE_ID=0
-DCO_HOST_API -c src/colinux/os/linux/user/daemon/main.c -o
src/colinux/os/linux/user/daemon/main.o
In file included from src/colinux/common/config.h:13,
                 from src/colinux/user/daemon.h:14,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/common/common.h:28:31: error: linux/cooperative.h: No such file
or directory
In file included from src/colinux/user/daemon.h:14,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/common/config.h:178: error: 'CO_MODULE_MAX_COBD' undeclared here
(not in a function)
src/colinux/common/config.h:184: error: 'CO_MODULE_MAX_CONET' undeclared
here (not in a function)
src/colinux/common/config.h:189: error: 'CO_MODULE_MAX_COFS' undeclared here
(not in a function)
src/colinux/common/config.h:194: error: 'CO_MODULE_MAX_SERIAL' undeclared
here (not in a function)
src/colinux/common/config.h:204: error: 'CO_BOOTPARAM_STRING_LENGTH'
undeclared here (not in a function)
In file included from src/colinux/user/daemon.h:15,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/common/messages.h:17: error: expected declaration specifiers or
'...' before 'co_message_t'
src/colinux/common/messages.h:26: error: expected specifier-qualifier-list
before 'co_module_t'
src/colinux/common/messages.h:44: error: expected specifier-qualifier-list
before 'co_module_t'
src/colinux/common/messages.h:49: error: expected specifier-qualifier-list
before 'co_message_t'
src/colinux/common/messages.h:53: error: expected specifier-qualifier-list
before 'co_module_t'
src/colinux/common/messages.h:59: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:60: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:62: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:62: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:63: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:64: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:65: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/common/messages.h:66: error: expected declaration specifiers or
'...' before 'co_message_t'
src/colinux/common/messages.h:67: error: expected declaration specifiers or
'...' before 'co_message_t'
src/colinux/common/messages.h:69: error: expected ')' before '*' token
src/colinux/common/messages.h:70: error: expected ')' before '*' token
src/colinux/common/messages.h:74: error: expected ')' before 'module'
In file included from src/colinux/user/daemon.h:16,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/common/console.h:51: error: expected specifier-qualifier-list
before 'co_cursor_pos_t'
src/colinux/common/console.h:58: error: expected declaration specifiers or
'...' before 'co_console_message_t'
In file included from src/colinux/user/monitor.h:16,
                 from src/colinux/user/daemon.h:19,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/common/ioctl.h:45: error: expected specifier-qualifier-list
before 'co_info_t'
src/colinux/common/ioctl.h:96: error: expected specifier-qualifier-list
before 'co_module_t'
src/colinux/common/ioctl.h:157: error: expected specifier-qualifier-list
before 'co_termination_reason_t'
src/colinux/common/ioctl.h:176: error: expected specifier-qualifier-list
before 'co_termination_reason_t'
In file included from src/colinux/os/kernel/manager.h:13,
                 from src/colinux/os/user/manager.h:15,
                 from src/colinux/user/monitor.h:17,
                 from src/colinux/user/daemon.h:19,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/kernel/manager.h:89: error: expected declaration specifiers or
'...' before 'co_message_t'
In file included from src/colinux/os/user/manager.h:15,
                 from src/colinux/user/monitor.h:17,
                 from src/colinux/user/daemon.h:19,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/os/kernel/manager.h:27: error: expected declaration specifiers
or '...' before 'co_message_t'
In file included from src/colinux/user/daemon.h:19,
                 from src/colinux/os/linux/user/daemon/main.c:18:
src/colinux/user/monitor.h:29: error: expected declaration specifiers or
'...' before 'co_module_t'
src/colinux/user/monitor.h:47: error: expected declaration specifiers or
'...' before 'co_message_t'
In file included from src/colinux/os/linux/user/daemon/main.c:21:
src/colinux/user/debug.h:16: error: expected ')' before '*' token
Error: Target not build (TargetNotBuildError)
make[1]: *** [colinux] Error 1
make[1]: Leaving directory
`/home/samir/Downloads/devel-colinux-20070819/src'
make: *** [colinux] Error 2
===================================================================================================


Regards
Samir


On 9/4/07, Henry Nestler <Hen...@ar...> wrote:
>
> Samir Kuthiala wrote:
> > So I guess there is no way of using co-linux on linux? I like the idea
> > of using vserver but can vserver run colinux images directly?
>
> Read this "5.3. For Linux as host":
>
> http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/building
>
> You need to compile the module colinux.ko from source.
> Kernels with REGPARM enabled dosn't work as host. Current kernel 2.6.22
> does only work, if you remove the regparm parameter from host kernel
> Makefile (and recompile the host kernel!).
>
> --
> Henry
>

Re: [coLinux-users] CoLinux not booting (exit code 84814401)

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

The error says, that the driver linux.sys returns an error.
Please check, that the coLinux driver is properly installed:

   colinu-daemon --status-driver

Try follow steps to reenable the driver:
   colinu-daemon --remove-driver
   colinu-daemon --install-driver

Under some situatuations needs to reboot Windows between remove and install.

-- 
Henry

MarkBykerkKauffman wrote:
> I believe I'm seeing the exact same error and would like to know the fix too. 
> Here is what I see..
> D:\coLinux>colinux-daemon.exe -t nt -c D:\coLinux\default.colinux.xml
> Cooperative Linux Daemon, 0.6.4
> Compiled on Mon May 29 22:19:09 2006
> 
> mapping cobd0 to \DosDevices\D:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb
> mapping cobd1 to \DosDevices\D:\coLinux\swap_1024Mb
> error initializing
> daemon: exit code 84814401
> daemon: error - CO_RC_ERROR_ERROR, line 81, file
> colinux/os/current/user/manager.o (36)
> 
> I started getting this after I defragmented the D: drive. 
> 
> Here is Larry's
> 
> Larry Crouch-3 wrote:
>>
>> Here is the boot sequence:
>> E:\CoLinux>colinux-daemon.exe -c config.xml
>> Cooperative Linux Daemon, 0.6.4
>> Compiled on Mon May 29 22:19:09 2006
>>
>> mapping cobd0 to \DosDevices\E:\CoLinux\d.4gb
>> mapping cobd1 to \DosDevices\E:\CoLinux\swapfile
>> error initializing
>> daemon: exit code 84814401
>> daemon: error - CO_RC_ERROR_ERROR, line 81, file
>> colinux/os/current/user/manager.o (36)
>>

Re: [coLinux-users] CoLinux not booting (exit code 84814401)

[MarkBykerkKauffman <Mar...@ya...>]

Rebooting the host OS, the one made up in Redmond, fixed the problem.  After
the reboot, colinux started again with no issues.

-- 
View this message in context: http://www.nabble.com/CoLinux-not-booting-%28exit-code-84814401%29-tf4240639.html#a12582145
Sent from the colinux-users mailing list archive at Nabble.com.

Re: [coLinux-users] CoLinux not booting (exit code 84814401)

[MarkBykerkKauffman <Mar...@ya...>]

I believe I'm seeing the exact same error and would like to know the fix too. 
Here is what I see..
D:\coLinux>colinux-daemon.exe -t nt -c D:\coLinux\default.colinux.xml
Cooperative Linux Daemon, 0.6.4
Compiled on Mon May 29 22:19:09 2006

mapping cobd0 to \DosDevices\D:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb
mapping cobd1 to \DosDevices\D:\coLinux\swap_1024Mb
error initializing
daemon: exit code 84814401
daemon: error - CO_RC_ERROR_ERROR, line 81, file
colinux/os/current/user/manager.o (36)

I started getting this after I defragmented the D: drive. 

Here is Larry's

Larry Crouch-3 wrote:
> 
> 
> Here is the boot sequence:
> E:\CoLinux>colinux-daemon.exe -c config.xml
> Cooperative Linux Daemon, 0.6.4
> Compiled on Mon May 29 22:19:09 2006
> 
> mapping cobd0 to \DosDevices\E:\CoLinux\d.4gb
> mapping cobd1 to \DosDevices\E:\CoLinux\swapfile
> error initializing
> daemon: exit code 84814401
> daemon: error - CO_RC_ERROR_ERROR, line 81, file
> colinux/os/current/user/manager.o (36)
> 
> 
> Here is my xml file (comments removed):
> <?xml version="1.0" encoding="UTF-8"?>
> <colinux>
>     <block_device index="0" path="\DosDevices\E:\CoLinux\d.4gb"
> enabled="true" />
>     <block_device index="1" path="\DosDevices\E:\CoLinux\swapfile"
> enabled="true" />
>     <bootparams>root=/dev/cobd0</bootparams>
>     <initrd path="initrd.gz" />
>     <image path="vmlinux" />
>     <memory size="96" />
>     <network index="0" type="bridged" name="Physical"
> mac="34:56:78:9A:BC:DE" />
> </colinux>
> --
> Larry Crouch
> lc...@di...
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 

-- 
View this message in context: http://www.nabble.com/CoLinux-not-booting-%28exit-code-84814401%29-tf4240639.html#a12580420
Sent from the colinux-users mailing list archive at Nabble.com.

Re: [coLinux-users] Installing via debian-40r1-i386-businesscard.iso breaks after popularity-contest config

[Oscar U. <osc...@pr...>]

using workaround mentioned below got me past this issue e.g. mapping to
/dev/null Thanks "A workarrount is to remove the /dev/mem, /dev/kmem and
/dev/core or
re-create the nodes with device node 1:3, same as /dev/null."

  ----- Original Message -----
  From: "Oscar Usifer"
  To: "Henry Nestler"
  Subject: Re: [coLinux-users] Installing via
  debian-40r1-i386-businesscard.iso breaks after popularity-contest
  config
  Date: Fri, 7 Sep 2007 17:10:35 -0500

  OK tried devel-coLinux-20070819.exe, install hangs on "Configuring
  popularity-contest" with vc4 saying,

  init: Starting pid 6842, console /dev/vc/4: '/usr/bin/tail'
  init: Process '/usr/bin/tail -f /var/log/syslog' (pid 6842) exited.
  Scheduing it for restart.

  Thanks,
  OSC

    ----- Original Message -----
    From: "Henry Nestler"
    To: "Oscar Usifer"
    Subject: Re: [coLinux-users] Installing via
    debian-40r1-i386-businesscard.iso breaks after popularity-contest
    config
    Date: Fri, 07 Sep 2007 21:02:49 +0200


    Oscar Usifer wrote:
    > I am attempting to install 0.6.4-linux-2.6.11 with Debian
    > Etch[*1] according to the wiki instructions[*2] on WinXp
    Pro[*3].
    > I used fltk console invoked from cmd.exe after starting the
    > colinux service. I was able to get most of the way with
    "Install
    > the base system", then selected linux-image-2.6-686 at 79%
    > complete. A little later I am prompted for "Configuring
    > popularity-contest" install option which said, "The system may
    > anonymously supply the distribution developers with statistics
    > about the most used packages on this system...." I switched to
    > virtual console 1, and issued the mknod commands to create
    > /target/dev/cobd[0123] block device nodes, and modified
    > /target/etc/fstab. In virtual screen 4, I observed the final
    > lines as follows. Then responding either "Yes" or "No" results
    in
    > the colinux-daemon crashing without completing the base system
    > install (additional backtrace included below in dpkg.log), at
    > this point the fltk windows console process would detach.

    The coLinux 0.6.4 is not protected to read from /dev/mem. Some
    new
    distributions tries to read the BIOS strings from this - to get
    info about your hardware. This crashes the linux or some times
    the
    host.
    A workarrount is to remove the /dev/mem, /dev/kmem and /dev/core
    or
    re-create the nodes with device node 1:3, same as /dev/null.

    In the newer coLinux versions this was fixed:
    http://www.colinux.org/snapshots/

    >
    >
    > enabled=3D"true" />
    >
    > path=3D"\DosDevices\c:\coLinux\swap_device" enabled=3D"true" />
    >
    > path=3D"\DosDevices\c:\coLinux\debian-40r1-i386-businesscard.iso"
    > enabled=3D"true" />
    >
    > path=3D"\DosDevices\c:\coLinux\debian-40r1-initrd" enabled=3D"true"
    />
    > root=3D/dev/cobd2
    >
    > [IMAGE]
    >
    >
    >
    >

    The new versions have no more the XML config. Have transform it
    on
    the fly into a simple text file (untested, hope all is right):
    kernel=3Dvmlinux
    cobd0=3Dc:\coLinux\root.fs
    cobd1=3Dc:\coLinux\swap_device
    cobd2=3Dc:\coLinux\debian-40r1-i386-businesscard.iso
    cobd3=3Dc:\coLinux\debian-40r1-initrd
    root=3D/dev/cobd2
    initrd=3Ddebian-40r1-initrd.gz
    mem=3D512
    eth0=3Dtuntap
    eth1=3Dpcap-bridge,"Local Area Connection"

    The new coLinux does also support hda1, so you can replace cobd0
    directly with "hda1=3Dc:\coLinux\root.fs" and so on.

    Complete list of config params founds here:
    http://colinux.svn.sourceforge.net/svnroot/colinux/branches/stable/doc/=
colinux-daemon

    -- Henry


  -- We've Got Your Name @ Mail.com !!!
  Get a FREE E-mail Account Today - Choose From 100+ Domains
  -------------------------------------------------------------------------
  This SF.net email is sponsored by: Microsoft
  Defy all challenges. Microsoft(R) Visual Studio 2005.
  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  _______________________________________________
  coLinux-users mailing list
  coL...@li...
  https://lists.sourceforge.net/lists/listinfo/colinux-users

--=20
We've Got Your Name @ www.mail.com!!!
Get a FREE E-mail Account Today - Choose From 100+ Domains

Re: [coLinux-users] Installing via debian-40r1-i386-businesscard.iso breaks after popularity-contest config

[Oscar U. <osc...@pr...>]

 OK tried devel-coLinux-20070819.exe, install hangs on "Configuring
popularity-contest" with vc4 saying,

init: Starting pid 6842, console /dev/vc/4: '/usr/bin/tail'
init: Process '/usr/bin/tail -f /var/log/syslog' (pid 6842) exited.
Scheduing it for restart.

Thanks,
OSC

  ----- Original Message -----
  From: "Henry Nestler"
  To: "Oscar Usifer"
  Subject: Re: [coLinux-users] Installing via
  debian-40r1-i386-businesscard.iso breaks after popularity-contest
  config
  Date: Fri, 07 Sep 2007 21:02:49 +0200


  Oscar Usifer wrote:
  > I am attempting to install 0.6.4-linux-2.6.11 with Debian
  > Etch[*1] according to the wiki instructions[*2] on WinXp Pro[*3].
  > I used fltk console invoked from cmd.exe after starting the
  > colinux service. I was able to get most of the way with "Install
  > the base system", then selected linux-image-2.6-686 at 79%
  > complete. A little later I am prompted for "Configuring
  > popularity-contest" install option which said, "The system may
  > anonymously supply the distribution developers with statistics
  > about the most used packages on this system...." I switched to
  > virtual console 1, and issued the mknod commands to create
  > /target/dev/cobd[0123] block device nodes, and modified
  > /target/etc/fstab. In virtual screen 4, I observed the final
  > lines as follows. Then responding either "Yes" or "No" results in
  > the colinux-daemon crashing without completing the base system
  > install (additional backtrace included below in dpkg.log), at
  > this point the fltk windows console process would detach.

  The coLinux 0.6.4 is not protected to read from /dev/mem. Some new
  distributions tries to read the BIOS strings from this - to get
  info about your hardware. This crashes the linux or some times the
  host.
  A workarrount is to remove the /dev/mem, /dev/kmem and /dev/core or
  re-create the nodes with device node 1:3, same as /dev/null.

  In the newer coLinux versions this was fixed:
  http://www.colinux.org/snapshots/

  >
  >
  > enabled=3D"true" />
  >
  > path=3D"\DosDevices\c:\coLinux\swap_device" enabled=3D"true" />
  >
  > path=3D"\DosDevices\c:\coLinux\debian-40r1-i386-businesscard.iso"
  > enabled=3D"true" />
  >
  > path=3D"\DosDevices\c:\coLinux\debian-40r1-initrd" enabled=3D"true" />
  > root=3D/dev/cobd2
  >
  > [IMAGE]
  >
  >
  >
  >

  The new versions have no more the XML config. Have transform it on
  the fly into a simple text file (untested, hope all is right):
  kernel=3Dvmlinux
  cobd0=3Dc:\coLinux\root.fs
  cobd1=3Dc:\coLinux\swap_device
  cobd2=3Dc:\coLinux\debian-40r1-i386-businesscard.iso
  cobd3=3Dc:\coLinux\debian-40r1-initrd
  root=3D/dev/cobd2
  initrd=3Ddebian-40r1-initrd.gz
  mem=3D512
  eth0=3Dtuntap
  eth1=3Dpcap-bridge,"Local Area Connection"

  The new coLinux does also support hda1, so you can replace cobd0
  directly with "hda1=3Dc:\coLinux\root.fs" and so on.

  Complete list of config params founds here:
  http://colinux.svn.sourceforge.net/svnroot/colinux/branches/stable/doc/co=
linux-daemon

  -- Henry

--=20
We've Got Your Name @ www.mail.com!!!
Get a FREE E-mail Account Today - Choose From 100+ Domains

Re: [coLinux-users] Installing via debian-40r1-i386-businesscard.iso breaks after popularity-contest config

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

Oscar Usifer wrote:
> I am attempting to install 0.6.4-linux-2.6.11 with Debian Etch[*1] according to the wiki instructions[*2] on WinXp Pro[*3]. I used fltk console invoked from cmd.exe after starting the colinux service. I was able to get most of the way with "Install the base system", then selected linux-image-2.6-686 at 79% complete. A little later I am prompted for "Configuring popularity-contest" install option which said, "The system may anonymously supply the distribution developers with statistics about the most used packages on this system...." I switched to virtual console 1, and issued the mknod commands to create /target/dev/cobd[0123] block device nodes, and modified /target/etc/fstab. In virtual screen 4, I observed the final lines as follows. Then responding either "Yes" or "No" results in the colinux-daemon crashing without completing the base system install (additional backtrace included below in dpkg.log), at this point the fltk windows console process would detach. 

The coLinux 0.6.4 is not protected to read from /dev/mem. Some new 
distributions tries to read the BIOS strings from this - to get info 
about your hardware. This crashes the linux or some times the host.
A workarrount is to remove the /dev/mem, /dev/kmem and /dev/core or 
re-create the nodes with device node 1:3, same as /dev/null.

In the newer coLinux versions this was fixed:
http://www.colinux.org/snapshots/

> <colinux>
>     <block_device index="0" path="\DosDevices\c:\coLinux\root.fs" enabled="true" />
>     <block_device index="1" path="\DosDevices\c:\coLinux\swap_device" enabled="true" />
>     <block_device index="2" path="\DosDevices\c:\coLinux\debian-40r1-i386-businesscard.iso" enabled="true" />
>     <block_device index="3" path="\DosDevices\c:\coLinux\debian-40r1-initrd" enabled="true" />
>     <bootparams>root=/dev/cobd2</bootparams>
>     <initrd path="debian-40r1-initrd.gz" />
>     <image path="vmlinux" />
>     <memory size="512" />
>     <network index="0" type="tap"/>
>     <network index="1" name="Local Area Connection" type="bridged" />
> </colinux>

The new versions have no more the XML config. Have transform it on the 
fly into a simple text file (untested, hope all is right):
   kernel=vmlinux
   cobd0=c:\coLinux\root.fs
   cobd1=c:\coLinux\swap_device
   cobd2=c:\coLinux\debian-40r1-i386-businesscard.iso
   cobd3=c:\coLinux\debian-40r1-initrd
   root=/dev/cobd2
   initrd=debian-40r1-initrd.gz
   mem=512
   eth0=tuntap
   eth1=pcap-bridge,"Local Area Connection"

The new coLinux does also support hda1, so you can replace cobd0 
directly with "hda1=c:\coLinux\root.fs" and so on.

Complete list of config params founds here: 
http://colinux.svn.sourceforge.net/svnroot/colinux/branches/stable/doc/colinux-daemon

-- 
Henry

Re: [coLinux-users] Problem with august snapshot of 0.8.0

[Josep Ma [JAZ] <jo...@gm...>]

I also thought about a problem with the linux distro rather than colinux 
itself, but i discarded it after seeing it could boot later on.
I have the linux swap in a disk partition, 478MB and yes, colinux sees 
it as such and with that size. (Swap:   489972k total) But who knows...
Also, i forgot to set initrd before running it for the first time, so 
the modules for the new kernel didn't get copied, which could have added 
to the problem (It also launched without them. that's how i realized i 
forgot them).
I've been running it without problems so far, so it might have really 
been about the driver not correctly registering, in conjunction with 
having run it before.

En/na Henry Nestler ha escrit:
> Same directory is not the problem. Have tested both snapsots, run the 
> one, and installed the other, back to the other and runs. No problems.
>
> In very old mails found, that an old swap between different kernel 
> versions does an problem and reboots/crashed the host some times. I 
> never seen such problem, and I have also a swap partition (from native 
> Linux). The solving was, to renew the swap partition with mkswap before 
> using in new kernel. I tend to use a file as swap for coLinux - this is 
> also faster, as a partition.
> If you have such problem again, try to boot without swap - simple 
> disable the cobd in the config.
>
> What is the size of swap partition? Please check it under coLinux and 
> under native Linux. Detects coLinux the size correctly?
>   

-- 
 _ _  /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
 o o  | Josep Ma [JAZ]                 |
   *  | ICQ UIN: 7014661               |
 '-'  | Messenger: ja...@ho... |
      \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/