colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] graphical console for colinux

[Henry N. <hen...@ar...>]

Hello Leon,


is non spectacular. It's simple a text console:
http://www.henrynestler.com/colinux/screenshoots/Console-sdl-preview_25x80.png

Paolo has improved the key bindings and added mouse copy and paste.
Because this console uses SDL, it is also usable for graphic later.

Henry

Leon Soderlund wrote:
> Hi,
>
> Can anyone post some screenshots ? (i'm on vacation and wanna see :D)
>
> //Leon
>
>
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf Of Henry
> Nestler
> Sent: Monday, September 15, 2008 8:42 PM
> To: Paolo Minazzi
> Cc: col...@li...
> Subject: Re: [coLinux-devel] graphical console for colinux
>
> Hello Paolo,
>
> Paolo Minazzi wrote:
>    
>> Hi colinux users,
>> I have published a first version of my colinux console on
>>
>> http://xoomer.alice.it/paolo.minazzi/colinux-console-nt.exe
>>
>> Use it quietly, I have compiled it with mingw under vmware. It cannot
>> have viruses.
>>
>> I can easily add other font. This one is the version with 8x14 pixel
>> for each char.
>> The console size if 80x25 chars.
>>
>> I have tried it enough and it is possible use it without problems.
>> I have used it at work ( I develop on an ARM linux system) and I use
>> colinux to cross compiling.
>> I have tested the console on 0.7.3 stable version.
>>
>> * Copy and Paste
>>     It is possible using the mouse. Double click select and copy a word.
>>     Selecting copy the text in the clipboard
>>     Right button do paste.
>>
>> * How try it
>>     The easiset way is to rename the old colinux-console-nt.exe and
>> copy the new one.
>>     An other way can be detach the old colinux-console-nt.exe with
>> ALT+WIN and run my version.
>> The only thing I have to remind is to avoid paste-ing of large block
>> od fata because it can block the colinux machine.
>>
>> As soon as it is very very stable, I will send source to Henry.
>>
>> Any suggestion is welcome.
>>
>> Paolo
>>
>>      
>
> have quick tested, and impressed from your copy&paste :-) A nice icon you
> have.
>
> Can you make the cursor flashing slower, think 1/4 from current frequency.
> Best would be disable  flashing, if the Window is not active.
>
> I have used your suggestion by copy your console over the other one, and it
> was launched from colinux-daemon without problems.
>
> --
> Henry N.
>
>    

[coLinux-devel] graphical console for colinux

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

Hi colinux users,
I have published a first version of my colinux console on

http://xoomer.alice.it/paolo.minazzi/colinux-console-nt.exe

Use it quietly, I have compiled it with mingw under vmware. It cannot
have viruses.

I can easily add other font. This one is the version with 8x14 pixel
for each char.
The console size if 80x25 chars.

I have tried it enough and it is possible use it without problems.
I have used it at work ( I develop on an ARM linux system) and I use
colinux to cross compiling.
I have tested the console on 0.7.3 stable version.

* Copy and Paste
  It is possible using the mouse. Double click select and copy a word.
  Selecting copy the text in the clipboard
  Right button do paste.

* How try it
  The easiset way is to rename the old colinux-console-nt.exe and copy
the new one.
  An other way can be detach the old colinux-console-nt.exe with
ALT+WIN and run my version.
The only thing I have to remind is to avoid paste-ing of large block
od fata because it can block the colinux machine.

As soon as it is very very stable, I will send source to Henry.

Any suggestion is welcome.

Paolo

Re: [coLinux-devel] graphical console for colinux

[Leon S. <ma...@r2...>]

Hi,

Can anyone post some screenshots ? (i'm on vacation and wanna see :D)

//Leon
 

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Henry
Nestler
Sent: Monday, September 15, 2008 8:42 PM
To: Paolo Minazzi
Cc: col...@li...
Subject: Re: [coLinux-devel] graphical console for colinux

Hello Paolo,

Paolo Minazzi wrote:
> Hi colinux users,
> I have published a first version of my colinux console on
>
> http://xoomer.alice.it/paolo.minazzi/colinux-console-nt.exe
>
> Use it quietly, I have compiled it with mingw under vmware. It cannot 
> have viruses.
>
> I can easily add other font. This one is the version with 8x14 pixel 
> for each char.
> The console size if 80x25 chars.
>
> I have tried it enough and it is possible use it without problems.
> I have used it at work ( I develop on an ARM linux system) and I use 
> colinux to cross compiling.
> I have tested the console on 0.7.3 stable version.
>
> * Copy and Paste
>    It is possible using the mouse. Double click select and copy a word.
>    Selecting copy the text in the clipboard
>    Right button do paste.
>
> * How try it
>    The easiset way is to rename the old colinux-console-nt.exe and 
> copy the new one.
>    An other way can be detach the old colinux-console-nt.exe with
> ALT+WIN and run my version.
> The only thing I have to remind is to avoid paste-ing of large block 
> od fata because it can block the colinux machine.
>
> As soon as it is very very stable, I will send source to Henry.
>
> Any suggestion is welcome.
>
> Paolo
>    

have quick tested, and impressed from your copy&paste :-) A nice icon you
have.

Can you make the cursor flashing slower, think 1/4 from current frequency.
Best would be disable  flashing, if the Window is not active.

I have used your suggestion by copy your console over the other one, and it
was launched from colinux-daemon without problems.

--
Henry N.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel

Re: [coLinux-devel] graphical console for colinux

[Henry N. <hen...@ar...>]

Hello Paolo,

Paolo Minazzi wrote:
> Hi colinux users,
> I have published a first version of my colinux console on
>
> http://xoomer.alice.it/paolo.minazzi/colinux-console-nt.exe
>
> Use it quietly, I have compiled it with mingw under vmware. It cannot
> have viruses.
>
> I can easily add other font. This one is the version with 8x14 pixel
> for each char.
> The console size if 80x25 chars.
>
> I have tried it enough and it is possible use it without problems.
> I have used it at work ( I develop on an ARM linux system) and I use
> colinux to cross compiling.
> I have tested the console on 0.7.3 stable version.
>
> * Copy and Paste
>    It is possible using the mouse. Double click select and copy a word.
>    Selecting copy the text in the clipboard
>    Right button do paste.
>
> * How try it
>    The easiset way is to rename the old colinux-console-nt.exe and copy
> the new one.
>    An other way can be detach the old colinux-console-nt.exe with
> ALT+WIN and run my version.
> The only thing I have to remind is to avoid paste-ing of large block
> od fata because it can block the colinux machine.
>
> As soon as it is very very stable, I will send source to Henry.
>
> Any suggestion is welcome.
>
> Paolo
>    

have quick tested, and impressed from your copy&paste :-)
A nice icon you have.

Can you make the cursor flashing slower, think 1/4 from current 
frequency. Best would be disable  flashing, if the Window is not active.

I have used your suggestion by copy your console over the other one, and 
it was launched from colinux-daemon without problems.

-- 
Henry N.

[coLinux-devel] autobuild org.colinux.devel 20080911 22:14:08

[coLinux a. <col...@he...>]

The autobuild system has detected a new revision in the source repository.
Review last changed from changelog.txt, also attached in mail.

