colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] shell scrip to build cygwin environment

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

On Thu, Feb 12, 2004 at 09:15:54AM -0000, Thomas Fritzsche wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello colinux-hackers,
> 
> I wrote a very simple script to automatically build the cygwin environment
> for colinux. This is not ready yet! The script also builds the dependend
> libs and colinux itself.
> It tries also to build the kernel file vmlinux, but this don't work yet,
> because I still get this strange terminations (reason 7) I wrote about on
> this list. But building the kernel should be an independend step to get
> this running.
> I just have a debian-unstable system to check this out, so it's possible
> that it don't work on other system. The script should try to download the
> necessary packages and patches with wget. So check if this is also
> installed.
> 
> How to use this script:
> 
> 1) create a new empty directory on a volume where you have 1.5 GB space.
> 2) copy cobuild.sh in this directory
> 3) start this script from this directory.... get a coffee (if it runs
> throw you will have the time if not, you will need it ;-))

Very good! I'll test this and send you my remarks. I think I'd also add 
this to the sources.

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

Re: [coLinux-devel] upgrade from Debian 3.0r0 to 3.0r3 with thishelper

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

The other mail I sent is slow is the process to reach the mail-list.  The
attached file is the corrected script with the "dot" swapfile and "dd"
command.

Good luck with Sarge or Sid.

----- Original Message -----
From: "Alejandro R. Sedeno" <as...@MI...>
To: "Ballard Jonathan" <sac...@ho...>
Cc: "coLinux Development" <col...@li...>
Sent: Thursday, February 12, 2004 6:00 PM
Subject: Re: [coLinux-devel] upgrade from Debian 3.0r0 to 3.0r3 with
thishelper


> Just to clear this one up.
>
> Debian 2.2 is Potato.
> Debian 3.0 is Woody. (current Stable)
> Debian 3.1 is Sarge. (current testing)
> Sid is perpetually unstable.
>
> For more information, see: http://www.debian.org/releases/
>
> -Alejandro
>
> On Thu, 2004-02-12 at 19:46, Ballard Jonathan wrote:
> > I attached a printscreen of a script to type in.  It works for me to
> > easily upgrade from potato, Debian-3.0r0, to sarge, Debian-3.0r3.  The
> > sarge version has a few upgrades that should fix a few problems
> > covered in this mail-list.  The script is meant for a fresh install of
> > the Debian-3.0r0 found on the coLinux project download.
> >
> >
>
>
>
> -------------------------------------------------------
> 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] upgrade from Debian 3.0r0 to 3.0r3 with this helper

[Alejandro R. S. <as...@MI...>]

Just to clear this one up.

Debian 2.2 is Potato.
Debian 3.0 is Woody. (current Stable)
Debian 3.1 is Sarge. (current testing)
Sid is perpetually unstable.

For more information, see: http://www.debian.org/releases/

-Alejandro

On Thu, 2004-02-12 at 19:46, Ballard Jonathan wrote:
> I attached a printscreen of a script to type in.  It works for me to
> easily upgrade from potato, Debian-3.0r0, to sarge, Debian-3.0r3.  The
> sarge version has a few upgrades that should fix a few problems
> covered in this mail-list.  The script is meant for a fresh install of
> the Debian-3.0r0 found on the coLinux project download.
>  
>  

Re: [coLinux-devel] Upgraded packages crashing system.

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

Hello Robert,

> I admit that if these devices were compiled out of the kernel then it
> would be more stable but would it ever be possible to not run the linux
> kernel in ring-0?
> I realise that a windows driver running in ring-0 will always be necessary
> but it would be nice if the linux kernel (or any loaded kernel module) did
> not have access to the entire memory space of the machine.

I think that if you want to move further out from the core, then you'll
be looking at an alternative project, such as Bochs;
http://bochs.sourceforge.net/cgi-bin/topper.pl?
name=Bochs+FAQ&url=http://bochs.sourceforge.net/doc/docbook/user/faq.html



--
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/

Re: [coLinux-devel] Upgraded packages crashing system.

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

> Installing the packages:
> procps (offending program: /sbin/sysctl)
> util-linux (offending program: /sbin/hwclock)
>
> Effects:
> They cause the system to completly hault. I started
> from scratch and updated each package one at a time to
> find the problems.

Hi All,

I have been lurking reading this list for a while.
I looked at this project because I wanted a way to run a linux only binary
on a cluster of windows boxes where I work (I was thinking of using Sun
Gridware to distribute the jobs, or Boinc - the SET@Home framework)

