colinux-users — coLinux users mailing list

[coLinux-users] feature requirement : delay in exec0 exec1

[Wufu C. <cc...@gm...>]

Hi
   feature requirement :
Would you implement the delay function in configuration : exec0 , exec1?

I try to auto lauch the xming (with xdmcp support) .
the ximg should be launched after the colinux guest start up (e.g gdm
executed)

exec0="Xming\Xlaunch -run xming\config.xdmcp"
exec1="sound\esd","-tcp -public"

==> new feature

exec0="Xming\Xlaunch -run xming\config.xdmcp"  -d 30
; -d 30 : means delay 30 seconds
currently , the workaround is :
I have to write a litter batch file
with vbs script to delay
~~~~~~~~~~~~~~~~~~~~~~~~~~~
auto.bat

colinux-daemon  @configuration.cfg

rem  delay about 60 seconds
start /w delay.vbs 60

rem xming launch supported xdmcp
Xming\Xlaunch -run xming\config.xdmcp


B.R

Wufu Chen

Re: [coLinux-users] TUN/TAP on linux as host

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

Jitesh Shah wrote:
> I have configured slirp on colinux with linux as a host.
> But, a problem I face is that if I run more than one guest, these are
> not visible to each other.
> I was wondering whether it is possible to configure TUN/TAP for linux as
> a host. (or may be libpcap)

The last part in this mails [1] [2] is a part with TUN/TAP under Linux
as host.

If you wandt to use more as one guest, you need a different tun/tap for
every guest and *must* set static routing tables between. The host
ipaddress must set after the coLinux networkdaemon is coming up. That's
why I have a delay 3 seconds.

I think, licpcap would work more easyly. It should be usable. I have
tested it long time ago (version 0.7.1) But, I have no config.

Slirp with different forwardings with different ports on host should
also be usable. Remember, that one guest see the other guest on address
10.0.2.2, not on the real ethernet address.

[1]
http://sourceforge.net/mailarchive/message.php?msg_id=4786AC56.3030803%40henry.ne.arcor.de
[2]
http://www.nabble.com/Re%3A-Colinux-crash-on-insmod-colinux.ko-p14746583.html


> I went through http://colinux.wikia.com/wiki/Network but the guide is
> for windows as a host.

Well, Linux as host is not good documented. Linux as host is no full
working. It't more for developing and debugging coLinux self.

-- 
Henry N.

[coLinux-users] TUN/TAP on linux as host

[Jitesh S. <jit...@gm...>]

hi!!
I have configured slirp on colinux with linux as a host.
But, a problem I face is that if I run more than one guest, these are not
visible to each other.
I was wondering whether it is possible to configure TUN/TAP for linux as a
host. (or may be libpcap)
I went through http://colinux.wikia.com/wiki/Network but the guide is for
windows as a host.


thanks.
-- 
Run away from difficulties to stand to fight them tomorrow :):)

http://aterriblewasteoflife.blogspot.com
http://worstjokes.blogspot.com

Re: [coLinux-users] process accounting: Function not implemented

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

Rainer Zocholl wrote:
> Bug or feature or superfluous?

Feature. For a single user?

> COLINUX:~# atop
> activate process accounting: Function not implemented
> warning: no process exit detection!
> 
> man atop
>        When atop is started, it switches on the process accounting mechanism in the ker-
>        nel.  This forces the kernel to write a record with accounting information to the
>        accounting file whenever a process ends.  Apart from  the  kernel administration
>        related  to the running processes, atop also interprets the accounting records on
>        disk with every interval; in this way atop can also show the activity of  a  pro-
>        cess during the interval in which it is finished.

zgrep "CONFIG_BSD_PROCESS_ACCT" </proc/config.gz
# CONFIG_BSD_PROCESS_ACCT is not set

I think, this is the kernel feature, what "atop" needs.
You can enable this kernel feature and recompile the kernel.
Because we copy the kernels config from older kernel and not enable all
feature, we have not enabled it. The default kernel config
arch/i386/defconfig has also not enabled this.

By the while: Process accounting under virtual machines would not
perfect work. The timer dosn't run in constant time slices. Same problem
we have with the 'HZ' value.

-- 
Henry N.

[coLinux-users] process accounting: Function not implemented

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

Bug or feature or superfluous?


COLINUX:~# atop
activate process accounting: Function not implemented
warning: no process exit detection!

