colinux-devel

[coLinux-devel] Memory size and killing console by Esc

[Paul S. <coo...@ua...>]

Hello colinux-devel,

  I would like to report success running coLinux on
P4/2.66GHz(no-hyperthreading)/1Gb/SiS chipset (forget which one ;-).
I had that image size problem but apart from that everything seems to
run smooth.

  There're two feature requests I'd like to sound which somehow were
touched on the list, but doesn't seem to draw much attention:

1. Could memory size for coLinux be configurable? Current 24Mb or so
is a joke. Yes, swap can be mounted, but why experience perfomance of
vmware level? ;-) It would be nice to have memory size configurable in
XML config, but if it's some time to do, could next release ship with
at least slightly decent amount, like 64Mb (128Mb better ;-).

2. Could Esc key stop killing console? I currently work that around by
Alt+27 on numeric keyboard, but it's just pain in the eye.

  Ah, and yes - default image provided is pretty bare. It would be
nice to have at least ftpd and telnetd, and less included - it's not
always suitable to do apt-get (for example, for people with networking
problems). I guess, that's request for some kind sole who can
contribute such an image, coLinux author has other stuff to do ;-)


Thanks and have a great weekend!

-- 
Best regards,
 Paul                          mailto:coo...@ua...

Re: [coLinux-devel] Memory size and killing console by Esc

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

I don't know about 1 or 2, but I highly second the request for a different
image. I'd actually like to use Arch Linux; would being 686 targeted be a
problem? The package management sounds much like Debian and it sounds like
you could start with a fairly small image as well.

I tried to make one at work earlier but something happened with the
networking and I couldn't dd off the image :-)

Richard

----- Original Message ----- 
From: "Paul Sokolovsky" <coo...@ua...>
To: <col...@li...>
Sent: Friday, February 06, 2004 4:52 PM
Subject: [coLinux-devel] Memory size and killing console by Esc


> Hello colinux-devel,
>
>   I would like to report success running coLinux on
> P4/2.66GHz(no-hyperthreading)/1Gb/SiS chipset (forget which one ;-).
> I had that image size problem but apart from that everything seems to
> run smooth.
>
>   There're two feature requests I'd like to sound which somehow were
> touched on the list, but doesn't seem to draw much attention:
>
> 1. Could memory size for coLinux be configurable? Current 24Mb or so
> is a joke. Yes, swap can be mounted, but why experience perfomance of
> vmware level? ;-) It would be nice to have memory size configurable in
> XML config, but if it's some time to do, could next release ship with
> at least slightly decent amount, like 64Mb (128Mb better ;-).
>
> 2. Could Esc key stop killing console? I currently work that around by
> Alt+27 on numeric keyboard, but it's just pain in the eye.
>
>   Ah, and yes - default image provided is pretty bare. It would be
> nice to have at least ftpd and telnetd, and less included - it's not
> always suitable to do apt-get (for example, for people with networking
> problems). I guess, that's request for some kind sole who can
> contribute such an image, coLinux author has other stuff to do ;-)
>
>
> Thanks and have a great weekend!
>
> -- 
> Best regards,
>  Paul                          mailto:coo...@ua...
>
>
>
> -------------------------------------------------------
> 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] Memory size and killing console by Esc

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

On Sat, Feb 07, 2004 at 12:52:31AM +0200, Paul Sokolovsky wrote:

> 1. Could memory size for coLinux be configurable? Current 24Mb or so
> is a joke. Yes, swap can be mounted, but why experience perfomance of
> vmware level? ;-) It would be nice to have memory size configurable in
> XML config, but if it's some time to do, could next release ship with
> at least slightly decent amount, like 64Mb (128Mb better ;-).

The major problem with what you are suggesting, is the limitations 
enforced by Windows' non cached memory allocator. This pool is 
hardcoded to a limit of 256MB and even 128MB on some systems. Allocating 
too much memory from that pool can destabilze Windows.
 
> 2. Could Esc key stop killing console? I currently work that around by
> Alt+27 on numeric keyboard, but it's just pain in the eye.

An FLTK fixable issue, I'll take care of that.
 
>   Ah, and yes - default image provided is pretty bare. It would be
> nice to have at least ftpd and telnetd, and less included - it's not
> always suitable to do apt-get (for example, for people with networking
> problems). I guess, that's request for some kind sole who can
> contribute such an image, coLinux author has other stuff to do ;-)

We will distribue further images in the future.

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

Re: [coLinux-devel] Memory size and killing console by Esc

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

On Saturday 07 February 2004 00:42, Dan Aloni wrote:
> On Sat, Feb 07, 2004 at 12:52:31AM +0200, Paul Sokolovsky wrote:
> >   Ah, and yes - default image provided is pretty bare. It would be
> > nice to have at least ftpd and telnetd, and less included - it's not
> > always suitable to do apt-get (for example, for people with networking
> > problems). I guess, that's request for some kind sole who can
> > contribute such an image, coLinux author has other stuff to do ;-)
>
> We will distribue further images in the future.

Would rather know what has changed between a normal install of deb and this 
image.

Re: [coLinux-devel] Memory size and killing console by Esc

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

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

Hi Dan,

if I understand you right you can'n allocate the memory from within the
kernel space, but what abount a kind of ramdisk (in userspace). Such a ram
disc could  then be used as swap-partition in the linux world. Of course
there is much overhead to transfer memory always from userspace but maybe
this is nevertheless faster then reading/writing to hd?

Thanks and regards,
 Thomas

> On Sat, Feb 07, 2004 at 12:52:31AM +0200, Paul Sokolovsky wrote:
>
>> 1. Could memory size for coLinux be configurable? Current 24Mb or so
>> is a joke. Yes, swap can be mounted, but why experience perfomance of
>> vmware level? ;-) It would be nice to have memory size configurable in
>> XML config, but if it's some time to do, could next release ship with
>> at least slightly decent amount, like 64Mb (128Mb better ;-).
>
> The major problem with what you are suggesting, is the limitations
> enforced by Windows' non cached memory allocator. This pool is
> hardcoded to a limit of 256MB and even 128MB on some systems. Allocating
> too much memory from that pool can destabilze Windows.


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

iD8DBQFAJVf1nwJBIFTVIqwRAk4xAKCOSFT0pMlHjXRUWwe2LC37N1TNewCgxdFo
wjcCXjLZ5HpvQGbZmoIxn0s=
=X7kG
-----END PGP SIGNATURE-----

Re: [coLinux-devel] Memory size and killing console by Esc

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

On Sat, Feb 07, 2004 at 09:26:14PM -0000, Thomas Fritzsche wrote:

> if I understand you right you can'n allocate the memory from within the
> kernel space, but what abount a kind of ramdisk (in userspace). Such a ram
> disc could  then be used as swap-partition in the linux world. Of course
> there is much overhead to transfer memory always from userspace but maybe
> this is nevertheless faster then reading/writing to hd?

While it is already possible to use a Windows file as swap space for 
Linux, future versions of coLinux will use a Windows process to allocate 
virtual userspace memory, without using a file.

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