colinux-users — coLinux users mailing list

Re: [coLinux-users] does the usb network adapter work on colinux ?

[George P B. <geo...@gm...>]

rider wrote:
> i am a begineer of colinux.
> i use the debian sarge on my colinux with kernel 2.6.12-co-0.7.1 
> i would like to build a dhcp server , and there is only one network
> interface for use.
> So i try to plug a usb network adapter for expansion , but it doesn't work .
> Does anyone one how the usb network adapter work on colinux?
> thanks...
>   

coLinux for Windows or coLinux for Linux?  You didn't say.

Anyways, coLinux will see/use the host's network device. so you get it
working on the host, then use TAP adapter(s) w/host based bridging, or
winpcap for coLinux-based bridging.  At which point coLinux should be
able to see the additional network when configured accordingly.

At any rate, IT SHOULD be do able with coLinux and the right configuration.
George

Re: [coLinux-users] cannot install debian from iso

[Holger K. <hol...@gm...>]

Henry Nestler schrieb:
> Hello Wolfram,
> 
> Wolfram Wadepohl wrote:
>> Henry Nestler schrieb:
>>
>>> Wolfram Wadepohl wrote:

>>> Testings under a Linux:
>> used Knoppix 5.2
>>> Copy the file i:\initrd into a Linux, and try to mount it as loop:
>>>    mount -o loop,ro initrd /mnt
>>> Check the filesystem of the file initrd:
>>>    fsck -f initrd
>> losetup /dev/loop0 initrd
>> fsck -f /dev/loop0
>> cannot find ext2 superblock (oroginal output was german)
> 
> What does losetup do? If that non mount it, you can not check it with 
> fsck. View what are currently mountet after losetup.  But better, you 
> does my steps.  Think, losetup use a ramdisk, not an initrd file.
> 
> Perhaps do "modprobe loop" before "mount -o loop,ro initrd /mnt"

losetup just connects the file to the loop device without assigning a
mountpoint. You need that if you have additional parameters for the loop
device that mount does not now.

And fsck doesn't work on mounted filesystems.

What he did will work, but he should try mount /dev/loop0 to find what
filesystem is on initrd.

Re: [coLinux-users] cannot install debian from iso

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

Hello Wolfram,

Wolfram Wadepohl wrote:
> Henry Nestler schrieb:
> 
>> Wolfram Wadepohl wrote:
>>
>>> trying to install debian etch rc2 businesscard image as described in the 
>>> "colinx: Install debian From Iso" every attempt failed.
>>>
>>> I've extracted initrd.gz from iso iamge and unpacked to initrd.
>>> My colinux.xml look like:
>>> (...)
>>>     <block_device index="3" path="\DosDevices\i:\initrd" enabled="true" />
>>>     <bootparams>root=/dev/cobd3</bootparams>
>>>     <initrd path="initrd.gz" />
>>>     <image path="vmlinux" />
>>> (...)
>>>
>>> Every time starting the colinux-daemon i get the error that /dev/codb3 
>>> cannot be mounted.
>> [...]
>> Testings under a Linux:
> used Knoppix 5.2
>> Copy the file i:\initrd into a Linux, and try to mount it as loop:
>>    mount -o loop,ro initrd /mnt
> 
>> Check the filesystem of the file initrd:
>>    fsck -f initrd
> losetup /dev/loop0 initrd
> fsck -f /dev/loop0
> cannot find ext2 superblock (oroginal output was german)

What does losetup do? If that non mount it, you can not check it with 
fsck. View what are currently mountet after losetup.  But better, you 
does my steps.  Think, losetup use a ramdisk, not an initrd file.

Perhaps do "modprobe loop" before "mount -o loop,ro initrd /mnt"

Try this before you mounts it:
This should say, that is a filesystem Minix, or ext2.
"LANG=C file initrd"
   initrd: Minix filesystem, 30 char names

>> Last:
>> Use an newer coLinux 0.8.0 and run it with option "-v 3".
> where can i find this? tried www.colinux.org but could not find a link

http://www.colinux.org/snapshots/

