colinux-users — coLinux users mailing list

Re: [coLinux-users] Killing colinux-daemon.exe

[Paolo M. <pao...@gm...>]

Hi,
in my opinion the best thing that you can do is to help to trace the problem.
It is better understand the problem and solve it.
Kill the daemon is only a work-around.

In this moment I'm searching with Henry a bug that arise when I change
some kernel configuration.
If I had the oop (the crash) I have your same problem. I cannot kill
the colinux-daemon. And I cannot close cleanly WindowsXp.
My colinux-daemon is at 99% of the CPU.

It is very interesting know what exacly is your problem.
Can you post a log ?
If you want to help us, I can send you a particular version of
colinux-debug-daemon that help us to trace the problem.
It is interesting know if I and you have the same problem.

I don't know any way to kill the daemon ....

Bye,
Paolo

On Thu, May 29, 2008 at 5:57 PM, Asif Iqbal <a....@ie...> wrote:
> At times my colinux 0.72 hangs under XP. I stop the service which only
> stops after quite some time. Then colinux-daemon.exe stays running in
> the task list. I try, in all possible ways, to kill colinux-daemon.exe
> but it simply doesn't get killed.
>
> I have tried:
>
> taskkill /im colinux-daemon.exe /f
> and
> taskkill /F /FI "SERVICES eq andLinux"
> and
> taskkill /F /FI "IMAGENAME eq colinux-daemon.exe"
>
> It says SUCCCESS: Process with PID XXXX terminated. But there it is in
> the task list driving me crazy.
>
> Any help??
> Thanks.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Killing colinux-daemon.exe

[Asif I. <a....@ie...>]

At times my colinux 0.72 hangs under XP. I stop the service which only
stops after quite some time. Then colinux-daemon.exe stays running in
the task list. I try, in all possible ways, to kill colinux-daemon.exe
but it simply doesn't get killed.

I have tried:

taskkill /im colinux-daemon.exe /f
and
taskkill /F /FI "SERVICES eq andLinux"
and
taskkill /F /FI "IMAGENAME eq colinux-daemon.exe"

It says SUCCCESS: Process with PID XXXX terminated. But there it is in
the task list driving me crazy.

Any help??
Thanks.

[coLinux-users] Colinux without adminstrator

[Paolo M. <pao...@gm...>]

> Fortunatly yes :) But i'd like to know why we have to install this
> driver. Is it because perf reason ? or just because colinux access to
> a very low level system and Windows don't accept that so we setup a
> driver to access to this memory ??

Yes,  colinux needs to access to some low-level, for example setting
page-tables.
It is not possibile use it without the driver.
What you need is a win32 of uml, or umlwin32.
But I don't know if it is usable. And it is not updated.

> Yes, that works but if your are not administrator and he don't want
> you use colinux, you can't :/

I know. But for now we don't have other way.

Bye,
Paolo

[coLinux-users] Colinux without adminstrator

[Julien L. <jul...@gm...>]

Hi,