I think it is an amzing idea to run linux and windows cooperatively.
Thanks Dan

What worries me though is the stability (and security) of such a system.
I admit there have been few cases of people reporting windows to crash -
but there is this report where it looks like the cooperative multitasking
between windows and linux is not working and there was someone who tried
to start X and got the machine to bluescreen.

I admit that if these devices were compiled out of the kernel then it
would be more stable but would it ever be possible to not run the linux
kernel in ring-0?
I realise that a windows driver running in ring-0 will always be necessary
but it would be nice if the linux kernel (or any loaded kernel module) did
not have access to the entire memory space of the machine.

Could someone explain the architecure of colinux to me in terms of the
different components and what priviledge level they run in?

Also I would like to know how the cooperation between colinux and windows
works. Does colinux yield to windows in the idle loop? the timer
interrupt? any system call
Running a process that can consume 100% CPU in both colinux and windows
simulateneously seems to share.

I did have a look at the code but I have to admit I am not much wiser and
it makes sense to ask rather than guess

Thanks

---
Robert Stonehouse

RE: [Fwd: Re: [coLinux-devel] Cpu Utilization]

[TP D. <out...@di...>]

Please help me to set up coLinux's network settings.

I'm running under Win2K (SP4) and the coLinux binaries 0.5.3-pre2-2.4.24.

If I don't enable Windows Internet Connection Sharing, I can't ping anything
from within coLinux.

If I do enable ICS (by sharing the NIC connected to my modem), I can connect
to the NIC's address, but not out to addresses beyond it. For whatever
reason, when ICS is setup, the coLinux TAP32 adapter gets IP address
192.168.0.1, but no default gateway.

In the short term, I'd like to get coLinux set up so that I can use ssh
rather than the coLinux terminal, and connect out in order to install
whatever I need (???) to get an xserver running in coLinux.

In the longer term, I already use Windows ICS to provide internet
connectivity to a device (ok, a Zaurus) connected via wifi to a wifi adapter
connected to my PC. Ideally, I want to let both the zaurus, over wifi, and
colInux share Windows internet connect - but I have no clue how to do this,
as the MS-Windows ICS setup explicitly set sharing for one particular
connection.

Oh, and ideally, I'd like everything except the address my ISP assign me to
be static, so everything "knows" where everything else is.

So, can anyone step me through setting up ICS for colInux, and then for
setting ICS for both colInix and my wifi adapter?

Thanks,
Tom

[coLinux-devel] Upgraded packages crashing system.

[Origional T. <tra...@ya...>]

Praise:
coLinux, awsome. Granting me capabilities that I
really need.

Problem:
I don't know if this is a direct issue with coLinux,
but was wondering if others have had the same issue.
And if there may be a root cause for what is
happening.

Background:
I'm running WinXP home (hey it came with the machine)
on a stock Toshiba P25-S5093 laptop. (specs available
from Toshiba's website:
http://cdgenp01.csd.toshiba.com/content/product/pdf_files/detailed_specs/satellite_P25-S5093.pdf)

Actions:
When I take the base Debian root image supplied, run:

apt-get update
apt-get upgrade

Installing the packages:
procps (offending program: /sbin/sysctl)
util-linux (offending program: /sbin/hwclock)

Effects:
They cause the system to completly hault. I started
from scratch and updated each package one at a time to
find the problems.

Not crash, just freeze, but slowly. 
The Task Manager stops updating. I can still move some
windows around. But this soon stops as well. The
daemon window can be closed, but that doesn't stop the
net-daemon process. Eventually the system lets out a
death cry in a never-ending loud system beep.
This forces a hard-reset with the Microsoft
popularized "one-finger salute". (Pick a finger)

Conclusion confusion:
In any case, I don't know if this is an issue with my
hardware, my OS, installed software, or a conflict in
compiled code with debian's updates.

I have been sucessful in recompiling a patched kernel
and using that (added some filesystems to mount some
other drives, but really need a stable NTFS driver)

 - Brandon

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

[Fwd: Re: [coLinux-devel] Cpu Utilization]

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

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

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

Hello Vins,

this is already discussed on this list. Dan is working on this problem (or
maybe he has solved this meanwhile).  It is not the colinux-daemon that
causes this problem it's the colinux-console. If you close the console (or
run console-daemon with option -d) you can work with the colinux-daemon
via ssh or telnet without this issue.

Regards,
 Thomas

