colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] Initrd support?

[Eric A. <ea...@ma...>]

initrd= doesn't work for coLinux because it can't find the file. This is
fine, as I should be able to simulate the same result by using
root=/dev/cobd0 init=/linuxrc, which works. The problem comes when the
pivot_root call is made..

EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic: Attempted to kill init!
 daemon: monitor terminated, reason 3
switch_message: freed message a047010 (2 to 4)
daemon: module disconnected: console
colinux: shutting down
daemon: daemon cleanup
Removing kernel driver
Stopping driver service
Removing driver service

Unfortunately, this also makes the Console go completely blank on me, so
it's hard to see if there were any other problems.

If anyone could give some assistance, that would be great.

-- 
Eric Andresen
Junior Systems Administrator
Mars Space Flight Facility
Arizona State University
ea...@ma...

On Wed, 2004-03-03 at 05:49, ch...@to... wrote:
> see initrd.txt in a 2.4.24 kernel source documentation.
> the newer way of specifying initrd with the explicit change_root may work.
> you will need to compile your own kernel at this time as the coLinux
> binary kernel does not support initrd. Just apply the coLinux patch and
> make shure you have all the initrd related options selected in .configure
> .
> 
> I was experimenting with an initrd based setup that I was using but after
> eleminating the stuff I didn't need for coLinux mode from linuxrc I
> realized that I could just skip the initrd and boot directly to the root
> image.
> 
> initrd supplying hardware modules should not be necessary because the
> "hardware enviroment" is fixed and taken care of by the coLinux patch.
> the initrd mounting loops may also be unnecessary because you could just
> set that all up in the coLinux config and fstab.
> 
> so It may be worth considering do you really need the initrd.
> 
> chris
> 
> > Hi,
> >
> > I'm trying to essentially port my current UML configuration over to a
> > similar coLinux setup, but the first obvious problem that comes to mind
> > is that there does not appear to be a way to specify initrds.
> >
> > Am I mistaken, or is this so? This is a requirement for my setup,
> > because the initrd creates a number of tmpfs filesystems for /etc, /var,
> > and /tmp (for specific reasons outside of the realm of this topic).
> >
> > Also, regarding the memory restrictions: is there no other possible way
> > to allocate physical ram? I find it hard to think that no Windows
> > application surpasses this memory usage (VMware? Most games?); is there
> > a chance that one of these alternate memory allocation sources could be
> > used, thus allowing more realistic physical memory usages?
> >
> > Thanks,
> > -- Eric Andresen
> >    Junior Systems Administrator
> >    Mars Space Flight Facility
> >    Arizona State University
> >    ea...@ma...
> >

Re: [coLinux-devel] how to compile the kernel?

[Gregor M. <mi...@ra...>]

Hi,

> All seemed to work fine for me.

Thank's. Now it works fine for me, too.

smbfs running! That's fun. :-)

This is what I've actually done:

1) $ cd /usr/src
2) unpack the source tarball of coLinux
3) unpack the Linux kernel tarball
    (version 2.4.24, can be obtained from www.kernel.org)
4) Make sure that the directory of the Linux kernel is named 'linux'.
    $ mv kernel-source-2.4.24 linux
5) $ cd linux
6) ~/colinux-0.5.3/linux# patch -p1 < ../colinux-xxx/patch/linux

7)
The coLinux package is supplied with a premaid Linux kernel
configuration file. Copy it to your Linux tree:

    ~/colinux-0.5.3/linux# cp ../colinux-xxx/conf/linux-config .config

8)
And then, to build vmlinux:
     ~/colinux-0.5.3/linux# make oldconfig
9)
Make your changes to the config
                          $ make xconfig
     ~/colinux-0.5.3/linux# make dep
     ~/colinux-0.5.3/linux# make vmlinux
10)                      $ make modules
11)                      $ make modules_install

12) Copy the new vmlinux to C:/coLinux/vmlinux
13) Reboot

--Gregor

[coLinux-devel] Some file creation utilities

[Daniel S. <dan...@au...>]

I have created some utilities for creating large files under windows for
file systems. You can get them at
http://www.geocities.com/dan_slater/colinux/utils.zip

In this zip file you will find 3 executables and sources. The utilities
are:

mkFile.exe - use this to easily create a large file for your
file-system. If you have an ntfs 5.0 partition ( the default for Windows
2000 and later ). Then be sure to use the -s option to create a sparse
file. When you create a sparse file, windows only allocates disk space
for the non-zero data. For example:

mkFile -s root_fs 10G

This will create a 10GB empty file named root_fs. If you look at the
file with explorer properties or use the spsize utility, you will see
that the while the file is 10 GB, the allocated disk space is 0 bytes.

spsize - use this to check the size of a sparse file - it will report
both the file size and the disk space used

mkSparse - run this on an existing file to convert it to a sparse file -
note: there is a lot of room for improvement for this one. Also, be
aware this one modifies your file so it has the potential to destroy
your data if I got something wrong.

Still to do: would be nice to have a linux utility that walks the free
space on your filesystem and zeros out any non-zero clusters before
running mkSparse.

[coLinux-devel] New Website

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

I've created a website where I'm going to keep my experimental images.  Please go to:

http://killashandra.magenet.com/~s0be/

(temporary location, will become colinux.drunkencodepoets.com)

Pat Erley

RE: [coLinux-devel] how to compile the kernel?

[Daniel R. S. <dan...@ya...>]

Did you remember to copy the linux-config file to your .config file and run
make oldconfig? I downloaded the kernel-source of 2.4.24 directly from
www.kernel.org , applied the patch, copied linux-config to .config, executed
make oldconfig. Then ran make xconfig to add some other filesystem drivers
as modules. Then ran make dep && make vmlinux && make modules && make
modules_install


All seemed to work fine for me.

Dan


-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Gregor
Mitsch
Sent: Wednesday, March 03, 2004 1:00 PM
To: col...@li...
Subject: Re: [coLinux-devel] how to compile the kernel?

Hi,

> You need to compile your own kernel. To get started look at
> doc/building in the coLinux tarball.

I followed the instructions from doc/building. Applying the patch 
succeeded. But $ make vmlinux
fails with the following error message from cooperative.c:

[...]
cooperative.c:16: parse error before `*'
cooperative.c:16: warning: type defaults to `int' in declaration of 
`co_passage_page'
cooperative.c:16: warning: data definition has no type or storage class
cooperative.c:27: `CO_BOOTPARAM_STRING_LENGTH' undeclared here (not in a 
function)
cooperative.c:29: parse error before `*'
cooperative.c:30: warning: function declaration isn't a prototype
[...]

You can see the whole output below.

I downloaded the kernel-source of 2.4.24 via apt-get and used gcc 
version 2.95.4 to compile it.

Any hints?

--Gregor


----------------


(Z)root@colinux:/usr/src/kernel-source-2.4.24> make vmlinux
. scripts/mkversion > .tmpversion
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.24/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 
-pipe -mpreferred-stack-boundary=2 -march=i386  -DUTS_MACHINE='"i386"' 
-DKBUILD_BASENAME=version -c -o init/version.o init/version.c
make CFLAGS="-D__KERNEL__ -I/usr/src/kernel-source-2.4.24/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 
-pipe -mpreferred-stack-boundary=2 -march=i386 " -C  kernel
make[1]: Entering directory `/usr/src/kernel-source-2.4.24/kernel'
make all_targets
make[2]: Entering directory `/usr/src/kernel-source-2.4.24/kernel'
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.24/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 
-pipe -mpreferred-stack-boundary=2 -march=i386   -nostdinc -iwithprefix 
include -DKBUILD_BASENAME=cooperative  -c -o cooperative.o cooperative.c
cooperative.c:16: parse error before `*'
cooperative.c:16: warning: type defaults to `int' in declaration of 
`co_passage_page'
cooperative.c:16: warning: data definition has no type or storage class
cooperative.c:27: `CO_BOOTPARAM_STRING_LENGTH' undeclared here (not in a 
function)
cooperative.c:29: parse error before `*'
cooperative.c:30: warning: function declaration isn't a prototype
cooperative.c: In function `colinux_start_c':
cooperative.c:32: `passage_page' undeclared (first use in this function)
cooperative.c:32: (Each undeclared identifier is reported only once
cooperative.c:32: for each function it appears in.)
cooperative.c:34: request for member `params' in something not a 
structure or union
cooperative.c:35: request for member `params' in something not a 
structure or union
cooperative.c:36: request for member `params' in something not a 
structure or union
cooperative.c:37: request for member `params' in something not a 
structure or union
cooperative.c:39: request for member `params' in something not a 
structure or union
cooperative.c:39: request for member `params' in something not a 
structure or union
cooperative.c: At top level:
cooperative.c:50: parse error before `*'
cooperative.c:51: warning: return-type defaults to `int'
cooperative.c: In function `co_send_message_save':
cooperative.c:53: request for member `operation' in something not a 
structure or union
cooperative.c:53: `CO_OPERATION_MESSAGE_TO_MONITOR' undeclared (first 
use in this function)
cooperative.c:54: request for member `params' in something not a 
structure or union
cooperative.c:55: `co_message_t' undeclared (first use in this function)
cooperative.c:55: parse error before `)'
cooperative.c:55: request for member `params' in something not a 
structure or union
cooperative.c:56: warning: control reaches end of non-void function
cooperative.c: In function `co_send_message_restore':
cooperative.c:60: warning: implicit declaration of function 
`co_switch_wrapper'
cooperative.c: At top level:
cooperative.c:64: parse error before `*'
cooperative.c:65: warning: function declaration isn't a prototype
cooperative.c: In function `co_send_message_s':
cooperative.c:66: `co_message_t' undeclared (first use in this function)
cooperative.c:66: `message' undeclared (first use in this function)
cooperative.c:67: `params' undeclared (first use in this function)
cooperative.c:67: warning: statement with no effect
cooperative.c:68: parse error before `unsigned'
cooperative.c:70: `flags' undeclared (first use in this function)
cooperative.c:71: request for member `operation' in something not a 
structure or union
cooperative.c:71: `CO_OPERATION_MESSAGE_TO_MONITOR' undeclared (first 
use in this function)
cooperative.c:72: request for member `params' in something not a 
structure or union
cooperative.c:73: parse error before `)'
cooperative.c:73: request for member `params' in something not a 
structure or union
cooperative.c:75: `data' undeclared (first use in this function)
cooperative.c: At top level:
cooperative.c:82: parse error before `from'
cooperative.c:88: warning: function declaration isn't a prototype
cooperative.c: In function `co_send_message':
cooperative.c:89: `co_message_t' undeclared (first use in this function)
cooperative.c:89: parse error before `params'
cooperative.c:91: `params' undeclared (first use in this function)
cooperative.c:91: `from' undeclared (first use in this function)
cooperative.c:92: `to' undeclared (first use in this function)
cooperative.c:93: `priority' undeclared (first use in this function)
cooperative.c:94: `type' undeclared (first use in this function)
cooperative.c:95: `size' undeclared (first use in this function)
cooperative.c:97: `data' undeclared (first use in this function)
cooperative.c: At top level:
cooperative.c:100: parse error before `*'
cooperative.c:101: warning: function declaration isn't a prototype
cooperative.c: In function `co_receive_message':
cooperative.c:103: parse error before `co_message_t'
cooperative.c:103: warning: no semicolon at end of struct or union
cooperative.c:104: `co_linux_message_t' undeclared (first use in this 
function)
cooperative.c: At top level:
cooperative.c:105: warning: type defaults to `int' in declaration of 
`linux_message'
cooperative.c:105: warning: data definition has no type or storage class
cooperative.c:107: warning: type defaults to `int' in declaration of 
`linux_message'
cooperative.c:107: conflicting types for `linux_message'
cooperative.c:105: previous declaration of `linux_message'
cooperative.c:107: `message' undeclared here (not in a function)
cooperative.c:107: warning: data definition has no type or storage class
cooperative.c:109: parse error before `&'
cooperative.c:109: warning: type defaults to `int' in declaration of 
`co_handle_device_interrupt'
cooperative.c:109: warning: function declaration isn't a prototype
cooperative.c:109: warning: data definition has no type or storage class
cooperative.c: In function `co_callback':
cooperative.c:114: request for member `operation' in something not a 
structure or union
cooperative.c:114: `CO_OPERATION_MESSAGE_FROM_MONITOR' undeclared (first 
use in this function)
cooperative.c:115: `co_message_t' undeclared (first use in this function)
cooperative.c:115: parse error before `)'
cooperative.c:115: request for member `params' in something not a 
structure or union
cooperative.c:116: request for member `params' in something not a 
structure or union
cooperative.c:120: request for member `operation' in something not a 
structure or union
cooperative.c: In function `co_idle_processor':
cooperative.c:130: request for member `operation' in something not a 
structure or union
cooperative.c:130: `CO_OPERATION_IDLE' undeclared (first use in this 
function)
cooperative.c: In function `co_printk':
cooperative.c:138: `CO_MODULE_LINUX' undeclared (first use in this function)
cooperative.c:139: `CO_MODULE_PRINTK' undeclared (first use in this 
function)
cooperative.c:140: `CO_PRIORITY_DISCARDABLE' undeclared (first use in 
this function)
cooperative.c:141: `CO_MESSAGE_TYPE_STRING' undeclared (first use in 
this function)
cooperative.c: In function `co_debug_line':
cooperative.c:157: request for member `operation' in something not a 
structure or union
cooperative.c:157: `CO_OPERATION_DEBUG_LINE' undeclared (first use in 
this function)
cooperative.c:158: request for member `params' in something not a 
structure or union
cooperative.c: In function `co_trace_ent_name':
cooperative.c:179: warning: unsigned int format, pointer arg (arg 6)
cooperative.c: In function `co_trace_ent':
cooperative.c:202: warning: unsigned int format, pointer arg (arg 5)
cooperative.c: At top level:
cooperative.c:209: parse error before `do'
cooperative.c:212: `flags' used prior to declaration
cooperative.c:215: parse error before `do'
cooperative.c:216: parse error before `='
cooperative.c:217: parse error before `sizeof'
cooperative.c:217: warning: type defaults to `int' in declaration of 
`vsnprintf'
cooperative.c:217: warning: function declaration isn't a prototype
cooperative.c:217: warning: type defaults to `int' in declaration of `fmt'
cooperative.c:217: warning: type defaults to `int' in declaration of `args'
cooperative.c:217: conflicting types for `args'
cooperative.c:213: previous declaration of `args'
cooperative.c:217: parse error before `)'
cooperative.c:218: parse error before `void'
cooperative.c:219: warning: type defaults to `int' in declaration of 
`co_debug_line'
cooperative.c:219: warning: parameter names (without types) in function 
declaration
cooperative.c:219: conflicting types for `co_debug_line'
cooperative.c:147: previous declaration of `co_debug_line'
cooperative.c:219: warning: data definition has no type or storage class
cooperative.c:220: parse error before `__volatile__'
cooperative.c:228: parse error before `->'
cooperative.c:230: warning: type defaults to `int' in declaration of 
`co_switch_wrapper'
cooperative.c:230: warning: function declaration isn't a prototype
cooperative.c:230: warning: data definition has no type or storage class
cooperative.c:231: parse error before `__volatile__'
cooperative.c: In function `co_get_host_time':
cooperative.c:240: request for member `operation' in something not a 
structure or union
cooperative.c:240: `CO_OPERATION_GET_TIME' undeclared (first use in this 
function)
cooperative.c:242: request for member `params' in something not a 
structure or union
cooperative.c:237: warning: `time' might be used uninitialized in this 
function
make[2]: *** [cooperative.o] Error 1
make[2]: Leaving directory `/usr/src/kernel-source-2.4.24/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/kernel-source-2.4.24/kernel'
make: *** [_dir_kernel] Error 2
(Z)root@colinux:/usr/src/kernel-source-2.4.24>



-------------------------------------------------------
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] how to compile the kernel?

[Gregor M. <mi...@ra...>]

Hi,

> You need to compile your own kernel. To get started look at
> doc/building in the coLinux tarball.

I followed the instructions from doc/building. Applying the patch 
succeeded. But $ make vmlinux
fails with the following error message from cooperative.c:

[...]
cooperative.c:16: parse error before `*'
cooperative.c:16: warning: type defaults to `int' in declaration of 
`co_passage_page'
cooperative.c:16: warning: data definition has no type or storage class
cooperative.c:27: `CO_BOOTPARAM_STRING_LENGTH' undeclared here (not in a 
function)
cooperative.c:29: parse error before `*'
cooperative.c:30: warning: function declaration isn't a prototype
[...]