man atop
       When atop is started, it switches on the process accounting mechanism in the ker-
       nel.  This forces the kernel to write a record with accounting information to the
       accounting file whenever a process ends.  Apart from  the  kernel administration
       related  to the running processes, atop also interprets the accounting records on
       disk with every interval; in this way atop can also show the activity of  a  pro-
       cess during the interval in which it is finished.


colinux:~# uname -a
Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Sat Dec 22 05:08:37 UTC 2007 i686
GNU/Linux


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

Re: [coLinux-users] suggestion: linux runtime environment

[Christopher D. C. <ccl...@ac...>]

Michael Reichenbach <mic...@fr...> wrote:
> Christopher D. Clausen wrote:
>> Running coLinux is certinaly not as safe and easy as running a
>> piece of Java code in a VM.
>
> Never thought that this could become the biggest problem. If so, why
> this project exists then? Just for fun and to show that it`s possible?
> Sure not, what?

Back when I was first using coLinux, Virtual PC was not free (as in no 
money.)

>> Also be aware of security implications of doing such things.  Java is
>> somewhat sandboxed, coLinux is not.  CoLinux can crash your computer.
>
> Is this a big problem? No workarround?

It is a big problem for me.  Running Linux in Virtual PC or Virtual 
Server these days costs nothing additional and has a significantly lower 
change of taking down the host OS.  With hardware virtualization support 
in newer processor, the performance impact in significantly reduced.

> There is no big package archive like the one from debian. And
> realistic, I doub`t there will ever be one. So this program may be
> nice but it lacks contributers.

The program itself is fine.  And many packages are available for Windows 
in MSI format.  Someone just needs to actually create a repository. 
Trying to get non-native stuff to sort-of work will provide an 
alternative and further delay the work to just install things using MSIs 
directly from a Windows software repository.

>> Again, why not just port these things to run on Windows?
>
> Porting is sometimes complicated. Ok, if you use platform portable
> libs then it`s much more easy. But often the program was native for
> one platform only, then users started asking for a port. If it`s
> using linux specific libs or posix api or specific things like
> /proc/cpuinfo which windows does not provide then porting is not so
> easy.

Yes, but you could look at using the Subsystem for Unix applications 
(SUA) to port non-Windows code to Windows.

> Another reason is that there are tons of programs. Why "10.000" people
> start porting all those apps if just 1 project could allow to run all
> linux native programs also on windows because of this "trick"?

There are even more programs for Windows.  Someone just needs to bundle 
them in MSIs and setup a repository.

>> And windows has a packaging technology that uses MSI files.  Just
>> download an MSI and install.  Why mess with a non-native system for
>> software installs?  It is complicated and will certainly always be
>> more dificult than just using native software.
>
> I see you are not that convicted of my idea. :) No offense at all.

I just don't want you to spend a lot of time on something I don't think 
a lot of people will use due to the ability to crash and/or break into 
the host OS.

> May I ask why you are interested in this project?

When I started using it, Microsoft Virtual PC cost money.  It is now 
free and has nearly replaced my need to use coLinux.  And this need will 
be even further reduced with the hypervisor in Windows 2008 Server.

<<CDC 

Re: [coLinux-users] suggestion: linux runtime environment

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

Jitesh Shah wrote:
> Well... what you suggest is very close to what current virtualisation
> solutions provide, including colinux. You can run applications on linux as a
> guest, communicate with the host apps.
> how would linux runtime environment differ??

- Porting (colinux) is much faster then virtualizers (like vmware) and 
this is the biggest advantage.
- colinux is Free Software, the mature one virtualizers (vmware, 
virtualbox) are not really Free Software, just some parts are
- I did check out AndLinux. It`s really great, the integration with the 
host os is much better, the speed is great, the look and feel is great, 
copy and paste works, sounds works, easy installer, no slow virtual cards.

Henry Nestler wrote:
 > Perhaps you wish what Lina does? http://openlina.org/
 > Promo-Video: http://www.youtube.com/watch?v=KtIZglgt-Mo

The idea is great but this project won`t get accept by Free Software 
developers since lina uses software patents.

It`s also a little bit limited compared to colinux. Colinux could let 
run also proprietary linux native only software on windows.

  > coLinux is the base VM for running every Linux. We can not provide all
 > in one box installation from Windows side. After you have a running
 > Linux in coLinux, you can use the Linux packet manager and downloading
 > and installing more packets (apt-get, yum, yast, ...).
 >
 > Some "box" installations with coLinux as background exist.

Ok, I begin to understand this a little big better. Colinux is like 
linux, it`s the base. But colinux is not ubuntu a preconfigured distro 
wich runs out of the box, this must be picked up by interested third 
party developers like AndLinux who want to use colinux as base.