Download the compiled version:
http://www.henrynestler.com/colinux/autobuild/devel-20080911/

 colinux-0.8.0-20080911.src.tgz  (693227 Bytes)
 daemons-0.8.0-20080911.dbg.zip  (1349796 Bytes)
 daemons-0.8.0-20080911.zip  (1047850 Bytes)

Note, the autobuild compilation does not include an installer.
Remember to reload the driver with these commands:

	colinux-daemon.exe --remove-driver
	colinux-daemon.exe --install-driver

The vmlinux and modules are up to date. Please use last version from
http://www.henrynestler.com/colinux/autobuild/devel-20080907/

The autobuild compilations are not official releases of Cooperative Linux
software.  There is no warranty that any autobuild version is stable.  If
use this autobuild version, please give us feedback of your experience.

Job runs on machine with 64 bit version of gcc 4.1.2.
A service from http://gcc.gnu.org/wiki/CompileFarm

-- 
Lots of fun with newest version,
Henry Nestler
------------------------------------------------------------------------
r1120 | henryn | 2008-09-11 22:14:08 +0000 (Thu, 11 Sep 2008) | 1 line
Changed paths:
   M /branches/devel/NEWS
   M /branches/devel/src/colinux/user/cmdline.c

* Fixed Bug #2013501: Stop with error message on empty parameters.
------------------------------------------------------------------------

[coLinux-devel] [ colinux-Bugs-2013501 ] The configuration file format is fragile

[SourceForge.net <no...@so...>]

Bugs item #2013501, was opened at 2008-07-08 15:36
Message generated for change (Settings changed) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2013501&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: Configuration
Group: v0.7.x (release)
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Adrien Beau (abeau)
Assigned to: Henry N. (henryn)
Summary: The configuration file format is fragile

Initial Comment:
While experimenting with cofs, I made the following mistake:

# --- config start ---

# There is no need to bother creating an ISO-9660 image
# for the installation CD-ROM, we can directly point to
# the files downloaded from slackware.at thanks to cofs.
cofs0= C:\Linux\archive\slackware-12.1\www.slackware.at\data\slackware-12.1
#cofs1=D:\
#cofs2=D:\temp

# --- config end ---

The mistake is the space left after the equal sign in the cofs0 line.

coLinux parses this config file as if "cofs0=" was on a line by itself, and then independantly parses C:\Linux\... (being an unknown entity, it is passed as-is to the Linux kernel command line).

The cofs path being empty, is considered a path relative to the configuration file location, so we end up with cofs0 directly pointing to the configuration directory. (A somewhat dangerous configuration I would say, since it also often contains the filesystem images.)

Maybe the parser should be improved so that it ignores the whitespace characters right before and after the first equal sign in the configuration file lines? At least a warning should be added to colinux-daemon.txt.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-09-12 00:15

Message:
Fixed in SVN revision 1120.


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-07-09 22:11

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Adrien.

many thanks for your bug reports. We will fix it next.

Bebbo, the function GetPrivateProfileString is not usable here. The
command parser should not depend on Windows platform. We have also coLinux
for Linux and a (very long) plan was more platforms. But the second makes
more priority: All not parsed arguments must be forward to Linux kernel
command line, for example a simple "ro" or "root=/dev/...".

Henry

----------------------------------------------------------------------

Comment By: Stefan Franke (bebbo)
Date: 2008-07-08 16:32

Message:
Logged In: YES 
user_id=406985
Originator: NO

why use an own parser? Simply use the GetPrivateProfileString functio.

=> http://msdn.microsoft.com/en-us/library/ms724353.aspx

Bebbo

----------------------------------------------------------------------

Comment By: Adrien Beau (abeau)
Date: 2008-07-08 16:23

Message:
Logged In: YES 
user_id=787269
Originator: YES

My cofs0 line was broken in two when I posted the bug report. Like I
described, in the config file, I had cofs0= and the C:\Linux path on the
same line, separated by a space.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2013501&group_id=98788

[coLinux-devel] [ colinux-Bugs-2013501 ] The configuration file format is fragile

[SourceForge.net <no...@so...>]

Bugs item #2013501, was opened at 2008-07-08 15:36
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2013501&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.7.x (release)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Adrien Beau (abeau)
Assigned to: Henry N. (henryn)
Summary: The configuration file format is fragile

Initial Comment:
While experimenting with cofs, I made the following mistake:

# --- config start ---

# There is no need to bother creating an ISO-9660 image
# for the installation CD-ROM, we can directly point to
# the files downloaded from slackware.at thanks to cofs.
cofs0= C:\Linux\archive\slackware-12.1\www.slackware.at\data\slackware-12.1
#cofs1=D:\
#cofs2=D:\temp

# --- config end ---

The mistake is the space left after the equal sign in the cofs0 line.

coLinux parses this config file as if "cofs0=" was on a line by itself, and then independantly parses C:\Linux\... (being an unknown entity, it is passed as-is to the Linux kernel command line).

The cofs path being empty, is considered a path relative to the configuration file location, so we end up with cofs0 directly pointing to the configuration directory. (A somewhat dangerous configuration I would say, since it also often contains the filesystem images.)

Maybe the parser should be improved so that it ignores the whitespace characters right before and after the first equal sign in the configuration file lines? At least a warning should be added to colinux-daemon.txt.

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-09-12 00:15

Message:
Fixed in SVN revision 1120.


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-07-09 22:11

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Adrien.

many thanks for your bug reports. We will fix it next.

Bebbo, the function GetPrivateProfileString is not usable here. The
command parser should not depend on Windows platform. We have also coLinux
for Linux and a (very long) plan was more platforms. But the second makes
more priority: All not parsed arguments must be forward to Linux kernel
command line, for example a simple "ro" or "root=/dev/...".

Henry

----------------------------------------------------------------------

Comment By: Stefan Franke (bebbo)
Date: 2008-07-08 16:32

Message:
Logged In: YES 
user_id=406985
Originator: NO

why use an own parser? Simply use the GetPrivateProfileString functio.

=> http://msdn.microsoft.com/en-us/library/ms724353.aspx

Bebbo

----------------------------------------------------------------------

Comment By: Adrien Beau (abeau)
Date: 2008-07-08 16:23

Message:
Logged In: YES 
user_id=787269
Originator: YES

My cofs0 line was broken in two when I posted the bug report. Like I
described, in the config file, I had cofs0= and the C:\Linux path on the
same line, separated by a space.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2013501&group_id=98788

[coLinux-devel] a way to crush colinux 0.7.3 stable version

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

Hello,
I have seen that it is possible to crush colinux in the following way :

- using nt-console
- copy in the clipboard a large enought block of data ( for example
using notepad)
- paste in the colinux-nt console

After this, daemon gets 100% of the CPU and colinux became not usable.

I'm writing a graphical console, and implementing paste I have the same problem.
More exactly, if I send a lot of char with the send_key(), I have this
type of problem.

Regards,
Paolo

Re: [coLinux-devel] autobuild org.colinux.devel 20080907 12:26:17

[Henry N. <hen...@ar...>]

Hello Harald,