>
> I've just tried the latest version of Colinux and it works great! I'm using
> it on a Centrino Laptop with Windows XP Pro sp1, and I could boot the
Debian
> Image successfully (didn't tried anything else yet).
>
> I'd like to know if It's normal that colinux-daemon is taking the CPU
utilization
> up to 100%.
>
> Thanks.
>
> Vins
>
>
>
> -------------------------------------------------------
> 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_id56&alloc_id438&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)

iD8DBQFAK6w4nwJBIFTVIqwRAjPsAJ4/rw1H8tPx5tDeWFWyZi01wrhVwwCgodP7
0q7MuQKuIYQZyeF+2Ydr+po=
=tJBL
-----END PGP SIGNATURE-----

[coLinux-devel] Cpu Utilization

[<gla...@fa...>]

I've just tried the latest version of Colinux and it works great! I'm usi=
ng
it on a Centrino Laptop with Windows XP Pro sp1, and I could boot the Deb=
ian
Image successfully (didn't tried anything else yet).

I'd like to know if It's normal that colinux-daemon is taking the CPU uti=
lization
up to 100%.

Thanks.

Vins

[coLinux-devel] Debugging the colinux kernel?

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

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

Hi colinux-hackers,

here a stupid userquestion. I would like debug colinux-kernel but I have
never done kernel debugging before. So I googled around and found this
documentation about kernel debugging:
http://www-106.ibm.com/developerworks/linux/library/l-kdbug/

This report describe the process off debugging with KDB:
http://oss.sgi.com/projects/kdb/

Is this also the recommend way for the colinux-kernel!? Are there any
problem applying the KDB-patch and the colinux-patch together?
I just would like to get a backtrace and other usefull information at a
specific line of code in the kernel. How do I set a breakpoint before
starting the kernel boot.

Thanks a lot and kind regards,
 Thomas



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

iD8DBQFAK2gSnwJBIFTVIqwRAllzAJsG3FZCHUt6dLkP5u+QqvtBNuwaZwCfTI85
q+dAv1yQL8m/IJyTr0VuQKA=
=gRiq
-----END PGP SIGNATURE-----

[coLinux-devel] shell scrip to build cygwin environment

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

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

Hello colinux-hackers,

I wrote a very simple script to automatically build the cygwin environment
for colinux. This is not ready yet! The script also builds the dependend
libs and colinux itself.
It tries also to build the kernel file vmlinux, but this don't work yet,
because I still get this strange terminations (reason 7) I wrote about on
this list. But building the kernel should be an independend step to get
this running.
I just have a debian-unstable system to check this out, so it's possible
that it don't work on other system. The script should try to download the
necessary packages and patches with wget. So check if this is also
installed.

How to use this script:

1) create a new empty directory on a volume where you have 1.5 GB space.
2) copy cobuild.sh in this directory
3) start this script from this directory.... get a coffee (if it runs
throw you will have the time if not, you will need it ;-))


If all runs through you should have a self compiled versions of colinux in
the build subdir of your folder. To run this you can copy the
.exe-files+linux.sys to windows. Currently you can also try to use the
vmlinux file that was build, but on my system I get this "termination",
but I can run successsfully with the vmlinux file from the binary
colinux-file.

Hope this helps someone.

Kind regards,
 Thomas


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

iD8DBQFAK0RKnwJBIFTVIqwRAo/nAKDGU0WmEjeKVMopaS/u5MiDodeJNACgpFEC
2ewyB+1h3rfl7nHZrA+RVlc=
=wTwq
-----END PGP SIGNATURE-----

Re: [coLinux-devel] Is there a way to increase total memory?

[Bart K. <bar...@su...>]

>Is there an easy way to increase total memory?  29MB

On my system, coLinux starts to eat up the whole system memory wich 
after a while slows down both Windows and Linux. Therefore I increased 
the "memory" by adding a swapdrive. Initially this seems to give some 
relief. After a while nearly all system memory is in use again and 
switching from coLinux <> WindowsXP (1.8G + 512M mem) becomes very slow. 
It would be nice to limit the maximum of system resources (memory) cL 
uses, forcing it to use the cL swap-disk instead of the Windows-swap.

I also have a problem with my filesystem: since the cL seems to be 
unable to set the OS-time on boot, I have to do a fsch on the 
filesystems every boot, than remount and give an init3 (or init5). 
Running with ext3 seems not to bother.

The systems runs for about 30 minutes than it dies, without error 
warnings. This has been since the install, so I think I have to await a 
new version and start allover.