Re: [coLinux-users] suggestion: linux runtime environment

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

Henry Nestler wrote:
> A Debian based "full" installation with small handwork is
> http://docs.blackfin.uclinux.org/doku.php?id=colinux

Sorry, this one comes also with a full featured "installer" and creates
all coLinux files automaticly.

-- 
Henry N.

Re: [coLinux-users] suggestion: linux runtime environment

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

Michael Reichenbach wrote:
> This project is really awesome. I think it`s a great chance for all
> linux based distributions to become even more successfully.
> 
> Sure you know java runtime environment, net framework or direct x. Often
> it`s shipped on a cd with your software or you download it. Just click a
> few times to "ok, install, yes" and your`re done or there is also a
> -silent option.
> 
> What about turning CoLinux into 'linux runtime environment'? Currently
> it`s hard to set up and no jump in solution. Why not create a version
> which runs out of the box?
> 
> This would allow any kind of software developer, hobbyist or commercial
> developer to develop software under linux and for linux exclusively
> without porting. On windows there would be just need to install 'linux
> runtime environment'.
> 
> CoLinux just needs better a bit better integration into windows. Like
> linking deb/rpm.

Perhaps you wish what Lina does? http://openlina.org/
Promo-Video: http://www.youtube.com/watch?v=KtIZglgt-Mo

I'm not concerned in Lina. I don't know about the background. I can only
answer the coLinux questions...

coLinux can not translate the windows EXE format to run under Linux or
via versa. coLinux is a VM (virtual machine). Inside the running Linux
guest OS don't know about existing Windows.

coLinux is the base VM for running every Linux. We can not provide all
in one box installation from Windows side. After you have a running
Linux in coLinux, you can use the Linux packet manager and downloading
and installing more packets (apt-get, yum, yast, ...).

Some "box" installations with coLinux as background exist.

The first was http://www.andlinux.org/
After installation you have a X11 under Windows and full integration in
may Windows style start menus. Check the screen shots ;-)
There you have one big file with contains all: coLinux, basic linux
image, network setup, Xserver, Sound, ...

http://topologilinux.com/ is a Slackware out of the box coLinux
installation (Kde, Gnome, network, sound, OpenOffice, ...)

A Debian based "full" installation with small handwork is
http://docs.blackfin.uclinux.org/doku.php?id=colinux

There exist some more specialny installtions.

-- 
Henry N.

Re: [coLinux-users] swap partition not working (device or resource busy)

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

Andrew Roth wrote:
> Hi all,
> 
> I used to be able to mount my swap partition in colinux, but it seems to
> be failing silently now.
> 
> [...]
> --(23:47)-- $ sudo mkswap /dev/hda5
> /dev/hda5: Device or resource busy
> --(/home/andrewr)-----------------------------------(andrewr@andrewr-laptop:1)--
> --(23:47)-- $
> 
> My config is pretty simple:
> [...]
> # File systems
> hda5=\Device\HarddiskVolume4 # swap
> hda6=\Device\HarddiskVolume5 # ubuntu

Doubble check, that you used the right Volume number 4.
>From http://www.chrysocome.net/dd run
  dd --list
and check that the name HarddiskVolume4 is linked to your Partition.

I'm preffer more the style in form
  hda5=\Device\Harddisk0\Partition4 # swap
  hda6=\Device\Harddisk0\Partition5 # ubuntu
There the names are coded by hardware, and not from windows internal
counts of "HarddiskVolume*".

Other idea is to use a swapfile in the mounted hda6 filesystem.

-- 
Henry N.

Re: [coLinux-users] suggestion: linux runtime environment

[Jitesh S. <jit...@gm...>]

On Jan 26, 2008 10:38 AM, Michael Reichenbach <
mic...@fr...> wrote:

> Christopher D. Clausen wrote:
>  > Running coLinux is certinaly not as safe and easy as running a piece of
> > Java code in a VM.
>
> Never thought that this could become the biggest problem. If so, why
> this project exists then? Just for fun and to show that it`s possible?
> Sure not, what?


Search for applications of virtualisation... or you can also refer to the
paper by Dan Aloni in the Linux Symposium 2004, in order to get an
understanding of where it can be used

>
>
> > Also be aware of security implications of doing such things.  Java is
> > somewhat sandboxed, coLinux is not.  CoLinux can crash your computer.
>
> Is this a big problem? No workarround?


Well .. colinux runs on ring 0 with the host OS. Personally, I doubt there
can be any workarounds (unless ring 1 or ring 3 virtualisation is used..
which defeats the purpose of colinux). Hardware support may help. something
like Intel-VT.

>
>
>  > Why would one just not use a Windows version of apt to install native
> > Windows software?
> >
>



>
> > For instance: http://www.acm.uiuc.edu/projects/Wipt/
> There is no big package archive like the one from debian. And realistic,
> I doub`t there will ever be one. So this program may be nice but it
> lacks contributers.



>
> > Again, why not just port these things to run on Windows?
>
> Porting is sometimes complicated. Ok, if you use platform portable libs
> then it`s much more easy. But often the program was native for one
> platform only, then users started asking for a port. If it`s using linux
> specific libs or posix api or specific things like /proc/cpuinfo which
> windows does not provide then porting is not so easy.
>
> Another reason is that there are tons of programs. Why "10.000" people
> start porting all those apps if just 1 project could allow to run all
> linux native programs also on windows because of this "trick"?


Well... what you suggest is very close to what current virtualisation
solutions provide, including colinux. You can run applications on linux as a
guest, communicate with the host apps.
how would linux runtime environment differ??

>
>
> > And windows has a packaging technology that uses MSI files.  Just
> > download an MSI and install.  Why mess with a non-native system for
> > software installs?  It is complicated and will certainly always be more
> > dificult than just using native software.
>
> I see you are not that convicted of my idea. :) No offense at all.
>
> May I ask why you are interested in this project?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] suggestion: linux runtime environment

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

Christopher D. Clausen wrote:
  > Running coLinux is certinaly not as safe and easy as running a piece of
> Java code in a VM.

Never thought that this could become the biggest problem. If so, why 
this project exists then? Just for fun and to show that it`s possible? 
Sure not, what?

> Also be aware of security implications of doing such things.  Java is 
> somewhat sandboxed, coLinux is not.  CoLinux can crash your computer.

Is this a big problem? No workarround?

  > Why would one just not use a Windows version of apt to install native
> Windows software?
> 
> For instance: http://www.acm.uiuc.edu/projects/Wipt/
There is no big package archive like the one from debian. And realistic, 
I doub`t there will ever be one. So this program may be nice but it 
lacks contributers.

> Again, why not just port these things to run on Windows?

Porting is sometimes complicated. Ok, if you use platform portable libs 
then it`s much more easy. But often the program was native for one 
platform only, then users started asking for a port. If it`s using linux 
specific libs or posix api or specific things like /proc/cpuinfo which 
windows does not provide then porting is not so easy.

Another reason is that there are tons of programs. Why "10.000" people 
start porting all those apps if just 1 project could allow to run all 
linux native programs also on windows because of this "trick"?

> And windows has a packaging technology that uses MSI files.  Just 
> download an MSI and install.  Why mess with a non-native system for 
> software installs?  It is complicated and will certainly always be more 
> dificult than just using native software.

I see you are not that convicted of my idea. :) No offense at all.

May I ask why you are interested in this project?

[coLinux-users] swap partition not working (device or resource busy)

[Andrew R. <and...@gm...>]

