colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] RedHat on coLinux ?

[John L. <jo...@su...>]

Whoops, just realized you're talking about a redhat distro.  Well, it 
still might be the same bug.  But maybe not.

John

John LeSueur wrote:

> This is actually a bug in apt-utils.  If you limit your sources.list 
> to one source, then you should be able to upgrade apt-utils(from 
> testing).  Then you can have as many sources as needed.
>
> John
>

Re: [coLinux-devel] RedHat on coLinux ?

[John L. <jo...@su...>]

This is actually a bug in apt-utils.  If you limit your sources.list to 
one source, then you should be able to upgrade apt-utils(from testing).  
Then you can have as many sources as needed.

John

Rob McDonald wrote:

>Thanks for making that image available.
>
>It seems to work good for starters, but when I try to do an apt-get update,
>it downloads the release and pkglist files, and then crashes with an alloc
>failure while it is trying to read the package lists.
>
>I tried adding
>
>APT::Cache-Limit "8388608";
>
>to the /etc/apt/apt.conf
>
>And I tried removing some of the servers from (to make the package list
>smaller)
>
>/etc/apt/sources.list
>
>Did you have this problem?  Any ideas for a solution?
>
>I am running the latest binary release of coLinux.
>
>Thanks again,
>
>           Rob
>
>
>  
>

Re: [coLinux-devel] RedHat on coLinux ?

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Rob,

do use swap space? Memory is very limited in the standard configuration.
There was also discussion about a apt-get bug on this list.

Thomas

> Thanks for making that image available.
>
> It seems to work good for starters, but when I try to do an apt-get
> update,
> it downloads the release and pkglist files, and then crashes with an alloc
> failure while it is trying to read the package lists.
>
> I tried adding
>
> APT::Cache-Limit "8388608";
>
> to the /etc/apt/apt.conf
>
> And I tried removing some of the servers from (to make the package list
> smaller)
>
> /etc/apt/sources.list
>
> Did you have this problem?  Any ideas for a solution?
>
> I am running the latest binary release of coLinux.
>
> Thanks again,
>
>            Rob
>
>
>> I am using coLinux with RedHat 9.0. If you want to try (49 MB):
>>
>> http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2
>>
>> It contains only based packages. Man is installed but no man pages for
> APIs
>> at all. Anyway, you can use apt-get to install anythings you want
>> easily.
>> The pre-configured sources are pointing to freshrpms and dag
>> repositories.
>> So the first step is to modify /etc/resolv.conf and run apt-get update
>> to
>> get the packages list.
>>
>> Actually, you can build your own root image by rpm command (like me).
>> For
>> example:
>>
>> dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576
>> mkfs.ext3 redhat-9.0.ext3.1gb
>> mkdir root
>> mount -o loop redhat-9.0.ext3.1gb root
>> rpm --initdb --root=$PWD/root
>>
>> At this point, you can install whatever you want. All rpm commands must
>> be
>> added --root option. That's all and then bzip2 it.
>>
>> umount root
>> bzip2 -k -9 redhat-9.0.ext3.1gb
>>
>> Good luck,
>>
>>
>> > Installing a "normal" distribution on coLinux - "The Slackware on
> coLinux
>> > HOWTO"I am very impressed with the power of coLinux.  Great work for a
>> > 1-month old (public) project.
>> >
>> > Has anyone attempted or succeeded in getting a recent RedHat install
> done
>> > through coLinux?  I've read the threads started by Nir Perry about his
>> > experiences with Slackware, but I am not experienced enough with Linux
>> > administration to try to duplicate them, much less apply them to
>> RedHat.
>> >
>> > I've had a lot of luck with the Debian starter image, but some of my
>> > programs behave very strangely (crash).  The behavior looks like it
> could
>> be
>> > due to incompatibilities between compiler and library versions, or
>> they
>> > might be due to coLinux.  I really can't tell, and would like to take
> the
>> > distribution differences out of the loop to isolate the problem.
>> >
>> > I realize that the coLinux developers have lots to do, but
>> fortunately,
>> the
>> > images aren't impacted by coLinux development.  Is there another
>> source
> of
>> > images out there? (vmware users)  Is there enough interest to start a
>> projct
>> > compiling a library of images?  Or is it just easier to focus effort
>> on
>> > getting coLinux to boot generic install CD's, and go from there?
>> >
>> > Any help would be appretiated.
>> >
>> >          Rob
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>> > Build and deploy apps & Web services for Linux with
>> > a free DVD software kit from IBM. Click Now!
>> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>> > _______________________________________________
>> > coLinux-devel mailing list
>> > coL...@li...
>> > https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>
>>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFANOArnwJBIFTVIqwRAvAhAJ9fe46AC8++Veq+4322EftPZROj8gCffsF3
hRX8ux9aH0ktscdvMQHyxnM=
=HBAy
-----END PGP SIGNATURE-----

