colinux-users — coLinux users mailing list

Re: [coLinux-users] Colinux Ubuntu Guest Extremely slow

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

pa...@wa...(Paul Waldo)  21.12.07 08:52


>I am running the latest colinux (0.7.1), 

Please try the devlopement release 0.8.
It's stable enough for a developer ,)

>and it seems to be running quite slow.  
>The KDE UI is somewhat jerky because of the slowness, but
>my main concern is raw processing power.  I am hoping to be able to do
>Java software development at work without having to interact with
>Windows.  I'm willing to deal with the fact that coLinux is only using
>one of the two CPUs, but I can't justify using it on a daily basis if
>it takes significantly longer to do my job.

>Here are the platform details:

>Host
>*******
>Windows XP
>coLinux 0.7.1
>Pentuim D, ~3 GHz
>3GB RAM

>Guest
>*********
>Kubuntu Gutsy i386

>I booted my Kubuntu Live CD and found that it reported the bogoMIPS at
>5990.33.  coLinux reports the bogoMIPS at 1520.43.  That means the
>coLinux guest is running at ~25% of native speed.  I know that
>bogoMIPS are not an true speed representation, but I think it is close
>enough to give a general idea of what is going on.

>Any help on getting colinux up to speed would be greatly appreciated!

Maybe fiddling with "boot.ini" might help to find the core problem

Some ideas:

/burnmemory=1024
/maxmem=1024 (better use burnmemory)
/3GB (or not?)
/userva=2900 (or less?)
/PAE (?)
/pcilock  (?)

Please report your results.

http://support.microsoft.com/kb/833721/EN-US/
"Available switch options for the Windows XP and the Windows Server 2003 Boot.ini files"
Rainer---<=====>                         Vertraulich
             //  
           //                              
         <=====>--------------ocholl, Kiel, Germany ------------

[coLinux-users] Colinux Ubuntu Guest Extremely slow

[Paul W. <pa...@wa...>]

Hi all,

I am running the latest colinux (0.7.1), and it seems to be running 
quite slow.  The KDE UI is somewhat jerky because of the slowness, but 
my main concern is raw processing power.  I am hoping to be able to do 
Java software development at work without having to interact with 
Windows.  I'm willing to deal with the fact that coLinux is only using 
one of the two CPUs, but I can't justify using it on a daily basis if it 
takes significantly longer to do my job.

Here are the platform details:

Host
*******
Windows XP
coLinux 0.7.1
Pentuim D, ~3 GHz
3GB RAM

Guest
*********
Kubuntu Gutsy i386

I booted my Kubuntu Live CD and found that it reported the bogoMIPS at 
5990.33.  coLinux reports the bogoMIPS at 1520.43.  That means the 
coLinux guest is running at ~25% of native speed.  I know that bogoMIPS 
are not an true speed representation, but I think it is close enough to 
give a general idea of what is going on.

Any help on getting colinux up to speed would be greatly appreciated!

Paul

Re: [coLinux-users] starting gnome from colinux possible?

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

Which memory size do you have configured for andLinux? The default size 
is 128MB of RAM and 256 of swap. This might not be enough for running 
the whole gnome desktop.

Also, you might want to install the dbus package (apt-get install dbus 
). That will solve the error message (but i don't think it's the main 
cause).

Finally, beware of updating to 7.10. The init daemon changed, and it 
won't open automatically the desktop. I don't have here the details of 
how to fix that, but it's about creating an init script in some 
directory instead of relying on /etc/inittab

[coLinux-users] starting gnome from colinux possible?

[Michael R. <mic...@fr...>]

Hi there!