SGkgYWxsLAoKSSB1c2VkIHRvIGJlIGFibGUgdG8gbW91bnQgbXkgc3dhcCBwYXJ0aXRpb24gaW4g
Y29saW51eCwgYnV0IGl0IHNlZW1zIHRvIGJlCmZhaWxpbmcgc2lsZW50bHkgbm93LgoKSXQgc2Vl
bXMgdG8gYmUgZ2V0dGluZyB0aGUgcmlnaHQgdW5kZXJseWluZyBkcml2ZToKCi0tKDIzOjQ2KS0t
ICQgc3VkbyBoZWFkIC9kZXYvaGRhNQrilqDilqAs4pag4pag4pagV+KWoELilqDilqBe4pagdeKW
oDJTV0FQU1BBQ0UyIyEgL2Jpbi9zaAojIFhzZXR1cCAtIHJ1biBhcyByb290IGJlZm9yZSB0aGUg
bG9naW4gZGlhbG9nIGFwcGVhcnMKCiN4Y29uc29sZSAtZ2VvbWV0cnkgNDgweDEzMC0wLTAgLW5v
dGlmeSAtdmVyYm9zZSAtZm4gZml4ZWQgLWV4aXRPbkZhaWwgLWZpbGUKL2RlCnYveGNvbnNvbGUg
JgpOOmNvYmQxMApNOjExNzoxMApFOkRFVlRZUEU9ZGlzawojISAvYmluL3NoCiMgWHN0YXJ0dXAg
LSBydW4gYXMgcm9vdCBiZWZvcmUgc2Vzc2lvbiBzdGFydHMKCgpCdXQgZXZlcnkgdGltZSBJIHRy
eSB0byB1c2UgaXQsIEkgZ2V0ICdEZXZpY2Ugb3IgcmVzb3VyY2UgYnVzeSc6CgotLSgvaG9tZS9h
bmRyZXdyKS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKGFuZHJld3JAYW5kcmV3
ci1sYXB0b3AKOjEpLS0KLS0oMjM6NDYpLS0gJCBzdWRvIHN3YXBvbiAvZGV2L2hkYTUKc3dhcG9u
OiAvZGV2L2hkYTU6IERldmljZSBvciByZXNvdXJjZSBidXN5Ci0tKC9ob21lL2FuZHJld3IpLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0oYW5kcmV3ckBhbmRyZXdyLWxhcHRvcAo6
MSktLQotLSgyMzo0NyktLSAkIHN1ZG8gbWtzd2FwIC9kZXYvaGRhNQovZGV2L2hkYTU6IERldmlj
ZSBvciByZXNvdXJjZSBidXN5Ci0tKC9ob21lL2FuZHJld3IpLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0oYW5kcmV3ckBhbmRyZXdyLWxhcHRvcAo6MSktLQotLSgyMzo0NyktLSAk
CgpNeSBjb25maWcgaXMgcHJldHR5IHNpbXBsZToKIiIiIiIiCiMgVGhlIGRlZmF1bHQga2VybmVs
Cmtlcm5lbD12bWxpbnV4CgojIEZpbGUgc3lzdGVtcwpoZGE1PVxEZXZpY2VcSGFyZGRpc2tWb2x1
bWU0ICMgc3dhcApoZGE2PVxEZXZpY2VcSGFyZGRpc2tWb2x1bWU1ICMgdWJ1bnR1CgojIFRlbGwg
a2VybmVsIHRoZSBuYW1lIG9mIHJvb3QgZGV2aWNlCnJvb3Q9L2Rldi9oZGE2CgojIEluaXRyZCBp
bnN0YWxscyBtb2R1bGVzIGludG8gdGhlIHJvb3QgZmlsZSBzeXN0ZW0uCiMgTmVlZCBvbmx5IG9u
IGZpcnN0IGJvb3QuCmluaXRyZD1pbml0cmQuZ3oKCiMgTWF4aW1hbCBtZW1vcnkgZm9yIGxpbnV4
IGd1ZXN0Cm1lbT0xMjggIyBidW1wZWQgaXMgc2luY2UgSSBnb3Qgbm8gc3dhcCA6KAoKIyBTbGly
cCBmb3IgaW50ZXJuZXQgY29ubmVjdGlvbiAob3V0Z29pbmcpIG9uIHNlY29uZCBsaW51eCBhZGFw
dGVyLgojIEluc2lkZSBydW5uaW5nIGNvTGludXggY29uZmlndXJlIGV0aDAgd2l0aCB0aGlzIHN0
YXRpYyBzZXR0aW5nczoKZXRoMD1zbGlycAoKIyBOZXR3b3JraW5nICh0dW50YXAgYXMgcHJpdmF0
ZSBuZXR3b3JrIGJldHdlZW4gZ3VzdCBhbmQgaG9zdCkKZXRoMT10dW50YXAsImNvbGludXgiCiIi
IiIiCgpBbnlvbmUgaGF2ZSBhbnkgaWRlYXMgd2h5IG9yIHdoYXQgSSBjYW4gdHJ5PwoKT2ggeWVh
aCAtIEknbSB1c2luZyB0aGUgSmFuIDIwLCAyMDA4IGRldiB2ZXJzaW9uLgoKTWFueSB0aGFua3Mg
LSBJIHVzZSBjb2xpbnV4IHByZXR0eSBtdWNoIGV2ZXJ5IGRheSB0byBnZXQgYSBuaWNlIGxpbnV4
IHByb21wdAphbmQgc2hlbGwgdG9vbHMuCgotQW5kcmV3Cg==