faster from germman:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070302-Snapshot/

-- 
Henry

Re: [coLinux-users] cannot install debian from iso

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

Henry Nestler schrieb:

> Wolfram Wadepohl wrote:
>=20
>>trying to install debian etch rc2 businesscard image as described in th=
e=20
>>"colinx: Install debian From Iso" every attempt failed.
>>
>>I've extracted initrd.gz from iso iamge and unpacked to initrd.
>>My colinux.xml look like:
>>(...)
>>     <block_device index=3D"3" path=3D"\DosDevices\i:\initrd" enabled=3D=
"true" />
>>     <bootparams>root=3D/dev/cobd3</bootparams>
>>     <initrd path=3D"initrd.gz" />
>>     <image path=3D"vmlinux" />
>>(...)
>>
>>Every time starting the colinux-daemon i get the error that /dev/codb3 =

>>cannot be mounted.
>=20
>=20
> Double check, that you have no typofixies in the config.  cobd and codb=
=20
> are not the same.
checked an OK
> Double check that, the file exists. Try a "DIR I:\initrd" on same=20
> windows prompt, you starts coLinux.
checked and OK
> Do not run coLinux in a CygWin shell.  Use simple CMD.EXE.
used cmd.exe
> Check, that I:\INITRD is readable file and not on a network.  Copy it t=
o=20
> other dir, for sample under C:\TEMP and use it as C:\TEMP\initrd.
checked and OK
>=20
> Testings under a Linux:
used Knoppix 5.2
> Copy the file i:\initrd into a Linux, and try to mount it as loop:
>    mount -o loop,ro initrd /mnt

> Check the filesystem of the file initrd:
>    fsck -f initrd
losetup /dev/loop0 initrd
fsck -f /dev/loop0
cannot find ext2 superblock (oroginal output was german)
>=20
> Some distries does ship initrd.gz not as compressed image file. They us=
e=20
> a CPIO archicves.  CPIO can not use as cobd.  You need to transform it =

> into an image file (create an empty image with dd if=3D/dev/zero of=3Di=
mage=20
> ..., mkfs ..., mount -o loop ..., unpack the cpio archive into the=20
> mounted image).
maybe i have to do this ...
>=20
> Last:
> Use an newer coLinux 0.8.0 and run it with option "-v 3".
where can i find this? tried www.colinux.org but could not find a link
>=20


--=20
Sch=F6ne Gr=FC=DFe aus Reutlingen

Wolfram Wadepohl
Forschung & Entwicklung

E&K AUTOMATION
Indumat GmbH & Co. KG
Siemensstra=DFe 3
72766 Reutlingen
Deutschland

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

Diese Nachricht ist keine gesch=E4ftliche Mitteilung i. S. des EHUG.

Bitte senden Sie mir keine Word- oder PowerPoint- (tm Microsoft) Anh=E4ng=
e.
Senden Sie mir einfachen Text, HTML oder PDF.
Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html

[coLinux-users] does the usb network adapter work on colinux ?

[rider <rs...@gm...>]

hello, all

i am a begineer of colinux.
i use the debian sarge on my colinux with kernel 2.6.12-co-0.7.1 
i would like to build a dhcp server , and there is only one network
interface for use.
So i try to plug a usb network adapter for expansion , but it doesn't work .
Does anyone one how the usb network adapter work on colinux?
thanks...
-- 
View this message in context: http://www.nabble.com/does-the-usb-network-adapter-work-on-colinux---tf3478857.html#a9708870
Sent from the colinux-users mailing list archive at Nabble.com.

Re: [coLinux-users] NFS booting?

[Ph. M. <phi...@bm...>]

Hello Henry!

On Tuesday 27 March 2007 22:26, Henry Nestler wrote:
> Here you can try:
> http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070327-nfskernel/
Thank you very much.
Sadly I still get the same error. I'll investigate if maybe my network 
settings are wrong -- although the linux kernel sees a eth0 device.

Maybe CONFIG_IP_PNP is not set? 


Regards,

Phil

Re: [coLinux-users] cannot install debian from iso

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