To tease the system, I upgraded to SID and installed KDE - all seems to 
be fine, but a bit slow due to the leak of system resources.

Any tips?

Bart

---
Bart Kerver

SURFnet - dep. Middleware Services
phone : +31 (0)30 2 305 373
fax   : +31 (0)30 2 305 329
web   : http://www.surfnet.nl/

Re: [coLinux-devel] Is there a way to increase total memory?

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

And, I forgot the thing about "mkswap" before the ... um... dang it... you
know.

----- Original Message -----
From: "Ballard Jonathan" <sac...@ho...>
To: <col...@li...>
Sent: Wednesday, February 11, 2004 1:39 PM
Subject: Re: [coLinux-devel] Is there a way to increase total memory?


> > > > /dev/cobd1 /mnt/cobd1 ext2 defaults 0 2
>
> That should read "ext3" instead of ext2 if mkfs.ext3 is used.
>
>
> -------------------------------------------------------
> 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:Re[2]: [coLinux-devel] Some problems....

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

Yes - there is a default.xml file where the image name should be
replaced with the new name (if there is a new name - ie, not copying
over the Deb 1Gbyte image file).



----- Original Message -----
>From: "3DoFF" <3D...@ma...>
>To: "Ian Latter" <Ian...@mq...>
>Subject:  Re[2]: [coLinux-devel] Some problems....
>Date: Wed, 11 Feb 2004 12:43:43 +0300
>
> Hello, Ian,
> 
> Wednesday, February 11, 2004, 9:39:40 AM, you wrote:
> 
> IL>   I think you'll find that there's no ISO FS support in the coLinux
> IL> kernel (mentioned a few days ago on the list IIRC) ... you'll not
> IL> get it to mount an ISO FS without support for it.  If you want to
> IL> use that ISO, you'll need to copy the contents onto an ext2/3
> IL> file system and use that instead.
> 
> Shold I change any config file or coLinux will find that partition
> itself?
> 
> -- 
> 3DoFF
> 
> 

--
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/

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

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