I am using AndLinux and it`s great! Now I can enjoy using most linux 
native apps with nearly full speed on windows. :)

The standard disk size was about 2 GB, I used successfully the resize 
tool and resized to 7 GB. Then I done apt-get install ubuntu-desktop. It 
installed without any error.

I hear the start sound, I see some windows and then it stops. If you 
need any further infos form me just ask.

andLinux:~# gnome-session
SESSION_MANAGER=local/andLinux:/tmp/.ICE-unix/2938
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
alarm-notify.c:366 (alarm_notify_new) - Alarm Notify New
  alarm-notify.c:302 (alarm_channel_setup) - Channel Setup
  alarm-notify.c:241 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1871 (alarm_queue_init)
alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Mon Dec 17 
19:00:00 200

evolution-alarm-notify-Message: Setting timeout for 54871 1197936000 
1197881129
evolution-alarm-notify-Message:  Mon Dec 17 19:00:00 2007

evolution-alarm-notify-Message:  Mon Dec 17 03:45:29 2007

libnotify-Message: Unable to get session bus: Unable to determine the 
address o
  the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)

-----

There was an error starting the GNOME Settings Daemon.

Some things, such as themes, sounds, or background settings may not work 
correctly.

The last error message was:

Unable to determine the address of the message bus (try 'man 
dbus-launch' and 'man dbus-daemon' for help)

GNOME will still try to restart the Settings Daemon next time you log in.

-----

The information about the crash has been successfully collected.

The application that crashed is not known to bug-buddy, therefore the 
bug report can not be sent to the GNOME Bugzilla.  Please save the bug 
to a text file and report it to the appropriate bug tracker for this 
application.

Memory status: size: 24629248 vsize: 0 resident: 24629248 share: 0 rss: 
8843264 rss_rlim: 0
CPU usage: start_time: 1197881271 rtime: 0 utime: 40 stime: 0 cutime:37 
cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/evolution-alarm-notify'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232426640 (LWP 2988)]
[New Thread -1232573520 (LWP 2999)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7271e91 in waitpid () from /lib/libc.so.6
#0  0xb7271e91 in waitpid () from /lib/libc.so.6
#1  0xb7d851b6 in gnome_gtk_module_info_get () from 
/usr/lib/libgnomeui-2.so.0
#2  <signal handler called>
#3  0xb7210986 in raise () from /lib/libc.so.6
#4  0xb7212043 in abort () from /lib/libc.so.6
#5  0xb73cf122 in g_logv () from /usr/lib/libglib-2.0.so.0
#6  0xb73cf159 in g_log () from /usr/lib/libglib-2.0.so.0
#7  0x0805d500 in main ()

Thread 2 (Thread -1232573520 (LWP 2999)):
#0  0xb729b5d9 in poll () from /lib/libc.so.6
No symbol table info available.
#1  0xb73c9813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#2  0xb73c9b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#3  0xb79637e0 in link_set_io_thread () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#4  0xb73e438f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#5  0xb70210fb in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#6  0xb68864b0 in ?? ()
No symbol table info available.
#7  0xb68864b0 in ?? ()
No symbol table info available.
#8  0xb68864b0 in ?? ()
No symbol table info available.
#9  0xb68864b0 in ?? ()
No symbol table info available.
#10 0x00000000 in ?? ()
No symbol table info available.

Thread 1 (Thread -1232426640 (LWP 2988)):
#0  0xb7271e91 in waitpid () from /lib/libc.so.6
No symbol table info available.
#1  0xb7d851b6 in gnome_gtk_module_info_get () from 
/usr/lib/libgnomeui-2.so.0
No symbol table info available.
#2  <signal handler called>
No symbol table info available.
#3  0xb7210986 in raise () from /lib/libc.so.6
No symbol table info available.
#4  0xb7212043 in abort () from /lib/libc.so.6
No symbol table info available.
#5  0xb73cf122 in g_logv () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6  0xb73cf159 in g_log () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#7  0x0805d500 in main ()
No symbol table info available.
#0  0xb7271e91 in waitpid () from /lib/libc.so.6

Re: [coLinux-users] Win 2000

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

mj...@ma...(mattias)  15.12.07 19:39


>Ok
>But how to get internet accesss etc to colinux
>I meen i can't bridge connections
>In win 2000

 -Install Winpcap 
 - Use slip and forward ports

What is exactly (literally) your problem?

Re: [coLinux-users] Win 2000

[mattias <mj...@ma...>]

Ok
But how to get internet accesss etc to colinux
I meen i can't bridge connections
In win 2000

-----Ursprungligt meddelande-----
Fr=E5n: Henry Nestler [mailto:Hen...@Ar...]=20
Skickat: den 15 december 2007 18:22
Till: mattias
Kopia: col...@li...
=C4mne: Re: [coLinux-users] Win 2000


mattias wrote:
> Can i run colinux in windows 2000?

Yes.

--=20
Henry N.

Re: [coLinux-users] Win 2000

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

mattias wrote:
> Can i run colinux in windows 2000?

Yes.

-- 
Henry N.

[coLinux-users] Win 2000

[mattias <mj...@ma...>]

Can i run colinux in windows 2000?

Re: [coLinux-users] Lost root password.

[peter g. <plu...@p1...>]

> Is it possible to reset the root password on CoLinux?
>   
add init=/bin/sh to the bootparams, boot the system and run

mount -o remount,rw /
passwd root

and enter a new root password

Re: [coLinux-users] Lost root password.

[Holger K. <hol...@gm...>]

Dave Coventry schrieb:

> Is it possible to reset the root password on CoLinux?

Not that i tried, but i expect that if you mount the partition in another Linux/Colinux and erase the password hash for root in /etc/shadow you should be able to logon without password and set a new one.

[coLinux-users] Lost root password.

[Dave C. <dgc...@gm...>]

Hi,

Is it possible to reset the root password on CoLinux?

[coLinux-users] X

[mattias <mj...@ma...>]

are X supported in colinux yet?

Re: [coLinux-users] Beginners question/slirp/colinux 0.7.1

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

Christian Ritter wrote:
> Dear colinuxers,
> 
> I just installed colinux 1.7.1 under Vista on a brand new laptop. 'Went 
> almost like butter: slirp interface allowed connections to the outside, 
> tap interface to the windows OS on the laptop. However, frequently, 
> after about 10 minutes, the slirp connection dies (at least attempts of 
> reaching the outside via ssh requests or apt-get / I'm using a Debian 
> setup). On the other hand, established connections via ssh remain 
> operational.
> 
> Here is the information of the setup:
>     laptop connected to network via router modem (DSL)
>     laptop runs Vista, Comodo, Antivir (and, obviously colinux)
>    
> Today, I'll check over a different network entry point.
> 
> Any ideas what I could check to see what happens to the slirp when it 
> 'falls asleep'? so far I have not been able to get it back working 
> without halting colinux and restarting it.

Use ProcessExplorer (or taskman) to see the current command line of
slirp after startup. kill the task colinux-slirp-net-daemon.exe and
start it again on new command prompt with the same parameters, you seen
before.

If the error comes again, view messages from this. Any errors from this
daemon there? I hope. This would help to find out the problem.

CTRL-C the colinux-slirp-net-daemon.exe and start it again. Helps this?
True, this is an ugly workarrount to not reboot coLinux completely.

Other idea: An DNS problem?
Try wget of a website you know from within coLinux with dotted
ipaddress. The ipaddress will see with "ping www.google.com" on windows
before.

Check the DNS on your windows side "ipconfig.exe /ALL" before and after
the stopping. Are there different?

Have more as one DSN there? Try to add the second and third DNS from
windows side to /etc/resolv.conf

How many "connected" networks you have on the windows side?

Remember: Slirp has no ping support. But, can you get some from your
router, perhaps a webconfig or start page with "wget ip.of.your.router",
or from other computers on your network?

-- 
Henry N.

[coLinux-users] Beginners question/slirp/colinux 1.7.1

[Christian R. <chr...@uc...>]

Dear colinuxers,

I just installed colinux 1.7.1 under Vista on a brand new laptop. 'Went 
almost like butter: slirp interface allowed connections to the outside, 
tap interface to the windows OS on the laptop. However, frequently, 
after about 10 minutes, the slirp connection dies (at least attempts of 
reaching the outside via ssh requests or apt-get / I'm using a Debian 
setup). On the other hand, established connections via ssh remain 
operational.

Here is the information of the setup:
    laptop connected to network via router modem (DSL)
    laptop runs Vista, Comodo, Antivir (and, obviously colinux)
   
Today, I'll check over a different network entry point.

Any ideas what I could check to see what happens to the slirp when it 
'falls asleep'? so far I have not been able to get it back working 
without halting colinux and restarting it.

Chris

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

[colipa <co...@co...>]

huqianjb

Re: [coLinux-users] a small bug of cofs

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

Paolo Minazzi wrote:
> I'm using the new 0.7.1 and it semms stable ! Very good !
> 
> There is a small bug ( I think ) in the cofs
> 
> I have mounted in /mnt/c my C drive
> 
> If I digit the commands
>  > cd /mnt/c
>  > ls
> 
>  the output is
> 
> ...
> flash/
> ...
> 
> Ok. Now I digit
>  > cd FLA*
> and the prompt become
> /mnt/c/FLA* >
> 
> The I digit the "ls" command and I have
> 
> /usr/bin/ls: .: Input/output error
> 
> This is not an important problem, but I think that it is good if someone 
> can solve it.

Solved as chdir into a directory was existing with other upper/lower 
match as the wildcard was given. This line triggers this harmless bug 
with buggy working directory:
   mkdir /mnt/c/foo ; cd /mnt/c/FO*

Same problem on shell without resolving wildcards:
   mkdir /mnt/c/foo ; cd '/mnt/c/fo*'

Fixed in http://www.colinux.org/snapshots/ for version 0.8.0.
Chdir return with 'file not exist' as error now.

Thanks for reporting.

-- 
Henry N.

[coLinux-users] a small bug of cofs

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

I'm using the new 0.7.1 and it semms stable ! Very good !

There is a small bug ( I think ) in the cofs

I have mounted in /mnt/c my C drive

If I digit the commands
> cd /mnt/c
> ls

 the output is

...
flash/
...

Ok. Now I digit
> cd FLA*
and the prompt become
/mnt/c/FLA* >

The I digit the "ls" command and I have

/usr/bin/ls: .: Input/output error

This is not an important problem, but I think that it is good if someone can
solve it.
Thanks for this great SW !

Paolo

Re: [coLinux-users] Error compiling Colinux daemon 0.7.1

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

Paolo Minazzi wrote:
> /mnt/coLinux-0.7.1/stable-colinux-20070714>make colinux
> make[1]: Entering directory `/mnt/coLinux-0.7.1/stable-colinux-20070714/src'
> python ../bin/make.py colinux
> Traceback (most recent call last):
>   File "../bin/make.py", line 10, in ?
>     main()
>   File "../bin/make.py", line 6, in main
>     from comake import main as comake_main
> ImportError: No module named comake
> make[1]: *** [colinux] Error 1
> make[1]: Leaving directory `/mnt/coLinux-0.7.1/stable-colinux-20070714/src'
> make: *** [colinux] Error 2thon ../bin/make.py colinux
> Traceback (most recent call last):
>   File "../bin/make.py", line 10, in ?
>     main()
>   File "../bin/make.py", line 6, in main
>     from comake import main as comake_main
> ImportError: No module named comake

Hoops. Many thanks!
The file bin/comake/__init__.py is missing in archive. I will make the 
source tar archive again. By the while please pick it from SVN:
http://colinux.svn.sourceforge.net/svnroot/colinux/branches/stable/bin/comake/__init__.py

-- 
Henry N.

[coLinux-users] Error compiling Colinux daemon 0.7.1

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

Hi.
I tried to compile coLinux 0.7.1.
The compilation process works fine for linux kernel and modules but I have
the followin error when it tries to compile the daemon.
My system is Slackware 11.0

This is the output

Making kernel 2.6.12
Making Module 2.6.12
Create md5sum
/mnt/coLinux-0.7.1/stable-colinux-20070714>make colinux
make[1]: Entering directory `/mnt/coLinux-0.7.1/stable-colinux-20070714/src'
pyCreate md5sum
/mnt/coLinux-0.7.1/stable-colinux-20070714>make colinux
make[1]: Entering directory `/mnt/coLinux-0.7.1/stable-colinux-20070714/src'
python ../bin/make.py colinux
Traceback (most recent call last):
  File "../bin/make.py", line 10, in ?
    main()
  File "../bin/make.py", line 6, in main
    from comake import main as comake_main
ImportError: No module named comake
make[1]: *** [colinux] Error 1
make[1]: Leaving directory `/mnt/coLinux-0.7.1/stable-colinux-20070714/src'
make: *** [colinux] Error 2thon ../bin/make.py colinux
Traceback (most recent call last):
  File "../bin/make.py", line 10, in ?
    main()
  File "../bin/make.py", line 6, in main
    from comake import main as comake_main