Wolfram Wadepohl wrote:
> Hello,
> 
> trying to install debian etch rc2 businesscard image as described in the 
> "colinx: Install debian From Iso" every attempt failed.
> 
> I've extracted initrd.gz from iso iamge and unpacked to initrd.
> My colinux.xml look like:
> (...)
>      <block_device index="3" path="\DosDevices\i:\initrd" enabled="true" />
>      <bootparams>root=/dev/cobd3</bootparams>
>      <initrd path="initrd.gz" />
>      <image path="vmlinux" />
> (...)
> 
> Every time starting the colinux-daemon i get the error that /dev/codb3 
> cannot be mounted.

Double check, that you have no typofixies in the config.  cobd and codb 
are not the same.
Double check that, the file exists. Try a "DIR I:\initrd" on same 
windows prompt, you starts coLinux.
Do not run coLinux in a CygWin shell.  Use simple CMD.EXE.
Check, that I:\INITRD is readable file and not on a network.  Copy it to 
other dir, for sample under C:\TEMP and use it as C:\TEMP\initrd.

Testings under a Linux:
Copy the file i:\initrd into a Linux, and try to mount it as loop:
   mount -o loop,ro initrd /mnt
Check the filesystem of the file initrd:
   fsck -f initrd

Some distries does ship initrd.gz not as compressed image file. They use 
a CPIO archicves.  CPIO can not use as cobd.  You need to transform it 
into an image file (create an empty image with dd if=/dev/zero of=image 
..., mkfs ..., mount -o loop ..., unpack the cpio archive into the 
mounted image).

Last:
Use an newer coLinux 0.8.0 and run it with option "-v 3".

-- 
Henry

Re: [coLinux-users] NFS booting?

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

Ph. Marek wrote:
> On Monday 26 March 2007 16:05, George P Boutwell wrote:
>> Ph. Marek wrote:
>>> I think it's not possible with NFS as module.
>>> So, here's my question again: Can somebody build the colinux kernel with
>>> nfs (and the other requirements) built-in?
>>>
>> a module or easier to just make it required to be built in).  At any
>> rate.  What coLinux version are you using for this attempt to boot from
>> NFS?
> Well, I'm just experimenting right now, so any current snapshot is fine. I 
> deployed the 2.6.17 modules on the NFS server, but that's no problem.
> The newer the better :-)

Here you can try:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070327-nfskernel/

-- 
Henry

[coLinux-users] cannot install debian from iso

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

Hello,

trying to install debian etch rc2 businesscard image as described in the =

"colinx: Install debian From Iso" every attempt failed.

I've extracted initrd.gz from iso iamge and unpacked to initrd.
My colinux.xml look like:
(...)
     <block_device index=3D"3" path=3D"\DosDevices\i:\initrd" enabled=3D"=
true" />
     <bootparams>root=3D/dev/cobd3</bootparams>
     <initrd path=3D"initrd.gz" />
     <image path=3D"vmlinux" />
(...)

Every time starting the colinux-daemon i get the error that /dev/codb3=20
cannot be mounted.

What's going wrong?

--=20
Sch=F6ne Gr=FC=DFe aus Reutlingen

Wolfram Wadepohl
Forschung & Entwicklung

E&K AUTOMATION
Indumat GmbH & Co. KG
Siemensstra=DFe 3
72766 Reutlingen
Deutschland

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

Diese Nachricht ist keine gesch=E4ftliche Mitteilung i. S. des EHUG.

Bitte senden Sie mir keine Word- oder PowerPoint- (tm Microsoft) Anh=E4ng=
e.
Senden Sie mir einfachen Text, HTML oder PDF.
Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

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

Jason Ahrens wrote:
> Henry Nestler wrote:
>> Ok. You have shutting down the linux by sending CTRL-ALT-DEL key code. 
>> After this should be follow a "daemon: service stopped." in the event
>> logger.
>>
>> Have you set to halt in your /etc/inittab?  If not, try this:
>>    # What to do when CTRL-ALT-DEL is pressed.
>>    ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -h now
>>   
> 
> Thanks! This seems to have done the trick!
> 
> I run a 'scratch' Gentoo image, so the default for that line was '-r
> now'. Worked fine in 0.6.4, but I guess the newer revisions have
> modified the behaviour a bit.