I'm looking for a way to run Colinux on a machine without a
administrator installation. I read the FAQ
(http://colinux.wikia.com/wiki/CoLinux_FAQ#Q0._Do_I_need_Administrator_rights_on_my_Windows_computer_.3F)
and it appear it's not possible ... But i'd like to know why ?

If i understand correctly, Colinux need an administrator to install
the Colinux driver (monitor) which is used to run a low level process
in Windows.
So what does that mean ? That mean if you are not the administrator,
you can't run a low level process ? So is there possible to run
Colinux as a high level process ?

I'm really sorry if my questions are stupid but i'm not familiar with
the Windows process behaviour so i'm not sure to understand what is a
"low level" process.

Thanks in advance

-- 
 Julien

PS: Ulteo Virutal Desktop beta was released last week. It's using
Colinux (like AndLinux but don't use it), pulse audio and Xming

Re: [coLinux-users] Rolling your own kernel

[Christopher D. C. <c.d...@re...>]

Thanks Guys!

#make kernel 

Did the trick

"Why is Gaffa tape like the force?
Because it has a light side, a dark side, and it holds the universe together!"

----------------===========----------------
Christopher Chapman
Systems Programmer ITNG
School of Systems Engineering
The University of Reading

E-mail: c.d...@re...
Phone:  +44 (0)118 3787664

School of Systems Engineering
The University of Reading
PO Box 225
Whiteknights
Reading
RG6 6AY
----------------===========----------------


-----Original Message-----
From: Paolo Minazzi [mailto:pao...@gm...] 
Sent: 23 May 2008 18:05
To: Christopher David Chapman
Subject: Re: [coLinux-users] Rolling your own kernel

the ...build directory is the directory with objects (the soruce is
getted from the ....source directory)
the ....source contains the source code patched with colinux drivers
regards
paolo

On Fri, May 23, 2008 at 6:25 PM, Christopher David Chapman
<c.d...@re...> wrote:
> Hi Paolo,
>
> Thank you very much for getting back to me.
>
> So far I have downloaded the stable-xxxxxx.tar.gz and run
>
>>make kernel (just make failed on binutils!)
>
> I now have linux-xxx-source and linux-xxx-build. What's the difference between the two?
>
> Is linux-xxx-source the vanilla kernel and linux-xxx-build the coLinux patched one?
>
> You mention patching linux-xxx-source but from the looks of the make output its already been done.
>
> Cheers
>  Chris
>
>
> ====================================
>
> [root@cg-217-130 stable-colinux-20080512]# make kernel
> log: /usr/src/log/build-colinux-9739.log
> err: /usr/src/log/build-colinux-9739.err
> Check kernel and modules: vmlinux or modules don't exist, build it now
> Downloading linux-2.6.22.18.tar.bz2
> --16:42:35--  http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.18.tar.bz2
>           => `linux-2.6.22.18.tar.bz2'
> Resolving wwwcache.rdg.ac.uk... 134.225.2.160
> Connecting to wwwcache.rdg.ac.uk|134.225.2.160|:8080... connected.
> Proxy request sent, awaiting response... 200 OK
> Length: 45,103,645 (43M) [application/x-bzip2]
>
> 100%[===============================================================================================>] 45,103,645   103.69K/s    ETA 00:00
>
> 16:47:04 (164.40 KB/s) - `linux-2.6.22.18.tar.bz2' saved [45103645/45103645]
>
> Extracting Kernel 2.6.22.18
> reading base-2.6.22.diff
> patching file CREDITS
> patching file Makefile
> patching file arch/i386/Kconfig
> patching file arch/i386/Kconfig.cpu
> patching file arch/i386/kernel/Makefile
> patching file arch/i386/kernel/cooperative.c
> patching file arch/i386/kernel/cpu/common.c
> patching file arch/i386/kernel/entry.S
> patching file arch/i386/kernel/head.S
> patching file arch/i386/kernel/i387.c
> patching file arch/i386/kernel/process.c
> patching file arch/i386/kernel/setup.c
> patching file arch/i386/kernel/traps.c
> patching file arch/i386/kernel/vmlinux.lds.S
> patching file arch/i386/mm/fault.c
> patching file arch/i386/mm/init.c
> patching file arch/i386/mm/ioremap.c
> patching file include/asm-i386/bug.h
> patching file include/asm-i386/cooperative.h
> patching file include/asm-i386/cooperative_internal.h
> patching file include/asm-i386/dma.h
> patching file include/asm-i386/fixmap.h
> patching file include/asm-i386/io.h
> patching file include/asm-i386/mach-default/irq_vectors.h
> patching file include/asm-i386/mach-default/irq_vectors_limits.h
> patching file include/asm-i386/mc146818rtc.h
> patching file include/asm-i386/mmzone.h
> patching file include/asm-i386/page.h
> patching file include/asm-i386/pgalloc.h
> patching file include/asm-i386/pgtable-2level.h
> patching file include/asm-i386/pgtable.h
> patching file include/asm-i386/processor.h
> patching file include/linux/cooperative.h
> patching file include/linux/cooperative_internal.h
> patching file kernel/Makefile
> patching file kernel/cooperative.c
> patching file kernel/panic.c
> patching file kernel/printk.c
> patching file mm/bootmem.c
> patching file mm/page_alloc.c
> patching file mm/vmscan.c
> patching file drivers/char/mem.c
> patching file include/linux/elf.h
> patching file arch/i386/kernel/cpu/bugs.c
> patching file arch/i386/kernel/reboot_cooperative.c
> patching file arch/i386/mach-default/setup.c
> patching file arch/i386/kernel/i8259_cooperative.c
> patching file arch/i386/kernel/ioport_cooperative.c
> reading timer-2.6.22.diff
> patching file arch/i386/kernel/timer_cooperative.c
> patching file arch/i386/kernel/cpu/common.c
> patching file arch/i386/lib/delay.c
> patching file arch/i386/mach-default/setup.c
> patching file include/asm-i386/delay.h
> patching file include/asm-i386/mach-default/do_timer.h
> patching file include/asm-i386/timex.h
> reading coconsole-core.diff
> patching file drivers/video/console/cocon.c
> reading coconsole-2.6.22.diff
> patching file drivers/video/console/Kconfig
> patching file include/linux/console.h
> patching file drivers/video/console/Makefile
> patching file drivers/video/console/cocon.c
> reading serial-core.diff
> patching file drivers/char/cocd.c
> reading serial-2.6.22.diff
> patching file drivers/char/Makefile
> patching file drivers/char/cocd.c
> patching file drivers/char/Kconfig
> reading conet-core.diff
> patching file drivers/net/conet.c
> reading conet-2.6.22.diff
> patching file drivers/net/Kconfig
> patching file drivers/net/Makefile
> patching file drivers/net/conet.c
> reading cobd-core.diff
> patching file drivers/block/cobd.c
> reading cobd-2.6.22.diff
> patching file include/linux/major.h
> patching file drivers/block/Kconfig
> patching file drivers/block/Makefile
> patching file drivers/block/cobd.c
> reading kbd-core.diff
> patching file drivers/input/serio/cokbd.c
> reading kbd-2.6.22.diff
> patching file drivers/input/keyboard/Kconfig
> patching file drivers/input/keyboard/atkbd.c
> patching file drivers/input/serio/Kconfig
> patching file drivers/input/serio/Makefile
> patching file drivers/input/serio/cokbd.c
> reading mouse-2.6.22.diff
> patching file drivers/input/mouse/Kconfig
> patching file drivers/input/mouse/Makefile
> patching file drivers/input/mouse/comouse.c
> reading cofs-core.diff
> patching file fs/cofusefs/dev.c
> patching file fs/cofusefs/dir.c
> patching file fs/cofusefs/file.c
> patching file fs/cofusefs/fuse_i.h
> patching file fs/cofusefs/inode.c
> patching file fs/cofusefs/util.c
> patching file include/linux/cooperative_fs.h
> reading cofs-2.6.22.diff
> patching file fs/Kconfig
> patching file fs/Makefile
> patching file fs/cofusefs/Makefile
> patching file fs/cofusefs/file.c
> patching file fs/cofusefs/fuse_i.h
> patching file fs/cofusefs/dir.c
> patching file fs/cofusefs/inode.c
> reading cloop-core-2.06.diff
> patching file drivers/block/cloop.c
> patching file drivers/block/compressed_loop.h
> reading cloop-2.6.22.diff
> patching file drivers/block/Kconfig
> patching file drivers/block/Makefile
> reading squashfs3.2-core.diff
> patching file fs/squashfs/inode.c
> patching file fs/squashfs/Makefile
> patching file fs/squashfs/squashfs2_0.c
> patching file fs/squashfs/squashfs.h
> patching file include/linux/squashfs_fs.h
> patching file include/linux/squashfs_fs_i.h
> patching file include/linux/squashfs_fs_sb.h
> patching file init/do_mounts_rd.c
> reading squashfs3.2-2.6.22.diff
> patching file fs/Kconfig
> patching file fs/Makefile
> Configuring Kernel 2.6.22.18
> Making Kernel 2.6.22.18
> Making Modules 2.6.22.18
> Create Modules archive
> Create md5sum
> [root@cg-217-130 stable-colinux-20080512]#
>
> ====================================
>
> "Why is Gaffa tape like the force?
> Because it has a light side, a dark side, and it holds the universe together!"
>
> ----------------===========----------------
> Christopher Chapman
> Systems Programmer ITNG
> School of Systems Engineering
> The University of Reading
>
> E-mail: c.d...@re...
> Phone:  +44 (0)118 3787664
>
> School of Systems Engineering
> The University of Reading
> PO Box 225
> Whiteknights
> Reading
> RG6 6AY
> ----------------===========----------------
>
>
> -----Original Message-----
> From: col...@li... [mailto:col...@li...] On Behalf Of Paolo Minazzi
> Sent: 23 May 2008 12:38
> To: col...@li...
> Subject: Re: [coLinux-users] Rolling your own kernel
>
> Hi,
> My advice is to use the stable-xxxxxx.tar.gz source code.
> use
>
>>./configure
>> make
>
> This will compile compilers, kernel and colinux form source.
> This process don't touch your linux distro. You can use it.
>
> At the end of this process you will find a directory "../build".
> In this directory there are linux-xxx-source and linux-xxx-build
> You have to apply patch to the linux-xxx-source tree.
> This is kernel patched with colinux drivers.
> Now apply your patch to this tree (linux-xxx-source)
>
> When this is done, you can compile using
>>make
>
> in the linux-xxx-build directory.
>
> If you need to change the .config copy your .conf in the
> linux-xxx-build directory.
>
> I hope this is OK. I do it. If something is wrong ....
>
>
> Bye,
> Paolo
>
>
>
> On Fri, May 23, 2008 at 12:39 PM, Christopher David Chapman
> <c.d...@re...> wrote:
>> Hi,
>>
>> I am trying to get autofs working under fc8 and coLinux.
>> Autofs is complaining that it is missing a kernel module autofs4.
>> Ok, I thought I will need to add it into the kernel.
>>
>> Following the instruction in the FAQ (http://colinux.wikia.com/wiki/CoLinux_FAQ#Q19._How_do_I_build_my_own_kernel_for_coLinux.3F)
>>
>> I downloaded the latest stable source ball for coLinux and the kernel source for 2.6.22 from kernel.org
>> Untar'd them both and cd'd into /usr/src/linux
>>
>> When trying the line "patch -p1 < (extraction-point)/colinux-20040529/patch/linux" /patch/linux is not found and if I try to do the 2.6.22 diff files by hand I get as far as "cobd-2.6.22.diff" and if fails saying there is no "drivers/block/cobd.c", which indeed there is not.
>>
>> I short, I'm lost
>>
>>
>> Any clues much appreciated.
>>
>> Cheers
>>  Chris
>>
>> "Why is Gaffa tape like the force?
>> Because it has a light side, a dark side, and it holds the universe together!"
>>
>> ----------------===========----------------
>> Christopher Chapman
>> Systems Programmer ITNG
>> School of Systems Engineering
>> The University of Reading
>>
>> E-mail: c.d...@re...
>> Phone:  +44 (0)118 3787664
>>
>> School of Systems Engineering
>> The University of Reading
>> PO Box 225
>> Whiteknights
>> Reading
>> RG6 6AY
>> ----------------===========----------------
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] MSN

[Paolo M. <pao...@gm...>]

>> An other question: the cursor position. Why sometimes it is in a wrong
>> position ?
>
> Perhaps it is, what is not working for you?
>
> In my nt console the cursor is only badly on startup. It hangs on top of
> screen. But after type the first letter, it's ok. all times,
>
> Only, sometimes, if I delete char in middle of line, the last char was
> double, or not cleared with space. For example I have a line
> "123456789", and goe with cuursor to middle and remove the 345, then it
> was seen as "123678999". But very rarely.

For me (on XP) sometimes it is in a bad position.
For example when I compile the kernel, the cursor is in the first line
(not in the last line).
When I press a key on the keyboard, it returns in the right position.
Not an important problem, but why does it happen ?
Other colinux-users have seen this ?

Bye,
Paolo

Re: [coLinux-users] Rolling your own kernel

[Henry N. <Hen...@Ar...>]

Paolo Minazzi wrote:
> Hi,
> My advice is to use the stable-xxxxxx.tar.gz source code.
> use
> 
>> ./configure
>> make

  ./configure
  make kernel

is enouth to have kernel only. You not need all of the mingw32 cross
build environment.

> This will compile compilers, kernel and colinux form source.
> This process don't touch your linux distro. You can use it.
> 
> At the end of this process you will find a directory "../build".
> In this directory there are linux-xxx-source and linux-xxx-build
> You have to apply patch to the linux-xxx-source tree.
> This is kernel patched with colinux drivers.
> Now apply your patch to this tree (linux-xxx-source)
> 
> When this is done, you can compile using
> make
> 
> in the linux-xxx-build directory.
> 
> If you need to change the .config copy your .conf in the
> linux-xxx-build directory.
> 
> I hope this is OK. I do it. If something is wrong ....
> 
> Paolo
> 
> On Fri, May 23, 2008 at 12:39 PM, Christopher David Chapman
> <c.d...@re...> wrote:
>>
>> I am trying to get autofs working under fc8 and coLinux.
>> Autofs is complaining that it is missing a kernel module autofs4.
>> Ok, I thought I will need to add it into the kernel.
>>
>> Following the instruction in the FAQ (http://colinux.wikia.com/wiki/CoLinux_FAQ#Q19._How_do_I_build_my_own_kernel_for_coLinux.3F)

Oh, that's true outdated.

Please follow "4.2 Compiling the Cooperative Linux kernel" from
http://colinux.wikia.com/wiki/BuildingColinux0.8.0
The same file exist in source as doc/building.

-- 
Henry N.

Re: [coLinux-users] Rolling your own kernel

[Paolo M. <pao...@gm...>]

Hi,
My advice is to use the stable-xxxxxx.tar.gz source code.
use

>./configure
> make

This will compile compilers, kernel and colinux form source.
This process don't touch your linux distro. You can use it.

At the end of this process you will find a directory "../build".
In this directory there are linux-xxx-source and linux-xxx-build
You have to apply patch to the linux-xxx-source tree.
This is kernel patched with colinux drivers.
Now apply your patch to this tree (linux-xxx-source)

When this is done, you can compile using
>make

in the linux-xxx-build directory.

If you need to change the .config copy your .conf in the
linux-xxx-build directory.

I hope this is OK. I do it. If something is wrong ....


Bye,
Paolo



On Fri, May 23, 2008 at 12:39 PM, Christopher David Chapman
<c.d...@re...> wrote:
> Hi,
>
> I am trying to get autofs working under fc8 and coLinux.
> Autofs is complaining that it is missing a kernel module autofs4.
> Ok, I thought I will need to add it into the kernel.
>
> Following the instruction in the FAQ (http://colinux.wikia.com/wiki/CoLinux_FAQ#Q19._How_do_I_build_my_own_kernel_for_coLinux.3F)
>
> I downloaded the latest stable source ball for coLinux and the kernel source for 2.6.22 from kernel.org
> Untar'd them both and cd'd into /usr/src/linux
>
> When trying the line "patch -p1 < (extraction-point)/colinux-20040529/patch/linux" /patch/linux is not found and if I try to do the 2.6.22 diff files by hand I get as far as "cobd-2.6.22.diff" and if fails saying there is no "drivers/block/cobd.c", which indeed there is not.
>
> I short, I'm lost
>
>
> Any clues much appreciated.
>
> Cheers
>  Chris
>
> "Why is Gaffa tape like the force?
> Because it has a light side, a dark side, and it holds the universe together!"
>
> ----------------===========----------------
> Christopher Chapman
> Systems Programmer ITNG
> School of Systems Engineering
> The University of Reading
>
> E-mail: c.d...@re...
> Phone:  +44 (0)118 3787664
>
> School of Systems Engineering
> The University of Reading
> PO Box 225
> Whiteknights
> Reading
> RG6 6AY
> ----------------===========----------------
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Rolling your own kernel

[Christopher D. C. <c.d...@re...>]

Hi,

I am trying to get autofs working under fc8 and coLinux.
Autofs is complaining that it is missing a kernel module autofs4.
Ok, I thought I will need to add it into the kernel.

Following the instruction in the FAQ (http://colinux.wikia.com/wiki/CoLinux_FAQ#Q19._How_do_I_build_my_own_kernel_for_coLinux.3F)

I downloaded the latest stable source ball for coLinux and the kernel source for 2.6.22 from kernel.org
Untar'd them both and cd'd into /usr/src/linux

When trying the line "patch -p1 < (extraction-point)/colinux-20040529/patch/linux" /patch/linux is not found and if I try to do the 2.6.22 diff files by hand I get as far as "cobd-2.6.22.diff" and if fails saying there is no "drivers/block/cobd.c", which indeed there is not.

I short, I'm lost


Any clues much appreciated.

Cheers
  Chris

"Why is Gaffa tape like the force?
Because it has a light side, a dark side, and it holds the universe together!"

----------------===========----------------
Christopher Chapman
Systems Programmer ITNG
School of Systems Engineering
The University of Reading

E-mail: c.d...@re...
Phone:  +44 (0)118 3787664

School of Systems Engineering
The University of Reading
PO Box 225
Whiteknights
Reading
RG6 6AY
----------------===========----------------

Re: [coLinux-users] hang on xp

[Paolo M. <pao...@gm...>]

>> A question :
>> ***************
>> Is it secure remove the ntdriver and install a new ntdriver without rebooting ?
>> Under linux it is possibile and it is secure, under XP I don't know.
>
> Yes, it's save, if you have verifyed, that the driver was unloaded.
> Under Windows the driver sometimes can not unload, if any daemon is
> active. So, I remember, you don't get an error. After --remove-driver
> you should check, that the driver is true unloaded. Only if no driver is
> installed, the next --install-driver is working.

OK, my old driver was unloaded correctly because I could install the new driver.

>> Now I have recompiled all (with my patch) and it is working OK. I have
>> recompiled qemu under colinux and all is OK.
>>
>> I underline that I have used
>>> make clean colinux kernel
>> to rebuild my version, because there is a little bug in colinux
>> buildind process.
>> Using make clean I am sure the building is OK.
>
> You have cleaned the Linux kernel?

No, I have not cleaned the Linux kernel.
I have only rebuild it using make in the linux-xxx-build directory
I thought that the linux building process automatically sees the
changes and recompiles the new source.
Maybe it was better to make clean and rebuild all the Linux kernel to
avoid dependecies problems.
.
>
> The source has no dependency to "include/linux/cooperative.h". You needs
> to remove all objects (*.o) and archives (*.a), which can have the
> console size compiled in.

Ok, is this done by make clean in the linux-xxx-build ? Is it right ?

>
> Your patch needs to rebuild all. All means coLinux ntkernel (linux.sys),
> daemons (colinux-console-nt) and the Linux kernel (vmlinux).
>
> I suggest you to use these patches:
>  console-size-40x120-colinux-0.7.3.patch
>  console-size-40x120-linux-2.6.22.18-co-0.7.3.patch
> There don't exist build time depency for console size between Linux
> kernel and ntkernel. Only rebuild the coLinux driver and daemons ("make
> clean && make colinux"), than reinstall the driver and use the new
> daemons to have the new console size.
> You not need to rebuild Linux kernel, after you have ones compiled with
> the runtime size set (CO_OPERATION_CONSOLE_SIZES).
>
> This patch for console sizes defines exist in 0.8.0 now, since yesterday
> ;-) Checkout the last source from SVN or from autobuild.
>
> I have also uploaded console with 40x120 for 0.8.0:
> http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080520-con-40x120/
>
> The same as 0.7.3:
> http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080521-con-40x120/

OK, Now I check my changes to understand if I have made some error
(maybe some dependencies problem).
In the future I will use your patch.

I think that the problem is mine (not a colinux problem) because in
the OOP trace I have seen the "cocon" string.
I will post if I will have the same error or if the error vanishes.

Then I small idea ....
Don't you think that in the main Makefile a "make clean-kernel" is missing ?
The "make clean" only clean colinux daemon and driver, the kernel is
not touched.
But maybe you prefer do it manually.....

Thanks for your time !

Paolo

Re: [coLinux-users] How to access a logical partition

[Harald W. <hwe...@gm...>]

Hello,

>Interesting. Now, we know, that coLinux and dd.exe can't read this
>partition type 0x8e. But why? Exist any other "read" for such type of
>drive?

I don't know of such processes. It's an almoust freshly setup Windows XP
Home SP2 without special processes or hacks.

When Windows was installed, only hda1 and hda2 were partitioned, the
remaining hard disk was unpartitioned space. Later, the space was
partitioned using the Debian installer.

>New idea:
>Use coLinux 0.8.0 and the "whole disk" as
>
>  scsi0=disk,\\?\Device\Harddisk0\Partition0
>
>This is an other driver inside Linux kernel. You should see partitions
>sda3, sda5 and so, directly after boot in the kernel messages.

It does not work directly this way...

scsi0 : Cooperative Linux SCSI Adapter
scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
coscsi0: unable to open device! rc: 1
coscsi0: unable to open device! rc: 1
coscsi0: unable to open device! rc: 1
coscsi0: unable to open device! rc: 1
sd 0:0:0:0: [sda] READ CAPACITY failed
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x00
sd 0:0:0:0: [sda] Sense not available.
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO
and FUA
sd 0:0:0:0: [sda] Attached SCSI disk

colinux:/tmp# dd if=/dev/sda of=test.img bs=512 count=1 
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0 seconds, Infinity B/s

colinux:/tmp# dd if=/dev/sda3 of=test.img bs=512 count=1
dd: opening `/dev/sda3': No such file or directory

But with a slight modification, it works really fine:

scsi0=disk,\Device\Harddisk0\Partition0

scsi0 : Cooperative Linux SCSI Adapter
scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO
and FUA
sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO
and FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: [sda] Attached SCSI disk

...and all partitions are visible and can be used inside coLinux, even
LVM works!

Thanks a lot!

Regards,
Harald

Re: [coLinux-users] hang on xp

[Henry N. <Hen...@Ar...>]

Hello Paolo,

Paolo Minazzi wrote:
> today for the first time I try your RC4 under XP.
> I have modified the console size X and Y.
> 
> I have do it several times, so I think to do it in a correct way.
> 
> This time I have change a little my patch.
> I have added two #define in include/linux/cooperative.h
> #define CONSOLE_SIZE_X 120
> #define CONSOLE_SIZE_Y 60
> 
> and all (kernel cocon.c, daemons and ntdriver) use
> #include <linux/cooperative.h>
> 
> and use CONSOLE_SIZE_X and CONSOLE_SIZE_Y.
> [...]
> After that I use the old colinux-daemon --remove-driver to remove the driver.
> Then I have installed the new package and install the new driver with
> the new colinux-daemon --install-driver
> I have removed and installed the ntdriver WITHOUT rebooting.

Have you replaced the file "vmlinux"? You should!

> I have worked for some hours, than I have tried to compile qemu under colinux.
> After a while I have had internal  OOP, like when under a real linux
> system I make an error coding a module.
> I saw several line and at the end of them a line with <cocon> and an address.
> I have thought I made an error in patching the size of console, so I
> didn't take note about the fault.
> I could using other windows opened, but I could not close the console-nt window.
> I could not close windowXP in a clean way.
> Using task manager I had the colinux-daemon at 99% of the CPU.
> 
> Now I have checked my changes and I think all was OK.

Yes, I saw  are all changes, I know. Think, you have changed correctly.

> Before trying the RC4 I used the original 0.7.2 with the endless
> patch. My console was 100 x 50. (not 120 x 60, like the new one).
> 
> A question :
> ***************
> Is it secure remove the ntdriver and install a new ntdriver without rebooting ?
> Under linux it is possibile and it is secure, under XP I don't know.

Yes, it's save, if you have verifyed, that the driver was unloaded.
Under Windows the driver sometimes can not unload, if any daemon is
active. So, I remember, you don't get an error. After --remove-driver
you should check, that the driver is true unloaded. Only if no driver is
installed, the next --install-driver is working.

> Now I have recompiled all (with my patch) and it is working OK. I have
> recompiled qemu under colinux and all is OK.
> 
> I underline that I have used
>> make clean colinux kernel
> to rebuild my version, because there is a little bug in colinux
> buildind process.
> Using make clean I am sure the building is OK.

You have cleaned the Linux kernel?

The source has no dependency to "include/linux/cooperative.h". You needs
to remove all objects (*.o) and archives (*.a), which can have the
console size compiled in.

Your patch needs to rebuild all. All means coLinux ntkernel (linux.sys),
daemons (colinux-console-nt) and the Linux kernel (vmlinux).

I suggest you to use these patches:
  console-size-40x120-colinux-0.7.3.patch
  console-size-40x120-linux-2.6.22.18-co-0.7.3.patch
There don't exist build time depency for console size between Linux
kernel and ntkernel. Only rebuild the coLinux driver and daemons ("make
clean && make colinux"), than reinstall the driver and use the new
daemons to have the new console size.
You not need to rebuild Linux kernel, after you have ones compiled with
the runtime size set (CO_OPERATION_CONSOLE_SIZES).

This patch for console sizes defines exist in 0.8.0 now, since yesterday
;-) Checkout the last source from SVN or from autobuild.

I have also uploaded console with 40x120 for 0.8.0:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080520-con-40x120/

The same as 0.7.3:
http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080521-con-40x120/

-- 
Henry N.

Re: [coLinux-users] How to access a logical partition

[Henry N. <Hen...@Ar...>]

Harald Weidner wrote:
> Henry Nestler:
> 
>> coLinux can copen the devie but can't ead any?
>> Is the device locked? Is the device opened by Windows perhaps?
> 
> I don't think so.
> 
>> Please try to read a block with the windows variant of dd:
>>  dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1
>>
>> Try the official names "\\?\Device\Harddisk0\Partition4" or
>> "\\?\Device\HarddiskVolume4", as you have seen from dd --list.
> 
> The result is:
> 
> D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1
> rawwrite dd for windows version 0.5.
> Written by John Newbigin <jn...@it...>
> This program is covered by the GPL.  See copying.txt for details
> Error reading file: 2 Das System kann die angegebene Datei nicht finden
> 0+0 records in
> 0+0 records out
> 
> Same for the HarddiskVolume4 partition, and also for the Partition 6.
> [...]
> 
> This means that Windows can access the two partitions of type 0x83 (Linux),
> but refuses access to type 0x8e (Linux LVM).

Interesting. Now, we know, that coLinux and dd.exe can't read this
partition type 0x8e. But why? Exist any other "read" for such type of
drive? Any tool for "raw read" any partition type?
Is Windows handling such devices and trying to made a disk array?
The other of interesting is, that dd.exe does not show the blocksize.

> While coLinux is running, none of the partitions can be accessed, but the
> error messages are different:
> 
> (Type 0x8e Linux LVM)
> D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1
> rawwrite dd for windows version 0.5.
> Written by John Newbigin <jn...@it...>
> This program is covered by the GPL.  See copying.txt for details
> Error reading file: 2 Das System kann die angegebene Datei nicht finden
> 0+0 records in
> 0+0 records out
> 
> (Type 0x83 Linux)
> D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition5 of=foo bs=512 count=1
> rawwrite dd for windows version 0.5.
> Written by John Newbigin <jn...@it...>
> This program is covered by the GPL.  See copying.txt for details
> Error native opening input file: 0 Der Vorgang wurde erfolgreich beendet

That is ok. coLinux has open the partition exclusivly.


New idea:
Use coLinux 0.8.0 and the "whole disk" as

  scsi0=disk,\\?\Device\Harddisk0\Partition0

This is an other driver inside Linux kernel. You should see partitions
sda3, sda5 and so, directly after boot in the kernel messages.

-- 
Henry N.

Re: [coLinux-users] How to access a logical partition

[Harald W. <hwe...@gm...>]

Hello,

Henry Nestler <Hen...@Ar...>:

>coLinux can copen the devie but can't ead any?
>Is the device locked? Is the device opened by Windows perhaps?

I don't think so.

>Please try to read a block with the windows variant of dd:
>  dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1
>
>Try the official names "\\?\Device\Harddisk0\Partition4" or
>"\\?\Device\HarddiskVolume4", as you have seen from dd --list.

The result is:

D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn...@it...>
This program is covered by the GPL.  See copying.txt for details
Error reading file: 2 Das System kann die angegebene Datei nicht finden
0+0 records in
0+0 records out

Same for the HarddiskVolume4 partition, and also for the Partition 6.
On the other two partitions, it works fine:

D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition5 of=foo bs=512 count=1
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn...@it...>
This program is covered by the GPL.  See copying.txt for details
1+0 records in
1+0 records out

This means that Windows can access the two partitions of type 0x83 (Linux),
but refuses access to type 0x8e (Linux LVM).

While coLinux is running, none of the partitions can be accessed, but the
error messages are different:

(Type 0x8e Linux LVM)
D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition4 of=foo bs=512 count=1
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn...@it...>
This program is covered by the GPL.  See copying.txt for details
Error reading file: 2 Das System kann die angegebene Datei nicht finden
0+0 records in
0+0 records out

(Type 0x83 Linux)
D:\coLinux>dd.exe if=\\?\Device\Harddisk0\Partition5 of=foo bs=512 count=1
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn...@it...>
This program is covered by the GPL.  See copying.txt for details
Error native opening input file: 0 Der Vorgang wurde erfolgreich beendet

Regards,
Harald

Re: [coLinux-users] A strange problem about using cofs in emacs

[netawater <net...@ya...>]

Henry Nestler <Hen...@Ar...> writes:

> netawater wrote:
>> I mount a windows partion as cofs in colinux with defaults option.
>> It works well when I use nano to edit a file, however I try to use
>> emacs to edit it and save it, it will report a error:
>> Debugger entered--Lisp error: (error "IO error writing 
>> /mnt/i/backup/history/backup.sh: Input/output error")
>>   write-region(1 109 "/mnt/i/backup/history/backup.sh" nil t 
>> "/mnt/i/backup/history/backup.sh")
>>   basic-save-buffer-2()
>>   basic-save-buffer-1()
>>   basic-save-buffer()
>>   save-buffer(1)
>>   call-interactively(save-buffer)
>> 
>> What is this problem? Thanks!
>
> I think it's a problem from asynchronious implementation. Cofs based opn
> fuse. Check for problems with "emacs + fuse"
>
> What coLinux version?
>
> Check the kernel logs ("dmesg"). Any errors on cofs?
>
> In coLinux 0.7.3 and 0.8.0 exist the option "nocache".
> Try this, for example:
>   mount -t cofs cofs0 -o nocache /mnt/windows
>
> -- 
> Henry N.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Thank you! I have updated colinux to 0.7.3 and it is OK now!
I haven't tried to use nocache option.

[coLinux-users] hang on xp

[Paolo M. <pao...@gm...>]

Hi Henry

today for the first time I try your RC4 under XP.
I have modified the console size X and Y.

I have do it several times, so I think to do it in a correct way.

This time I have change a little my patch.
I have added two #define in include/linux/cooperative.h
#define CONSOLE_SIZE_X 120
#define CONSOLE_SIZE_Y 60

and all (kernel cocon.c, daemons and ntdriver) use
#include <linux/cooperative.h>

and use CONSOLE_SIZE_X and CONSOLE_SIZE_Y.

These are my changes :

build/linux-2.6.22.18-source/drivers/video/console/cocon.c:	c->vc_cols
= CONSOLE_SIZE_X; // 80; BY PAOLO
build/linux-2.6.22.18-source/drivers/video/console/cocon.c:	c->vc_rows
= CONSOLE_SIZE_Y; // 25; BY PAOLO
build/linux-2.6.22.18-source/include/linux/cooperative.h:#define
CONSOLE_SIZE_X 120  // BY PAOLO
build/linux-2.6.22.18-source/include/linux/cooperative.h:#define
CONSOLE_SIZE_Y 60   // BY PAOLO
stable-colinux-20080512/src/colinux/kernel/monitor.c:#include
<linux/cooperative.h> // BY PAOLO
stable-colinux-20080512/src/colinux/kernel/monitor.c:	rc =
co_console_create(CONSOLE_SIZE_X, CONSOLE_SIZE_Y, 0, &cmon->console);
// 80,25 BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:#include
<linux/cooperative.h> // BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:
       r.bottom = fs.Y * CONSOLE_SIZE_Y;  // 25 BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:
       r.right = fs.X * CONSOLE_SIZE_X;   // 80 BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:	size.X
= CONSOLE_SIZE_X; // 80 BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:
       size.Y = CONSOLE_SIZE_Y; // 25 BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:
       region.Right = CONSOLE_SIZE_X-1;  // 79 BY PAOLO
stable-colinux-20080512/src/colinux/os/winnt/user/console-nt/widget.cpp:
       region.Bottom = CONSOLE_SIZE_Y-1; // 24 BY PAOLO

As you can see I have inserted a comment "BY PAOLO" at every change.

All is compiled OK (under vmware, slackware 11.0).

After that I use the old colinux-daemon --remove-driver to remove the driver.
Then I have installed the new package and install the new driver with
the new colinux-daemon --install-driver
I have removed and installed the ntdriver WITHOUT rebooting.

I have worked for some hours, than I have tried to compile qemu under colinux.
After a while I have had internal  OOP, like when under a real linux
system I make an error coding a module.
I saw several line and at the end of them a line with <cocon> and an address.
I have thought I made an error in patching the size of console, so I
didn't take note about the fault.
I could using other windows opened, but I could not close the console-nt window.
I could not close windowXP in a clean way.
Using task manager I had the colinux-daemon at 99% of the CPU.

Now I have checked my changes and I think all was OK.

Before trying the RC4 I used the original 0.7.2 with the endless
patch. My console was 100 x 50. (not 120 x 60, like the new one).

A question :
***************
Is it secure remove the ntdriver and install a new ntdriver without rebooting ?
Under linux it is possibile and it is secure, under XP I don't know.

Now I have recompiled all (with my patch) and it is working OK. I have
recompiled qemu under colinux and all is OK.

I underline that I have used
> make clean colinux kernel
to rebuild my version, because there is a little bug in colinux
buildind process.
Using make clean I am sure the building is OK.

I realize that it is difficult trace an error with this information.
But I have decided to post the error.

Regards
Paolo

Re: [coLinux-users] A strange problem about using cofs in emacs

[Henry N. <Hen...@Ar...>]

netawater wrote:
> I mount a windows partion as cofs in colinux with defaults option.
> It works well when I use nano to edit a file, however I try to use
> emacs to edit it and save it, it will report a error:
> Debugger entered--Lisp error: (error "IO error writing 
> /mnt/i/backup/history/backup.sh: Input/output error")
>   write-region(1 109 "/mnt/i/backup/history/backup.sh" nil t 
> "/mnt/i/backup/history/backup.sh")
>   basic-save-buffer-2()
>   basic-save-buffer-1()
>   basic-save-buffer()
>   save-buffer(1)
>   call-interactively(save-buffer)
> 
> What is this problem? Thanks!

I think it's a problem from asynchronious implementation. Cofs based opn
fuse. Check for problems with "emacs + fuse"

What coLinux version?

Check the kernel logs ("dmesg"). Any errors on cofs?

In coLinux 0.7.3 and 0.8.0 exist the option "nocache".
Try this, for example:
  mount -t cofs cofs0 -o nocache /mnt/windows

-- 
Henry N.

Re: [coLinux-users] Stability of coFS

[Henry N. <Hen...@Ar...>]

Wolfram Wadepohl wrote:
> how stable is cofs? Shall i use cofs to access files on a corporate windows 
>   file server mapped to a local drive letter, or better not?

cofs is save to use for copy files between host and Linux.
For compiling it's usable, but very slow. The file is opened and closed
for every block you write or read.

Data integry is very stable. I can do loop mounts to manage coLinux
images, copying big zipped files from Linux to host and back. Never got
wrong datas.

Only the timing problems can stop some programs. (see the mail today
about emacs)

cofs is asynchron. At the time the file is written, colinux opens the
file exclusivly for this "write" and returns very fast to Linux. Some
programs have troubble with it.

Remember, that cofs based on fuseFS. All what you would do with fuse,
you can also do with cofs.

-- 
Henry N.

[coLinux-users] A strange problem about using cofs in emacs

[netawater <net...@ya...>]

I mount a windows partion as cofs in colinux with defaults option.
It works well when I use nano to edit a file, however I try to use
emacs to edit it and save it, it will report a error:
Debugger entered--Lisp error: (error "IO error writing 
/mnt/i/backup/history/backup.sh: Input/output error")
  write-region(1 109 "/mnt/i/backup/history/backup.sh" nil t 
"/mnt/i/backup/history/backup.sh")
  basic-save-buffer-2()
  basic-save-buffer-1()
  basic-save-buffer()
  save-buffer(1)
  call-interactively(save-buffer)

What is this problem? Thanks!

[coLinux-users] Stability of coFS

[Wolfram W. <Wol...@ek...>]

Hello,

how stable is cofs? Shall i use cofs to access files on a corporate windows 
  file server mapped to a local drive letter, or better not?

-- 
Schöne Grüße aus Reutlingen

Wolfram Wadepohl
Forschung & Entwicklung

E&K AUTOMATION
Indumat GmbH & Co. KG
Siemensstraße 3
72766 Reutlingen
Deutschland

Tel.  +49 7121 514-289
Fax   +49 7121 514-299
eMail Wol...@ek...
       W.W...@ie...
WWW   http://www.ek-automation.com
       http://www.indumat.de

Diese Nachricht ist keine geschäftliche Mitteilung i. S. des EHUG.

Bitte senden Sie mir keine Word- oder PowerPoint- (tm Microsoft) oder OOXML 
Anhänge.
Senden Sie mir einfachen Text, HTML oder PDF(ISO/IEC 32000).
Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html

Re: [coLinux-users] How to access a logical partition

[Harald W. <hwe...@gm...>]

Hello Henry,

Henry Nestler <Hen...@Ar...>:

>I have one free partition. How can I setup it as "Linux LVM"?
>Short steps or a link to any simple help side would help me, please.

The only thing you need to do to reproduce the behavior is to
set the partition type to 8e ("Linux LVM / Solaris") with fdisk.

If you want to make further experiments with LVM, you should boot
a diskless Linux (e.g. Knoppix) and  set the partition type to 8e.

Then:
create a LVM physical volume on the partition:
  pvcreate /dev/hda8

create a volume group:
  vgcreate test /dev/hda8

create a logical volume within the volume group
  lvcreate -n vol1 -L 1G test

The volume group's device is now visible under /dev/test/vol1 , which
is a symbolic link to /dev/mapper/test-vol1 . You can handle it like
an ordinary partition, e.g.

mkfs.ext3 /dev/test/vol1
mount -t ext3 /dev/test/vol1 /mnt/volume1

Use the commands pvs, vgs, and lvs to list the physical volumes,
volume groups, and logical volumes on your system.

Use pvscan, vgscan, and lvscan to rescan the LVM configuration
after attaching a device or making externally changes.

Thank you for your support!

Regards,
Harald

Re: [coLinux-users] How to access a logical partition

[Robert B. <ro...@ro...>]

On Tue, 20 May 2008 01:51:14 +0200
Henry Nestler <Hen...@Ar...> wrote:

> I have one free partition. How can I setup it as "Linux LVM"?
> Short steps or a link to any simple help side would help me, please.

http://www.gentoo.org/doc/en/lvm2.xml

is what I follow. I know it's Gentoo specific, but the LVM parts are
pretty much distro agnostic...

Unless your / is on the LVM, it's pretty straight forward to use...

Rob.

Re: [coLinux-users] How to access a logical partition

[Henry N. <Hen...@Ar...>]

Harald Weidner wrote:
> hda5 type "Linux LVM" and an LVM physical volume
> hda6 type "Linux", but contains also an LVM PV
> hda7 type "Linux LVM" but contains an ext3 partition
> hda8 type "Linux" and contains an ext3 partition
> 
> The results:
> 
> Only the devices of type "Linux" are recognized by coLinux.
> The partitions of type "Linux LVM" are ignored and yield to the
> error message "No such device" when being accessed with cat or dd.
> 
> The ext3 partition hda8 can be mounted without further problems into
> colinux.
> 
> The LVM partition hda6 is not recognized by LVM inside coLinux, unless
> the following parameter is set in /etc/lvm/lvm.conf:
> 
>     # List of pairs of additional acceptable block device types found
>     # in /proc/devices with maximum (non-zero) number of partitions.
>     types = [ "cobd", 32 ]
> 
> 
> All in all, this is not nice but solves my problems accessing a logical
> partition containing LVM.
> 
> 
>> That's a strong result. In normal case, all Linux Partition have a line
>>  "Fixed hard disk media. Block size = 512"
>> Is that normal for LVM, that they don't have? I don't know.
> 
> With the above configuration, it looks like:
> 
> [...]
> \\?\Device\Harddisk0\Partition4
>   link to \\?\Device\HarddiskVolume4
>   size is 55002415104 bytes
> \\?\Device\Harddisk0\Partition5
>   link to \\?\Device\HarddiskVolume5
>   Fixed hard disk media. Block size = 512
>   size is 55002415104 bytes
> \\?\Device\Harddisk0\Partition6
>   link to \\?\Device\HarddiskVolume6
>   size is 55002415104 bytes
> \\?\Device\Harddisk0\Partition7
>   link to \\?\Device\HarddiskVolume7
>   Fixed hard disk media. Block size = 512
>   size is 55306750464 bytes
> [...]
> 
> E.g. all partitions of type "Linux" are displayed with the "Fixed hard
> disk media. Block size = 512" line, but not the "Linux LVM" partitions.
> It does not matter wether the partitions actually contain LVM or ext3.

I have one free partition. How can I setup it as "Linux LVM"?
Short steps or a link to any simple help side would help me, please.

-- 
Henry N.

Re: [coLinux-users] How to access a logical partition

[Henry N. <Hen...@Ar...>]

Harald Weidner wrote:
>>> colinux:~# cat /dev/cobd2
>>> cat: /dev/cobd2: No such device
> 
> [...]
> 
>> If not, run the coLinux debugger to see more about problems an the
>> windows detailed error message. Run the debugger:
>>  colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml
>> Than try to read one block.
>> Stop the debugger. Open the file debug.xml with IE or notepad. Typicaly
>> at the end you should see the error from block device read and the
>> Windows internal error code.
> 
> The according messages are:
> 
> - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c"
>   timestamp="00000016.3900969652" local_index="668" facility="0"
>   function="co_os_file_block_get_size" line="212" level="10"
>   driver_index="802">
>   <string>device \Device\Harddisk0\Partition4</string> 
>   </log>
> - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c"
>   timestamp="00000016.3900971984" local_index="669" facility="0"
>   function="co_os_file_block_detect_size_harddisk" line="154" level="10"
>   driver_index="803">
>   <string>fail status C000000E</string> 
>   </log>

The translated error message from include/ddk/ntstatus.h:
STATUS_NO_SUCH_DEVICE ((NTSTATUS)0xC000000EL)
That means the ZwDeviceIoControlFile(..., IOCTL_DISK_GET_LENGTH_INFO,
...) does not work. That's harmless.

> - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c"
>   timestamp="00000016.3900972192" local_index="670" facility="0"
>   function="co_os_file_block_detect_size_binary_search" line="99" level="3"
>   driver_index="804">
>   <string>size is zero</string> 
>   </log>

coLinux can copen the devie but can't ead any?
Is the device locked? Is the device opened by Windows perhaps?

Please try to read a block with the windows variant of dd:
  dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1

Try the official names "\\?\Device\Harddisk0\Partition4" or
"\\?\Device\HarddiskVolume4", as you have seen from dd --list.

-- 
Henry N.

Re: [coLinux-users] [ExternalEmail] Problems accessing postgres db on my windows machine from colinux

[<Dav...@cs...>]

Sorry to everyone.
 
I havent enabled external connections to my postgres db.

Doh!
 
Thanks in advance
 
David

	-----Original 

	-----Original Message----- 
	From: Miron, David (LI, Armidale) 
	Sent: Mon 19/05/2008 3:15 PM 
	To: Miron, David (LI, Armidale); 'col...@li...' 
	Cc: 
	Subject: RE: [ExternalEmail] [coLinux-users] Problems accessing postgres db on my windows machine from colinux
	
	

	I should have mnentione dthat I also have tuntap working and can access

	My tomcat page using http://192.168.0.1:8080 <http://192.168.0.1:8080/>  from colinux

	 

	D

	 

	
  _____  


	From: Miron, David (LI, Armidale) 
	Sent: Monday, 19 May 2008 2:53 PM
	To: Miron, David (LI, Armidale); col...@li...
	Subject: RE: [ExternalEmail] [coLinux-users] Problems accessing postgres db on my windows machine from colinux

	 

	I forgot to mention I am using windows XP.

	 

	D

	 

	
  _____  


	From: col...@li... [mailto:col...@li...] On Behalf Of Miron, David (LI, Armidale)
	Sent: Monday, 19 May 2008 2:19 PM
	To: col...@li...
	Subject: [ExternalEmail] [coLinux-users] Problems accessing postgres db on my windows machine from colinux

	 

	 

	Hi All

	 

	I have been using colinux for about 6 months now with the fedora image with no issues. SLiRP works fine but I am little confused with this current problem.

	 

	I have a postgres db running on my windows machine on the standard port 5432.  I also have tomcat running as well.  I can access the tomcat homepage from colinux usingthe url

	http://my-ip-address:8080

	 

	No problem but cannot connect to the db from colinux?

	 

	 

	I have TAP installed on 192.168.0.1

	 

	Am I missing something here?  

	 

	Any help much appreciated.

	 

	Kind regards

	 

	David

	 

	Dr David Miron

	CSIRO

	02 6776 1375