Re: [coLinux-users] suggestion: linux runtime environment

[Christopher D. C. <ccl...@ac...>]

Michael Reichenbach <mic...@fr...> wrote:
> Oscar Usifer wrote:
>> Not sure there is a good bridge for this, or what exactly the
>> function of it would be. You might be able to share file systems,
>> but running Linux apps on Windows seamlessly is sort of a VM thing.
>
> A virtual machine isn`t best choice. It`s good to have a virtual
> computer where you can do testings and so on or if you want to sell
> virtual servers or you have a old mailserver or whatever and want all
> apps in it`s own virtual computer.
>
> But virtual machines are not that good for guis and so on. Them are a
> bit to slow and integration with other devices such as printers is not
> so good yet. Them are also slow. I guess if the developers of this
> project would have been happy with vmware/virtualbox them wouldn`t
> have started this project which goes another way then virtualisation
> (them chose porting).

Running coLinux is certinaly not as safe and easy as running a piece of 
Java code in a VM.

Also be aware of security implications of doing such things.  Java is 
somewhat sandboxed, coLinux is not.  CoLinux can crash your computer.

>> Can you explain better what kind of integration your shooting for?
>
> I think colinux is great software and vision is to have it in a useful
> and more easy state also for normal users. Currently it`s hard to set
> up and the integration is not so good.
>
> Features I am thinking of you are downloading 'linux runtime
> environment', install it... Then go to some website and download some
> .deb or .rpm package, save it on desktop, double click it and it will
> be installed, then you can start it directly from windows. Or open a
> terminal and type apt-get install whatever.

Why would one just not use a Windows version of apt to install native 
Windows software?

For instance: http://www.acm.uiuc.edu/projects/Wipt/

> Colinux provides this functions already "nearly".
>
> If I think right this would also simplify other developers live.
> Example, you program some office suite using C++ and Qt or GTK,
> compile it for linux and create a .deb package, you`re done. No more
> need to compile it under windows because windows gets the function to
> run also linux apps because the kernel (and some more goodies) got
> ported.

Again, why not just port these things to run on Windows?  Use 
http://www.bloodshed.net/dev/devcpp.html to compile software for Windows 
natively.  And there are Windows ports of many things available on 
Linux.

And windows has a packaging technology that uses MSI files.  Just 
download an MSI and install.  Why mess with a non-native system for 
software installs?  It is complicated and will certainly always be more 
dificult than just using native software.

<<CDC 

Re: [coLinux-users] suggestion: linux runtime environment

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

Oscar Usifer wrote:
> Not sure there is a good bridge for this, or what exactly the function of it would be. You might be able to share file systems, but running Linux apps on Windows seamlessly is sort of a VM thing.
A virtual machine isn`t best choice. It`s good to have a virtual 
computer where you can do testings and so on or if you want to sell 
virtual servers or you have a old mailserver or whatever and want all 
apps in it`s own virtual computer.

But virtual machines are not that good for guis and so on. Them are a 
bit to slow and integration with other devices such as printers is not 
so good yet. Them are also slow. I guess if the developers of this 
project would have been happy with vmware/virtualbox them wouldn`t have 
started this project which goes another way then virtualisation (them 
chose porting).

> Can you explain better what kind of integration your shooting for?
I think colinux is great software and vision is to have it in a useful 
and more easy state also for normal users. Currently it`s hard to set up 
and the integration is not so good.

Features I am thinking of you are downloading 'linux runtime 
environment', install it... Then go to some website and download some 
.deb or .rpm package, save it on desktop, double click it and it will be 
installed, then you can start it directly from windows. Or open a 
terminal and type apt-get install whatever.

Colinux provides this functions already "nearly".

If I think right this would also simplify other developers live. 
Example, you program some office suite using C++ and Qt or GTK, compile 
it for linux and create a .deb package, you`re done. No more need to 
compile it under windows because windows gets the function to run also 
linux apps because the kernel (and some more goodies) got ported.

Re: [coLinux-users] suggestion: linux runtime environment

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

Not sure there is a good bridge for this, or what exactly the function of i=
t would be. You might be able to share file systems, but running Linux apps=
 on Windows seamlessly is sort of a VM thing. Basically you'd need cygwin's=
 X11 on top for windowing environments. Since coLinux runs with in it's own=
 process space, not sure how the cross communication would be. Can you expl=