Yes, older coLinux has no "reboot". So, "-r" and "-h" was the same.

Found in changelog for the 0.7.0:
2005-02-12T18:35:53  da-x at colinux.org

	Improve rebooting support.
	 * Reason of Linux's termination is now brought to the knowledge
	   of the daemon, which decides whether to reboot or to abort.
	 * Ctrl-Alt-Shift-Del now sends Ctrl-Alt-Del in console-nt.
-- 
Henry

Re: [coLinux-users] NFS booting?

[Ph. M. <phi...@bm...>]

On Monday 26 March 2007 16:05, George P Boutwell wrote:
> Ph. Marek wrote:
> > I think it's not possible with NFS as module.
> > So, here's my question again: Can somebody build the colinux kernel with
> > nfs (and the other requirements) built-in?
> >
> :(.  That I suppose makes senses (might be hard to boot from NFS if it's
>
> a module or easier to just make it required to be built in).  At any
> rate.  What coLinux version are you using for this attempt to boot from
> NFS?
Well, I'm just experimenting right now, so any current snapshot is fine. I 
deployed the 2.6.17 modules on the NFS server, but that's no problem.
The newer the better :-)




Regards,

Phil

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

[Jason A. <ja...@co...>]

Henry Nestler wrote:
> Ok. You have shutting down the linux by sending CTRL-ALT-DEL key code. 
> After this should be follow a "daemon: service stopped." in the event
> logger.
>
> Have you set to halt in your /etc/inittab?  If not, try this:
>    # What to do when CTRL-ALT-DEL is pressed.
>
>    ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -h now
>   

Thanks! This seems to have done the trick!

I run a 'scratch' Gentoo image, so the default for that line was '-r
now'. Worked fine in 0.6.4, but I guess the newer revisions have
modified the behaviour a bit.

So I also updated the Wiki I made with the info at
http://colinux.wikia.com/wiki/Gentoo_Installing_From_Scratch

Jason

Re: [coLinux-users] NFS booting?

[George P B. <geo...@gm...>]

Ph. Marek wrote:
> I now tried that, but it doesn't work. I always get "Please append a correct 
> root= option...".
> Looking into the sources I see this (from lines 1697 on):
> 	config ROOT_NFS
> 	       bool "Root file system on NFS"
> 	       depends on NFS_FS=y && IP_PNP
> (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=fs/Kconfig/Kconfig;h=3c4886b849f57e21d4fbde30fd7b633139165790;hb=HEAD)
>
>
> I think it's not possible with NFS as module.
> So, here's my question again: Can somebody build the colinux kernel with nfs 
> (and the other requirements) built-in?
>
>   
:(.  That I suppose makes senses (might be hard to boot from NFS if it's
a module or easier to just make it required to be built in).  At any
rate.  What coLinux version are you using for this attempt to boot from NFS?

Thanks,

George

Re: [coLinux-users] NFS booting?

[Ph. M. <phi...@bm...>]

Hello Henry!

Thank you for your tip.

On Sunday 25 March 2007 23:45, Henry Nestler wrote:
...
> > In the current snapshots I found nfs.ko - but that would be needed for
> > booting!
> > Is there some version that has NFS compiled in?
> No.
>
> You can try to boot with your own initrd?
...
> This are my some ideas, have never checked such boot.
I now tried that, but it doesn't work. I always get "Please append a correct 
root= option...".
Looking into the sources I see this (from lines 1697 on):
	config ROOT_NFS
	       bool "Root file system on NFS"
	       depends on NFS_FS=y && IP_PNP
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=fs/Kconfig/Kconfig;h=3c4886b849f57e21d4fbde30fd7b633139165790;hb=HEAD)


I think it's not possible with NFS as module.
So, here's my question again: Can somebody build the colinux kernel with nfs 
(and the other requirements) built-in?


Regards,

Phil

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

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

Hello Jason,