In my tests (RH7.2) "cp -R" did maintain attributes and symlinks (I end up
with a correct /dev/*).  And I'm not sure that ISOFS support symlinks?


----- Original Message -----
>From: "Bjorn Sodergren" <sw...@in...>
>To: "'Ian Latter'" <Ian...@mq...>, "'3DoFF'" <3D...@ma...>
>Subject:  RE: Re[2]: [coLinux-devel] Some problems....
>Date: Wed, 11 Feb 2004 18:52:53 -0600
>
> One little minor correction, 
> 
> You would probably want to use -a instead of -R , which will preserve any
> attributes and symlinks
> 
> >      # copy the contents from the old to the new
> >      cd newfs
> >      cp -R ../oldfs/* .
> 
> 
> 
> -------------------------------------------------------
> 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
> 

--
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/

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

[Bjorn S. <sw...@in...>]

One little minor correction, 

You would probably want to use -a instead of -R , which will preserve any
attributes and symlinks

>      # copy the contents from the old to the new
>      cd newfs
>      cp -R ../oldfs/* .

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

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

Hello,

  No, without ISO FS the coLinux kernel won't be able to mount either
an ISO "file" or a CDROM.  You need to copy the contents of the ISO
image into an EXT2 or EXT3 filesystem.

  Ie;  assuming your ISO image is called "mycd.iso", then under some 
other Linux installation perform the following;


     # work in the /tmp dir (make sure you have at least 1.6Gbytes free
     # before you copy in the ISO image).
     cd /tmp

     # mount the old file system
     mkdir oldfs
     mount -o loop ./mycd.iso ./oldfs

     # make the new file system (I only have ext2 under RH7.2)
     dd if=/dev/zero of=./myfs.ext2 bs=1M count=800
     mkfs.ext2 -F ./myfs.ext2 

     # mount the new file system
     mkdir newfs
     mount -o loop ./myfs.ext2 ./newfs

     # copy the contents from the old to the new
     cd newfs
     cp -R ../oldfs/* .

     # sync and unmount the filesystems
     cd ..
     sync
     umount ./newfs
     umount ./oldfs


  The file "myfs.ext2" in the /tmp directory should then work as an
ext2 file system under the coLinux kernel.  If you have a newer 
OS to build it from, then make it an ext3 file system (replace the ext2
bits with ext3 in the above).

  Alternatively, wait until a newer version of the binary coLinux
release comes out, supporting ISO FS natively.


Hope that helps,




----- Original Message -----
>From: "3DoFF" <3D...@ma...>
>To: "Ian Latter" <Ian...@mq...>, <col...@li...>
>Subject:  Re[2]: [coLinux-devel] Some problems....
>Date: Wed, 11 Feb 2004 23:57:13 +0300
>
> Hello, Ian,
> 
> Wednesday, February 11, 2004, 9:39:40 AM, you wrote:
> 
> IL>   I think you'll find that there's no ISO FS support in the coLinux
> IL> kernel (mentioned a few days ago on the list IIRC) ... you'll not
> IL> get it to mount an ISO FS without support for it.  If you want to
> IL> use that ISO, you'll need to copy the contents onto an ext2/3
> IL> file system and use that instead.
> 
> Burnt CD-Rom with this image is a right way to go too?
> 
> -- 
> 3DoFF
> 
> 

--
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/

Re: [coLinux-devel] Is there a way to increase total memory?

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

On Wed, Feb 11, 2004 at 07:19:36PM +0200, Paul Sokolovsky wrote:

>     And still some brave souls would prefer to have more real memory
> despite any would-be crashes. Dan, could you find some time to
> implement xml config element to set that? There's no need to put it by
> default, just implement and describe somewhere ;-)

Maybe I'll add that to the next version.

Or prehaps someone can save me time and send me a patch that adds this 
and I will apply.

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

[coLinux-devel] Report to Recipient(s)

[SofExtR4/<So...@So...>]

Incident Information:-

Originator: col...@li...
Recipients: "coLinux Development" <col...@li...>
Subject:    [coLinux-devel] Empty image files attached!

Generic Alert: Exception was 'Corrupt File' scanning attachment
'4gb.empty.image.tar.bz2'

[coLinux-devel] Empty image files attached!

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

SGksDQoNCkF0dGFjaGVkIHRvIHRoaXMgbWFpbCBhcmUgZW1wdHkgaW1hZ2UgZmlsZXMuIEFueSBv
ZiB0aGVzZSBmaWxlcw0Kd2hlbiBleHRyYWN0ZWQgY291bGQgYmUgdXNlZCB0byBjcmVhdGUgbW9y
ZSBmaWxlIHN5c3RlbXMgb3INCnN3YXAgZmlsZXMuDQoNCkFzIGhhcyBiZWVuIGRlc2NyaWJlZCBw
cmV2aW91c2x5IHlvdSB3b3VsZCBuZWVkIHRvIHJlZmVyZW5jZQ0KdGhlIGltYWdlIGZpbGUgaW4g
eW91ciB4bWwgY29uZmlnIGZpbGUuIEFmdGVyIGJvb3RpbmcgaW50byBjb0xpbnV4DQp5b3UgY2Fu
IHRoZW4gZG8sIGVnLiANCm1rZnMuZXh0MiAvZGV2L2NvYmQzDQpta2ZzLmV4dDMgL2Rldi9jb2Jk
MSAgDQpta3N3YXAgL2Rldi9jb2JkMg0KLi5ldGMuDQoNClRoZXNlIGZpbGVzIHdlcmUgY3JlYXRl
ZCB1c2luZyB0aGUgZm9sbG93aW5nIGNvbW1hbmQ6DQojIGRkIGlmPS9kZXYvemVybyBvZj0/Py5l
bXB0eS5pbWFnZSBicz0xMDI0IGNvdW50PT8/Pw0KV2l0aCBhIGNvdW50IG9mIDI1NjAwMCwgNTEy
MDAwLCAxMDI0MDAwIGV0Yy4NCmFuZCB0aGVuIGNvbXByZXNzZWQgd2l0aCB0YXIuIChidHcsIEkg
d291bGQgc3VnZ2VzdCBpZiB5b3UgYXJlDQpuZXcgdG8gTGludXggdGhhdCB5b3UgZ2V0IGhvbGQg
b2YgV2luUkFSIGFzIGl0IHN1cHBvcnRzDQptb3N0ICpuaXggYXJjaGl2ZSBmb3JtYXRzKS4NCg0K
Q2hlZXJzLA0KDQpTZWFuLg==

Re: [coLinux-devel] Is there a way to increase total memory?

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

> > > /dev/cobd1 /mnt/cobd1 ext2 defaults 0 2

That should read "ext3" instead of ext2 if mkfs.ext3 is used.

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

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

Hello, Ian,

Wednesday, February 11, 2004, 9:39:40 AM, you wrote:

IL>   I think you'll find that there's no ISO FS support in the coLinux
IL> kernel (mentioned a few days ago on the list IIRC) ... you'll not
IL> get it to mount an ISO FS without support for it.  If you want to
IL> use that ISO, you'll need to copy the contents onto an ext2/3
IL> file system and use that instead.

Burnt CD-Rom with this image is a right way to go too?

-- 
3DoFF

Re: [coLinux-devel] Is there a way to increase total memory?

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

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIk1pY2hhZWwgSGFsbGVyIiA8
aGFsbGVyX21qQGhvdG1haWwuY29tPg0KVG86IDxlcGFjQGtvcmlnYW4ubmV0PjsgPHNhY3JhbWVu
dG9raWRkQHlhaG9vLmNvbT4NCkNjOiA8Y29saW51eC1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5u
ZXQ+DQpTZW50OiBXZWRuZXNkYXksIEZlYnJ1YXJ5IDExLCAyMDA0IDc6MzggUE0NClN1YmplY3Q6
IFJlOiBbY29MaW51eC1kZXZlbF0gSXMgdGhlcmUgYSB3YXkgdG8gaW5jcmVhc2UgdG90YWwgbWVt
b3J5Pw0KDQoNCnwgRG9pbmcgaXQgdGhhdCB3YXkgZ2l2ZXMgdGhlIGZvbGxvd2luZyBlcnJvcjoN
CnwgDQp8IG1rc3dhcDogZXJyb3I6IHN3YXAgYXJlYSBuZWVkcyB0byBiZSBhdCBsZWFzdCA0MGtC
DQp8IFVzYWdlOiBta3N3YXAgWy1jXSBbLXYwfC12MV0gWy1wUEFHRVNaXSAvZGV2L25hbWUgW2Js
b2Nrc10NCg0KVGhlIGltYWdlIGZpbGUgdGhhdCB3aWxsIGhvbGQgdGhlIHN3YXAgZmlsZSB3b3Vs
ZCBuZWVkIHRvIGFscmVhZHkgZXhpc3QgDQppbiB0aGUgV2luZG93cyBmaWxlIHN5c3RlbSBvciB0
aGUgYmxvY2sgZGV2aWNlIHJlZmVyZW5jZWQgd291bGQgbmVlZCANCnRvIGJlIHBvaW50ZWQgdG8g
YW4gYWN0dWFsIGxpbnV4IHN3YXAgcGFydGl0aW9uIGZyb20gdGhlIHhtbCBmaWxlLg0KDQp8IA0K
fCANCnwgYW5kIEkndmUgYmVlbiBzcG9pbGVkIHdpdGggZ2VudG9vIGxpbnV4Li4uIGluIG9yZGVy
IHRvIG1ha2UgYSBzd2FwIGFsbCBJIA0KfCBub3JtYWxseSBuZWVkIHRvIHR5cGUgaXMgJ21rc3dh
cCAvZGV2L2hkeHgnDQoNCkluIGdlbnRvbyBMaW51eCwgY29MaW51eCwgb3IgYW55IG90aGVyIExp
bnV4IHlvdSBuZWVkIHRvIGNyZWF0ZSBzb21ld2hlcmUNCmZvciB0aGUgc3dhcCBmaWxlIHRvIGJl
IHN0b3JlZCwgd2hldGhlciBpbiBhIGZpbGUgb3IgYSBwYXJ0aXRpb24uLi4uIFRoaXMgbWVhbnMN
CnlvdSB3b3VsZCBhbHJlYWR5IGhhdmUgY3JlYXRlZCB5b3VyIHN3YXAgcGFydGl0aW9uIGFzIGlu
IHlvdXIgYWJvdmUgY29tbWVudC4NCg0KfCANCnwgDQp8ID5Gcm9tOiBlUEFjIDxlcGFjQGtvcmln
YW4ubmV0Pg0KfCA+VG86IEpvbmF0aGFuIEJhbGxhcmQgPHNhY3JhbWVudG9raWRkQHlhaG9vLmNv
bT4NCnwgPkNDOiBNaWNoYWVsIEhhbGxlciA8aGFsbGVyX21qQGhvdG1haWwuY29tPiwgICAgICAg
IGNvTGludXggRGV2ZWxvcG1lbnQgDQp8ID48Y29saW51eC1kZXZlbEBsaXN0cy5zb3VyY2Vmb3Jn
ZS5uZXQ+DQp8ID5TdWJqZWN0OiBSZTogW2NvTGludXgtZGV2ZWxdIElzIHRoZXJlIGEgd2F5IHRv
IGluY3JlYXNlIHRvdGFsIG1lbW9yeT8NCnwgPkRhdGU6IFdlZCwgMTEgRmViIDIwMDQgMTE6MjI6
NTQgLTA4MDAgKFBTVCkNCnwgPg0KfCA+ID4gPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0i
VVRGLTgiPz4NCnwgPiA+IDxjb2xpbnV4Pg0KfCA+ID4gICAgIDxibG9ja19kZXZpY2UgaW5kZXg9
IjAiDQp8ID4gPiBwYXRoPSJcRG9zRGV2aWNlc1xjOlxjb0xpbnV4XERlYmlhbi0zLjByMC5leHQz
LjFnYiINCnwgPiA+IGVuYWJsZWQ9InRydWUiPg0KfCA+ID4gICAgIDwvYmxvY2tfZGV2aWNlPg0K
fCA+ID4gICAgIDxibG9ja19kZXZpY2UgaW5kZXg9IjEiDQp8ID4gPiBwYXRoPSJcRG9zRGV2aWNl
c1xjOlxjb0xpbnV4XGNvYmQuMSINCnwgPiA+IGVuYWJsZWQ9InRydWUiPg0KfCA+ID4gICAgIDwv
YmxvY2tfZGV2aWNlPg0KfCA+ID4gICAgIDxib290cGFyYW1zPnJvb3Q9L2Rldi9jb2JkMDwvYm9v
dHBhcmFtcz4NCnwgPiA+ICAgICA8aW1hZ2UgcGF0aD0idm1saW51eCI+PC9pbWFnZT4NCnwgPiA+
IDwvY29saW51eD4NCnwgPg0KfCA+dGhhdCBpcyBnb29kLg0KfCA+DQp8ID4gPg0KfCA+ID4gKiBz
dGFydHVwIGNvTGludXgtZGFlbW9uIHdpdGggdGhlIG5ldyBjb25maWcgIFsNCnwgPiA+ICJjb2xp
bnV4LWRhZW1vbiAtZCAtYw0KfCA+ID4gY29saW51eC54bWwiIF0NCnwgPiA+ICogbG9naW4gYXMg
cm9vdA0KfCA+DQp8ID50aGF0IGlzIG5vdCBuZWNlc3Nhcnk6DQp8ID4NCnwgPiA+ICogJCBta2Rp
ciAvbW50L2NvYmQxDQp8ID4gPiAqICQgbWtmcy5leHQzIC9kZXYvY29iZDENCnwgPiA+ICogJCBt
b3VudCAvZGV2L2NvYmQxIC9tbnQvY29iZDENCnwgPiA+ICogJCBjZCAvbW50L2NvYmQxDQp8ID4g
PiAqICQgZGQgaWY9L2Rldi96ZXJvIG9mPXN3YXBmaWxlIGJzPTEwMjQgY291bnQ9MjYyMTQ0DQp8
ID4gPiAgIFsgMTAyNCpicyoyNTY9MjU2TUINCnwgPiA+IHN3YXBmaWxlIF0NCnwgPiA+ICogZWRp
dCAvZXRjL2ZzdGFiIGFuZCBhZGQgZW50cmllcyBmb3IgY29iZDEgYW5kIHRoZQ0KfCA+ID4gc3dh
cGZpbGUgaW4gbW91bnQgb3JkZXIsDQp8ID4gPiBsaWtlOg0KfCA+ID4NCnwgPiA+IC9kZXYvY29i
ZDAgLyBleHQyIGRlZmF1bHRzIDAgMQ0KfCA+ID4gcHJvYyAvcHJvYyBwcm9jIGRlZmF1bHRzIDAg
MA0KfCA+ID4gL2Rldi9jb2JkMSAvbW50L2NvYmQxIGV4dDIgZGVmYXVsdHMgMCAyDQp8ID4gPiAv
bW50L2NvYmQxL3N3YXBmaWxlIG5vbmUgc3dhcCBkZWZhdWx0cyAwIDANCnwgPiA+DQp8ID4gPiAq
ICQgbW91bnQgLWENCnwgPiA+ICogJCBzd2Fwb24gLWENCnwgPiA+DQp8ID4NCnwgPnRoYXQgb24g
dGhlIG90aGVyIGhhbmQsIGlzIGV4dHJhIHdvcmsuDQp8ID4NCnwgPndoeSBub3QgdXNlIHRoZSAi
cmF3IiBjb2JkIGZvciBzd2FwID8NCnwgPg0KfCA+eW91IHNob3VsZCBiZSBhYmxlIHRvIGRvOg0K
fCA+DQp8ID5ta3N3YXAgL2Rldi9jb2JkMQ0KfCA+YW5kIGFkZA0KfCA+LS0tODwtLS04PC0tLQ0K
fCA+L2Rldi9jb2JkMSBub25lIHN3YXAgZGVmYXVsdHMNCnwgPi0tLTg8LS0tODwtLS0NCnwgPnRv
IHlvdXIgZnN0YWIgYW5kIGhhdmUgdGhlIHNhbWUgcmVzdWx0LCB3aXRob3V0IHVzaW5nIGFuIGV4
dHJhDQp8ID5tb3VudHBvaW50Li4uDQp8ID50aGVuIHRoZSBzYW1lIHN3YXBvbiAtYSAuLiB0aGUg
ZnN0YWIsIHRoZSBuZXh0IHRpbWUgeW91IGJvb3Qgc2hvdWxkIHRha2UNCnwgPmNhcmUgb2YgZG9p
bmcgdGhlIHN3YXBvbiBmb3IgeW91Li4gOm8pDQp8ID4NCnwgPkpvaw0KfCA+DQp8ID4NCnwgPi0t
LQ0KfCA+Tm90aGluZyBpcyBmb29scHJvb2YgdG8gYSBzdWZmaWNpZW50bHkgdGFsZW50ZWQgZm9v
bC4uLg0KfCA+ICAgb28NCnwgPiwoLi4pXA0KfCA+ICAgfn4NCnwgDQp8IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQp8IEZp
bmQgZ3JlYXQgbG9jYWwgaGlnaC1zcGVlZCBJbnRlcm5ldCBhY2Nlc3MgdmFsdWUgYXQgdGhlIE1T
TiBIaWdoLVNwZWVkIA0KfCBNYXJrZXRwbGFjZS4gaHR0cDovL2NsaWNrLmF0ZG10LmNvbS9BVkUv
Z28vb25tMDAyMDAzNjBhdmUvZGlyZWN0LzAxLw0KfCANCnwgDQp8IA0KfCAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQp8IFNGLk5ldCBpcyBz
cG9uc29yZWQgYnk6IFNwZWVkIFN0YXJ0IFlvdXIgTGludXggQXBwcyBOb3cuDQp8IEJ1aWxkIGFu
ZCBkZXBsb3kgYXBwcyAmIFdlYiBzZXJ2aWNlcyBmb3IgTGludXggd2l0aA0KfCBhIGZyZWUgRFZE
IHNvZnR3YXJlIGtpdCBmcm9tIElCTS4gQ2xpY2sgTm93IQ0KfCBodHRwOi8vYWRzLm9zZG4uY29t
Lz9hZF9pZD0xMzU2JmFsbG9jX2lkPTM0Mzgmb3A9Y2xpY2sNCnwgX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnwgY29MaW51eC1kZXZlbCBtYWlsaW5nIGxp
c3QNCnwgY29MaW51eC1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCnwgaHR0cHM6Ly9saXN0
cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vY29saW51eC1kZXZlbA==

Re: [coLinux-devel] Is there a way to increase total memory?

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

I documented making a swap file in a previous email and it worked fine. In
addition, I just made a 1gb swap file by mounting a copy of the 1gb debian
image as /dev/cobd1, booting into cL, doing mkswap /dev/cobd1, and swapon
/dev/cobd1. Seems to work fine from this end.
----- Original Message ----- 
From: "Ballard Jonathan" <sac...@ho...>
To: "ePAc" <ep...@ko...>
Cc: "Michael Haller" <hal...@ho...>; "coLinux Development"
<col...@li...>
Sent: Wednesday, February 11, 2004 2:24 PM
Subject: Re: [coLinux-devel] Is there a way to increase total memory?


> > why not use the "raw" cobd for swap ?
>
> I have not fully tested a 1GB swap device (file or block device) with only
> 26MB of kernel memory.  Let us know if it works.  One page of swap of
memory
> allocated 2 bytes of kernel memory.
>
>
>
> -------------------------------------------------------
> 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] Is there a way to increase total memory?

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

> why not use the "raw" cobd for swap ?

I have not fully tested a 1GB swap device (file or block device) with only
26MB of kernel memory.  Let us know if it works.  One page of swap of memory
allocated 2 bytes of kernel memory.