You can see the whole output below.

I downloaded the kernel-source of 2.4.24 via apt-get and used gcc 
version 2.95.4 to compile it.

Any hints?

--Gregor


----------------


(Z)root@colinux:/usr/src/kernel-source-2.4.24> make vmlinux
. scripts/mkversion > .tmpversion
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.24/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 
-pipe -mpreferred-stack-boundary=2 -march=i386  -DUTS_MACHINE='"i386"' 
-DKBUILD_BASENAME=version -c -o init/version.o init/version.c
make CFLAGS="-D__KERNEL__ -I/usr/src/kernel-source-2.4.24/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 
-pipe -mpreferred-stack-boundary=2 -march=i386 " -C  kernel
make[1]: Entering directory `/usr/src/kernel-source-2.4.24/kernel'
make all_targets
make[2]: Entering directory `/usr/src/kernel-source-2.4.24/kernel'
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.24/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 
-pipe -mpreferred-stack-boundary=2 -march=i386   -nostdinc -iwithprefix 
include -DKBUILD_BASENAME=cooperative  -c -o cooperative.o cooperative.c
cooperative.c:16: parse error before `*'
cooperative.c:16: warning: type defaults to `int' in declaration of 
`co_passage_page'
cooperative.c:16: warning: data definition has no type or storage class
cooperative.c:27: `CO_BOOTPARAM_STRING_LENGTH' undeclared here (not in a 
function)
cooperative.c:29: parse error before `*'
cooperative.c:30: warning: function declaration isn't a prototype
cooperative.c: In function `colinux_start_c':
cooperative.c:32: `passage_page' undeclared (first use in this function)
cooperative.c:32: (Each undeclared identifier is reported only once
cooperative.c:32: for each function it appears in.)
cooperative.c:34: request for member `params' in something not a 
structure or union
cooperative.c:35: request for member `params' in something not a 
structure or union
cooperative.c:36: request for member `params' in something not a 
structure or union
cooperative.c:37: request for member `params' in something not a 
structure or union
cooperative.c:39: request for member `params' in something not a 
structure or union
cooperative.c:39: request for member `params' in something not a 
structure or union
cooperative.c: At top level:
cooperative.c:50: parse error before `*'
cooperative.c:51: warning: return-type defaults to `int'
cooperative.c: In function `co_send_message_save':
cooperative.c:53: request for member `operation' in something not a 
structure or union
cooperative.c:53: `CO_OPERATION_MESSAGE_TO_MONITOR' undeclared (first 
use in this function)
cooperative.c:54: request for member `params' in something not a 
structure or union
cooperative.c:55: `co_message_t' undeclared (first use in this function)
cooperative.c:55: parse error before `)'
cooperative.c:55: request for member `params' in something not a 
structure or union
cooperative.c:56: warning: control reaches end of non-void function
cooperative.c: In function `co_send_message_restore':
cooperative.c:60: warning: implicit declaration of function 
`co_switch_wrapper'
cooperative.c: At top level:
cooperative.c:64: parse error before `*'
cooperative.c:65: warning: function declaration isn't a prototype
cooperative.c: In function `co_send_message_s':
cooperative.c:66: `co_message_t' undeclared (first use in this function)
cooperative.c:66: `message' undeclared (first use in this function)
cooperative.c:67: `params' undeclared (first use in this function)
cooperative.c:67: warning: statement with no effect
cooperative.c:68: parse error before `unsigned'
cooperative.c:70: `flags' undeclared (first use in this function)
cooperative.c:71: request for member `operation' in something not a 
structure or union
cooperative.c:71: `CO_OPERATION_MESSAGE_TO_MONITOR' undeclared (first 
use in this function)
cooperative.c:72: request for member `params' in something not a 
structure or union
cooperative.c:73: parse error before `)'
cooperative.c:73: request for member `params' in something not a 
structure or union
cooperative.c:75: `data' undeclared (first use in this function)
cooperative.c: At top level:
cooperative.c:82: parse error before `from'
cooperative.c:88: warning: function declaration isn't a prototype
cooperative.c: In function `co_send_message':
cooperative.c:89: `co_message_t' undeclared (first use in this function)
cooperative.c:89: parse error before `params'
cooperative.c:91: `params' undeclared (first use in this function)
cooperative.c:91: `from' undeclared (first use in this function)
cooperative.c:92: `to' undeclared (first use in this function)
cooperative.c:93: `priority' undeclared (first use in this function)
cooperative.c:94: `type' undeclared (first use in this function)
cooperative.c:95: `size' undeclared (first use in this function)
cooperative.c:97: `data' undeclared (first use in this function)
cooperative.c: At top level:
cooperative.c:100: parse error before `*'
cooperative.c:101: warning: function declaration isn't a prototype
cooperative.c: In function `co_receive_message':
cooperative.c:103: parse error before `co_message_t'
cooperative.c:103: warning: no semicolon at end of struct or union
cooperative.c:104: `co_linux_message_t' undeclared (first use in this 
function)
cooperative.c: At top level:
cooperative.c:105: warning: type defaults to `int' in declaration of 
`linux_message'
cooperative.c:105: warning: data definition has no type or storage class
cooperative.c:107: warning: type defaults to `int' in declaration of 
`linux_message'
cooperative.c:107: conflicting types for `linux_message'
cooperative.c:105: previous declaration of `linux_message'
cooperative.c:107: `message' undeclared here (not in a function)
cooperative.c:107: warning: data definition has no type or storage class
cooperative.c:109: parse error before `&'
cooperative.c:109: warning: type defaults to `int' in declaration of 
`co_handle_device_interrupt'
cooperative.c:109: warning: function declaration isn't a prototype
cooperative.c:109: warning: data definition has no type or storage class
cooperative.c: In function `co_callback':
cooperative.c:114: request for member `operation' in something not a 
structure or union
cooperative.c:114: `CO_OPERATION_MESSAGE_FROM_MONITOR' undeclared (first 
use in this function)
cooperative.c:115: `co_message_t' undeclared (first use in this function)
cooperative.c:115: parse error before `)'
cooperative.c:115: request for member `params' in something not a 
structure or union
cooperative.c:116: request for member `params' in something not a 
structure or union
cooperative.c:120: request for member `operation' in something not a 
structure or union
cooperative.c: In function `co_idle_processor':
cooperative.c:130: request for member `operation' in something not a 
structure or union
cooperative.c:130: `CO_OPERATION_IDLE' undeclared (first use in this 
function)
cooperative.c: In function `co_printk':
cooperative.c:138: `CO_MODULE_LINUX' undeclared (first use in this function)
cooperative.c:139: `CO_MODULE_PRINTK' undeclared (first use in this 
function)
cooperative.c:140: `CO_PRIORITY_DISCARDABLE' undeclared (first use in 
this function)
cooperative.c:141: `CO_MESSAGE_TYPE_STRING' undeclared (first use in 
this function)
cooperative.c: In function `co_debug_line':
cooperative.c:157: request for member `operation' in something not a 
structure or union
cooperative.c:157: `CO_OPERATION_DEBUG_LINE' undeclared (first use in 
this function)
cooperative.c:158: request for member `params' in something not a 
structure or union
cooperative.c: In function `co_trace_ent_name':
cooperative.c:179: warning: unsigned int format, pointer arg (arg 6)
cooperative.c: In function `co_trace_ent':
cooperative.c:202: warning: unsigned int format, pointer arg (arg 5)
cooperative.c: At top level:
cooperative.c:209: parse error before `do'
cooperative.c:212: `flags' used prior to declaration
cooperative.c:215: parse error before `do'
cooperative.c:216: parse error before `='
cooperative.c:217: parse error before `sizeof'
cooperative.c:217: warning: type defaults to `int' in declaration of 
`vsnprintf'
cooperative.c:217: warning: function declaration isn't a prototype
cooperative.c:217: warning: type defaults to `int' in declaration of `fmt'
cooperative.c:217: warning: type defaults to `int' in declaration of `args'
cooperative.c:217: conflicting types for `args'
cooperative.c:213: previous declaration of `args'
cooperative.c:217: parse error before `)'
cooperative.c:218: parse error before `void'
cooperative.c:219: warning: type defaults to `int' in declaration of 
`co_debug_line'
cooperative.c:219: warning: parameter names (without types) in function 
declaration
cooperative.c:219: conflicting types for `co_debug_line'
cooperative.c:147: previous declaration of `co_debug_line'
cooperative.c:219: warning: data definition has no type or storage class
cooperative.c:220: parse error before `__volatile__'
cooperative.c:228: parse error before `->'
cooperative.c:230: warning: type defaults to `int' in declaration of 
`co_switch_wrapper'
cooperative.c:230: warning: function declaration isn't a prototype
cooperative.c:230: warning: data definition has no type or storage class
cooperative.c:231: parse error before `__volatile__'
cooperative.c: In function `co_get_host_time':
cooperative.c:240: request for member `operation' in something not a 
structure or union
cooperative.c:240: `CO_OPERATION_GET_TIME' undeclared (first use in this 
function)
cooperative.c:242: request for member `params' in something not a 
structure or union
cooperative.c:237: warning: `time' might be used uninitialized in this 
function
make[2]: *** [cooperative.o] Error 1
make[2]: Leaving directory `/usr/src/kernel-source-2.4.24/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/kernel-source-2.4.24/kernel'
make: *** [_dir_kernel] Error 2
(Z)root@colinux:/usr/src/kernel-source-2.4.24>

Re: [coLinux-devel] coLinux on NT4?

[Benoit M. <ben...@cg...>]

memory allocated with ExAllocatePoolWithTag can also be freed with
ExFreePool (wich is NT4 supported)
in the file src/colinux/winnt/kernel/lowlevel/alloc.c
I gonna try to compile tonight with the second in place of the first......

And this function is declared in win32api, include/ddk/winddk.h
these functions are dependent of a flag : POOL_TAGGING, does someone know if
this is set in colinux cross compilation tools? I don't think so.

thx
Ben


----- Original Message -----
From: "Benoit MICHEL" <ben...@cg...>
To: "Digital Infra, Inc." <ok...@di...>
Cc: "Cooperative Linux Development" <col...@li...>
Sent: Wednesday, March 03, 2004 9:59 AM
Subject: Re: [coLinux-devel] coLinux on NT4?


> Hi
>
> I'd like to use it at work, where i'm still using nt4 (really heavy to use
> cL through vmware)
> It is for a real usage AND optionnaly ;) for my pleasure ;)
> but at home.... XP, colinux rulez
> what do you mean by BSOD??
> and the daemon doesn't trapp, just show a messagebox with "device driver
> d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in
> ntoskrnl.exe driver" (litteral traduction, original was in french ;) )
then
> close the windows when I click on OK.
>
> It all began with the same symptoms complaining about GlobalMemoryStatusEx
> (not supported by NT4)
> I made these modifications in /src/colinux/os/winnt/user/misc.c
>
> diff says :
> 20,21c20,21
> <  MEMORYSTATUSEX m;
> <  BOOL ret;
> ---
> >  MEMORYSTATUS m;
> >  //BOOL ret;
> 24,25c24,25
> <  ret = GlobalMemoryStatusEx(&m);
> <  if (ret != TRUE) {
> ---
> >  /*ret = */GlobalMemoryStatus(&m);
> >  /*if (ret != TRUE) {
> 28c28
> <  }
> ---
> >  }*/
> 30c30
> <  if (m.ullTotalPhys > (DWORDLONG)0xFF000000) {
> ---
> >  if (m.dwTotalPhys > (DWORDLONG)0xFF000000) {
> 36c36
> <  *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF);
> ---
> >  *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF);
>
>
> just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4
system
> is far below the 2GB limit ;) )
>
> no pb anymore to compile it at home using cobuild.sh (edited to not
> averwrite my modifications)
> and when I tried it today here, the daemon complains about
ExFreePoolWithTag
>
> When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not
> ExFreePoolWithTag
>
> The doc I found say that nt4 SP4 workstation support this API, i'm in
sp6a.
>
> Benoit
>
>
> ----- Original Message -----
> From: "Digital Infra, Inc." <ok...@di...>
> To: "Benoit MICHEL" <bem...@ca...>
> Cc: "Cooperative Linux Development" <col...@li...>
> Sent: Tuesday, March 02, 2004 4:07 PM
> Subject: Re: [coLinux-devel] coLinux on NT4?
>
>
> >
> > Hello
> >
> > BTW, Why you have an interest about coLinux on NT4?
> > Just your hobby? or you have real usage?
> > but, at least, I welcome your effort very much.
> > because, with your effort, we can collect more hints to
> > stabilize coLinux. thanks Benoit!.
> > and please give us your history of BSOD with a stack trace.
> >
> >             --- Okajima.
>
>
>
> -------------------------------------------------------
> 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] Wiki site.

[<ch...@to...>]

I found that a version specific link to my page worked.
so I just selected edit old revision then save. This restored my page.

I also found that if I went to the page create link of other pages that
were deleted and the changed the url from ?action=Create to
?action=PageHistory I could get the history for that page. I took the
liberty of restoring the others as well to what appeared to be the most
recent legit version.

Anyone making modifications yesterday please check my work to be shure it
is back to the versions the authors intended. I did not make any
modifications so a diff with the last legit version should come up blank.

chris

Re: [coLinux-devel] Wiki site.

[<ch...@to...>]

Looks like the howto I wrote for using Topologi-linux with coLinux
disappeared too. I do have a backup of the raw text but I did alot of
tweeking to the format an links after pasiting in. I would like to repost
it when it is more secure.

chris

> On Tue, Mar 02, 2004 at 07:06:59PM -0500, Clemmitt M. Sigler wrote:
>> Hi,
>>
>> I hope I'm just witnessing a reorganization of the Wiki site.  I've
>> spent some time working on some small additions to the Wiki pages.
>> Now I see some of the pages have been deleted.  Or am I missing
>> something?
>> The FAQ is gone, for example.
>>
>> Also, I created a new page, "How to Ask a Question," which someone had
>> posted as a link without content to be filled in.  Now that's gone.
>> Naturally, I didn't save my work and, if it's lost, will have to
>> recreate it from scratch if it's deemed valuable enough to post
>> again.
>>
>> If possible, would someone please check the Wiki site?  I'd hate
>> to think we'd have to go to a "moderated" Wiki with a web page
>> manager checking in all edits.  More work for all.  TIA.
>
> Some moron script kiddie apparently messed with it.
>
> Yes, we will have to go to moderated one.
>
> --
> Dan Aloni
> da...@co...
>
>
> -------------------------------------------------------
> 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] slirp

[<ch...@to...>]

If what you are getting to here is networking and a vnc client and or X
server that can be started from auto run so that there is no pre
configuration on the machine. Then I vote for that too.

One thing I was thinking of for an autorun cd is if cygwin's X can be used
it has a mode for letting windows be the window manager. That mode has a
nice seemless look to it. That combined with a nice linux "task bar" at
the top of the screen would be really cool.


> while chatting about network configuration for a coknoppix type distro in
> #colinux someone mentioned slirp http://slirp.sourceforge.net/ while slirp
> does not compile out of the box on cygwin a patch can be found at
> http://www.geocrawler.com/archives/3/3071/2002/8/0/9308943/ I tested slirp
> over ssh between 2 linux systems (i don't have a functiong sshd on cygwin
> atm and i didn't wan't to do a lot of configuration to find out if it did
> what it said on the tin :) ). slirp can be considered as a user-mode nat
> to
> the client it looks like a ppp or slip server to the host it runs on it
> looks like a normal network client app
>
> ok now for the crunch
>
> would it be possible/practical to add a feature to colinux to create a
> charachtor mode device and link it to a user specified app on the windows
> side?
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/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] coLinux on NT4?

[Benoit M. <ben...@cg...>]

Hi

I'd like to use it at work, where i'm still using nt4 (really heavy to use
cL through vmware)
It is for a real usage AND optionnaly ;) for my pleasure ;)
but at home.... XP, colinux rulez
what do you mean by BSOD??
and the daemon doesn't trapp, just show a messagebox with "device driver
d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in
ntoskrnl.exe driver" (litteral traduction, original was in french ;) ) then
close the windows when I click on OK.

It all began with the same symptoms complaining about GlobalMemoryStatusEx
(not supported by NT4)
I made these modifications in /src/colinux/os/winnt/user/misc.c

diff says :
20,21c20,21
<  MEMORYSTATUSEX m;
<  BOOL ret;
---
>  MEMORYSTATUS m;
>  //BOOL ret;
24,25c24,25
<  ret = GlobalMemoryStatusEx(&m);
<  if (ret != TRUE) {
---
>  /*ret = */GlobalMemoryStatus(&m);
>  /*if (ret != TRUE) {
28c28
<  }
---
>  }*/
30c30
<  if (m.ullTotalPhys > (DWORDLONG)0xFF000000) {
---
>  if (m.dwTotalPhys > (DWORDLONG)0xFF000000) {
36c36
<  *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF);
---
>  *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF);


just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4 system
is far below the 2GB limit ;) )

no pb anymore to compile it at home using cobuild.sh (edited to not
averwrite my modifications)
and when I tried it today here, the daemon complains about ExFreePoolWithTag

When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not
ExFreePoolWithTag

The doc I found say that nt4 SP4 workstation support this API, i'm in sp6a.

Benoit


----- Original Message -----
From: "Digital Infra, Inc." <ok...@di...>
To: "Benoit MICHEL" <bem...@ca...>
Cc: "Cooperative Linux Development" <col...@li...>
Sent: Tuesday, March 02, 2004 4:07 PM
Subject: Re: [coLinux-devel] coLinux on NT4?


>
> Hello
>
> BTW, Why you have an interest about coLinux on NT4?
> Just your hobby? or you have real usage?
> but, at least, I welcome your effort very much.
> because, with your effort, we can collect more hints to
> stabilize coLinux. thanks Benoit!.
> and please give us your history of BSOD with a stack trace.
>
>             --- Okajima.

Re: [coLinux-devel] Wiki site.

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

On Wed, Mar 03, 2004 at 06:58:04AM +0200, Dan Aloni wrote:
> On Tue, Mar 02, 2004 at 07:06:59PM -0500, Clemmitt M. Sigler wrote:
> > Hi,
> > 
> > I hope I'm just witnessing a reorganization of the Wiki site.  I've
> > spent some time working on some small additions to the Wiki pages.
> > Now I see some of the pages have been deleted.  Or am I missing something?
> > The FAQ is gone, for example.
> > 
> > Also, I created a new page, "How to Ask a Question," which someone had 
> > posted as a link without content to be filled in.  Now that's gone.
> > Naturally, I didn't save my work and, if it's lost, will have to
> > recreate it from scratch if it's deemed valuable enough to post
> > again.
> > 
> > If possible, would someone please check the Wiki site?  I'd hate
> > to think we'd have to go to a "moderated" Wiki with a web page
> > manager checking in all edits.  More work for all.  TIA.
> 
> Some moron script kiddie apparently messed with it.
> 
> Yes, we will have to go to moderated one.

Or at least something that needs access rights.

-- 
Dan Aloni
da...@co...

Re: [coLinux-devel] Wiki site.

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

On Tue, Mar 02, 2004 at 07:06:59PM -0500, Clemmitt M. Sigler wrote:
> Hi,
> 
> I hope I'm just witnessing a reorganization of the Wiki site.  I've
> spent some time working on some small additions to the Wiki pages.
> Now I see some of the pages have been deleted.  Or am I missing something?
> The FAQ is gone, for example.
> 
> Also, I created a new page, "How to Ask a Question," which someone had 
> posted as a link without content to be filled in.  Now that's gone.
> Naturally, I didn't save my work and, if it's lost, will have to
> recreate it from scratch if it's deemed valuable enough to post
> again.
> 
> If possible, would someone please check the Wiki site?  I'd hate
> to think we'd have to go to a "moderated" Wiki with a web page
> manager checking in all edits.  More work for all.  TIA.

Some moron script kiddie apparently messed with it.

Yes, we will have to go to moderated one.

-- 
Dan Aloni
da...@co...

[coLinux-devel] Initrd support?

[Eric A. <ea...@ma...>]

Hi,

I'm trying to essentially port my current UML configuration over to a
similar coLinux setup, but the first obvious problem that comes to mind
is that there does not appear to be a way to specify initrds.

Am I mistaken, or is this so? This is a requirement for my setup,
because the initrd creates a number of tmpfs filesystems for /etc, /var,
and /tmp (for specific reasons outside of the realm of this topic).

Also, regarding the memory restrictions: is there no other possible way
to allocate physical ram? I find it hard to think that no Windows
application surpasses this memory usage (VMware? Most games?); is there
a chance that one of these alternate memory allocation sources could be
used, thus allowing more realistic physical memory usages?

Thanks,
-- Eric Andresen
   Junior Systems Administrator
   Mars Space Flight Facility
   Arizona State University
   ea...@ma...

[coLinux-devel] Wiki site.

[Clemmitt M. S. <sig...@bl...>]

Hi,

I hope I'm just witnessing a reorganization of the Wiki site.  I've
spent some time working on some small additions to the Wiki pages.
Now I see some of the pages have been deleted.  Or am I missing something?
The FAQ is gone, for example.

Also, I created a new page, "How to Ask a Question," which someone had 
posted as a link without content to be filled in.  Now that's gone.
Naturally, I didn't save my work and, if it's lost, will have to
recreate it from scratch if it's deemed valuable enough to post
again.

If possible, would someone please check the Wiki site?  I'd hate
to think we'd have to go to a "moderated" Wiki with a web page
manager checking in all edits.  More work for all.  TIA.

					Clemmitt

[coLinux-devel] slirp

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

while chatting about network configuration for a coknoppix type distro in
#colinux someone mentioned slirp http://slirp.sourceforge.net/ while slirp
does not compile out of the box on cygwin a patch can be found at
http://www.geocrawler.com/archives/3/3071/2002/8/0/9308943/ I tested slirp
over ssh between 2 linux systems (i don't have a functiong sshd on cygwin
atm and i didn't wan't to do a lot of configuration to find out if it did
what it said on the tin :) ). slirp can be considered as a user-mode nat to
the client it looks like a ppp or slip server to the host it runs on it
looks like a normal network client app

ok now for the crunch

would it be possible/practical to add a feature to colinux to create a
charachtor mode device and link it to a user specified app on the windows
side?
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004

[coLinux-devel] Re: 0.5.4/colinux-bridged-net-daemon not being built

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

----- Original Message ----- 
From: "Alejandro R. Sedeno" <as...@MI...>
To: "Sean Brook" <sea...@so...>
Cc: "coLinux Development" <col...@li...>
Sent: Monday, March 01, 2004 9:39 PM
Subject: Re: 0.5.4/colinux-bridged-net-daemon not being built


| This one confused me for a moment too. :p
|
| Dan set the bridged daemon aside in the makefile. From the colinux/src
| dir:
|
| make bridged_net_daemon
|
| You may also need the winpcap headers, those are available on the
| winpcap site (google for link). I've been using the 3.0 Developer's
| Pack. Careful how you integrate these with the existing includes, make a
| backup of what's there since pcap includes some different versions of
| what's already there.

Many thanks for replying and pointing me in the right direction.
I have tried to place the include files but get all kinds of errors.
I can see how the include files conflict with the cygwin includes but
dont know how to work around it.

Is there any possibility *please* you (or anyone) could give me a few
pointers of how to intergrate the include files? (maybe relevant: my
cygwin cross build tools have been made with the cobuild.sh script).


|
| Good luck!
|
| -Alejandro
|
| On Mon, 2004-03-01 at 16:25, Sean Brook wrote:
| > I want to try the colinux-bridged-net-daemon but it is not being built
as
| > part of make colinux
| >
| > What is the build process for colinux-bridged-net-daemon?
| >
| > Cheers.
| >
|

Re[2]: [coLinux-devel] mounting cdrom

[keksov <ke...@gm...>]

CMS> disk partitions, CD-ROM and other IDE devices, and similar.  Is
CMS> it path="\Device\HarddiskVolumeX", or is it 
CMS> path="\Device\HarddiskVolumeX\PartitionY", or what?

Just my two cents, it works fine for me:
I have two HHDs in my PC, both are on first IDE controller,
Master disk is for WIndows XP, Slave disk is for Linux.
Well, to access RAW partitions from second disk I use the following line in XML
config file:
<block_device index="6" path="\DEVICE\Harddisk2\Partition1" enabled="true"/>

Re: [coLinux-devel] Tap, Distros, irc

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

On Tue, Mar 02, 2004 at 10:52:24AM +0000, Mark Olliver wrote:
> Hi All
> 
> I am interested in helping with / using different distributions on 
> colinux. I may need a hand to start with to get some of the basic ideas.
> 
> I have downloaded and tried the Debain image and am looking at trying a 
> few others. I do have one question though. How can I specify which tap 
> adapter colinux should like to on my xp computer. As I am currently 
> running openvpn most of the time which also uses tap but I have it 
> connected to a specific device. However, colinux seamed to like that tap 
> interface.

Support for naming the TAP adapter will be added in the next version, 
hopefully.

> I also thought it might be usefull for the distribution to have an irc 
> room, as I can not presently find one, hope this is ok. But I have 
> created one on irc.freenode.net #colinux . Later in the day I will put a 
> bot in the room to keep it open and hopefully start answering questions 
> when it learns some of the answers.

The official #colinux channel is on irc.oftc.net. 

-- 
Dan Aloni
da...@co...

[coLinux-devel] 0.5.4: i686-optimized vmlinux along with i686-optimized userspace - segfaults

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

Hello,

I've figured the issue mentioned in the topic. Well, apparently the optimized
kernel code corrupts MMX / FPU registers for userspace while in the path 
between hardware interrupt handling and forwarding to the host. 

It occurs more often when the coLinux machine gets more CPU from the host, 
since hardware interrupts are caught more often in that situation.

A i386-compatible vmlinux gets around it, but it's not the solution I want.

I'm now working on a fix, while also merging Ballard's patches.

-- 
Dan Aloni
da...@co...

Re: [coLinux-devel] cygwin resize2fs

[<ch...@to...>]

While waiting on your reply I downloaded the source to e2fsprogs-1.35
which contains resize2fs I was not able to make the whole thing but was
able to make resize2fs.exe and tried it on an image file that I enlarged
with my gui tool I had to use -f but hopefully I will be able to build
e2fsck to run before and after. So far so good. I will then attempt to
wrap all this in the gui that enlarges the file itself.

I am familiar with the Loopback Root Filesystem HOWTO but maby I'll give
it another look. I have been working with root on loop with topologilinux
for some time now.

I'll keep working with this version because it is the actively developed
one. I heard somewhere that It was first developed for partition magic or
something else commercial like that I don't know what os runs under that.

Thanks for the history lesson. I always wondered if they were related. I
think that I tried both at the time I was attempting this before. But I
must have had a version that was not compatable with cygwin

chris

> ----- Original Message -----
> From: <ch...@to...>
> To: <col...@li...>
> Sent: Tuesday, March 02, 2004 6:54 PM
> Subject: [coLinux-devel] cygwin resize2fs
>
>
> | On the expanding root wiki page I saw mention of running resize2fs under
> | cygwin. I just did a carefull install of cygwin looking for any packages
> | that may contain this but could not find it.
> You wont find e2fsprogs in cygwin. Cygwin does not need to know about
> file systems (until now of course with coLinux).
>
> |
> | I tried downloading the sources under cygwin 6 months ago and was not
> able
> | to get it to work.
> |
> | Where can I obtain this. I wrote a program with tcl/tk that is a
> starpack
> | that can increase the size of the file but It requires a script to run
> in
> | linux to resize the file system. If I could find this I will try to
> adapt
> | my program to do the whole process in windows with a nice gui.
>
> resize2fs started out as ext2resize before it was merged in a few years
> ago. The last released version of ext2resize was 0.7. This version had
> problems with large filesystems and did not support ext3 (though you could
> get around that by removing the journal and adding it back after the
> resize).
> However, if you go to http://sourceforge.net/projects/ext2resize/ you can
> checkout what would have been 0.8 from cvs.
> For reference read this: The Loopback Root Filesystem HOWTO
> The versions of this document from tldp and elsewhere lack the section
> that I think is relevant: 5.7 Resizing a loop linux system
> Here is a link to this version:
> http://217.109.169.18/download/looplinux/loop-root-fs.txt
>
> A gui in Windows that would do this sounds fantastic :)
>
> |
> | anyone know where I can get this. Or instructions for getting it to
> | compile and work in windows.
> |
> | chris
> |
> |
> | -------------------------------------------------------
> | 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
>

Re: [coLinux-devel] cygwin resize2fs

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

I think I made a mistake calling the last version 0.8. I may
have been thinking about a completely different package.
The point is the same though. The last version was never
released and is in cvs. The official one is resize2fs and I 
guess you know where to get the sources for that.

Re: [coLinux-devel] how to obtain kernel modules?

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

----- Original Message ----- 
From: "Gregor Mitsch" <mi...@ra...>
To: <col...@li...>
Sent: Tuesday, March 02, 2004 4:46 PM
Subject: [coLinux-devel] how to obtain kernel modules?


| Hi,
| 
| this is probably a silly question: How can make the kernel modules of 
| coLinux to be available? I'd like to modprobe 'smbfs'
You need to compile your own kernel. To get started look at
doc/building in the coLinux tarball.
Alternatively someone may compile it for you but there are lots of
variables here. One module does not fit all.

| 
| Thank's for any answers.
| 
| --Gregor
| 
| 
| -------------------------------------------------------
| 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] cygwin resize2fs

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

----- Original Message ----- 
From: <ch...@to...>
To: <col...@li...>
Sent: Tuesday, March 02, 2004 6:54 PM
Subject: [coLinux-devel] cygwin resize2fs


| On the expanding root wiki page I saw mention of running resize2fs under
| cygwin. I just did a carefull install of cygwin looking for any packages
| that may contain this but could not find it.
You wont find e2fsprogs in cygwin. Cygwin does not need to know about
file systems (until now of course with coLinux).

|
| I tried downloading the sources under cygwin 6 months ago and was not able
| to get it to work.
|
| Where can I obtain this. I wrote a program with tcl/tk that is a starpack
| that can increase the size of the file but It requires a script to run in
| linux to resize the file system. If I could find this I will try to adapt
| my program to do the whole process in windows with a nice gui.

resize2fs started out as ext2resize before it was merged in a few years
ago. The last released version of ext2resize was 0.7. This version had
problems with large filesystems and did not support ext3 (though you could
get around that by removing the journal and adding it back after the
resize).
However, if you go to http://sourceforge.net/projects/ext2resize/ you can
checkout what would have been 0.8 from cvs.
For reference read this: The Loopback Root Filesystem HOWTO
The versions of this document from tldp and elsewhere lack the section
that I think is relevant: 5.7 Resizing a loop linux system
Here is a link to this version:
http://217.109.169.18/download/looplinux/loop-root-fs.txt

A gui in Windows that would do this sounds fantastic :)

|
| anyone know where I can get this. Or instructions for getting it to
| compile and work in windows.
|
| chris
|
|
| -------------------------------------------------------
| 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

[coLinux-devel] cygwin resize2fs

[<ch...@to...>]

On the expanding root wiki page I saw mention of running resize2fs under
cygwin. I just did a carefull install of cygwin looking for any packages
that may contain this but could not find it.

I tried downloading the sources under cygwin 6 months ago and was not able
to get it to work.

Where can I obtain this. I wrote a program with tcl/tk that is a starpack
that can increase the size of the file but It requires a script to run in
linux to resize the file system. If I could find this I will try to adapt
my program to do the whole process in windows with a nice gui.

anyone know where I can get this. Or instructions for getting it to
compile and work in windows.

chris