George P Boutwell wrote:
>> Jason Ahrens wrote:
>>   
>>> I'm trying out the 0.7.1 pre-release, so far everything is working
>>> perfect except shut down.
>>>
>>> I run coLinux as a service on Windows XP, and what happens when
>>> 'shutting down' is, the Linux portion seems to shut down fine,
>>> eventually reaching  a safe to power off point, but the colinux-daemon
>>> doesn't properly terminate. Windows thinks the service is still
>>> 'shutting down' and it never reaches a 'power off' point. If I manually
>>> kill the colinux-daemon process, Windows then restarts it right away.
>>> Oddness.
>>>
>>> [...snip...]
>>> Found in the Application log:
>>> [...snip...]
>>> daemon: service control STOP.

Ok. You have shutting down the linux by sending CTRL-ALT-DEL key code. 
After this should be follow a "daemon: service stopped." in the event
logger.

Have you set to halt in your /etc/inittab?  If not, try this:
   # What to do when CTRL-ALT-DEL is pressed.

   ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -h now

> I'm curious, too, if other people who run coLinux as  service have seen
> this problem or not.  Other than that Jason, we are looking into this
> problem and should have an patch applied once we figure out what the
> issue is.  It would help, alot to know your command-line, especially the
> options that you are sending to coLinux when you register your service.

Service is normal stopping in 0.7.1 prerelease with build date 20070319
and 20070101.  I do shutting down coLinux in the Windows Service 
Manager, or on Windows command line 'net stop "Cooperative Linux"'. 
With -h and also with -r in the inittab.
I see no problems.  colinux-daemon.exe exits after linux is down.

-- 
Henry

Re: [coLinux-users] NFS booting?

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

Ph. Marek wrote:
> I wanted to try colinux, and boot from an NFS server.
> So my configuration file looks like this:
> 
> 	ip=<myip>:<server>:<gw>:<netmask>
> 	root=nfs
> 	nfsroot=<path>
> 	nfsaddrs=<server>
> 	init=/bin/bash
> 	kernel=vmlinuz
> 	eth0=tuntap
> 	mem=64
> This parameters I took from bootparam(7).
> 
> 
> On starting colinux-daemon I get
> 	...
> 	VFS: Cannot open root device "nfs" or unknown-block(0,0)
> 	Please append a correct "root=" boot option
> 	Kernel panic: ...
> 
> In the current snapshots I found nfs.ko - but that would be needed for 
> booting!
> Is there some version that has NFS compiled in?

No.

You can try to boot with your own initrd?
Unpack the initrd.gz, mount it as loop, edit the script 'linuxrc' to
load the module (insmod sunrpc; insmod lockd; insmod nfs).  Copy the
modules to /lib/modules in the initrd system.  You not need all modules,
the 3 are enouth.   Unmount the loop and compress initrd to an initrd.gz
Than add
	initrd=initrd.gz
to your coLinux configuration.

Best way is, to view inito initrd.gz from your distribution, to see how
nfs boot would work.

With the initrd.gz from coLinux you would have problems, becuase it
tries to install modules in an block device, that is mounted as
/mnt/linux.  For your nfs boot you should remove the complete block for
installing modules after the echo "Mounting /", and replace it with your
lines for loading nfs modules.  $ROOTDEv is "nfs" in your case.  So, you
can create an alternate 'if'-condition for normal and the other for nfs
boot.

This are my some ideas, have never checked such boot.

-- 
Henry

[coLinux-users] para adelante

[Enesto G. <ega...@tu...>]

estoy de acuerdo

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

[Jason A. <ja...@co...>]

George P Boutwell wrote:
> I'm curious, too, if other people who run coLinux as  service have seen
> this problem or not.  Other than that Jason, we are looking into this
> problem and should have an patch applied once we figure out what the
> issue is.  It would help, alot to know your command-line, especially the
> options that you are sending to coLinux when you register your service.
>   

I posted all the requested information to the list yesterday :)

Unfortunately it topped out just a little over 'maxsize' so went to the
admin for approval. Hopefully he approves it soon to let it through!