Re: [coLinux-devel] RedHat on coLinux ?

[Rob M. <ro...@as...>]

Thanks for making that image available.

It seems to work good for starters, but when I try to do an apt-get update,
it downloads the release and pkglist files, and then crashes with an alloc
failure while it is trying to read the package lists.

I tried adding

APT::Cache-Limit "8388608";

to the /etc/apt/apt.conf

And I tried removing some of the servers from (to make the package list
smaller)

/etc/apt/sources.list

Did you have this problem?  Any ideas for a solution?

I am running the latest binary release of coLinux.

Thanks again,

           Rob


> I am using coLinux with RedHat 9.0. If you want to try (49 MB):
>
> http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2
>
> It contains only based packages. Man is installed but no man pages for
APIs
> at all. Anyway, you can use apt-get to install anythings you want easily.
> The pre-configured sources are pointing to freshrpms and dag repositories.
> So the first step is to modify /etc/resolv.conf and run apt-get update to
> get the packages list.
>
> Actually, you can build your own root image by rpm command (like me). For
> example:
>
> dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576
> mkfs.ext3 redhat-9.0.ext3.1gb
> mkdir root
> mount -o loop redhat-9.0.ext3.1gb root
> rpm --initdb --root=$PWD/root
>
> At this point, you can install whatever you want. All rpm commands must be
> added --root option. That's all and then bzip2 it.
>
> umount root
> bzip2 -k -9 redhat-9.0.ext3.1gb
>
> Good luck,
>
>
> > Installing a "normal" distribution on coLinux - "The Slackware on
coLinux
> > HOWTO"I am very impressed with the power of coLinux.  Great work for a
> > 1-month old (public) project.
> >
> > Has anyone attempted or succeeded in getting a recent RedHat install
done
> > through coLinux?  I've read the threads started by Nir Perry about his
> > experiences with Slackware, but I am not experienced enough with Linux
> > administration to try to duplicate them, much less apply them to RedHat.
> >
> > I've had a lot of luck with the Debian starter image, but some of my
> > programs behave very strangely (crash).  The behavior looks like it
could
> be
> > due to incompatibilities between compiler and library versions, or they
> > might be due to coLinux.  I really can't tell, and would like to take
the
> > distribution differences out of the loop to isolate the problem.
> >
> > I realize that the coLinux developers have lots to do, but fortunately,
> the
> > images aren't impacted by coLinux development.  Is there another source
of
> > images out there? (vmware users)  Is there enough interest to start a
> projct
> > compiling a library of images?  Or is it just easier to focus effort on
> > getting coLinux to boot generic install CD's, and go from there?
> >
> > Any help would be appretiated.
> >
> >          Rob
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > coLinux-devel mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
>

RE: [coLinux-devel] my comments on colinux

[Robert S. <rj...@ze...>]

I asked about security before and got no response (other than a suggestion
to use bochs)

As far as I have been able to work out the arhictecture of colinux is like
this (please someone correct me if this is wrong):-

The colinux kernel runs in ring 0 (highest permission) on the CPU with
full control over the virtual memory system

To load the kernel colinux-daemon.exe (which is a user process) loads a
windows kernel driver (linux.sys).

This driver runs in ring0 (as it is part of the windows kernel) and
reserves physical memory for the colinux kernel to use.
The linux kernel has been patched so that it only maps its virtual memory
onto the physical memory that has been reserved from windows.

The linux and windows kernels cooperatively multitask.
Messages are passed between the linux kernel and linux.sys to implement
the console, cobd and conet

For the colinux block device, linux.sys reads the file from kernel space
For conet, IPC is used to communicate with a user-space thread that
makes calls to the TAP driver. (This is one reason why networking will be
slow)


Security implications
=====================
Any exploits that can be used in linux to gain root will still work

Root from linux does not have access to the physical RAM that windows is
using unless
 * extra code is loaded into the kernel (e.g. kernel recompile or module
loaded) which manipulates the page tables and maps the rest of the
physical memory
 * requests are made to linux.sys which causes it to access memory

Root in linux cannot make system calls to windows unless it can get
linux.sys to make them.

The file that backs the block device is read by the windows kernel
(probably as the SYSTEM user). This should not be a risk as you need to be
an Administrator to run colinux anyway.

In summary I agree that colinux is potentially dangerous. A priviledged
user on either OS, could insert code into the kernel, which allowed the
page tables to be manipulated, which futher allowed the other OS to be
compromised by reading and/or writing its kernel memory.
I don't think this situation will ever change ...