Harald Weidner wrote:
>> http://www.henrynestler.com/colinux/autobuild/devel-20080907/
>>      
> [...]
>    
>> Add sysenter / sysexit restoration support
>>      
> [...]
>    
>> If host CPU supports sysenter (SEP), then coLinux kernel will use
>> sysenter now. Sysenter is faster as the old Int 0x80.
>>      
>
> I updated from Build 20080823 to 20080907 and expected coLinux to
> become faster. However, the opposite seems true.
>
> My standard "benchmark" is a compile run of the plain Linux kernel
> 2.6.18, doing "make clean; make defconfig; time make all". I issued
> three runs each. Here are the results (real/user/sys min:sec):
>
> coLinux Snapshot 20080823
> 1. 6:17 / 4:25 / 1:51
> 2. 6:15 / 4:28 / 1:49
> 3. 6:14 / 4:26 / 1:45
>
> coLinux Snapshot 20080907
> 1. 6:30 / 4:26 / 2:03
> 2. 6:32 / 4:26 / 2:04
> 3. 6:30 / 4:28 / 2:01
>
> Building the Linux kernel is mainly a CPU and memory intensive task;
> however, there are also many small files created and removed, which
> invokes syscalls.
>
> The host machine has an Intel Core2 Duo 6400 processor at 2.13 GHz
> and 2 GB of RAM, running an (otherwise unloaded) Windows XP Professional
> SP 3. coLinux has 512 MB of memory and runs Debian 4.0r4 with the
> kernel shipped with coLinux.
>
>    
I have seen also such effects. After coLinux boots up: 3x build OpenVPN, 
every with unpacking source, configure and make.

Version 0.8.0-20080823:
51.911s / 26.770s / 12.160s
29.330s / 16.470s / 11.380s
29.290s / 15.040s / 12.890s

Version 0.8.0-20080907:
37.811s / 14.900s / 10.600s  (Faster from Windows file cache after 
coLinux reboot)
29.460s / 16.240s / 12.030s  (+0.4%)
29.580s / 16.520s / 11.740s  (+1%)
( real / user / sys )

In vanilla Linux sysenter should run faster as Int80. But, nobody says 
how mutch faster.

CoLinux needs to save and restore 3 more special registers now. This are 
3*RDMSR + 3*WRMSR on every operating system switch, typically hardware 
interrupts for harddisk and timer, and for memory allocation or free. 
This cost also some time. I don't know how many. The counts of switching 
can read from /proc/colinx/stats (stats_clear clears the counters after 
read). I assume, that the time we got from sysenter, will lose on OS 
switch now.

Currently I'm not sure, is the distribution using sysenter? I only know, 
that the sysenter exist from kernel. I have tested with [1]. I have not 
idea how can check, that glibc or the elf-loader use the sysenter. For 
example a staticly linked old program will use Int 0x80.

Someone found, that syscalls on Pentium 4 are slower as Pentium III [2,3].
In [4] is a good summary about sysenter inside Linux kernel.

[1] http://www.trilithium.com/johan/2005/08/linux-gate/
[2] http://kerneltrap.org/node/531
[3] http://marc.info/?l=linux-kernel&m=103942289025149&w=2
[4] http://manugarg.googlepages.com/systemcallinlinux2_6.html

-- 
Henry N.

Re: [coLinux-devel] autobuild org.colinux.devel 20080907 12:26:17

[Harald W. <hwe...@gm...>]

Hello,

coLinux autobuild <col...@he...>:

>http://www.henrynestler.com/colinux/autobuild/devel-20080907/
[...]
>Add sysenter / sysexit restoration support
[...]
>If host CPU supports sysenter (SEP), then coLinux kernel will use
>sysenter now. Sysenter is faster as the old Int 0x80.

I updated from Build 20080823 to 20080907 and expected coLinux to
become faster. However, the opposite seems true.

My standard "benchmark" is a compile run of the plain Linux kernel
2.6.18, doing "make clean; make defconfig; time make all". I issued
three runs each. Here are the results (real/user/sys min:sec):

coLinux Snapshot 20080823
1. 6:17 / 4:25 / 1:51
2. 6:15 / 4:28 / 1:49
3. 6:14 / 4:26 / 1:45

coLinux Snapshot 20080907
1. 6:30 / 4:26 / 2:03
2. 6:32 / 4:26 / 2:04
3. 6:30 / 4:28 / 2:01

Building the Linux kernel is mainly a CPU and memory intensive task;
however, there are also many small files created and removed, which
invokes syscalls.

The host machine has an Intel Core2 Duo 6400 processor at 2.13 GHz
and 2 GB of RAM, running an (otherwise unloaded) Windows XP Professional
SP 3. coLinux has 512 MB of memory and runs Debian 4.0r4 with the
kernel shipped with coLinux.

Regards,
Harald

[coLinux-devel] autobuild org.colinux.devel 20080907 12:26:17

[coLinux a. <col...@he...>]

The autobuild system has detected a new revision in the source repository.
Review last changed from changelog.txt, also attached in mail.

Download the compiled version:
http://www.henrynestler.com/colinux/autobuild/devel-20080907/

 colinux-0.8.0-20080907.src.tgz  (692859 Bytes)
 daemons-0.8.0-20080907.dbg.zip  (1348807 Bytes)
 daemons-0.8.0-20080907.zip  (1047037 Bytes)
 modules-2.6.22.18-co-0.8.0-20080907.tgz  (2602814 Bytes)
 vmlinux-2.6.22.18-co-0.8.0-20080907.zip  (1762646 Bytes)

Note, the autobuild compilation does not include an installer.
Remember to reload the driver with these commands:

	colinux-daemon.exe --remove-driver
	colinux-daemon.exe --install-driver