Here though is part of the post, minus the log outputs which is what
caused it to go oversize.:

Henry Nestler wrote:

> > Your command line for installing the service and the config file would 
> > be interesting, and the current directory where you stays on installing 
> > the service.
> >   
>   
C:\Program Files\coLinux>colinux-daemon --install-service "coLinux -
Lynx" @d:\coLinux\Configuration\Lynx.config

(Lynx.config)
kernel="c:\Program Files\coLinux\vmlinux"
mem=256
cobd0=d:\coLinux\FileSystems\Lynx\root_fs
cobd1=d:\coLinux\FileSystems\Lynx\swap_file
eth0=tuntap,"TAP"
root=/dev/cobd0
ro

> > CoLinux 0.7.1 use a new internal parameter for starting service, if path 
> > for installing and running is differ.  This could be a problem?
> > Are you shure, to re-installed the service after update from 0.6.4 to 
> > 0.7.1?  Re-installing means two calls --remove-service and --remove-service.
> >   
>   
Yes. I clean-installed Windows onto an empty hard disk then installed
coLinux 0.7.1 (just transfered the root_fs file), so I know there was no
prior 0.6.4 config cruft.

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

[George P B. <geo...@gm...>]

Jason Ahrens wrote:
> Was just wondering if anyone might have any suggestions. If not, I guess
> I'll have to go back to 0.6.4.
>
> Jason
>
> Jason Ahrens wrote:
>   
>> I'm trying out the 0.7.1 pre-release, so far everything is working
>> perfect except shut down.
>>
>> I run coLinux as a service on Windows XP, and what happens when
>> 'shutting down' is, the Linux portion seems to shut down fine,
>> eventually reaching  a safe to power off point, but the colinux-daemon
>> doesn't properly terminate. Windows thinks the service is still
>> 'shutting down' and it never reaches a 'power off' point. If I manually
>> kill the colinux-daemon process, Windows then restarts it right away.
>> Oddness.
>>
>> I'm not sure what informtion I might provide that's useful, so if
>> there's anything let me know:
>> C:\Program Files\coLinux>colinux-daemon.exe
>> Cooperative Linux Daemon, 0.7.1
>> Compiled on Mon Jan  1 03:59:29 2007
>>
>> C:\Program Files\coLinux>ver
>>
>> Microsoft Windows XP [Version 5.1.2600]
>>
>> Found in the Application log:
>> The description for Event ID ( 1 ) in Source ( coLinux ) cannot be
>> found. The local computer may not have the necessary registry
>> information or message DLL files to display messages from a remote
>> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
>> description; see Help and Support for details. The following information
>> is part of the event: daemon: service control STOP.
>> .
>>     

I'm curious, too, if other people who run coLinux as  service have seen
this problem or not.  Other than that Jason, we are looking into this
problem and should have an patch applied once we figure out what the
issue is.  It would help, alot to know your command-line, especially the
options that you are sending to coLinux when you register your service.

Thanks,

George

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

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

Hallo,

