colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] 0.5.3pre2: dselect, mmap [ was: klog, dpkg, alloc_pages error ]

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

Can you have all three sources at once? stable, testing, and unstable? Won't
your packages get all out of sync if you try to mix releases?

I'm not super familiar with Debian so excuse me if I'm wrong :-)

Richard



----- Original Message ----- 
From: "Ballard Jonathan" <sac...@ho...>
To: "coLinux Development" <col...@li...>
Sent: Tuesday, February 10, 2004 8:05 PM
Subject: [coLinux-devel] 0.5.3pre2: dselect, mmap [ was: klog, dpkg,
alloc_pages error ]


> I added 256MB of a swapfile.  After I added more entries to the
> /etc/apt/sources.list, dselect complained about MMap.
>
> ---
>
> Reading Package Lists... Error!
> E: Dynamic MMap ran out of room
> E: Error occured while processing doc-rfc-3000-3999 (NewVersion1)
> E: Problem with MergeList
>
/var/lib/apt/lists/http.us.debian.org_debian_dists_testing_non-free_binary-i
> 386_Packages
> E: The package lists or status file could not be parsed or opened.
>
> update available list script returned error exit status 1.
>
> ---
>
> I did not find any kernel message displayed about the issue.
> Here is my /etc/apt/sources.list:
>
> ----
>
>
> deb http://http.us.debian.org/debian stable main contrib non-free
> deb http://http.us.debian.org/debian testing main contrib non-free
> deb http://http.us.debian.org/debian unstable main contrib non-free
>
> ---
>
> I guess I can shorten the list for now.
>
> ----- Original Message -----
> From: "Richard Goodwin" <ric...@ri...>
> To: "coLinux Development" <col...@li...>
> Sent: Tuesday, February 10, 2004 9:47 AM
> Subject: Re: [coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while
> configed
>
>
> > Jonathan,
> >
> > I belive from what I have discussed with Dan that that is a standard
"out
> of
> > memory" condition. Have you setup swap space?
> >
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
>

[coLinux-devel] 0.5.3pre2: dselect, mmap [ was: klog, dpkg, alloc_pages error ]

[Ballard J. <sac...@ho...>]

I added 256MB of a swapfile.  After I added more entries to the
/etc/apt/sources.list, dselect complained about MMap.

---

Reading Package Lists... Error!
E: Dynamic MMap ran out of room
E: Error occured while processing doc-rfc-3000-3999 (NewVersion1)
E: Problem with MergeList
/var/lib/apt/lists/http.us.debian.org_debian_dists_testing_non-free_binary-i
386_Packages
E: The package lists or status file could not be parsed or opened.

update available list script returned error exit status 1.

---

I did not find any kernel message displayed about the issue.
Here is my /etc/apt/sources.list:

----


deb http://http.us.debian.org/debian stable main contrib non-free
deb http://http.us.debian.org/debian testing main contrib non-free
deb http://http.us.debian.org/debian unstable main contrib non-free

---

I guess I can shorten the list for now.

----- Original Message -----
From: "Richard Goodwin" <ric...@ri...>
To: "coLinux Development" <col...@li...>
Sent: Tuesday, February 10, 2004 9:47 AM
Subject: Re: [coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while
configed


> Jonathan,
>
> I belive from what I have discussed with Dan that that is a standard "out
of
> memory" condition. Have you setup swap space?
>

[coLinux-devel] Re:0.5.3pre2: klog, dpkg utils errored while configed

[Ballard J. <sac...@ho...>]

I created an extra block device, cobd1.  I put a 256MB swapfile on cobd1.

colinux:/etc# cat fstab
/dev/cobd0 / ext2 defaults 0 1
proc /proc proc defaults 0 0
/dev/cobd1 /mnt/cobd1 ext2 defaults 0 2
/mnt/cobd1/swapfile none swap defaults 0 0

I ran dselect again, and I have not seen any kernel complaints.

When I compiled binutils before, I noticed it did not handle situations when
some utilities where not available.  Specifically, it did not handle no
"msgfmt" or no "flex" well.  After I added the swapfile, dselect noticed
that "gettext" was downloaded but not installed.  That explains why the "no"
utility not found message appeared.

Seems like I need a generic cobd0 and a cobd1 that can quickly resetup
cobd0.  The coLinux projects sure does make reinstalls much much easier.

----- Original Message -----
From: "Richard Goodwin" <ric...@ri...>
To: "coLinux Development" <col...@li...>
Sent: Tuesday, February 10, 2004 9:47 AM
Subject: Re: [coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while
configed


> Jonathan,
>
> I belive from what I have discussed with Dan that that is a standard "out
of
> memory" condition. Have you setup swap space?
>
> ----- Original Message -----
> From: "Ballard Jonathan" <sac...@ho...>
> To: "coLinux Development" <col...@li...>
> Sent: Tuesday, February 10, 2004 11:07 AM
> Subject: [coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while
configed
>
>
> Before I hunt down the issue any further, I'll posted the messages I
> received when I tried to run dselect configuration.   When I selected the
> configure option, a random appearance of an error occurred.  Seems like it
> happened within the perl utilities.
>
> __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> VM: killing process $PROCNAME
>
> such that $PROCNAME is an element of { su, http, mandb, dpkg,
> dpkg-preconfigu, klogd }
>
> My attempt to configure the system with 0.5.3pre2 worked better than the
> 0.5.2 version, as I did not get all the configuration screens with 0.5.2.
> I do not remember such messages as the __alloc_pages.
>
> Further, I untarred and cvs'ed the colinux and linux sources without
> problems.  I compiled binutils, yet that did not finish because it could
not
> find the "no" utility.
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

Re: [coLinux-devel] Some problems....

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

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

Hi  3DoFF,

I'm not 100% sure but I think colinux can not handle iso-images. You must
also do slightly modification to the image (creating /dev/cobd*-devices
and enties in /dev/fstab).
You will need a HD image (lo-device-image) instead.

Thomas

> Hello, colinux-devel,
>
> See the screenshot.
> I'm trying to run MorphixBase-0.3-4.iso which I copied into C:\coLinux
> dir.
> Do I have to change default.colinux.xml file?
> I changed it to:
> <?xml version="1.0" encoding="UTF-8"?>
> <colinux>
>     <block_device index="0"
> path="\DosDevices\c:\coLinux\MorphixBase-0.3-4.iso" enabled="true">
>     </block_device>
>     <bootparams>root=/dev/cobd0</bootparams>
>     <image path="vmlinux">MorphixBase-0.3-4.iso</image>
> </colinux>
>
> and so:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <colinux>
>     <block_device index="0"
> path="\DosDevices\c:\coLinux\MorphixBase-0.3-4.iso" enabled="true">
>     </block_device>
>     <bootparams>root=/dev/cobd0</bootparams>
>     <image path="vmlinux"></image>
> </colinux>
>
> Nothing works. It leads me to error, shown on print screen in the
> attach.
>
> --
> 3DoFF


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

iD8DBQFAKVhgnwJBIFTVIqwRArcgAKC0XPAdZUG1ea9M30RQJ9AFdq+pIACgvoxD
Usz3Al/EHkQ7bPQwYAcVg1I=
=QCxX
-----END PGP SIGNATURE-----

[coLinux-devel] Some problems....

[3DoFF <3D...@ma...>]

Hello, colinux-devel,

See the screenshot.
I'm trying to run MorphixBase-0.3-4.iso which I copied into C:\coLinux
dir.
Do I have to change default.colinux.xml file?
I changed it to:
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0" path="\DosDevices\c:\coLinux\MorphixBase-0.3-4.iso" enabled="true">
    </block_device>
    <bootparams>root=/dev/cobd0</bootparams>
    <image path="vmlinux">MorphixBase-0.3-4.iso</image>
</colinux>

and so:

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0" path="\DosDevices\c:\coLinux\MorphixBase-0.3-4.iso" enabled="true">
    </block_device>
    <bootparams>root=/dev/cobd0</bootparams>
    <image path="vmlinux"></image>
</colinux>

Nothing works. It leads me to error, shown on print screen in the
attach.

-- 
3DoFF

RE: [coLinux-devel] X-windows configuration question

[Deagan, T. <tim...@at...>]

 This works great!  I'm using the cygwin X server.  

For those who are rusty on this (like I was :-), on the PC X window side
just (I'll use my own IP, change it to yours):
# Set DISPLAY variable (set DISPLAY="192.168.1.100:0")
# I did an export (export DISPLAY)
# Allow colinux to connect to your X server (xhost +192.168.1.77)
# on the colinux side start up something (xterm -display 192.168.1.100:0)
--Tim

-----Original Message-----
From: Dan Aloni
To: Deagan, Tim
Cc: 'col...@li...'
Sent: 2/10/2004 3:01 PM
Subject: Re: [coLinux-devel] X-windows configuration question

On Tue, Feb 10, 2004 at 02:49:59PM -0600, Deagan, Tim wrote:
> I have the latest binary working nicely on XP Home.  TAP driver set up
as a
> bridged connection to my existing LAN connection.  Used combo of
information
> from the recent 'Working Great' post and the 'Network configuration'
post.
> Had to use ctrl-c instead of Esc in vi to edit files.
> 
> Networking now with no problem, used apt-get update and then apt-get
install
> to get x-windows and kde.
> 
> Chose generic vga, standard us pc everything in xconfig.  XP crashes
> (gracefully and returns in a 640x480x8 'safe' mode without rebooting.)
I'm
> guessing sync modes might not be right or somesuch.  Had to get it to
stop
> trying to auto-start xwindows or it XP crashed every time.
> 
> Anyone care to share the xconfig settings chosen?

You can't run an X server on coLinux at the moment. Use an existing X
server 
such as XFree86's and start a remote session across the virtual network.

Far from that, it would be nice to find that place in the kernel which
the X server you installed uses in order to change video modes, and
disable
that place in the patch.

-- 
Dan Aloni
da...@gm...

Re: [coLinux-devel] X-windows configuration question

[Dan A. <da...@gm...>]

On Tue, Feb 10, 2004 at 02:49:59PM -0600, Deagan, Tim wrote:
> I have the latest binary working nicely on XP Home.  TAP driver set up as a
> bridged connection to my existing LAN connection.  Used combo of information
> from the recent 'Working Great' post and the 'Network configuration' post.
> Had to use ctrl-c instead of Esc in vi to edit files.
> 
> Networking now with no problem, used apt-get update and then apt-get install
> to get x-windows and kde.
> 
> Chose generic vga, standard us pc everything in xconfig.  XP crashes
> (gracefully and returns in a 640x480x8 'safe' mode without rebooting.)  I'm
> guessing sync modes might not be right or somesuch.  Had to get it to stop
> trying to auto-start xwindows or it XP crashed every time.
> 
> Anyone care to share the xconfig settings chosen?

You can't run an X server on coLinux at the moment. Use an existing X server 
such as XFree86's and start a remote session across the virtual network.

Far from that, it would be nice to find that place in the kernel which
the X server you installed uses in order to change video modes, and disable
that place in the patch.

-- 
Dan Aloni
da...@gm...

[coLinux-devel] X-windows configuration question

[Deagan, T. <tim...@at...>]

I have the latest binary working nicely on XP Home.  TAP driver set up as a
bridged connection to my existing LAN connection.  Used combo of information
from the recent 'Working Great' post and the 'Network configuration' post.
Had to use ctrl-c instead of Esc in vi to edit files.

Networking now with no problem, used apt-get update and then apt-get install
to get x-windows and kde.

Chose generic vga, standard us pc everything in xconfig.  XP crashes
(gracefully and returns in a 640x480x8 'safe' mode without rebooting.)  I'm
guessing sync modes might not be right or somesuch.  Had to get it to stop
trying to auto-start xwindows or it XP crashed every time.

Anyone care to share the xconfig settings chosen?

Thanks, what a bad-ass hunk of code!
--Tim
 

Re: [coLinux-devel] The upcoming release

[andre <avb...@gm...>]

On Tuesday 10 February 2004 19:08, Nir Perry wrote:
> Hi,
>
> You can't just install any distribution on coLinux, much like you can't
> do it under UML.
> It is simply because kernel  is modified, and you'll need that kernel
> after the installation.

The kernel is about the only thing that is changed so if you install the 
colinux kernel than it should work. I think you can even install a real linux 
installation from inside windows and than start it with the windows boot 
selector.

>
> What you should probably have is a bootable 'floppy' or similar with a
> coLinux kernel that is compatible with that distribution (for example,
> have all the modules the installation program depends on), and a few
> scripts to replace the kernel after installation.
> I'm affraid you'll have to tweak one such bootable for every
> distribution (unless they run the same isolinux or installer).

They almost all use the same methode and the number of modules is very limited 
as in iso9660, cloop & cramfs. Most of them allow X output to another screen 
and the only real problem is the automatic searching for devices which you 
often can be done manual and the filesystem selection and formatation can be 
a problem

>
> Basically, this is just a tip, but someone can go through with it and
> make such bootables.
> Maybe someday, even I will try.
>

Re: [coLinux-devel] The upcoming release

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

Hi,

You can't just install any distribution on coLinux, much like you can't 
do it under UML.
It is simply because kernel  is modified, and you'll need that kernel 
after the installation.

What you should probably have is a bootable 'floppy' or similar with a 
coLinux kernel that is compatible with that distribution (for example, 
have all the modules the installation program depends on), and a few 
scripts to replace the kernel after installation.
I'm affraid you'll have to tweak one such bootable for every 
distribution (unless they run the same isolinux or installer).

Basically, this is just a tip, but someone can go through with it and 
make such bootables.
Maybe someday, even I will try.

Nir


ePAc wrote:

>>Amongst the changes for tomorrow's release, we have:
>>
>>  * The daemon is killable like any other Windows process. Closing it,
>>    CTRL-C, or ending the task, will all cleanly shutdown the Linux
>>    system.
>>  * printk()s are routed to the output of the colinux-daemon box, so you
>>    can see the kernel as it boots without opening the console.
>>  * Some fixes, especially for that BSOD bug lots of you have seen on
>>    startup, and for the network packet corruption issue.
>>  * The build doesn't depend anymore on the Microsoft DDK.
>>  * Overall design improvements.
>>
>>    
>>
>
>could there also be "isofs"/"iso9660" support in kernel ?
>(so as to be able to mount a CDROM and boot off it.. :o)
>
>it would be sweet to be able to boot off a ramdisk from a install CD, load
>the CD up and install "Your Favorite Distro", which can then be shared
>with everyone ... :o)
>
>Thanks,
>Jok
>
>---
>Nothing is foolproof to a sufficiently talented fool...
>  oo
>,(..)\
>  ~~
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>  
>

Re: [coLinux-devel] Monitor terminated, reason 7?

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

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

Hi colinuxer,

I found an other easy way to reproduce this error. I just used colinux
(pre2) with the standard-debian-image.

I updated the system to "testing" with apt-get and installed gcc (3.3.2),
make... and the other stuff to build the kernel. I then used patch and
linux-config file from the same colinux release (pre2) and compiled
colinux-kernel within colinux.

Then I copy the vmlinux kernel back to the windows system and replaced
just the vmlinux file with the new compiled version. If I try to start
again I also receive this termination.
Is there someone how could build the colinux-kernel within colinux?

Thanks and regards,
 Thomas



> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello coLinux-hackers,
>
> I build colinux-20040208 with the first network-init patch from source. My
> problem is that I receive the message: "Monitor terminated, reason 7".
> In detail:
> after starting the daemon the console pops up and I see the begin of the
> kernel boot:
>
>  ....BogoMIPS....CPU:.... Linux NET4.0... Initializing RT netlink socket..
> Starting kswapd... Journalled Block Device driver loaded.
>
> The message with the "Block Device" is the last in the console. The
> console stays open and I see the message that the TAP-WIN network was
> disconnected (message in systemtray).
>
> In the MS-Dos window I see Monitor terminated, reason 7 and other messages
> that the Monitor is shutting down etc.
>
> Any Hints?
>
> Thanks and regards,
>  Thomas
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFAJ78ZnwJBIFTVIqwRAkaXAKCAXddyYUhy4EPBtrZbRF+/aS8YCACgyBhE
> /DkzYAYIyEsGzGvno6Gon3w=
> =9YT5
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>


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

iD8DBQFAKR9BnwJBIFTVIqwRAlSsAJ9tt0+frn9s2atFLqowBHMj/CIY0gCfe0Mn
U36b0PTK/nzRjs8J4lfpdKU=
=rDwe
-----END PGP SIGNATURE-----

Re: [coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while configed

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

Jonathan,

I belive from what I have discussed with Dan that that is a standard "out of
memory" condition. Have you setup swap space?

----- Original Message ----- 
From: "Ballard Jonathan" <sac...@ho...>
To: "coLinux Development" <col...@li...>
Sent: Tuesday, February 10, 2004 11:07 AM
Subject: [coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while configed


Before I hunt down the issue any further, I'll posted the messages I
received when I tried to run dselect configuration.   When I selected the
configure option, a random appearance of an error occurred.  Seems like it
happened within the perl utilities.

__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process $PROCNAME

such that $PROCNAME is an element of { su, http, mandb, dpkg,
dpkg-preconfigu, klogd }

My attempt to configure the system with 0.5.3pre2 worked better than the
0.5.2 version, as I did not get all the configuration screens with 0.5.2.
I do not remember such messages as the __alloc_pages.

Further, I untarred and cvs'ed the colinux and linux sources without
problems.  I compiled binutils, yet that did not finish because it could not
find the "no" utility.

Re: [coLinux-devel] The upcoming release

[ePAc <ep...@ko...>]

> Amongst the changes for tomorrow's release, we have:
>
>   * The daemon is killable like any other Windows process. Closing it,
>     CTRL-C, or ending the task, will all cleanly shutdown the Linux
>     system.
>   * printk()s are routed to the output of the colinux-daemon box, so you
>     can see the kernel as it boots without opening the console.
>   * Some fixes, especially for that BSOD bug lots of you have seen on
>     startup, and for the network packet corruption issue.
>   * The build doesn't depend anymore on the Microsoft DDK.
>   * Overall design improvements.
>

could there also be "isofs"/"iso9660" support in kernel ?
(so as to be able to mount a CDROM and boot off it.. :o)

it would be sweet to be able to boot off a ramdisk from a install CD, load
the CD up and install "Your Favorite Distro", which can then be shared
with everyone ... :o)

Thanks,
Jok

---
Nothing is foolproof to a sufficiently talented fool...
  oo
,(..)\
  ~~

[coLinux-devel] 0.5.3pre2: klog, dpkg utils errored while configed

[Ballard J. <sac...@ho...>]

Before I hunt down the issue any further, I'll posted the messages I =
received when I tried to run dselect configuration.   When I selected =
the configure option, a random appearance of an error occurred.  Seems =
like it happened within the perl utilities.

__alloc_pages: 0-order allocation failed (gfp=3D0x1d2/0)
VM: killing process $PROCNAME

such that $PROCNAME is an element of { su, http, mandb, dpkg, =
dpkg-preconfigu, klogd }

My attempt to configure the system with 0.5.3pre2 worked better than the =
0.5.2 version, as I did not get all the configuration screens with =
0.5.2.   I do not remember such messages as the __alloc_pages.

Further, I untarred and cvs'ed the colinux and linux sources without =
problems.  I compiled binutils, yet that did not finish because it could =
not find the "no" utility. =20

[coLinux-devel] How boot KNOPPIX under coLinux?

[Sergey S. <sg...@se...>]

Hello colinux-devel,

  How boot Knoppix or any other Live-cd under coLinux?

-- 
Best regards,
 Sergey                          mailto:sg...@se...

Re: [coLinux-devel] Re: Output 20040208 (pre patch)

[Ian L. <Ian...@mq...>]

I've downloaded the Debian ISOs - I'll build up a Debian dev environment
and get myself closer to your build environment.  This won't be ready
before the weekend though, I don't think.

Thanks for the feedback.


----- Original Message -----
>From: "Dan Aloni" <da...@gm...>
>To: "Ian Latter" <Ian...@mq...>
>Subject:  Re: [coLinux-devel] Re: Output 20040208 (pre patch)
>Date: Mon, 09 Feb 2004 23:32:47 +0200
>
> On Mon, Feb 09, 2004 at 07:19:33PM +1000, Ian Latter wrote:
> > Hello Dan,
> > 
> >   I've included all of the details I can think to .. I've also attached
> > the kernel that this combination produced. Let me know if you 
> > need something/anything else.
> 
> You are using gcc 3.2. I use gcc 3.3 to compile all code for coLinux, 
> including vmlinux and linux.sys. There could be a binary incompatibility 
> between the version of your gcc (3.2) and the gcc that linux.sys was 
> compiled against (3.3).
> 
> My current compilers versions:
> 
> [23:22 pts/10,callisto ~]% gcc -v
> Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs
> Configured with: ../src/configure -v --enable-
languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
> --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-
dir=/usr/include/c++/3.3 --enable-shared 
> --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-
clocale=gnu --enable-debug 
> --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
> Thread model: posix
> gcc version 3.3.3 20040125 (prerelease) (Debian)
> 
> [23:24 pts/10,callisto ~]% i686-pc-cygwin-gcc -v
> Reading specs from /usr/local/w32build/lib/gcc-lib/i686-pc-cygwin/3.3.2/specs
> Configured with: ./configure --target=i686-pc-cygwin --prefix=/usr/local/w32build --enable-
languages=c,c++
> Thread model: single
> gcc version 3.3.2
> 
> 
> -- 
> Dan Aloni
> da...@gm...
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 

--
Ian Latter
Internet and Networking Security Officer
Macquarie University

 Meet me at the Australian Unix and open systems
   User Group (AUUG) Security Symposium; 2004
  http://www.auug.org.au/events/2004/security/

[coLinux-devel] Re: terminated, reason 7 / new releases pre2

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

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

Hello Dan,

today I made the followning test. I used my self build binary files
(console , daemon, linux.sys )
and just used your kernel file from the "flamed chicken" release. This
works without the "termination message reason 7". So this is a kernel
issue.

You wrote about the used gcc version. Is this issue solved? I'm at work
now so I could just have a look at the bin-version of pre2 release. But a
cat /proc/version gives me the same debian gcc-version that I use. (I
don't have checked gcc-version of your pre1 release)

A few commands about the bin-pre2 release:

- - I also have 99% CPU load for the console. If I use the daemon without
the console this is no issue.

- - For some reason I don't have network connection after installing the new
version of the TAP-WIN32 driver. I think this is no colinux issue. I just
disabled IP-sharing and enabled it again and that solved this problem.

- - The network corruption is solved. I'm also missing the delay connecting
from ssh (putty)

- - I still have this fsck issue!?! I enable the rootfs option again a have
this error. I tried to fix this by running fsck manualy without success.

Thanks and regards,
 Thomas


> On Mon, Feb 09, 2004 at 10:57:01PM +0200, Dan Aloni wrote:
>> On Mon, Feb 09, 2004 at 05:10:49PM -0000, Thomas Fritzsche wrote:
>>
>> > I build colinux-20040208 with the first network-init patch from
>> source. My
>> > problem is that I receive the message: "Monitor terminated, reason 7".
>
> I take that back. Verify your compiler versions first.
>>
>> If you have some kernel debugging experience, I suggest you investigate
>> from where one of these functions is called on your setup.
>
> --
> Dan Aloni
> da...@gm...
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>


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

iD8DBQFAKJpSnwJBIFTVIqwRAlNqAJ9UnCfspkS6wdd6p1BcJw+LtVJJ4ACdE62+
l3A32u5H6DdjHfE93RHNeHY=
=QnhH
-----END PGP SIGNATURE-----

Re: [coLinux-devel] Working great!

[Dan A. <da...@gm...>]

On Mon, Feb 09, 2004 at 07:04:39PM -0800, Christophe Thibault wrote:
> Just start colinux-deamon.exe with the "-d" parameter and it won't launch a
> console.
> 
> By the way, does anyone else experience colinux-console.exe to take 100% CPU
> under NT Task Manager?

Yes. I'm working on that issue.

-- 
Dan Aloni
da...@gm...

[coLinux-devel] feature request for 2.0: NT security

[Ballard J. <sac...@ho...>]

I have an earily request to make for version 2.0 of coLinux.  I would =
like to coLinux operate under two different security levels.  The first =
level would be like how coLinux runs now but limited to only access the =
files that the user account that started coLinux can access.  The second =
mode would be a system (non-NT-login admin) account.  The system account =
would start coLinux at boot and run detached from the NT terminal =
server.  Only a local console run by an user admin account would be able =
to log into the system priviledged coLinux.  That could be done with a =
modified TAP driver that only allows admin access.

Something to think about.  I figure version 1.0 would have open access.

Jonathan

Re: [coLinux-devel] Working great!

[Ben L. <lev...@ya...>]

--- Ben Levitt <lev...@ya...> wrote:
> In /etc/network/interfaces, I changed the line that
> read:
>    auto lo eth0
> to
>    iface lo inet loopback

Ooops.  I should have said:

In /etc/network/interfaces, after the line that
read:
   auto lo eth0
I added the line:
   iface lo inet loopback

Otherwise the network doesn't start up automatically 
:]

(You learn something new every day!)

Ben



__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

Re: [coLinux-devel] Working great!

[Christophe T. <ch...@ae...>]

Just start colinux-deamon.exe with the "-d" parameter and it won't launch a
console.

By the way, does anyone else experience colinux-console.exe to take 100% CPU
under NT Task Manager?

-Christophe

----- Original Message ----- 
From: "Ben Levitt" <lev...@ya...>
To: <coL...@li...>
Sent: Monday, February 09, 2004 6:52 PM
Subject: [coLinux-devel] Working great!


> Wow, excellent project!
>
> It took me a tiny bit of tweaking but I now have a
> great, working, seemingly stable copy of debian
> working on my Win2000 box at work.
>
> I installed the TAP driver, and then in "Network and
> Dial-up Connections", I opened "Local Area
> Connection", clicked Properties, then clicked
> "Sharing", then Enabled Internet Connection Sharing.
>
> I also had to edit a few files in the default debian
> image to get things working.  (Using the 20040210
> version of colinux.)
>
> In /etc/network/interfaces, I changed the line that
> read:
>    auto lo eth0
> to
>    iface lo inet loopback
>
> I created /etc/hosts with these 3 lines:
> 127.0.0.1     localhost colinux
> 192.168.0.40  colinux
> 192.168.0.1   windows
>
> Then networking worked right.  (Not being able to ping
> localhost was bugging me. :]  )
>
> I then ran apt-get update, and then apt-get install'd
> a bunch of stuff, including X, vnc, etc.  It all
> works!
>
> I sheepishly must admit that I haven't grabbed the
> coLinux source, so it's probably an easy fix I could
> make, but one change that would make me even happier
> would be if starting the colinux-daemon did _not_
> start the console.  I have it up and running with an
> ssh server, so I don't feel the need to use the
> console.  It just gets in the way until I disconnect
> it.  It seem like it would be so easy for users to
> start up the console if they want it, that there's no
> need to make it auto-start...
>
> Anyway, thanks very much!  It works great!
>
> Ben
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online.
> http://taxes.yahoo.com/filing.html
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel

[coLinux-devel] Working great!

[Ben L. <lev...@ya...>]

Wow, excellent project!

It took me a tiny bit of tweaking but I now have a
great, working, seemingly stable copy of debian
working on my Win2000 box at work.

I installed the TAP driver, and then in "Network and
Dial-up Connections", I opened "Local Area
Connection", clicked Properties, then clicked
"Sharing", then Enabled Internet Connection Sharing.

I also had to edit a few files in the default debian
image to get things working.  (Using the 20040210
version of colinux.)

In /etc/network/interfaces, I changed the line that
read:
   auto lo eth0
to
   iface lo inet loopback

I created /etc/hosts with these 3 lines:
127.0.0.1     localhost colinux
192.168.0.40  colinux
192.168.0.1   windows

Then networking worked right.  (Not being able to ping
localhost was bugging me. :]  )

I then ran apt-get update, and then apt-get install'd
a bunch of stuff, including X, vnc, etc.  It all
works!

I sheepishly must admit that I haven't grabbed the
coLinux source, so it's probably an easy fix I could
make, but one change that would make me even happier
would be if starting the colinux-daemon did _not_
start the console.  I have it up and running with an
ssh server, so I don't feel the need to use the
console.  It just gets in the way until I disconnect
it.  It seem like it would be so easy for users to
start up the console if they want it, that there's no
need to make it auto-start...  

Anyway, thanks very much!  It works great!

Ben


__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

Re: [coLinux-devel] coLinux 0.5.3-pre2

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

Anyone else getting filesystem check problems on a second mounted file?
Intermittently it's hanging on fsck at startup on my /dev/cobd1 (mounted as
/usr, it's a 1gb file) even with the newest release pre2. Running fsck
manually says the filesystem is clean.


----- Original Message ----- 
From: "Dan Aloni" <da...@gm...>
To: "Cooperative Linux Development" <col...@li...>
Sent: Monday, February 09, 2004 5:59 PM
Subject: [coLinux-devel] coLinux 0.5.3-pre2


> Hello,
>
> Besides some fixes against -pre1, there aren't many changes for this
> release.
>
> * Version 0.5.3-pre2
>   * Fixed the reported (and unreported) network bugs.
>   * Worked out some scheduling issue.
>
> -- 
> Dan Aloni
> da...@gm...
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
>

[coLinux-devel] coLinux 0.5.3-pre2

[Dan A. <da...@gm...>]

Hello, 

Besides some fixes against -pre1, there aren't many changes for this 
release.

* Version 0.5.3-pre2
  * Fixed the reported (and unreported) network bugs. 
  * Worked out some scheduling issue.

-- 
Dan Aloni
da...@gm...

Re: [coLinux-devel] Re: Output 20040208 (pre patch)

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

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

Hello Dan,

I missed the begin of this thread but I'm using exact the same compilers:

cross compiler:
 ./i686-pc-cygwin-gcc -v
Reading specs from ./../lib/gcc-lib/i686-pc-cygwin/3.3.2/specs
Konfiguriert mit: ./configure --prefix=/home/thomas/test-new/target
- --target=i686-pc-cygwin --enable-languages=c,c++ : (reconfigured)
./configure --prefix=/home/thomas/test-new/target --target=i686-pc-cygwin
- --enable-languages=c,c++
Thread model: single
gcc-Version 3.3.2
- -----------------------
native (debian) linux-compiler:
 gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs
Konfiguriert mit: ../src/configure -v
- --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
- --mandir=/usr/share/man --infodir=/usr/share/info
- --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
- --with-system-zlib --enable-nls --without-included-gettext
- --enable-__cxa_atexit --enable-clocale=gnu --enable-debug
- --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc-Version 3.3.3 20040125 (prerelease) (Debian)

Thanks and regards,
 Thomas



> On Mon, Feb 09, 2004 at 07:19:33PM +1000, Ian Latter wrote:
>> Hello Dan,
>>
>>   I've included all of the details I can think to .. I've also attached
>> the kernel that this combination produced. Let me know if you
>> need something/anything else.
>
> You are using gcc 3.2. I use gcc 3.3 to compile all code for coLinux,
> including vmlinux and linux.sys. There could be a binary incompatibility
> between the version of your gcc (3.2) and the gcc that linux.sys was
> compiled against (3.3).
>
> My current compilers versions:
>
> [23:22 pts/10,callisto ~]% gcc -v
> Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs
> Configured with: ../src/configure -v
> --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
> --mandir=/usr/share/man --infodir=/usr/share/info
> --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
> --with-system-zlib --enable-nls --without-included-gettext
> --enable-__cxa_atexit --enable-clocale=gnu --enable-debug
> --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
> Thread model: posix
> gcc version 3.3.3 20040125 (prerelease) (Debian)
>
> [23:24 pts/10,callisto ~]% i686-pc-cygwin-gcc -v
> Reading specs from
> /usr/local/w32build/lib/gcc-lib/i686-pc-cygwin/3.3.2/specs
> Configured with: ./configure --target=i686-pc-cygwin
> --prefix=/usr/local/w32build --enable-languages=c,c++
> Thread model: single
> gcc version 3.3.2
>
>
> --
> Dan Aloni
> da...@gm...
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>


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

iD8DBQFAKAn8nwJBIFTVIqwRAovdAJ0TPePncbLnGrPX7EsT5VVdInrrEgCfRgBz
dcgDiyK/gwfP9i+HzMURsFU=
=9unR
-----END PGP SIGNATURE-----