ImportError: No module named comake
make[1]: *** [colinux] Error 1
make[1]: Leaving directory `/mnt/coLinux-0.7.1/stable-colinux-20070714/src'
make: *** [colinux] Error 2

This is an error of my configuration ?
Thanks in advance
Paolo

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.1 released

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

Cooperative Linux version 0.7.1 is released now.

Version 0.7.1 was long time tested as release candidate (rc4) and is 
released now.  There are no changes between rc4 and release version, so 
we released the binary from builddate 14-Jul-2007. Users of this 
snapshot don't need update.

The most imported is, that the configuration is a plain text file now. 
Old XML files can simple convert with the tool coLinux-xml2cfg.

This is an upgrate with better performance, better memory allocation, 
new kernel 2.6.12 and lots of bugs where fixed. Cofs is full usable.
Details finds in News and more in source control Changelog.
Notes contains interestings about installing and upgrading.

Download:  http://sourceforge.net/projects/colinux/files
News:      http://colinux.wikia.com/wiki/Version_0.7.1
Notes: 
http://sourceforge.net/project/shownotes.php?group_id=98788&release_id=551328
Changelog: http://www.colinux.org/snapshots/stable-ChangeLog

NEWS of Version 0.7.1
* colinux-daemon:
   - Obsoleted the use of XML files for configuration.
     XML config files have been removed.  Use the command-line
     syntax in a name=value per line plain text file instead.  Please
     read syntax from colinux-daemon.txt and view into the file
     example.conf in coLinux install directory.
   - Added support for @ at the command line for passing simple
     configuration files.
   - Added '-k' option to suppress kernel messages on boot. This should
     let you watch other daemon's output more easily.
   - Incrase the maximum numbers of monitors from 16 to 64.
   - Warn about double configured index for cobd, eth, cofs, ttys, exec.
   - Print human readable error, if wrong linux.sys installed.
   - Return errorlevel procedures (return from running, --install-driver,
     --status-driver, ...)  Errorcodes: 0=OK, 3=driver version mismatch,
     14=driver no installed, 255=general fail (-1)
   - New: "execX=..." in configuration, launch external programs.
   - Bug fix: Quotation marks detection in config file and args, samples:
     eth0=tuntap,"LAN-Connection 14",00:11:22:33:44:55
     cofs0="C:\My files"
   - New: "ttysX=..." in configuration, launch coserial daemon.
     Internaly parameters "-f DeviceName -m Mode" for colinux-serial-daemon.
     Serial daemon is light usable under WinNT, you can login on /dev/ttyS0
     or redirect serial communication port (COM1 for sample).
   - Workaround for Xeon and P4 with DEP/noexecute problems (flush_tlb).
* Console:
   - "set COLINUX_CONSOLE_EXIT_ON_DETACH=1" to close FLTK/NT console
     after shutting down and detach coLinux.
   - Menu Monitor Select is usable to select ones from running instances.
* Service running:
   - Shutdown the service, if Windows is shutting down.
   - All files and config file no longer needs absolute path names on
     '--install-service'.  Working directory stored for service run later.
* Kernel:
   - has been updated from 2.6.11 to 2.6.12
   - Bug #1479042: Ignore bootparm "no387", while no emulation is enabled
   - Bug #1665812: Disable /proc/kcore from kernel config.
     Reading from this file would crash host system.
   - Bug #1643371: BSOD from dmidecode, fixed by disallow mmap on /dev/mem.
* Updated libraries:
   - MinGW from 3.7 to 3.9
   - w32api from 3.2 to 3.4
   - WinPcap from 3.1-beta4 to 3.1
   - FLTK from 1.1.4 to 1.1.6
   - Remove all XML libraries from source
* Installer:
   - Add new images ArchLinux and FedoraCore5.
   - Gentoo image updated.
   - Add locations Australia and SouthAmerica
   - Used NSIS version 2.22
* initrd:
   - Automatic use cofs31 as path to file vmlinux-modules.tar.gz.
   - Print error on console, if initrd can't load.
   - Bugfix: 'root=/dev/...' must no longer the first bootparm for initrd.
* cofs:
   - Break out the limit of filename length.  Basename length up to
     255 chars.  Fullpath is limited by path depth of 256 directories.
   - Bug #1151757: COFS disallow mutiple mounts.
   - Bug #1190080: Fix cofs file time/mode/flags after touch or write.
   - Fix mmap read error behind end of file (was not zero filled).
* TAP-Win32 device driver
   - version 8.4 update from openvpn-2.1_beta15a
   - usable without admin rights
   - fixed crashing Vista
   - connection speed status 100 MBit/s (show/view only)
   - 'Check for truncated IPv4 packets' diabled
   - without linker debug symbols, without runtime debugging
* pcap/Bridged:
   - Allows empty name for autosearch a connected LAN interface.
* slirp:
   - SLiRP is the first choice of colinux networking types (easy setup).
   - Multiple redirection as parameter ':count'
     (Thanks to Bernd Brandstetter)
   - UDP receive Buffer incrase to 32K (win32 default was 8K),
     maximal size of a packet is 32767 bytes now.
     (Thanks to Bernd Brandstetter)
   - Incrase TCP MSS from 512 to 1460 bytes.
   - Remove honypot ports 517, 518 and 7648 from udp listen.
     talk and Cu-Seeme are not implement, still remove the table mow.
   - Runtime debug code disabled.
* Introduce a new build system:
   - Target kernel dir splitt into source and objects.  New params
     --targetkernelsource and --targetkernelbuild as replacement for
     the obsolate --targetkerneldir for configure.
   - Allow to use ccache (http://ccache.samba.org/).
   - Use quilt for kernel patches, if quilt installed, fallback if not.
   - 'make package' creates one zip archive with and an other without
     debugging symbols.  The zip with symbols only will no more create.
   - New param --gcc-guest-build for configure: Creates the kernel gcc
     from source of cross gcc, if your system has an incompatible gcc.
   - New parameter --verbose for configure.
   - Python bin/make.py colinux:
     o Automatic awareness of changes in header files.
     o Doesn't require 'make clean' between compilation of
       different coLinux ports.
     o Clean, flexible and easier to maintain.
* Add icons to the other executables.
* Linux as host: More positive tested host kernels: 2.6.17, 2.6.18
* Wiki moved from wiki.colinux.org to http://colinux.wikia.com

-- 
Henry Nestler

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

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

VGhhbmtzIGZvciB5b3VyIHJlc3BvbnNlcywgZXZlcnlvbmUuICBGaWxlZCBhIGZlYXR1cmUgcmVx
dWVzdCB0byB0aGUgdHJhY2tlci4KCkFuc2h1bAoKT24gTm92IDEsIDIwMDcgMzoyMyBQTSwgSGVu
cnkgTmVzdGxlciA8SGVucnkuTmVAYXJjb3IuZGU+IHdyb3RlOgo+IEFuc2h1bCB3cm90ZToKPiA+
IEkgdGhvdWdodCBvZiB0aGF0IGJ1dCB0aGVyZSBpcyBubyBzdGFydC5leGUgaW4gd2luZG93cyBY
UC4KPiA+IFN0YXJ0aW5nIGl0IHZpYSBhIGJhdGNoIHNjcmlwdCBkaWRuJ3Qgd29yayB0b28gYmVj
YXVzZSB4bWluZyBkaWRuJ3QKPiA+IGV4aXQgd2l0aCBjb0xpbnV4Lgo+Cj4gU29ycnkuIFlvdSBh
cmUgcmlnaHQuIEhhdmUgbm8gU1RBUlQuRVhFIGluIFhQLiBJdCdzIGJ1aWxkaW4gb2YgQ01ELkVY
RQo+IG9ubHkuIFRoaXMgb3BlbnMgYSBuZXcgcHJvY2VzcyBJRCwgYW5kIGNvTGludXggZGFlbW9u
IGNhbiBub3QgdGVybWluYXRlCj4gaXQgYXV0b21hdGljbHkgYWZ0ZXIgc2h1dHRpbmcgZG93biBj
b0xpbnV4Lgo+Cj4gPiBDYW4gSSBwdXQgdGhpcyB1cCBhcyBhIGZlYXR1cmUgcmVxdWVzdD8KPgo+
IFllcywgb2YgY3Vyc2UuCj4KPgo+IC0tCj4gSGVucnkgTi4KPgoKCgotLSAKSSBoYXZlIG5vIHNw
ZWNpYWwgdGFsZW50cy4gSSBhbSBvbmx5IHBhc3Npb25hdGVseSBjdXJpb3VzLgogICAtLUFsYmVy
dCBFaW5zdGVpbgotLQpodHRwOi8vd3d3LmNtaS5hYy5pbi9+YW5zaHVsLwpodHRwOi8vYmFib29u
bG9naWMuY29tCi0tCuCkheCkguCktuClgeCksiAg4KSW4KSC4KSh4KWH4KSy4KS14KS+4KSyCg==

[coLinux-users] Slowdown in new version

[Ryan C. U. <nem...@ic...>]

I posted this issue:
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1824299&group_=
id=3D98788&atid=3D622063

Anyone have any ideas why I'm observing this problem?

--=20
Ryan C. Underwood, <ne...@ic...>

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

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

Anshul wrote:
> I thought of that but there is no start.exe in windows XP.
> Starting it via a batch script didn't work too because xming didn't
> exit with coLinux.

Sorry. You are right. Have no START.EXE in XP. It's buildin of CMD.EXE 
only. This opens a new process ID, and coLinux daemon can not terminate 
it automaticly after shutting down coLinux.

> Can I put this up as a feature request?

Yes, of curse.


-- 
Henry N.

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

[Holger K. <hol...@gm...>]

Anshul schrieb:
> I thought of that but there is no start.exe in windows XP.

Of course there is. If start is missing, something is wrong with your windows installation or you didn't use cmd.exe. Cygwins bash has no start command. 

 

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

[Brian D. <br...@de...>]

Anshul wrote:

> I thought of that but there is no start.exe in windows XP.

Sure there is, but it's called cmd.exe.

cmd.exe /c "start /abovenormal /b path-to\xming.exe"

Brian