---
Rob Stonehouse

On Thu, 19 Feb 2004, Nir Perry wrote:

> Hi,
>
> Not sure about the security - colinux uses the daemon to access windows
> indirectly...
> You should be aware that in general projects under development lack the
> security "stable" projects have.
>
> I wouldn't recommend you to use colinux if you require HIGH level of
> security. Note - the host windows OS isn't that secure anyone.
>
> Btw, if you want that security fix on 2.4.24 kernel, you can get kernel
> sources from slackware - they've patched the 2.4.24 with it. I think other
> distros did that too.
>
> Nir
>
> -----Original Message-----
> From: peter green [mailto:plu...@p1...]
> Sent: Thursday, February 19, 2004 16:02
> To: col...@li...
> Subject: RE: [coLinux-devel] my comments on colinux
>
>
> when i used 2.4.24 it built fine
>
> what are the security implications of colinux?
> can it be trusted to jail users within a colinux system from each other or
> are there ways for an app inside to make direct windows system calls and
> break out
>
> i know that 2.4.24 has a known local root hole and would like to know if is
> worth trying to find a backport of the security fix or if colinux has no
> security in the first place

RE: [coLinux-devel] my comments on colinux

[Nir P. <ni...@em...>]

Hi,
 
Not sure about the security - colinux uses the daemon to access windows
indirectly...
You should be aware that in general projects under development lack the
security "stable" projects have.
 
I wouldn't recommend you to use colinux if you require HIGH level of
security. Note - the host windows OS isn't that secure anyone.
 
Btw, if you want that security fix on 2.4.24 kernel, you can get kernel
sources from slackware - they've patched the 2.4.24 with it. I think other
distros did that too.
 
Nir

-----Original Message-----
From: peter green [mailto:plu...@p1...] 
Sent: Thursday, February 19, 2004 16:02
To: col...@li...
Subject: RE: [coLinux-devel] my comments on colinux


when i used 2.4.24 it built fine 
 
what are the security implications of colinux?
can it be trusted to jail users within a colinux system from each other or
are there ways for an app inside to make direct windows system calls and
break out
 
i know that 2.4.24 has a known local root hole and would like to know if is
worth trying to find a backport of the security fix or if colinux has no
security in the first place
 
 

RE: [coLinux-devel] my comments on colinux

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

RE: [coLinux-devel] my comments on colinuxwhen i used 2.4.24 it built fine

what are the security implications of colinux?
can it be trusted to jail users within a colinux system from each other or
are there ways for an app inside to make direct windows system calls and
break out

i know that 2.4.24 has a known local root hole and would like to know if is
worth trying to find a backport of the security fix or if colinux has no
security in the first place



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

RE: [coLinux-devel] my comments on colinux

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

well i did a dist-upgrade to sarge to get gcc 3.x

i now get a different error in the same line

colinux:~/colinux-20040214/linux# make vmlinux
gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
c -o init/main.o init/main.c
In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
                 from
/root/colinux-20040214/linux/include/linux/blkdev.h:11,
                 from /root/colinux-20040214/linux/include/linux/blk.h:4,
                 from init/main.c:25:
/root/colinux-20040214/linux/include/linux/cooperative.h:233:21: missing ')'
in macro parameter list
make: *** [init/main.o] Error 1
colinux:~/colinux-20040214/linux#

here is the line in question
#define co_debug(...args)         do {} while(0)


-----Original Message-----
From: Robert Stonehouse [mailto:rj...@ze...]
Sent: 19 February 2004 12:10
To: peter green
Cc: col...@li...
Subject: RE: [coLinux-devel] my comments on colinux


On Thu, 19 Feb 2004, peter green wrote:

> colinux:~/colinux-20040214/linux# make vmlinux
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> scripts/split-include scripts/split-include.c
> scripts/split-include include/linux/autoconf.h include/config
>
gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
>
types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
>
er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
> c -o init/main.o init/main.c
> In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
>                  from
> /root/colinux-20040214/linux/include/linux/blkdev.h:11,
>                  from /root/colinux-20040214/linux/include/linux/blk.h:4,
>                  from init/main.c:25:
> /root/colinux-20040214/linux/include/linux/cooperative.h:233: badly
> punctuated parameter list in `#define'
> make: *** [init/main.o] Error 1
> colinux:~/colinux-20040214/linux#
>
> any ideas what causes this?

Try using GCC version 3.x rather than 2.x
You can override the default compiler from your path with something like
make vmlinux CC=/some/path/bin/gcc_3_3_2

--
Rob Stonehouse
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

Re: [coLinux-devel] my comments on colinux

[s0be <s0...@ma...>]

On Thu, 19 Feb 2004 12:08:13 -0000
"peter green" <plu...@p1...> wrote:

> trying this i got errors about nothing to do for dep
> 
> so i wen't back into make menuconfig
> after comeing out of that i did make clean make dep make vmlinux
> 
> do you think useing kernel 2.4.25 is a likely source of theese problems?

well, depends.  since the patch for 2.4.24 won't apply cleanly to 2.4.25, quite possibly.

OTOH, you could have fixed that on your own.  I dunno. 

Pat Erley

RE: [coLinux-devel] my comments on colinux

[Robert S. <rj...@ze...>]

On Thu, 19 Feb 2004, peter green wrote:

> colinux:~/colinux-20040214/linux# make vmlinux
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> scripts/split-include scripts/split-include.c
> scripts/split-include include/linux/autoconf.h include/config
> gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
> types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
> er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
> c -o init/main.o init/main.c
> In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
>                  from
> /root/colinux-20040214/linux/include/linux/blkdev.h:11,
>                  from /root/colinux-20040214/linux/include/linux/blk.h:4,
>                  from init/main.c:25:
> /root/colinux-20040214/linux/include/linux/cooperative.h:233: badly
> punctuated parameter list in `#define'
> make: *** [init/main.o] Error 1
> colinux:~/colinux-20040214/linux#
>
> any ideas what causes this?

Try using GCC version 3.x rather than 2.x
You can override the default compiler from your path with something like
make vmlinux CC=/some/path/bin/gcc_3_3_2

--
Rob Stonehouse

RE: [coLinux-devel] my comments on colinux

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

trying this i got errors about nothing to do for dep

so i wen't back into make menuconfig
after comeing out of that i did make clean make dep make vmlinux

do you think useing kernel 2.4.25 is a likely source of theese problems?


-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Pat Erley
Sent: 19 February 2004 11:49
To: col...@li...
Subject: Re: [coLinux-devel] my comments on colinux


On Thu, 19 Feb 2004 11:40:41 -0000
"peter green" <plu...@p1...> wrote:

> colinux:~/colinux-20040214/linux# make vmlinux
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> scripts/split-include scripts/split-include.c
> scripts/split-include include/linux/autoconf.h include/config
>
gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
>
types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
>
er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
> c -o init/main.o init/main.c
> In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
>                  from
> /root/colinux-20040214/linux/include/linux/blkdev.h:11,
>                  from /root/colinux-20040214/linux/include/linux/blk.h:4,
>                  from init/main.c:25:
> /root/colinux-20040214/linux/include/linux/cooperative.h:233: badly
> punctuated parameter list in `#define'
> make: *** [init/main.o] Error 1
> colinux:~/colinux-20040214/linux#
>
> any ideas what causes this?
>
looks like stale kernel objects.

try:

cd /path/to/linux-2.4.24
cp .config ..
make mrproper
cp ../.config .
make dep
make clean
make vmlinux

Pat


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

Re: [coLinux-devel] my comments on colinux

[Pat E. <pat...@ma...>]

On Thu, 19 Feb 2004 11:40:41 -0000
"peter green" <plu...@p1...> wrote:

> colinux:~/colinux-20040214/linux# make vmlinux
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> scripts/split-include scripts/split-include.c
> scripts/split-include include/linux/autoconf.h include/config
> gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
> types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
> er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
> c -o init/main.o init/main.c
> In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
>                  from
> /root/colinux-20040214/linux/include/linux/blkdev.h:11,
>                  from /root/colinux-20040214/linux/include/linux/blk.h:4,
>                  from init/main.c:25:
> /root/colinux-20040214/linux/include/linux/cooperative.h:233: badly
> punctuated parameter list in `#define'
> make: *** [init/main.o] Error 1
> colinux:~/colinux-20040214/linux#
> 
> any ideas what causes this?
> 
looks like stale kernel objects. 

try:

cd /path/to/linux-2.4.24
cp .config ..
make mrproper
cp ../.config .
make dep
make clean
make vmlinux

Pat

RE: [coLinux-devel] my comments on colinux

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

colinux:~/colinux-20040214/linux# make vmlinux
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
scripts/split-include scripts/split-include.c
scripts/split-include include/linux/autoconf.h include/config
gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
c -o init/main.o init/main.c
In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
                 from
/root/colinux-20040214/linux/include/linux/blkdev.h:11,
                 from /root/colinux-20040214/linux/include/linux/blk.h:4,
                 from init/main.c:25:
/root/colinux-20040214/linux/include/linux/cooperative.h:233: badly
punctuated parameter list in `#define'
make: *** [init/main.o] Error 1
colinux:~/colinux-20040214/linux#

any ideas what causes this?

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Richard
Goodwin
Sent: 19 February 2004 01:13
To: peter green; col...@li...
Subject: Re: [coLinux-devel] my comments on colinux


It's pretty easy to recompile a kernel with smbfs from inside coLinux :-)


----- Original Message -----
From: "peter green" <plu...@p1...>
To: <col...@li...>
Sent: Wednesday, February 18, 2004 6:51 PM
Subject: [coLinux-devel] my comments on colinux


> ok i tired out colinux and was pretty impressed with it
>
> i do think you should include smbfs in the standard build though as it is
> the easiest way to get at files on the host box
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
>


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

RE: [coLinux-devel] my comments on colinux

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

yeah sure i installed that
that only installs the userland part support needs to be either compiled
into the kernel or loaded as a kernel module

that latter seems impossible as the modules plain aren't there

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Tim
Hunter
Sent: 19 February 2004 01:15
To: col...@li...
Subject: Re: [coLinux-devel] my comments on colinux


----- Original Message ----- 
From: "peter green" <plu...@p1...>
To: <col...@li...>
Sent: Wednesday, February 18, 2004 7:51 PM
Subject: [coLinux-devel] my comments on colinux


> ok i tired out colinux and was pretty impressed with it
>
> i do think you should include smbfs in the standard build though as it is
> the easiest way to get at files on the host box

the images are seperate from the build of colinux, not included as the
product but instead as helpful for new users, besides in the debian image
its easy to just do apt-get install samba

> ---



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

Re: [coLinux-devel] RedHat on coLinux ?

[Sugree P. <su...@hp...>]

I am using coLinux with RedHat 9.0. If you want to try (49 MB):

http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2

It contains only based packages. Man is installed but no man pages for APIs
at all. Anyway, you can use apt-get to install anythings you want easily.
The pre-configured sources are pointing to freshrpms and dag repositories.
So the first step is to modify /etc/resolv.conf and run apt-get update to
get the packages list.

Actually, you can build your own root image by rpm command (like me). For
example:

dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576
mkfs.ext3 redhat-9.0.ext3.1gb
mkdir root
mount -o loop redhat-9.0.ext3.1gb root
rpm --initdb --root=$PWD/root

At this point, you can install whatever you want. All rpm commands must be
added --root option. That's all and then bzip2 it.

umount root
bzip2 -k -9 redhat-9.0.ext3.1gb

Good luck,


> Installing a "normal" distribution on coLinux - "The Slackware on coLinux
> HOWTO"I am very impressed with the power of coLinux.  Great work for a
> 1-month old (public) project.
>
> Has anyone attempted or succeeded in getting a recent RedHat install done
> through coLinux?  I've read the threads started by Nir Perry about his
> experiences with Slackware, but I am not experienced enough with Linux
> administration to try to duplicate them, much less apply them to RedHat.
>
> I've had a lot of luck with the Debian starter image, but some of my
> programs behave very strangely (crash).  The behavior looks like it could
be
> due to incompatibilities between compiler and library versions, or they
> might be due to coLinux.  I really can't tell, and would like to take the
> distribution differences out of the loop to isolate the problem.
>
> I realize that the coLinux developers have lots to do, but fortunately,
the
> images aren't impacted by coLinux development.  Is there another source of
> images out there? (vmware users)  Is there enough interest to start a
projct
> compiling a library of images?  Or is it just easier to focus effort on
> getting coLinux to boot generic install CD's, and go from there?
>
> Any help would be appretiated.
>
>          Rob
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel

Re: [coLinux-devel] my comments on colinux

[Richard G. <ric...@ri...>]

It's pretty easy to recompile a kernel with smbfs from inside coLinux :-)


----- Original Message ----- 
From: "peter green" <plu...@p1...>
To: <col...@li...>
Sent: Wednesday, February 18, 2004 6:51 PM
Subject: [coLinux-devel] my comments on colinux


> ok i tired out colinux and was pretty impressed with it
> 
> i do think you should include smbfs in the standard build though as it is
> the easiest way to get at files on the host box
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 
> 

Re: [coLinux-devel] my comments on colinux

[Tim H. <ti...@br...>]

----- Original Message ----- 
From: "peter green" <plu...@p1...>
To: <col...@li...>
Sent: Wednesday, February 18, 2004 7:51 PM
Subject: [coLinux-devel] my comments on colinux


> ok i tired out colinux and was pretty impressed with it
>
> i do think you should include smbfs in the standard build though as it is
> the easiest way to get at files on the host box

the images are seperate from the build of colinux, not included as the
product but instead as helpful for new users, besides in the debian image
its easy to just do apt-get install samba

> ---

[coLinux-devel] my comments on colinux

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

ok i tired out colinux and was pretty impressed with it

i do think you should include smbfs in the standard build though as it is
the easiest way to get at files on the host box
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004

Re: [coLinux-devel] RE: Problem running KDE

[<my...@gm...>]

I actually have been running KDE remotely for over a year with no
problems. At work, I have a 1GHz Windows 2K PC with Cygwin/X11 server
connecting to a 1 GHz Linux PC over the corporate LAN (100Mbps with a fair
amount of network traffic). It is actually faster to run KDE remotely on
Linux than running it localy on Cygwin! I turned off the KDE animation
effects and sound and it words great. Although KDE is more heavyweight
that the original X apps, most modern PCs and LANs have much more capacity
than what was available in the early days of X. I would expect that KDE on
cL should be able to just work fine over a loopback connection - its just
a matter of working out all of the issues.

Larry

> I think that one of the problems is that KDE and Gnome are not designed to
> be run over a network connection. They are just too heavy to do that now
> unless you have a seriously fast network pipe. Their targets are desktop
> machines after all. I think the symptoms could be that services are
> silently timing out as the code is not intended to be run in this way
> (though fot example the dialog for arts daemon timing out etc is a recent
> implementation in kde).
>
> Historically window managers were mostly run over network connections from
> X-Terminals and there are many others to choose from: fvwm2 and
> Enlightenment do the job. If the virtual network card ran at a higher
> throughput (I have not done any benchmarks so I dont know what it is)
> things may be better. Being realistic Cygwin/X is pretty slow anyway.
> Having thought about it I would not expect running X apps remotely from it
> to be faster as they could only be slower because of the network link. How
> about conecting a physical machine and getting a baseline? All in all I
> consider this capability provided by coLinux to be a proof of concept.
>
> Something that I am currently looking at is tweaking KDE and/or Gnome so
> that all of the eye candy is disabled etc to alleviate some load. Perhaps
> try disabling sound before the session is started as sound wont work
> anyway and this is one of the things that I find on a native Linux box
> impairs performance. There are also patches to the kernel that optimize
> the scheduler and so on. Perhaps these could be applied. No idea. 2.6? I
> think that I will end up waiting until a virtual graphics card is
> implemented in coLinux as in vmware (the diffs for their card are
> available for this from their site btw as it is open source).
>
> Anyone had any other ideas along this line?
> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÒó^¶+,¦‰ì¢·o/Ò¥çJÖ«µŠ.¬¸§»)¦ÃhÃðnŠWZ×^¦Z2jšlýg›±êï‰Ç¬~ŠËŠ{±Â+aiúÞx5C²‡íÁªÞ’+_®‰ˆÏ–'$6Œÿ†ÛiÿÿÚvÏè±Ùÿr‰¿ý§ÿ‰ßžÿjYhsøóú)rOÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýÊŠ{±ýׯzYšŠX§‚X¬µÊŠ{±ýׯz_åŠËlþÊ.­ÇŸ¢¸þw­†Ûi³ÿÿ–+-³û(º·~Šà{ùÞ·ùb²Û?–+-ŠwèýÊ%Š{±ýׯ
>

[coLinux-devel] RedHat on coLinux ?

[Rob M. <ro...@as...>]

Installing a "normal" distribution on coLinux - "The Slackware on coLinux
HOWTO"I am very impressed with the power of coLinux.  Great work for a
1-month old (public) project.

Has anyone attempted or succeeded in getting a recent RedHat install done
through coLinux?  I've read the threads started by Nir Perry about his
experiences with Slackware, but I am not experienced enough with Linux
administration to try to duplicate them, much less apply them to RedHat.

I've had a lot of luck with the Debian starter image, but some of my
programs behave very strangely (crash).  The behavior looks like it could be
due to incompatibilities between compiler and library versions, or they
might be due to coLinux.  I really can't tell, and would like to take the
distribution differences out of the loop to isolate the problem.

I realize that the coLinux developers have lots to do, but fortunately, the
images aren't impacted by coLinux development.  Is there another source of
images out there? (vmware users)  Is there enough interest to start a projct
compiling a library of images?  Or is it just easier to focus effort on
getting coLinux to boot generic install CD's, and go from there?

Any help would be appretiated.

         Rob

[coLinux-devel] How to get X running in coLinux

[Florent C. <fl...@ch...>]

Hi everybody,

First, thanks for such a program. I have began to switch from VMWare to 
coLinux ;o) Works great in console mode, no problem at all for the moment.

But, I haven't manage to get X running (and KDE, I have the same 
problems as others, long duration time when launching...)  nor via a VNC 
client calling a VNC server on coLinux, nor with XDMPC via KDM (nothing 
in the kdm.log and no error in Cygwin/X ??? how bizarre), and no with 
export display.

If someone have time to tell me a detailled how-to, I haven't find such 
one in the mailing-list.

My questions are thoose one :

1 - Which parameters must be set during the configuration phase of the 
package xserver-xfree86. VGA adapter on 640*480 with 16 bits color and a 
little screen or the real model of my graphic card (an ATI RADEON 
mobility in my case, in 1024*768 with 24 bits color). Framebuffer or not

2 - Which is the best method between VNC, export display or XDMPC to use 
KDE or Gnome (or others window manager)

3 - Which is the detaille procedure to achieve the best method

Thanks in advance for your answer. I have made my way alone to increase 
memory and add a swap but for X, all my attemps where unsuccesfull (or 
near unsuccesfull), I think a good answer would be useful while there is 
not a doc section on the website.

Regards,
Florent CHANTRET

[coLinux-devel] Script to build debian image with debootstrap

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

just to show how easy it is to create a image for colinux I wrote a short
script to do the job. I'm using debootstrip to do this. I tested this in a
colinux-debian-1gb-image-system, where I updated to "testing" (should also
work with woody) and added debootstrap.

The size of the image is currently set to 150MB, but you just have to
change CO_SIZE at the begin of the script if you have different
preferences.

Kind regards,
 Thomas




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAM1EVnwJBIFTVIqwRAhtFAJwKzDAAPFny1eTUdv4NTcaTybxQswCgtxtS
JX5xjTFQPFaVgHve+Yx3pas=
=DhSV
-----END PGP SIGNATURE-----

Re: [coLinux-devel] RE: Problem running KDE

[Sean B. <sea...@so...>]

SSB0aGluayB0aGF0IG9uZSBvZiB0aGUgcHJvYmxlbXMgaXMgdGhhdCBLREUgYW5kIEdub21lIGFy
ZSBub3QgZGVzaWduZWQgdG8gYmUgcnVuIG92ZXIgYSBuZXR3b3JrIGNvbm5lY3Rpb24uIFRoZXkg
YXJlIGp1c3QgdG9vIGhlYXZ5IHRvIGRvIHRoYXQgbm93IHVubGVzcyB5b3UgaGF2ZSBhIHNlcmlv
dXNseSBmYXN0IG5ldHdvcmsgcGlwZS4gVGhlaXIgdGFyZ2V0cyBhcmUgZGVza3RvcCBtYWNoaW5l
cyBhZnRlciBhbGwuIEkgdGhpbmsgdGhlIHN5bXB0b21zIGNvdWxkIGJlIHRoYXQgc2VydmljZXMg
YXJlIHNpbGVudGx5IHRpbWluZyBvdXQgYXMgdGhlIGNvZGUgaXMgbm90IGludGVuZGVkIHRvIGJl
IHJ1biBpbiB0aGlzIHdheSAodGhvdWdoIGZvdCBleGFtcGxlIHRoZSBkaWFsb2cgZm9yIGFydHMg
ZGFlbW9uIHRpbWluZyBvdXQgZXRjIGlzIGEgcmVjZW50IGltcGxlbWVudGF0aW9uIGluIGtkZSku
IA0KDQpIaXN0b3JpY2FsbHkgd2luZG93IG1hbmFnZXJzIHdlcmUgbW9zdGx5IHJ1biBvdmVyIG5l
dHdvcmsgY29ubmVjdGlvbnMgZnJvbSBYLVRlcm1pbmFscyBhbmQgdGhlcmUgYXJlIG1hbnkgb3Ro
ZXJzIHRvIGNob29zZSBmcm9tOiBmdndtMiBhbmQgRW5saWdodGVubWVudCBkbyB0aGUgam9iLiBJ
ZiB0aGUgdmlydHVhbCBuZXR3b3JrIGNhcmQgcmFuIGF0IGEgaGlnaGVyIHRocm91Z2hwdXQgKEkg
aGF2ZSBub3QgZG9uZSBhbnkgYmVuY2htYXJrcyBzbyBJIGRvbnQga25vdyB3aGF0IGl0IGlzKSB0
aGluZ3MgbWF5IGJlIGJldHRlci4gQmVpbmcgcmVhbGlzdGljIEN5Z3dpbi9YIGlzIHByZXR0eSBz
bG93IGFueXdheS4gSGF2aW5nIHRob3VnaHQgYWJvdXQgaXQgSSB3b3VsZCBub3QgZXhwZWN0IHJ1
bm5pbmcgWCBhcHBzIHJlbW90ZWx5IGZyb20gaXQgdG8gYmUgZmFzdGVyIGFzIHRoZXkgY291bGQg
b25seSBiZSBzbG93ZXIgYmVjYXVzZSBvZiB0aGUgbmV0d29yayBsaW5rLiBIb3cgYWJvdXQgY29u
ZWN0aW5nIGEgcGh5c2ljYWwgbWFjaGluZSBhbmQgZ2V0dGluZyBhIGJhc2VsaW5lPyBBbGwgaW4g
YWxsIEkgY29uc2lkZXIgdGhpcyBjYXBhYmlsaXR5IHByb3ZpZGVkIGJ5IGNvTGludXggdG8gYmUg
YSBwcm9vZiBvZiBjb25jZXB0LiANCg0KU29tZXRoaW5nIHRoYXQgSSBhbSBjdXJyZW50bHkgbG9v
a2luZyBhdCBpcyB0d2Vha2luZyBLREUgYW5kL29yIEdub21lIHNvIHRoYXQgYWxsIG9mIHRoZSBl
eWUgY2FuZHkgaXMgZGlzYWJsZWQgZXRjIHRvIGFsbGV2aWF0ZSBzb21lIGxvYWQuIFBlcmhhcHMg
dHJ5IGRpc2FibGluZyBzb3VuZCBiZWZvcmUgdGhlIHNlc3Npb24gaXMgc3RhcnRlZCBhcyBzb3Vu
ZCB3b250IHdvcmsgYW55d2F5IGFuZCB0aGlzIGlzIG9uZSBvZiB0aGUgdGhpbmdzIHRoYXQgSSBm
aW5kIG9uIGEgbmF0aXZlIExpbnV4IGJveCBpbXBhaXJzIHBlcmZvcm1hbmNlLiBUaGVyZSBhcmUg
YWxzbyBwYXRjaGVzIHRvIHRoZSBrZXJuZWwgdGhhdCBvcHRpbWl6ZSB0aGUgc2NoZWR1bGVyIGFu
ZCBzbyBvbi4gUGVyaGFwcyB0aGVzZSBjb3VsZCBiZSBhcHBsaWVkLiBObyBpZGVhLiAyLjY/IEkg
dGhpbmsgdGhhdCBJIHdpbGwgZW5kIHVwIHdhaXRpbmcgdW50aWwgYSB2aXJ0dWFsIGdyYXBoaWNz
IGNhcmQgaXMgaW1wbGVtZW50ZWQgaW4gY29MaW51eCBhcyBpbiB2bXdhcmUgKHRoZSBkaWZmcyBm
b3IgdGhlaXIgY2FyZCBhcmUgYXZhaWxhYmxlIGZvciB0aGlzIGZyb20gdGhlaXIgc2l0ZSBidHcg
YXMgaXQgaXMgb3BlbiBzb3VyY2UpLg0KDQpBbnlvbmUgaGFkIGFueSBvdGhlciBpZGVhcyBhbG9u
ZyB0aGlzIGxpbmU/DQo=

[coLinux-devel] RE: Problem running KDE

[Alex <ab3...@ho...>]

I have similar problems. Often KDE stops responding, then after some =
timeout it resumes working.
Anybody have success in running KDE? Just curious is it common problem =
or something wrong in my setup?

Thank You


>>Hello,
>>
>> First I'd like to thank for a very interesting project! Keep good =
working!
>>
 >>I've tried it for some days and it look very usefull.
 >>
 >>Now to my question: I have a problem to run KDE environment. I've=20
 >>installed Cygwin X and permit host 192.168.0.40 (xhost +192.168.0.40) =

 >>which is colinux virtual machine on my Windows XP box. On colinux=20
 >>machine I've installed KDE (apt-get install kde), set DISPLAY (export =

 >>DISPLAY=3D"192.168.0.1:0") and tried to start kde (startkde). =
Starting KDE=20
 >>screen have appeared, but it has taken a VERY long time before KDE=20
 >>really started. There were also dialog boxes with messages like =
"Sound=20
 >>server fatal error: cpu overload, aborting" and "device /dev/dsp =
can't=20
 >>be opened" (the second is usual, when I don't have a rigth module in=20
 >>kernel for my sound card, I know, but I don't know yet, what to do =
with=20
 >>this in colinux).
>>=20
 >>Am I doing anything wrong? Should I kill (someway) arts daemon (or=20
 >>disable it, while starting KDE)?
>>=20
 >>Thank in advance for any help. Sorry for poor english.
>>=20
 >>Fastek

Re: [coLinux-devel] Installing regular distribution CDs

[Pat E. <pat...@ma...>]

well, since I don't seem to be able to e-mail you directly...

irc.oftc.net/#offtopic

I'm s0be

Pat Erley