Inside coLinux please update modules as follow:

	rm -rf /lib/modules/*-co-*
	tar -xzf modules-*-co-*-20080907.tgz -C /

The autobuild compilations are not official releases of Cooperative Linux
software.  There is no warranty that any autobuild version is stable.  If
use this autobuild version, please give us feedback of your experience.

Job runs on machine with 64 bit version of gcc 4.1.2.
A service from http://gcc.gnu.org/wiki/CompileFarm

-- 
Lots of fun with newest version,
Henry Nestler
------------------------------------------------------------------------
r1119 | henryn | 2008-09-07 12:26:17 +0000 (Sun, 07 Sep 2008) | 10 lines
Changed paths:
   M /branches/devel/NEWS
   M /branches/devel/patch/base-2.6.22.diff
   M /branches/devel/src/colinux/arch/i386/defs.h
   M /branches/devel/src/colinux/arch/i386/passage.c

Add sysenter / sysexit restoration support
* Add sysenter_cs, sysenter_esp, sysenter_eip to set of registers
* Incrase code space for passage (+0x30)
* Allow cpu to use X86_FEATURE_SEP
* Linux API version 12

If host CPU supports sysenter (SEP), then coLinux kernel will use
sysenter now. Sysenter is faster as the old Int 0x80.
Read more: http://www.trilithium.com/johan/2005/08/linux-gate/

------------------------------------------------------------------------

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 08:33
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2008-09-07 16:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

VDSO needs to telling the glibc how to make a syscall. With vdso=0 on
startup or with write 0 to vdso_enabled, the VDSO page is no loger fix
mapped on ffffe000 (see
http://www.trilithium.com/johan/2005/08/linux-gate/) - it goes to randomly
virtual address.

Debian 4 has problems, if I boot with vdso=1 (coLinux default) and write 0
later. The current terminal kills the INIT task. Linux can not shutdown.
The other consoles (tty1, tty2, ...) are still running.

I can boot all my distries (SuSE 9.0, Debian 3.0, Debian 4.0) with boot
parameter vdso=0.
Of curse, if I boot with 0, there is no problem with write 0 to
vdso_enabled.
vdso=0 is the default config for x86 Kernels ("CONFIG_COMPAT_VDSO is not
set").

Can we set vdso=0 as coLinux default now?
I think yes. Anybody can test this with boot parameter "vdso=0".

By the while have enabled the feature for sysenter and sysexit (SEP). All
current cpus would have this feature. This has also something to do with
the VDSO.

Eugenesan, please try this build and boot with vdso=0 and lets write to
vdso_enabled. This should run without problems.
Second, please test with parameter vdso=1 (or without this) and lets write
0 to vdso_enabled. Is this crashing?

New Snapshot exist on http://www.colinux.org/snapshots/

PS: Before you risk losing data from crash tests, it's good idea to SYNC
all data to harddisk before runs colinux-daemon. I have this in my batch
files for testings now:
http://technet.microsoft.com/en-us/sysinternals/bb897438.aspx

Henry


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-30 19:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

Ah, thanks. Very good detection.

Default for Linux VDSO is disabled. I know, that my coLinux SuSE 9.0
hangs, if VDSO is disabled in kernel config. I have explicitly enabled VDSO
compatibility in the config. But, I was not thinking about a User or Distry
would disable this at runtime.

If that helps: It would be easy for coLinux kernel code, to make
/proc/sys/vm/vdso_enabled read only. ;-)

Of curse, you can run "colinux-debug-daemon.exe -d -p -s prints=31,misc=31
..."  on a command prompt, before you starts the service from Windows
control applet. The parameter "misc=31" there is the same as you would run
"colinux-daemon -v 31 ..."


----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 16:25

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Boot-up problems solved, "echo 0 > /proc/sys/vm/vdso_enabled" hangs
coLinux.
Hope my software will survive that...

Can I enable debug when starting daemon as service?

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 14:49

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi,

After reboot debug started to work.
Digging in...


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-30 13:54

Message:
Logged In: YES 
user_id=579204
Originator: NO

Debugging.txt is up to date. The last you will find here:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging

To catch some from crashing, the debug-daemon often can't help.

To trace such, needs to put some debugging into the scripts inside the
distribution. You say, that it is a problem in runlevel 2, then try to
trace the steps between runlevel 1 and 2. Run you system with runlevel 1
("init 1") in the coLinux boot parameter. Add 'set -x' in the top of the
script for runlevel switching code. Than switch with command 'init 2' on
Linux prompt to next runlevel, 

For me it is the file /etc/init.d/rc under SuSE.

Good idea is also to put 'echo "$0 $service start ..."; sleep 3' into the
inner of the for-loop before execute the next script (ones of
/etc/init.d/rc2.d/S##...), to see what script will be start as next. - The
loop what is locate the K## and S## to start/stop actions. Some
distributions have a special environment in the rc scripts to enable a
verbose mode.

This is in my script for trace boot steps:
        blogger "$service start"
        echo "$0 $service start ..."; sleep 3    ### Trace: inserted for
coLinux debugging ###
        $i start; status=$?

Henry

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 13:08

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi Henry,
Thanks for reply.

I do use version you are proposing and still experiencing crashes.
In addition my system currently do not pass switching to runlevel 2, I've
even reinstalled the whole distribution.
Probably something changed in distribution's updated packages, because it
was working for months...

About debugging, I have hard times enabling it. Adding -v # makes no
change, debug daemon outputs nothing.
Is debugging.txt is outdated or I am missing something?

Thanks ahead
Eugene

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 20:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-2081835 ] add "andLinux" to repository of downloadable colinux images

[SourceForge.net <no...@so...>]

Feature Requests item #2081835, was opened at 2008-08-29 06:06
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081835&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: add "andLinux" to repository of downloadable colinux images

Initial Comment:
it would be nice for users to also have the option to directly download an andLinux image

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-09-01 03:32

Message:
Logged In: NO 

dragonlinux is also pretty lightweight, might be interesting to check out
for some!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081835&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-1898496 ] prepackaged GUI image

[SourceForge.net <no...@so...>]

Feature Requests item #1898496, was opened at 2008-02-21 08:05
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: prepackaged GUI image

Initial Comment:
The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux.

Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-31 20:33

Message:
Logged In: NO 

this is a rather academic discussion, those who tackle this idea are going
to decide what tools and languages they use

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-31 17:29

Message:
Logged In: NO 

"
Most
mainstream scripting languages are well-supported on a rather wide number
of platforms, unlike C# development tools, which still require numerous
non-standard dependencies to be properly installed and set up for each
platform individually.
"

Sorry, but this isin't true! To develope using C# you can use mono to
compile the stuff you write on all supported platform, windows too. You can
write it with any ide/rad you like, naturally there are tools to do like
monodevelop on linux and sharpdevelop/visual studio (express) on windows.
This is the same for any scripting language: you need the runtime to
execute the script and any editor to write the stuff

I didn't see any kinda of non-standard dependencies:
- On windows, you have the runtime simply doing updates
- On linux, many major distros has it ((open)suse, ubuntu, fedora,
gentoo)

Another example: if you use GTK you need binding ... like any other
programming language that doesn't resides directly on the libraries (note:
technically you can compile in the bindings using a couple of mono tools)



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-31 05:55

Message:
Logged In: NO 

I think, this frontend would be Win32-specific in any way, so it really
doesn't matter what language is used for implementation, however it may be
easier to favor an implementation language that is commonly and widely
known within the community of potential contributors, so that future
maintenance of such a frontend would not be limited to an unnecessarily
small group of contributor who are sufficiently familiar with the
corresponding language. Using a scripting language such as Python or Ruby
on the other hand, brings the added advantage that potential
contributors/maintainers of such a frontend would not necessarily have to
install any complex dependencies (think IDE, compilers, runtime libs). Most
mainstream scripting languages are well-supported on a rather wide number
of platforms, unlike C# development tools, which still require numerous
non-standard dependencies to be properly installed and set up for each
platform individually.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:16

Message:
Logged In: NO 

Just a note to the previous comment ...

if necessary you can use python too for development using ironpython!

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:14

Message:
Logged In: NO 

Python is awesome, i know, but why not C#?

Mono is distribuited with major linux systems and on windows you're fully
integrated with .NET! I think that a lot of users are windows based so a
fully native interface and a fully integrated application can do better
than a python application

Another really important stuff is that with .NET you can easely build two
interfaces and load the preferred at startup time simply checking the
operative system ... with the interfaces that relies on a set of
functionalities implemented in a backend


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 18:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

If somebody has knowledges about Python, then here are some of GUI scripts
for coLinux configuration, that has to be finish:

http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/configurator/

It's very old. First needs to remove the outdated XML from that.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 16:26

Message:
Logged In: NO 

The following site contains a listing of available GUI toolkit bindings
for python, including a section about UI-building toolkits (e.g. dialog
editors):

http://wiki.python.org/moin/GuiProgramming

In addition, here's  a site providing a full tutorial about PyQT
programming:

http://www.commandprompt.com/community/pyqt/book1
http://wiki.python.org/moin/PyQt

PythonStudio includes a full GUI editor, as well:
http://www.codeplex.com/IronPythonStudio

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:57

Message:
Logged In: NO 

thinking about it, the most promising approach would probably be to simply
implement this totally separate, using a scripting language and a GUI
toolkit, i.e. something like python or ruby with GTK/QT bindings. This way,
it would not unnecessarily affect any of the existing code, would be very
much straight forward and also flexible and easily extendsible for future
changes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:24

Message:
Logged In: NO 

something like this would probably be best implemented as a separate,
standaline "profile manager", so that creating/editing and deleting
profiles can be done via this app, and starting a profile would only entail
passing the stored parameters to the corresponding binaries, this would
keep the overhead to a minimum.



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:03

Message:
Logged In: NO 

see "andLinux"

however, usability could still be somewhat improved for users with a
non-nix background, in particular the whole setup process should either be
more intuitive or simply provide some more GUI frontends, i.e. by allowing
the most common actions to be directly done from the executables via UI
means, rather than requiring users to pass lots of cryptic options via
command line parameters. In this context, it would already be a significant
improvement if the most basic and relevant parameters could be configured
via some sort of GUI frontend, be it embedded or not, so that running a
process without REQUIRED parameters automatically brings up a dialog for
users to configure the most important parameters, and optionally save them
as startup profiles, so that they may next time select a startup profile or
create a new one.

Similar to how firefox starts actually: provide a way for customization,
preferably using lots of nifty tooltips and explanations and once a user
has a working config, enable them to save and reuse configs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-1898496 ] prepackaged GUI image

[SourceForge.net <no...@so...>]

Feature Requests item #1898496, was opened at 2008-02-21 08:05
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: prepackaged GUI image

Initial Comment:
The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux.

Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-31 17:29

Message:
Logged In: NO 

"
Most
mainstream scripting languages are well-supported on a rather wide number
of platforms, unlike C# development tools, which still require numerous
non-standard dependencies to be properly installed and set up for each
platform individually.
"

Sorry, but this isin't true! To develope using C# you can use mono to
compile the stuff you write on all supported platform, windows too. You can
write it with any ide/rad you like, naturally there are tools to do like
monodevelop on linux and sharpdevelop/visual studio (express) on windows.
This is the same for any scripting language: you need the runtime to
execute the script and any editor to write the stuff

I didn't see any kinda of non-standard dependencies:
- On windows, you have the runtime simply doing updates
- On linux, many major distros has it ((open)suse, ubuntu, fedora,
gentoo)

Another example: if you use GTK you need binding ... like any other
programming language that doesn't resides directly on the libraries (note:
technically you can compile in the bindings using a couple of mono tools)



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-31 05:55

Message:
Logged In: NO 

I think, this frontend would be Win32-specific in any way, so it really
doesn't matter what language is used for implementation, however it may be
easier to favor an implementation language that is commonly and widely
known within the community of potential contributors, so that future
maintenance of such a frontend would not be limited to an unnecessarily
small group of contributor who are sufficiently familiar with the
corresponding language. Using a scripting language such as Python or Ruby
on the other hand, brings the added advantage that potential
contributors/maintainers of such a frontend would not necessarily have to
install any complex dependencies (think IDE, compilers, runtime libs). Most
mainstream scripting languages are well-supported on a rather wide number
of platforms, unlike C# development tools, which still require numerous
non-standard dependencies to be properly installed and set up for each
platform individually.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:16

Message:
Logged In: NO 

Just a note to the previous comment ...

if necessary you can use python too for development using ironpython!

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:14

Message:
Logged In: NO 

Python is awesome, i know, but why not C#?

Mono is distribuited with major linux systems and on windows you're fully
integrated with .NET! I think that a lot of users are windows based so a
fully native interface and a fully integrated application can do better
than a python application

Another really important stuff is that with .NET you can easely build two
interfaces and load the preferred at startup time simply checking the
operative system ... with the interfaces that relies on a set of
functionalities implemented in a backend


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 18:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

If somebody has knowledges about Python, then here are some of GUI scripts
for coLinux configuration, that has to be finish:

http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/configurator/

It's very old. First needs to remove the outdated XML from that.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 16:26

Message:
Logged In: NO 

The following site contains a listing of available GUI toolkit bindings
for python, including a section about UI-building toolkits (e.g. dialog
editors):

http://wiki.python.org/moin/GuiProgramming

In addition, here's  a site providing a full tutorial about PyQT
programming:

http://www.commandprompt.com/community/pyqt/book1
http://wiki.python.org/moin/PyQt

PythonStudio includes a full GUI editor, as well:
http://www.codeplex.com/IronPythonStudio

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:57

Message:
Logged In: NO 

thinking about it, the most promising approach would probably be to simply
implement this totally separate, using a scripting language and a GUI
toolkit, i.e. something like python or ruby with GTK/QT bindings. This way,
it would not unnecessarily affect any of the existing code, would be very
much straight forward and also flexible and easily extendsible for future
changes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:24

Message:
Logged In: NO 

something like this would probably be best implemented as a separate,
standaline "profile manager", so that creating/editing and deleting
profiles can be done via this app, and starting a profile would only entail
passing the stored parameters to the corresponding binaries, this would
keep the overhead to a minimum.



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:03

Message:
Logged In: NO 

see "andLinux"

however, usability could still be somewhat improved for users with a
non-nix background, in particular the whole setup process should either be
more intuitive or simply provide some more GUI frontends, i.e. by allowing
the most common actions to be directly done from the executables via UI
means, rather than requiring users to pass lots of cryptic options via
command line parameters. In this context, it would already be a significant
improvement if the most basic and relevant parameters could be configured
via some sort of GUI frontend, be it embedded or not, so that running a
process without REQUIRED parameters automatically brings up a dialog for
users to configure the most important parameters, and optionally save them
as startup profiles, so that they may next time select a startup profile or
create a new one.

Similar to how firefox starts actually: provide a way for customization,
preferably using lots of nifty tooltips and explanations and once a user
has a working config, enable them to save and reuse configs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-1898496 ] prepackaged GUI image

[SourceForge.net <no...@so...>]

Feature Requests item #1898496, was opened at 2008-02-21 08:05
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: prepackaged GUI image

Initial Comment:
The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux.

Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-31 05:55

Message:
Logged In: NO 

I think, this frontend would be Win32-specific in any way, so it really
doesn't matter what language is used for implementation, however it may be
easier to favor an implementation language that is commonly and widely
known within the community of potential contributors, so that future
maintenance of such a frontend would not be limited to an unnecessarily
small group of contributor who are sufficiently familiar with the
corresponding language. Using a scripting language such as Python or Ruby
on the other hand, brings the added advantage that potential
contributors/maintainers of such a frontend would not necessarily have to
install any complex dependencies (think IDE, compilers, runtime libs). Most
mainstream scripting languages are well-supported on a rather wide number
of platforms, unlike C# development tools, which still require numerous
non-standard dependencies to be properly installed and set up for each
platform individually.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:16

Message:
Logged In: NO 

Just a note to the previous comment ...

if necessary you can use python too for development using ironpython!

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:14

Message:
Logged In: NO 

Python is awesome, i know, but why not C#?

Mono is distribuited with major linux systems and on windows you're fully
integrated with .NET! I think that a lot of users are windows based so a
fully native interface and a fully integrated application can do better
than a python application

Another really important stuff is that with .NET you can easely build two
interfaces and load the preferred at startup time simply checking the
operative system ... with the interfaces that relies on a set of
functionalities implemented in a backend


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 18:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

If somebody has knowledges about Python, then here are some of GUI scripts
for coLinux configuration, that has to be finish:

http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/configurator/

It's very old. First needs to remove the outdated XML from that.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 16:26

Message:
Logged In: NO 

The following site contains a listing of available GUI toolkit bindings
for python, including a section about UI-building toolkits (e.g. dialog
editors):

http://wiki.python.org/moin/GuiProgramming

In addition, here's  a site providing a full tutorial about PyQT
programming:

http://www.commandprompt.com/community/pyqt/book1
http://wiki.python.org/moin/PyQt

PythonStudio includes a full GUI editor, as well:
http://www.codeplex.com/IronPythonStudio

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:57

Message:
Logged In: NO 

thinking about it, the most promising approach would probably be to simply
implement this totally separate, using a scripting language and a GUI
toolkit, i.e. something like python or ruby with GTK/QT bindings. This way,
it would not unnecessarily affect any of the existing code, would be very
much straight forward and also flexible and easily extendsible for future
changes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:24

Message:
Logged In: NO 

something like this would probably be best implemented as a separate,
standaline "profile manager", so that creating/editing and deleting
profiles can be done via this app, and starting a profile would only entail
passing the stored parameters to the corresponding binaries, this would
keep the overhead to a minimum.



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:03

Message:
Logged In: NO 

see "andLinux"

however, usability could still be somewhat improved for users with a
non-nix background, in particular the whole setup process should either be
more intuitive or simply provide some more GUI frontends, i.e. by allowing
the most common actions to be directly done from the executables via UI
means, rather than requiring users to pass lots of cryptic options via
command line parameters. In this context, it would already be a significant
improvement if the most basic and relevant parameters could be configured
via some sort of GUI frontend, be it embedded or not, so that running a
process without REQUIRED parameters automatically brings up a dialog for
users to configure the most important parameters, and optionally save them
as startup profiles, so that they may next time select a startup profile or
create a new one.

Similar to how firefox starts actually: provide a way for customization,
preferably using lots of nifty tooltips and explanations and once a user
has a working config, enable them to save and reuse configs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 08:33
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2008-08-30 19:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

Ah, thanks. Very good detection.

Default for Linux VDSO is disabled. I know, that my coLinux SuSE 9.0
hangs, if VDSO is disabled in kernel config. I have explicitly enabled VDSO
compatibility in the config. But, I was not thinking about a User or Distry
would disable this at runtime.

If that helps: It would be easy for coLinux kernel code, to make
/proc/sys/vm/vdso_enabled read only. ;-)

Of curse, you can run "colinux-debug-daemon.exe -d -p -s prints=31,misc=31
..."  on a command prompt, before you starts the service from Windows
control applet. The parameter "misc=31" there is the same as you would run
"colinux-daemon -v 31 ..."


----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 16:25

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Boot-up problems solved, "echo 0 > /proc/sys/vm/vdso_enabled" hangs
coLinux.
Hope my software will survive that...

Can I enable debug when starting daemon as service?

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 14:49

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi,

After reboot debug started to work.
Digging in...


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-30 13:54

Message:
Logged In: YES 
user_id=579204
Originator: NO

Debugging.txt is up to date. The last you will find here:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging

To catch some from crashing, the debug-daemon often can't help.

To trace such, needs to put some debugging into the scripts inside the
distribution. You say, that it is a problem in runlevel 2, then try to
trace the steps between runlevel 1 and 2. Run you system with runlevel 1
("init 1") in the coLinux boot parameter. Add 'set -x' in the top of the
script for runlevel switching code. Than switch with command 'init 2' on
Linux prompt to next runlevel, 

For me it is the file /etc/init.d/rc under SuSE.

Good idea is also to put 'echo "$0 $service start ..."; sleep 3' into the
inner of the for-loop before execute the next script (ones of
/etc/init.d/rc2.d/S##...), to see what script will be start as next. - The
loop what is locate the K## and S## to start/stop actions. Some
distributions have a special environment in the rc scripts to enable a
verbose mode.

This is in my script for trace boot steps:
        blogger "$service start"
        echo "$0 $service start ..."; sleep 3    ### Trace: inserted for
coLinux debugging ###
        $i start; status=$?

Henry

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 13:08

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi Henry,
Thanks for reply.

I do use version you are proposing and still experiencing crashes.
In addition my system currently do not pass switching to runlevel 2, I've
even reinstalled the whole distribution.
Probably something changed in distribution's updated packages, because it
was working for months...

About debugging, I have hard times enabling it. Adding -v # makes no
change, debug daemon outputs nothing.
Is debugging.txt is outdated or I am missing something?

Thanks ahead
Eugene

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 20:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 09:33
Message generated for change (Comment added) made by eugenesan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: eugenesan (eugenesan)
Date: 2008-08-30 17:25

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Boot-up problems solved, "echo 0 > /proc/sys/vm/vdso_enabled" hangs
coLinux.
Hope my software will survive that...

Can I enable debug when starting daemon as service?

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 15:49

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi,

After reboot debug started to work.
Digging in...


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-30 14:54

Message:
Logged In: YES 
user_id=579204
Originator: NO

Debugging.txt is up to date. The last you will find here:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging

To catch some from crashing, the debug-daemon often can't help.

To trace such, needs to put some debugging into the scripts inside the
distribution. You say, that it is a problem in runlevel 2, then try to
trace the steps between runlevel 1 and 2. Run you system with runlevel 1
("init 1") in the coLinux boot parameter. Add 'set -x' in the top of the
script for runlevel switching code. Than switch with command 'init 2' on
Linux prompt to next runlevel, 

For me it is the file /etc/init.d/rc under SuSE.

Good idea is also to put 'echo "$0 $service start ..."; sleep 3' into the
inner of the for-loop before execute the next script (ones of
/etc/init.d/rc2.d/S##...), to see what script will be start as next. - The
loop what is locate the K## and S## to start/stop actions. Some
distributions have a special environment in the rc scripts to enable a
verbose mode.

This is in my script for trace boot steps:
        blogger "$service start"
        echo "$0 $service start ..."; sleep 3    ### Trace: inserted for
coLinux debugging ###
        $i start; status=$?

Henry

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 14:08

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi Henry,
Thanks for reply.

I do use version you are proposing and still experiencing crashes.
In addition my system currently do not pass switching to runlevel 2, I've
even reinstalled the whole distribution.
Probably something changed in distribution's updated packages, because it
was working for months...

About debugging, I have hard times enabling it. Adding -v # makes no
change, debug daemon outputs nothing.
Is debugging.txt is outdated or I am missing something?

Thanks ahead
Eugene

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 21:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 09:33
Message generated for change (Comment added) made by eugenesan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: eugenesan (eugenesan)
Date: 2008-08-30 15:49

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi,

After reboot debug started to work.
Digging in...


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-30 14:54

Message:
Logged In: YES 
user_id=579204
Originator: NO

Debugging.txt is up to date. The last you will find here:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging

To catch some from crashing, the debug-daemon often can't help.

To trace such, needs to put some debugging into the scripts inside the
distribution. You say, that it is a problem in runlevel 2, then try to
trace the steps between runlevel 1 and 2. Run you system with runlevel 1
("init 1") in the coLinux boot parameter. Add 'set -x' in the top of the
script for runlevel switching code. Than switch with command 'init 2' on
Linux prompt to next runlevel, 

For me it is the file /etc/init.d/rc under SuSE.

Good idea is also to put 'echo "$0 $service start ..."; sleep 3' into the
inner of the for-loop before execute the next script (ones of
/etc/init.d/rc2.d/S##...), to see what script will be start as next. - The
loop what is locate the K## and S## to start/stop actions. Some
distributions have a special environment in the rc scripts to enable a
verbose mode.

This is in my script for trace boot steps:
        blogger "$service start"
        echo "$0 $service start ..."; sleep 3    ### Trace: inserted for
coLinux debugging ###
        $i start; status=$?

Henry

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 14:08

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi Henry,
Thanks for reply.

I do use version you are proposing and still experiencing crashes.
In addition my system currently do not pass switching to runlevel 2, I've
even reinstalled the whole distribution.
Probably something changed in distribution's updated packages, because it
was working for months...

About debugging, I have hard times enabling it. Adding -v # makes no
change, debug daemon outputs nothing.
Is debugging.txt is outdated or I am missing something?

Thanks ahead
Eugene

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 21:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 08:33
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2008-08-30 13:54

Message:
Logged In: YES 
user_id=579204
Originator: NO

Debugging.txt is up to date. The last you will find here:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging

To catch some from crashing, the debug-daemon often can't help.

To trace such, needs to put some debugging into the scripts inside the
distribution. You say, that it is a problem in runlevel 2, then try to
trace the steps between runlevel 1 and 2. Run you system with runlevel 1
("init 1") in the coLinux boot parameter. Add 'set -x' in the top of the
script for runlevel switching code. Than switch with command 'init 2' on
Linux prompt to next runlevel, 

For me it is the file /etc/init.d/rc under SuSE.

Good idea is also to put 'echo "$0 $service start ..."; sleep 3' into the
inner of the for-loop before execute the next script (ones of
/etc/init.d/rc2.d/S##...), to see what script will be start as next. - The
loop what is locate the K## and S## to start/stop actions. Some
distributions have a special environment in the rc scripts to enable a
verbose mode.

This is in my script for trace boot steps:
        blogger "$service start"
        echo "$0 $service start ..."; sleep 3    ### Trace: inserted for
coLinux debugging ###
        $i start; status=$?

Henry

----------------------------------------------------------------------

Comment By: eugenesan (eugenesan)
Date: 2008-08-30 13:08

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi Henry,
Thanks for reply.

I do use version you are proposing and still experiencing crashes.
In addition my system currently do not pass switching to runlevel 2, I've
even reinstalled the whole distribution.
Probably something changed in distribution's updated packages, because it
was working for months...

About debugging, I have hard times enabling it. Adding -v # makes no
change, debug daemon outputs nothing.
Is debugging.txt is outdated or I am missing something?

Thanks ahead
Eugene

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 20:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 09:33
Message generated for change (Comment added) made by eugenesan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: eugenesan (eugenesan)
Date: 2008-08-30 14:08

Message:
Logged In: YES 
user_id=1010208
Originator: YES

Hi Henry,
Thanks for reply.

I do use version you are proposing and still experiencing crashes.
In addition my system currently do not pass switching to runlevel 2, I've
even reinstalled the whole distribution.
Probably something changed in distribution's updated packages, because it
was working for months...

About debugging, I have hard times enabling it. Adding -v # makes no
change, debug daemon outputs nothing.
Is debugging.txt is outdated or I am missing something?

Thanks ahead
Eugene

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 21:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-1898496 ] prepackaged GUI image

[SourceForge.net <no...@so...>]

Feature Requests item #1898496, was opened at 2008-02-21 08:05
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: prepackaged GUI image

Initial Comment:
The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux.

Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:16

Message:
Logged In: NO 

Just a note to the previous comment ...

if necessary you can use python too for development using ironpython!

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:14

Message:
Logged In: NO 

Python is awesome, i know, but why not C#?

Mono is distribuited with major linux systems and on windows you're fully
integrated with .NET! I think that a lot of users are windows based so a
fully native interface and a fully integrated application can do better
than a python application

Another really important stuff is that with .NET you can easely build two
interfaces and load the preferred at startup time simply checking the
operative system ... with the interfaces that relies on a set of
functionalities implemented in a backend


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 18:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

If somebody has knowledges about Python, then here are some of GUI scripts
for coLinux configuration, that has to be finish:

http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/configurator/

It's very old. First needs to remove the outdated XML from that.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 16:26

Message:
Logged In: NO 

The following site contains a listing of available GUI toolkit bindings
for python, including a section about UI-building toolkits (e.g. dialog
editors):

http://wiki.python.org/moin/GuiProgramming

In addition, here's  a site providing a full tutorial about PyQT
programming:

http://www.commandprompt.com/community/pyqt/book1
http://wiki.python.org/moin/PyQt

PythonStudio includes a full GUI editor, as well:
http://www.codeplex.com/IronPythonStudio

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:57

Message:
Logged In: NO 

thinking about it, the most promising approach would probably be to simply
implement this totally separate, using a scripting language and a GUI
toolkit, i.e. something like python or ruby with GTK/QT bindings. This way,
it would not unnecessarily affect any of the existing code, would be very
much straight forward and also flexible and easily extendsible for future
changes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:24

Message:
Logged In: NO 

something like this would probably be best implemented as a separate,
standaline "profile manager", so that creating/editing and deleting
profiles can be done via this app, and starting a profile would only entail
passing the stored parameters to the corresponding binaries, this would
keep the overhead to a minimum.



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:03

Message:
Logged In: NO 

see "andLinux"

however, usability could still be somewhat improved for users with a
non-nix background, in particular the whole setup process should either be
more intuitive or simply provide some more GUI frontends, i.e. by allowing
the most common actions to be directly done from the executables via UI
means, rather than requiring users to pass lots of cryptic options via
command line parameters. In this context, it would already be a significant
improvement if the most basic and relevant parameters could be configured
via some sort of GUI frontend, be it embedded or not, so that running a
process without REQUIRED parameters automatically brings up a dialog for
users to configure the most important parameters, and optionally save them
as startup profiles, so that they may next time select a startup profile or
create a new one.

Similar to how firefox starts actually: provide a way for customization,
preferably using lots of nifty tooltips and explanations and once a user
has a working config, enable them to save and reuse configs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-1898496 ] prepackaged GUI image

[SourceForge.net <no...@so...>]

Feature Requests item #1898496, was opened at 2008-02-21 08:05
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: prepackaged GUI image

Initial Comment:
The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux.

Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 19:14

Message:
Logged In: NO 

Python is awesome, i know, but why not C#?

Mono is distribuited with major linux systems and on windows you're fully
integrated with .NET! I think that a lot of users are windows based so a
fully native interface and a fully integrated application can do better
than a python application

Another really important stuff is that with .NET you can easely build two
interfaces and load the preferred at startup time simply checking the
operative system ... with the interfaces that relies on a set of
functionalities implemented in a backend


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-29 18:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

If somebody has knowledges about Python, then here are some of GUI scripts
for coLinux configuration, that has to be finish:

http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/configurator/

It's very old. First needs to remove the outdated XML from that.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 16:26

Message:
Logged In: NO 

The following site contains a listing of available GUI toolkit bindings
for python, including a section about UI-building toolkits (e.g. dialog
editors):

http://wiki.python.org/moin/GuiProgramming

In addition, here's  a site providing a full tutorial about PyQT
programming:

http://www.commandprompt.com/community/pyqt/book1
http://wiki.python.org/moin/PyQt

PythonStudio includes a full GUI editor, as well:
http://www.codeplex.com/IronPythonStudio

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:57

Message:
Logged In: NO 

thinking about it, the most promising approach would probably be to simply
implement this totally separate, using a scripting language and a GUI
toolkit, i.e. something like python or ruby with GTK/QT bindings. This way,
it would not unnecessarily affect any of the existing code, would be very
much straight forward and also flexible and easily extendsible for future
changes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:24

Message:
Logged In: NO 

something like this would probably be best implemented as a separate,
standaline "profile manager", so that creating/editing and deleting
profiles can be done via this app, and starting a profile would only entail
passing the stored parameters to the corresponding binaries, this would
keep the overhead to a minimum.



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 06:03

Message:
Logged In: NO 

see "andLinux"

however, usability could still be somewhat improved for users with a
non-nix background, in particular the whole setup process should either be
more intuitive or simply provide some more GUI frontends, i.e. by allowing
the most common actions to be directly done from the executables via UI
means, rather than requiring users to pass lots of cryptic options via
command line parameters. In this context, it would already be a significant
improvement if the most basic and relevant parameters could be configured
via some sort of GUI frontend, be it embedded or not, so that running a
process without REQUIRED parameters automatically brings up a dialog for
users to configure the most important parameters, and optionally save them
as startup profiles, so that they may next time select a startup profile or
create a new one.

Similar to how firefox starts actually: provide a way for customization,
preferably using lots of nifty tooltips and explanations and once a user
has a working config, enable them to save and reuse configs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

[coLinux-devel] [ colinux-Feature Requests-1898496 ] prepackaged GUI image

[SourceForge.net <no...@so...>]

Feature Requests item #1898496, was opened at 2008-02-21 09:05
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: prepackaged GUI image

Initial Comment:
The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux.

Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2008-08-29 20:50

Message:
Logged In: YES 
user_id=579204
Originator: NO

If somebody has knowledges about Python, then here are some of GUI scripts
for coLinux configuration, that has to be finish:

http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/configurator/

It's very old. First needs to remove the outdated XML from that.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 18:26

Message:
Logged In: NO 

The following site contains a listing of available GUI toolkit bindings
for python, including a section about UI-building toolkits (e.g. dialog
editors):

http://wiki.python.org/moin/GuiProgramming

In addition, here's  a site providing a full tutorial about PyQT
programming:

http://www.commandprompt.com/community/pyqt/book1
http://wiki.python.org/moin/PyQt

PythonStudio includes a full GUI editor, as well:
http://www.codeplex.com/IronPythonStudio

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 08:57

Message:
Logged In: NO 

thinking about it, the most promising approach would probably be to simply
implement this totally separate, using a scripting language and a GUI
toolkit, i.e. something like python or ruby with GTK/QT bindings. This way,
it would not unnecessarily affect any of the existing code, would be very
much straight forward and also flexible and easily extendsible for future
changes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 08:24

Message:
Logged In: NO 

something like this would probably be best implemented as a separate,
standaline "profile manager", so that creating/editing and deleting
profiles can be done via this app, and starting a profile would only entail
passing the stored parameters to the corresponding binaries, this would
keep the overhead to a minimum.



----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-29 08:03

Message:
Logged In: NO 

see "andLinux"

however, usability could still be somewhat improved for users with a
non-nix background, in particular the whole setup process should either be
more intuitive or simply provide some more GUI frontends, i.e. by allowing
the most common actions to be directly done from the executables via UI
means, rather than requiring users to pass lots of cryptic options via
command line parameters. In this context, it would already be a significant
improvement if the most basic and relevant parameters could be configured
via some sort of GUI frontend, be it embedded or not, so that running a
process without REQUIRED parameters automatically brings up a dialog for
users to configure the most important parameters, and optionally save them
as startup profiles, so that they may next time select a startup profile or
create a new one.

Similar to how firefox starts actually: provide a way for customization,
preferably using lots of nifty tooltips and explanations and once a user
has a working config, enable them to save and reuse configs

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788

[coLinux-devel] [ colinux-Bugs-2077641 ] Randoms Windows XPSP3 hangs

[SourceForge.net <no...@so...>]

Bugs item #2077641, was opened at 2008-08-27 08:33
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eugenesan (eugenesan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Randoms Windows XPSP3 hangs

Initial Comment:
Hi,

I've noticed that builds created in last several months randomly crashes or hangs my host system.
In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs...
I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously):
* CPU Pentium M => Core2Duo (IBM T43->T61)
* Windows SP2 => SP3
* No other notable changes performed

In addition crashes appears regardless usage of:
* cobd or scsi
* cobd async or sync
* pcap-bridnge or ndis-bridge

My coLinux starts as service using following command:

"C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

* cofs almost never used
* ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while.
* VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP).
* partitions (of course) never cross-mounted
* no signs of errors of any kind from linux side(but, maybe, some random networking outages)
* Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-(

I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have.

Thanks ahead





----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2008-08-29 20:35

Message:
Logged In: YES 
user_id=579204
Originator: NO

Hello Eugenesan,

have you checked the last build from http://www.colinux.org/snapshots/
from 23-Aug-2008?

I ask, because all versions before this snapshot have memory leakages and
race conditions in the interrupt handler. I found they by heavy network
checks with the ndis-bridge and the tool "netio". The last version was
running without problems over many hours. Some more details you can read
from "Recent ChangeLog", the revisions from r1114 and r1118 can also be
fixed the problem, you described here.

For debugging, run the command line you have posted from Windows prompt
without the parameter "--run-service:" and add the parameter "-v 3" instead
(Verbose).

A small bug I see: Path parameter is broken from space in "My Apps". Is
harmless, because you you have full paths for all files there.

Henry


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788