ain better what kind of integration your shooting for?? Of course, I only h=
ave a vague technical understanding of these things, so I'm not trying to t=
ype authoritatively on any of these issues.


> ----- Original Message -----
> From: "Michael Reichenbach" <mic...@fr...>
> To: col...@li...
> Subject: [coLinux-users] suggestion: linux runtime environment
> Date: Fri, 25 Jan 2008 23:28:48 +0100
>=20
>=20
> This project is really awesome. I think it`s a great chance for all
> linux based distributions to become even more successfully.
>=20
> Sure you know java runtime environment, net framework or direct x. Often
> it`s shipped on a cd with your software or you download it. Just click a
> few times to "ok, install, yes" and your`re done or there is also a
> -silent option.
>=20
> What about turning CoLinux into 'linux runtime environment'? Currently
> it`s hard to set up and no jump in solution. Why not create a version
> which runs out of the box?
>=20
> This would allow any kind of software developer, hobbyist or commercial
> developer to develop software under linux and for linux exclusively
> without porting. On windows there would be just need to install 'linux
> runtime environment'.
>=20
> CoLinux just needs better a bit better integration into windows. Like
> linking deb/rpm.
>=20
> It`s a suggestion. What is your opinion on this?
>=20
>=20
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

>


--=20
Want an e-mail address like mine?
Get a free e-mail account today at www.mail.com!

[coLinux-users] suggestion: linux runtime environment

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

This project is really awesome. I think it`s a great chance for all
linux based distributions to become even more successfully.

Sure you know java runtime environment, net framework or direct x. Often
it`s shipped on a cd with your software or you download it. Just click a
few times to "ok, install, yes" and your`re done or there is also a
-silent option.

What about turning CoLinux into 'linux runtime environment'? Currently
it`s hard to set up and no jump in solution. Why not create a version
which runs out of the box?

This would allow any kind of software developer, hobbyist or commercial
developer to develop software under linux and for linux exclusively
without porting. On windows there would be just need to install 'linux
runtime environment'.

CoLinux just needs better a bit better integration into windows. Like
linking deb/rpm.

It`s a suggestion. What is your opinion on this?

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[<2...@pe...>]

On Wed, 23 Jan 2008, Frédéric L. W. Meunier wrote:

> On Wed, 23 Jan 2008, Henry Nestler wrote:
>
>> Frédéric L. W. Meunier wrote:
>>> I don't know what caused it, but now everything works. I changed it to
>>> 
>>> eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080
>>> 
>>> and it works if I use in 80 or 8080.
>> 
>> This confiused me! ;-(
>> If you not have a server on port 8080 on coLinux (Linux) side, you
>> should no have a positive response from port 8080 on Windows side. Or,
>> you found a bug. Plesase send me your used colinux config file or batch
>> script and say, what distri you use.

I forgot to answer this. I tested the server in both ports, so 
no problem.

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[<2...@pe...>]

On Thu, 24 Jan 2008, Henry Nestler wrote:

> Frédéric L. W. Meunier wrote:
>> On Thu, 24 Jan 2008, Henry Nestler wrote:
>> 
>>> Frédéric L. W. Meunier wrote:
>>>> I'll set manually. In /var/log/messages there are lines "offered
>>>> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from
>>>> 10.0.2.2" "leased 10.0.2.16".
>>>
>>> That's very badly. What distry and what version of dhcp-client?
>> 
>> It's Slackware but with dhcpcd 3.1.19.
>
> Is that a special hacked version?
> Where can I get the source of your version?
>
> I only found up 3.1.9 on
> http://roy.marples.name/dhcpcd
>
> My working is 1.3.22 (SuSE 10.3)
> http://www.phystech.com/download/dhcpcd.html

No, sorry. It's 3.1.9. Slackware has 2.0.4. I'll see if I get 
another IP also with that version.

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

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

Frédéric L. W. Meunier wrote:
> On Thu, 24 Jan 2008, Henry Nestler wrote:
> 
>> Frédéric L. W. Meunier wrote:
>>> I'll set manually. In /var/log/messages there are lines "offered
>>> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from
>>> 10.0.2.2" "leased 10.0.2.16".
>>
>> That's very badly. What distry and what version of dhcp-client?
> 
> It's Slackware but with dhcpcd 3.1.19.

Is that a special hacked version?
Where can I get the source of your version?

I only found up 3.1.9 on
http://roy.marples.name/dhcpcd

My working is 1.3.22 (SuSE 10.3)
http://www.phystech.com/download/dhcpcd.html

-- 
Henry N.

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[<2...@pe...>]

On Thu, 24 Jan 2008, Henry Nestler wrote:

> Frédéric L. W. Meunier wrote:
>> I'll set manually. In /var/log/messages there are lines "offered
>> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from
>> 10.0.2.2" "leased 10.0.2.16".
>
> That's very badly. What distry and what version of dhcp-client?

It's Slackware but with dhcpcd 3.1.19.

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

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

Frédéric L. W. Meunier wrote:
> I'll set manually. In /var/log/messages there are lines "offered
> 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and "offered 10.0.2.18 from
> 10.0.2.2" "leased 10.0.2.16".

That's very badly. What distry and what version of dhcp-client?

-- 
Henry N.

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[<2...@pe...>]

On Wed, 23 Jan 2008, Henry Nestler wrote:

> Frédéric L. W. Meunier wrote:
>> I don't know what caused it, but now everything works. I 
>> changed it to
>> 
>> eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080
>> 
>> and it works if I use in 80 or 8080.
>
> This confiused me! ;-(
> If you not have a server on port 8080 on coLinux (Linux) side, you
> should no have a positive response from port 8080 on Windows side. Or,
> you found a bug. Plesase send me your used colinux config file or batch
> script and say, what distri you use.
>
>> But if I recall correctly, when it didn't work, dhcpcd had set 
>> my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything 
>> it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer 
>> 10.0.2.15.
>
> IP 10.0.2.16 is not ok for DHCP. Have you more about the DHCP protocoll
> from /var/log/message with typicaly OFFER/ACK/NAK messages? Sems me, we
> have the bug with badly DHCP offers not fixed.
> Only 10.0.2.15 is the right address. The DHCP-Server inside slirp should
> give only this one address all times.
> You can set the working config as static to have no problems in future.

I'll set manually. In /var/log/messages there are lines 
"offered 10.0.2.17 from 10.0.2.2" "leased 10.0.2.16" and 
"offered 10.0.2.18 from 10.0.2.2" "leased 10.0.2.16".

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

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

Frédéric L. W. Meunier wrote:
> I don't know what caused it, but now everything works. I 
> changed it to
> 
> eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080
> 
> and it works if I use in 80 or 8080.

This confiused me! ;-(
If you not have a server on port 8080 on coLinux (Linux) side, you
should no have a positive response from port 8080 on Windows side. Or,
you found a bug. Plesase send me your used colinux config file or batch
script and say, what distri you use.

> But if I recall correctly, when it didn't work, dhcpcd had set 
> my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything 
> it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer 
> 10.0.2.15.

IP 10.0.2.16 is not ok for DHCP. Have you more about the DHCP protocoll
from /var/log/message with typicaly OFFER/ACK/NAK messages? Sems me, we
have the bug with badly DHCP offers not fixed.
Only 10.0.2.15 is the right address. The DHCP-Server inside slirp should
give only this one address all times.
You can set the working config as static to have no problems in future.

-- 
Henry N.

Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[<2...@pe...>]

On Wed, 23 Jan 2008, Henry Nestler wrote:

>>> Try other port for remapping, for example
>>>   tcp:2222:22/tcp:4000:80
>>> Than on the windows side the port 4000 is your webserver and port 80
>>> inside coLinux. Type the URL http://localhost:4000/ in your Windows browser.
>> 
>> Remapping, both work.Now I really don't have any idea why using the
>> same ports doesn't.
>
> Only one program can agent as server on one tcp port.
> If you have a running program that is listen on port 80 (windows web
> Server ?), than an other program can not open the same port for listen.
> Or ir can open, but windows is faster and catch all the incommings. I
> don't know.
>
> Has your windows some more protections to not open ports lower than 1024
> from a user program as server? Some firewalls or secure tools forbidden
> and and blocks it (Zone Alarm, Norton, ...).
>
> For example on Linux an user land program can only listen on ports
>> 1023. On ports 22 and 80 only a user "root" can listen.

I don't know what caused it, but now everything works. I 
changed it to

eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080

and it works if I use in 80 or 8080.

But if I recall correctly, when it didn't work, dhcpcd had set 
my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything 
it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer 
10.0.2.15.

When it didn't work, I could connect from coLinux to localhost 
and 10.0.2.16.

Anyway, thanks for your help.