have no checked, so could no answer yes or no and why. :-(

> Jason Ahrens wrote:
>> I'm trying out the 0.7.1 pre-release, so far everything is working
>> perfect except shut down.
>>
>> I run coLinux as a service on Windows XP, and what happens when
>> 'shutting down' is, the Linux portion seems to shut down fine,
>> eventually reaching  a safe to power off point, but the colinux-daemon
>> doesn't properly terminate. Windows thinks the service is still
>> 'shutting down' and it never reaches a 'power off' point. If I manually
>> kill the colinux-daemon process, Windows then restarts it right away.
>> Oddness.
>>
>> I'm not sure what informtion I might provide that's useful, so if
>> there's anything let me know

Your command line for installing the service and the config file would 
be interesting, and the current directory where you stays on installing 
the service.

CoLinux 0.7.1 use a new internal parameter for starting service, if path 
for installing and running is differ.  This could be a problem?
Are you shure, to re-installed the service after update from 0.6.4 to 
0.7.1?  Re-installing means two calls --remove-service and --remove-service.

It would be help, if you runs the debugger on error time:
Start colinux service (normal, you does, without debugger)
After is full running: Run the debugger on a second windows prompt:
   colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug1.xml
Stop the service, wait for down. (make your error you have)
Stop the debugger with CTRL-C
Start the debugger again with an other outfile:
   colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug2.xml
Kill the colinux-daemon
Stop the debugger with CTRL-C

View the last lines in the files debug1.xml and the beginning in 
debug2.xml.  Is there any intersting print about problems, or a warning?

-- 
Henry

Re: [coLinux-users] 0.7.1 pre-release not properly 'shutting down'

[Jason A. <ja...@co...>]

Was just wondering if anyone might have any suggestions. If not, I guess
I'll have to go back to 0.6.4.

Jason

Jason Ahrens wrote:
> I'm trying out the 0.7.1 pre-release, so far everything is working
> perfect except shut down.
>
> I run coLinux as a service on Windows XP, and what happens when
> 'shutting down' is, the Linux portion seems to shut down fine,
> eventually reaching  a safe to power off point, but the colinux-daemon
> doesn't properly terminate. Windows thinks the service is still
> 'shutting down' and it never reaches a 'power off' point. If I manually
> kill the colinux-daemon process, Windows then restarts it right away.
> Oddness.
>
> I'm not sure what informtion I might provide that's useful, so if
> there's anything let me know:
> C:\Program Files\coLinux>colinux-daemon.exe
> Cooperative Linux Daemon, 0.7.1
> Compiled on Mon Jan  1 03:59:29 2007
>
> C:\Program Files\coLinux>ver
>
> Microsoft Windows XP [Version 5.1.2600]
>
> Found in the Application log:
> The description for Event ID ( 1 ) in Source ( coLinux ) cannot be
> found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following information
> is part of the event: daemon: service control STOP.
> .
>
> Jason
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>   

[coLinux-users] (no subject)

[Alessandro E. <eva...@gm...>]

Re: [coLinux-users] GET YORU UNIVERSITY{} DIPLOMA

[(270) 818-7. C. <25...@ma...>]

Good day Colinux-users!!!
A Genuine University Degree in notime! 

 
Have you ever thought that the only thing stopping you from a great job and better pay was a few lteters behind you name? 
Well now you can get them! 

 
BA BSc MA MSc MBA PhD 


 
Within notime! 
No Study Required! 
100% Verifialbe! 


 
These are real, genuine degrees taht include Bachelors, Masters, MBA and Doctorate Degrees. They are fully verifiable and certified transcripts are also available. 

 
Just call the number below. 
You?ll than kme later? 

 
Call Instantly +1 (270) 818-7244 
Good Anytime
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=






it  went  over, spilling the wine-thick and unwatered-into the troddenfiction and into fantasy such as, I like to think, the elephant-headedtheirs away as useless weight, discarding all to stampede like beasts.freed  gladiator. Best not think of them either. Life as a slave mighttoward  the  sound  of the conflict. "You want to know about my honor?

[coLinux-users] NFS booting?

[Ph. M. <phi...@bm...>]

Hello everybody!


I wanted to try colinux, and boot from an NFS server.
So my configuration file looks like this:

	ip=<myip>:<server>:<gw>:<netmask>
	root=nfs
	nfsroot=<path>
	nfsaddrs=<server>
	init=/bin/bash
	kernel=vmlinuz
	eth0=tuntap
	mem=64
This parameters I took from bootparam(7).


On starting colinux-daemon I get
	...
	VFS: Cannot open root device "nfs" or unknown-block(0,0)
	Please append a correct "root=" boot option
	Kernel panic: ...

In the current snapshots I found nfs.ko - but that would be needed for 
booting!
Is there some version that has NFS compiled in?


Please keep me cc'ed, I'm not subscribed.
Thank you!


Regards,

Phil

[coLinux-users] Dan Aloni gets a Wikipedia article.

[Jun O. <ok...@di...>]

http://en.wikipedia.org/wiki/Dan_Aloni
BTW, Who made this?

          --- Okajima, Jun. Tokyo, Japan.