colinux-users — coLinux users mailing list

[coLinux-users] Problem installing colinux service in 0.7.4

[Frank C. <vfc...@go...>]

I am trying to install a colinux vm as a service. The installation
succeeds, but wheneve I try to run it I get a this dialog -

Could not start the Colinux service on Local computer
Error 1053: The service did not respond to the start or control
request in a timely fashion.

The message comes immediately without delay.

When i try to run from the command line the result is as below


M:\Logger>net start Colinux
The service is not responding to the control function.

More help is available by typing NET HELPMSG 2186.


M:\Logger>net helpmsg 2186

The service is not responding to the control function.


EXPLANATION

The service cannot run your command at this time.

ACTION

Try the command again later.

If the problem persists, stop and restart the service.

However, if the problem continues after you have restarted the
service, report the problem. Be sure
to include the name of the service and the command that was refused,
to technical support.

I have been through the docs and it mentions some dependies,but the
colinux instlalation as complete. The notes mention that 0.7.5 doesn't
require any commands for additonal dependencies.

Wil the VMs work withouth problems on 0.7.5. I am reluctant to upgrade
incase there is some incompatibillity


-- 
Frank Church

=======================
http://devblog.brahmancreations.com

Re: [coLinux-users] Bridged network too slow

[Henry N. <hen...@ar...>]

  Hello Angel,

Angel Angelov wrote:
> I'm using coLinux 0.7.5 and WinPCAP 4.1.1
> The ping to the coLinux VM IP address is 7ms and I get only about 
> 10Mbit with bridged network, but my LAN supports 100Mbit.
>
> What can I do to fix this problem?

Inside your colinux configuration replace the word "pcap-bridge" with 
"ndis-bridge". That type works faster.

-- 
Henry N.

[coLinux-users] Bridged network too slow

[Angel A. <dex...@gm...>]

Hello
I'm using coLinux 0.7.5 and WinPCAP 4.1.1
The ping to the coLinux VM IP address is 7ms and I get only about 10Mbit
with bridged network, but my LAN supports 100Mbit.

What can I do to fix this problem?

Angel Angelov <dex...@gm...>

Re: [coLinux-users] Help needed starting and closing coLinux VM from application

[Henry N. <hen...@ar...>]

  On 28.01.2010 20:41, Frank Church wrote:
> I am using Lazarus/FreePascal to run a coLinux VM but the shutdown
> process just seems to terminate it abruptly and I would like to know
> if there is some other way.
>
> eg when you close click on the close button of a coLinux terminal
> window, it prints out a yellow notice and goes through a controlled
> shutdown process. In my case when I close from the Lazarus app, the
> window disappears abruptly, and I wonder if goes through a controlled
> shutdown.
>
> The start process is like this.
>
>    vmProcess := TProcess.Create
>    vmProcess.CommandLine :=  'c:\colinux\coLinux-daemon.exe -k -t NT -d
> @rt.conf';
>    vmProcess.Execute;
>    ShowMessage('process pid = ' + IntToStr(vmProcess.ProcessID));
>
> The ccommand to close is like this.
>
>   if Assigned(vmProcess) then
>   begin
>     vmProcess.Active := False;
>     vmProcess.Free;
>   end;
>
> Is there some value I can derive from the ProcesID than I can use to
> send a message to windows to close it properly?

I'm not a user of Pascal. I think, you killed the process to shortly 
after Active := False with the Free of this object.

http://lazarus-ccr.sourceforge.net/docs/fcl/process/tprocess.execute.html

I would say, you needs to use "Terminate" and than check "Running" in a 
time limited loop with some idle time for the CPU, to let the process 
gracefully shutting down. Last get the exit code with WaitOnExit.

-- 
Henry N.

[coLinux-users] Help needed starting and closing coLinux VM from application

[Frank C. <vfc...@go...>]

I am using Lazarus/FreePascal to run a coLinux VM but the shutdown
process just seems to terminate it abruptly and I would like to know
if there is some other way.

eg when you close click on the close button of a coLinux terminal
window, it prints out a yellow notice and goes through a controlled
shutdown process. In my case when I close from the Lazarus app, the
window disappears abruptly, and I wonder if goes through a controlled
shutdown.

The start process is like this.

  vmProcess := TProcess.Create
  vmProcess.CommandLine :=  'c:\colinux\coLinux-daemon.exe -k -t NT -d
@rt.conf';
  vmProcess.Execute;
  ShowMessage('process pid = ' + IntToStr(vmProcess.ProcessID));

The ccommand to close is like this.

 if Assigned(vmProcess) then
 begin
   vmProcess.Active := False;
   vmProcess.Free;
 end;

Is there some value I can derive from the ProcesID than I can use to
send a message to windows to close it properly?


-- 
Frank Church

=======================
http://devblog.brahmancreations.com

[coLinux-users] Setting maximum open files

[Ron A. <rav...@ya...>]

Hi,

How can I permanently set the maximum number of open files?
I noticed that setting the value in /etc/security/limits.conf has no effect.

ulimit -n works fine until restart.

Thanks,
Ron



      

Re: [coLinux-users] Fwd: Re: fsck of root fs fails

[<ger...@og...>]

Henry Nestler schrieb:
> Hello Andreas,
> 
> if you have hda1 in the file "/etc/fstab", then please use this config:
> 
> hda1="c:\Programme\coLinux\root_fs
> root=/dev/hda1

YES this did the trick.



yours
gerhard





> 
> Please don't use initrd.gz, if you have trobble with fsck, because this 
> initrd.gz tries to mount your filesystem "rw" to inject the modules. 
> Later (after fsck success), you can enable initrd for one boot. And more 
> later you never needs initrd again, as long you not upgraded coLinux 
> version.
> 
> Of curse "ro" is not ignored. That's why you see such mysterious output. 
> Mount will read some times from /etc/mtab, so that fails on read only 
> mounted filesystems. Please ask the kernel directly with "cat /proc/mounts".
> 
> Henry
> 
> 
> Am 25.11.2009 18:35, schrieb Peter Kuznetsov:
>> Please, try to add:
>>   hda1=:cobd0
>> after line
>>   cobd0="c:\Programme\coLinux\root_fs"
>>
>> Peter.
>>
>>
>>
>>    
>>> Here my config (all not commented lines)
>>>
>>> kernel=vmlinux
>>> ??cobd0="c:\Programme\coLinux\root_fs"
>>> ??root=/dev/cobd0
>>> ??ro
>>> ??initrd=initrd.gz
>>>
>>> So everything looks fine?
>>>
>>> ro seams to be ignored?
>>>
>>> Whats the location of the initrd file? It is not part of the
>>> c:\Programme\coLinux\ directory
>>>
>>>
>>> Full output of mount:
>>> /dev/hda1 on / type ext2 (rw,noatime)
>>> none on /proc type proc (rw)
>>> none on /sys type sysfs (rw)
>>> none on /dev/shm type tmpfs (rw)
>>>
>>> Looks fine for me.
>>>
>>>
>>> yours
>>> gerhard
>>>
>>>
>>> Andreas Göb schrieb:
>>>      
>>>> Hello,
>>>>
>>>> I never tried the provided ArchLinux image, but the problem seems to be
>>>> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or
>>>> similar. Please check the "root=" line in your LA.conf file for the
>>>> correct
>>>> device name and make sure that there is a corresponding line
>>>> cobd0="c:\path\to\your\root_fs" that points to the image file.
>>>>
>>>> Best regards,
>>>> Andreas Göb
>>>>
>>>>
>>>> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb
>>>> ger...@og...:
>>>>        
>>>>> Hello
>>>>>
>>>>> New to coLinux
>>>>>
>>>>> New installation
>>>>> Host: windows 2000 service pack 4
>>>>> coLinux: 0.7.5
>>>>> selected distro (from installation dialog): arch linux
>>>>> because it is the smallest one.
>>>>> extracted the 7z file
>>>>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
>>>>> (renamed to "root_fs")
>>>>>
>>>>> On windows:
>>>>> Start ->  Run ->  cmd
>>>>> cd to coLinux installation
>>>>> copy example.conf to LA.conf
>>>>> adjust the path from c:\coLinux to c:\Programme\coLinux
>>>>> type: colinux-daemon.exe @LA.conf
>>>>> boot looks nice
>>>>> mount of /dev/hda1 ->  / looks like working
>>>>> but fsck failes with:
>>>>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)
>>>>>
>>>>> going to maintenance console works
>>>>>
>>>>> cat /etc/issue
>>>>> tells me that I work on "Arch Linux (Core Dump)"
>>>>>
>>>>> mount shows:
>>>>> /dev/hda1 on / type ext2 (rw,noatime)
>>>>>
>>>>> fsck ends up with:
>>>>> fsck.ext3: No such device or address while trying to open /dev/hda1
>>>>> Possibly not existent or swap device?
>>>>>
>>>>> continuing with CTRL-D does a reboot ending up with the same failure
>>>>>
>>>>> Do I something wrong or is the provided arch-linux fs realy corrupt?
>>>>>
>>>>> thanks
>>>>> gerhard
>>>>>          
> 
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 

Re: [coLinux-users] Fwd: Re: fsck of root fs fails

[<ger...@og...>]

Peter Kuznetsov schrieb:
> Please, try to add:
>  hda1=:cobd0
> after line
>  cobd0="c:\Programme\coLinux\root_fs"

According to the docu this should solve the problem, but did not.

It is solved anyway (see ohter mail).

thanks
gerhard


> 
>> Here my config (all not commented lines)
>>
>> kernel=vmlinux
>> ??cobd0="c:\Programme\coLinux\root_fs"
>> ??root=/dev/cobd0
>> ??ro
>> ??initrd=initrd.gz
>>
>> So everything looks fine?
>>
>> ro seams to be ignored?
>>
>> Whats the location of the initrd file? It is not part of the 
>> c:\Programme\coLinux\ directory
>>
>>
>> Full output of mount:
>> /dev/hda1 on / type ext2 (rw,noatime)
>> none on /proc type proc (rw)
>> none on /sys type sysfs (rw)
>> none on /dev/shm type tmpfs (rw)
>>
>> Looks fine for me.
>>
>>
>> yours
>> gerhard
>>
>>
>> Andreas Göb schrieb:
>>> Hello,
>>>
>>> I never tried the provided ArchLinux image, but the problem seems to be
>>> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or
>>> similar. Please check the "root=" line in your LA.conf file for the
>>> correct
>>> device name and make sure that there is a corresponding line
>>> cobd0="c:\path\to\your\root_fs" that points to the image file.
>>>
>>> Best regards,
>>> Andreas Göb
>>>
>>>
>>> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb
>>> ger...@og...:
>>>> Hello
>>>>
>>>> New to coLinux
>>>>
>>>> New installation
>>>> Host: windows 2000 service pack 4
>>>> coLinux: 0.7.5
>>>> selected distro (from installation dialog): arch linux
>>>> because it is the smallest one.
>>>> extracted the 7z file
>>>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
>>>> (renamed to "root_fs")
>>>>
>>>> On windows:
>>>> Start -> Run -> cmd
>>>> cd to coLinux installation
>>>> copy example.conf to LA.conf
>>>> adjust the path from c:\coLinux to c:\Programme\coLinux
>>>> type: colinux-daemon.exe @LA.conf
>>>> boot looks nice
>>>> mount of /dev/hda1 -> / looks like working
>>>> but fsck failes with:
>>>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)
>>>>
>>>> going to maintenance console works
>>>>
>>>> cat /etc/issue
>>>> tells me that I work on "Arch Linux (Core Dump)"
>>>>
>>>> mount shows:
>>>> /dev/hda1 on / type ext2 (rw,noatime)
>>>>
>>>> fsck ends up with:
>>>> fsck.ext3: No such device or address while trying to open /dev/hda1
>>>> Possibly not existent or swap device?
>>>>
>>>> continuing with CTRL-D does a reboot ending up with the same failure
>>>>
>>>> Do I something wrong or is the provided arch-linux fs realy corrupt?
>>>>
>>>> thanks
>>>> gerhard
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>>> trial. Simplify your report design, integration and deployment - and focus on 
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now. ?http://p.sf.net/sfu/bobj-july
>>> _______________________________________________
>>> coLinux-users mailing list
>>> coL...@li...
>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>
>>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>> trial. Simplify your report design, integration and deployment - and focus on 
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. ?http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>
> 
> 

Re: [coLinux-users] Fwd: Re: fsck of root fs fails

[Henry N. <hen...@ar...>]

Hello Andreas,

if you have hda1 in the file "/etc/fstab", then please use this config:

hda1="c:\Programme\coLinux\root_fs
root=/dev/hda1


Please don't use initrd.gz, if you have trobble with fsck, because this 
initrd.gz tries to mount your filesystem "rw" to inject the modules. 
Later (after fsck success), you can enable initrd for one boot. And more 
later you never needs initrd again, as long you not upgraded coLinux 
version.

Of curse "ro" is not ignored. That's why you see such mysterious output. 
Mount will read some times from /etc/mtab, so that fails on read only 
mounted filesystems. Please ask the kernel directly with "cat /proc/mounts".

Henry


Am 25.11.2009 18:35, schrieb Peter Kuznetsov:
> Please, try to add:
>   hda1=:cobd0
> after line
>   cobd0="c:\Programme\coLinux\root_fs"
>
> Peter.
>
>
>
>    
>> Here my config (all not commented lines)
>>
>> kernel=vmlinux
>> ??cobd0="c:\Programme\coLinux\root_fs"
>> ??root=/dev/cobd0
>> ??ro
>> ??initrd=initrd.gz
>>
>> So everything looks fine?
>>
>> ro seams to be ignored?
>>
>> Whats the location of the initrd file? It is not part of the
>> c:\Programme\coLinux\ directory
>>
>>
>> Full output of mount:
>> /dev/hda1 on / type ext2 (rw,noatime)
>> none on /proc type proc (rw)
>> none on /sys type sysfs (rw)
>> none on /dev/shm type tmpfs (rw)
>>
>> Looks fine for me.
>>
>>
>> yours
>> gerhard
>>
>>
>> Andreas Göb schrieb:
>>      
>>> Hello,
>>>
>>> I never tried the provided ArchLinux image, but the problem seems to be
>>> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or
>>> similar. Please check the "root=" line in your LA.conf file for the
>>> correct
>>> device name and make sure that there is a corresponding line
>>> cobd0="c:\path\to\your\root_fs" that points to the image file.
>>>
>>> Best regards,
>>> Andreas Göb
>>>
>>>
>>> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb
>>> ger...@og...:
>>>        
>>>> Hello
>>>>
>>>> New to coLinux
>>>>
>>>> New installation
>>>> Host: windows 2000 service pack 4
>>>> coLinux: 0.7.5
>>>> selected distro (from installation dialog): arch linux
>>>> because it is the smallest one.
>>>> extracted the 7z file
>>>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
>>>> (renamed to "root_fs")
>>>>
>>>> On windows:
>>>> Start ->  Run ->  cmd
>>>> cd to coLinux installation
>>>> copy example.conf to LA.conf
>>>> adjust the path from c:\coLinux to c:\Programme\coLinux
>>>> type: colinux-daemon.exe @LA.conf
>>>> boot looks nice
>>>> mount of /dev/hda1 ->  / looks like working
>>>> but fsck failes with:
>>>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)
>>>>
>>>> going to maintenance console works
>>>>
>>>> cat /etc/issue
>>>> tells me that I work on "Arch Linux (Core Dump)"
>>>>
>>>> mount shows:
>>>> /dev/hda1 on / type ext2 (rw,noatime)
>>>>
>>>> fsck ends up with:
>>>> fsck.ext3: No such device or address while trying to open /dev/hda1
>>>> Possibly not existent or swap device?
>>>>
>>>> continuing with CTRL-D does a reboot ending up with the same failure
>>>>
>>>> Do I something wrong or is the provided arch-linux fs realy corrupt?
>>>>
>>>> thanks
>>>> gerhard
>>>>          
>>>

Re: [coLinux-users] Fwd: Re: fsck of root fs fails

[Peter K. <pet...@ma...>]

Please, try to add:
 hda1=:cobd0
after line
 cobd0="c:\Programme\coLinux\root_fs"

Peter.



> Here my config (all not commented lines)
> 
> kernel=vmlinux
> ??cobd0="c:\Programme\coLinux\root_fs"
> ??root=/dev/cobd0
> ??ro
> ??initrd=initrd.gz
> 
> So everything looks fine?
> 
> ro seams to be ignored?
> 
> Whats the location of the initrd file? It is not part of the 
> c:\Programme\coLinux\ directory
> 
> 
> Full output of mount:
> /dev/hda1 on / type ext2 (rw,noatime)
> none on /proc type proc (rw)
> none on /sys type sysfs (rw)
> none on /dev/shm type tmpfs (rw)
> 
> Looks fine for me.
> 
> 
> yours
> gerhard
> 
> 
> Andreas Göb schrieb:
> > Hello,
> > 
> > I never tried the provided ArchLinux image, but the problem seems to be
> > that the image is accessed via /dev/hda1. It should be /dev/cobd0 or
> > similar. Please check the "root=" line in your LA.conf file for the
> > correct
> > device name and make sure that there is a corresponding line
> > cobd0="c:\path\to\your\root_fs" that points to the image file.
> > 
> > Best regards,
> > Andreas Göb
> > 
> > 
> > Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb
> > ger...@og...:
> >> Hello
> >>
> >> New to coLinux
> >>
> >> New installation
> >> Host: windows 2000 service pack 4
> >> coLinux: 0.7.5
> >> selected distro (from installation dialog): arch linux
> >> because it is the smallest one.
> >> extracted the 7z file
> >> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
> >> (renamed to "root_fs")
> >>
> >> On windows:
> >> Start -> Run -> cmd
> >> cd to coLinux installation
> >> copy example.conf to LA.conf
> >> adjust the path from c:\coLinux to c:\Programme\coLinux
> >> type: colinux-daemon.exe @LA.conf
> >> boot looks nice
> >> mount of /dev/hda1 -> / looks like working
> >> but fsck failes with:
> >> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)
> >>
> >> going to maintenance console works
> >>
> >> cat /etc/issue
> >> tells me that I work on "Arch Linux (Core Dump)"
> >>
> >> mount shows:
> >> /dev/hda1 on / type ext2 (rw,noatime)
> >>
> >> fsck ends up with:
> >> fsck.ext3: No such device or address while trying to open /dev/hda1
> >> Possibly not existent or swap device?
> >>
> >> continuing with CTRL-D does a reboot ending up with the same failure
> >>
> >> Do I something wrong or is the provided arch-linux fs realy corrupt?
> >>
> >> thanks
> >> gerhard
> > 
> > ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> > trial. Simplify your report design, integration and deployment - and focus on 
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now. ?http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users
> > 
> > 
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. ?http://p.sf.net/sfu/bobj-july
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 

Re: [coLinux-users] Fwd: Re: fsck of root fs fails

[<ger...@og...>]

Here my config (all not commented lines)

kernel=vmlinux
  cobd0="c:\Programme\coLinux\root_fs"
  root=/dev/cobd0
  ro
  initrd=initrd.gz

So everything looks fine?

ro seams to be ignored?

Whats the location of the initrd file? It is not part of the 
c:\Programme\coLinux\ directory


Full output of mount:
/dev/hda1 on / type ext2 (rw,noatime)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/shm type tmpfs (rw)

Looks fine for me.


yours
gerhard


Andreas Göb schrieb:
> Hello,
> 
> I never tried the provided ArchLinux image, but the problem seems to be
> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or
> similar. Please check the "root=" line in your LA.conf file for the
> correct
> device name and make sure that there is a corresponding line
> cobd0="c:\path\to\your\root_fs" that points to the image file.
> 
> Best regards,
> Andreas Göb
> 
> 
> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb
> ger...@og...:
>> Hello
>>
>> New to coLinux
>>
>> New installation
>> Host: windows 2000 service pack 4
>> coLinux: 0.7.5
>> selected distro (from installation dialog): arch linux
>> because it is the smallest one.
>> extracted the 7z file
>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
>> (renamed to "root_fs")
>>
>> On windows:
>> Start -> Run -> cmd
>> cd to coLinux installation
>> copy example.conf to LA.conf
>> adjust the path from c:\coLinux to c:\Programme\coLinux
>> type: colinux-daemon.exe @LA.conf
>> boot looks nice
>> mount of /dev/hda1 -> / looks like working
>> but fsck failes with:
>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)
>>
>> going to maintenance console works
>>
>> cat /etc/issue
>> tells me that I work on "Arch Linux (Core Dump)"
>>
>> mount shows:
>> /dev/hda1 on / type ext2 (rw,noatime)
>>
>> fsck ends up with:
>> fsck.ext3: No such device or address while trying to open /dev/hda1
>> Possibly not existent or swap device?
>>
>> continuing with CTRL-D does a reboot ending up with the same failure
>>
>> Do I something wrong or is the provided arch-linux fs realy corrupt?
>>
>> thanks
>> gerhard
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 

[coLinux-users] Fwd: Re: fsck of root fs fails

[Andreas G. <ag...@gm...>]

Hello,

I never tried the provided ArchLinux image, but the problem seems to be
that the image is accessed via /dev/hda1. It should be /dev/cobd0 or
similar. Please check the "root=" line in your LA.conf file for the
correct
device name and make sure that there is a corresponding line
cobd0="c:\path\to\your\root_fs" that points to the image file.

Best regards,
Andreas Göb


Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb
ger...@og...:
> Hello
> 
> New to coLinux
> 
> New installation
> Host: windows 2000 service pack 4
> coLinux: 0.7.5
> selected distro (from installation dialog): arch linux
> because it is the smallest one.
> extracted the 7z file
> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
> (renamed to "root_fs")
> 
> On windows:
> Start -> Run -> cmd
> cd to coLinux installation
> copy example.conf to LA.conf
> adjust the path from c:\coLinux to c:\Programme\coLinux
> type: colinux-daemon.exe @LA.conf
> boot looks nice
> mount of /dev/hda1 -> / looks like working
> but fsck failes with:
> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)
> 
> going to maintenance console works
> 
> cat /etc/issue
> tells me that I work on "Arch Linux (Core Dump)"
> 
> mount shows:
> /dev/hda1 on / type ext2 (rw,noatime)
> 
> fsck ends up with:
> fsck.ext3: No such device or address while trying to open /dev/hda1
> Possibly not existent or swap device?
> 
> continuing with CTRL-D does a reboot ending up with the same failure
> 
> Do I something wrong or is the provided arch-linux fs realy corrupt?
> 
> thanks
> gerhard

[coLinux-users] fsck of root fs fails

[<ger...@og...>]

Hello

New to coLinux

New installation
Host: windows 2000 service pack 4
coLinux: 0.7.5
selected distro (from installation dialog): arch linux
because it is the smallest one.
extracted the 7z file
selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs
(renamed to "root_fs")


On windows:
Start -> Run -> cmd
cd to coLinux installation
copy example.conf to LA.conf
adjust the path from c:\coLinux to c:\Programme\coLinux
type: colinux-daemon.exe @LA.conf
boot looks nice
mount of /dev/hda1 -> / looks like working
but fsck failes with:
FILESYSTEM CHECK FAILED (Possibly not existent or swap device?)


going to maintenance console works

cat /etc/issue
tells me that I work on "Arch Linux (Core Dump)"

mount shows:
/dev/hda1 on / type ext2 (rw,noatime)

fsck ends up with:
fsck.ext3: No such device or address while trying to open /dev/hda1
Possibly not existent or swap device?


continuing with CTRL-D does a reboot ending up with the same failure


Do I something wrong or is the provided arch-linux fs realy corrupt?


thanks
gerhard

Re: [coLinux-users] CoLinux 0.7.5 / Windows 7 / WinPCap issue

[Henry N. <hen...@ar...>]

> Not sure if this is a CoLinux or Debian issue, any help welcomed. The 
> Debain image is from the CoLinux downloads page. Updated with latest 
> bits, dnsutils etc.
>
> 0.7.5 installed on a Windows 7 x86 box. Wireshark works so I am 
> guessing Winpcap is working too.
>
> In my CoLinux .conf file I have:
>
> # pcap
> eth0=pcap-bridge,"LAN"
>
> # tap
> eth1=tuntap
>
> At boot the set up for eth0 fails. No idea why. A grep through the 
> logs in /var/log shows nothing. The console shows this:
>
> Setting up networking....
> Configuring network interfaces...Operation failed.
> Failed to bring up eth0.
>
> As far as the Debian (sourceforge download) installation goes in 
> /etc/network/interfaces I've got:
>
> # The primary network interface (win-pcap)
> auto eth0
> iface eth0 inet dhcp
>
> # Second network (tap-win32)
> auto eth1
> # DHCP works on tap
> iface eth1 inet dhcp
> # static works on tap
> #iface eth1 inet static
> #   address 192.168.101.88
> #   netmask 255.255.255.0
> #   gateway 192.168.101.1
>
> Bizarrely perhaps I get the same problem if I reverse the 
> configuration i.e. have the tap adapter as eth0.
>
> Any clues on this?
>
> BTW For anyone else dealing with networking issues let me say that 
> eth1 works perfectly in a standard SoHo 'behind the router' 
> enviroment. I get DHCP and correct DNS resolution ( the latter only I 
> removed the wretched resolvconf and manually added a nameserver entry 
> to /etc/resolv.conf )

udev from Debian renames the network interfaces. Please read the 
comments and hints in Wiki:
http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2

Please read the related Bug report
http://sourceforge.net/tracker/?func=detail&aid=1861876&group_id=98788&atid=622063

-- 
Henry N.

[coLinux-users] CoLinux 0.7.5 / Windows 7 / WinPCap issue

[<g4...@no...>]

Not sure if this is a CoLinux or Debian issue, any help welcomed. The 
Debain image is from the CoLinux downloads page. Updated with latest 
bits, dnsutils etc.

0.7.5 installed on a Windows 7 x86 box. Wireshark works so I am guessing 
Winpcap is working too.

In my CoLinux .conf file I have:

# pcap
eth0=pcap-bridge,"LAN"

# tap
eth1=tuntap

At boot the set up for eth0 fails. No idea why. A grep through the logs 
in /var/log shows nothing. The console shows this:

Setting up networking....
Configuring network interfaces...Operation failed.
Failed to bring up eth0.

As far as the Debian (sourceforge download) installation goes in 
/etc/network/interfaces I've got:

# The primary network interface (win-pcap)
auto eth0
iface eth0 inet dhcp

# Second network (tap-win32)
auto eth1
# DHCP works on tap
iface eth1 inet dhcp
# static works on tap
#iface eth1 inet static
#   address 192.168.101.88
#   netmask 255.255.255.0
#   gateway 192.168.101.1

Bizarrely perhaps I get the same problem if I reverse the configuration 
i.e. have the tap adapter as eth0.

Any clues on this?

BTW For anyone else dealing with networking issues let me say that eth1 
works perfectly in a standard SoHo 'behind the router' enviroment. I get 
DHCP and correct DNS resolution ( the latter only I removed the wretched 
resolvconf and manually added a nameserver entry to /etc/resolv.conf )

Bravo and thanks to the team. CoLinux is a much neater solution than VMWare.

Jerry

[coLinux-users] coLinux and Ubuntu 9.10 Karmic Koala

[Andreas G. <ag...@gm...>]

Hello everybody,

as I am new to the coLinux users mailing list, I would first like to
introduce myself. I am a coLinux user for about half a year and use it on
an everyday basis. I have been using linux since quite a few years now and
very much like the coLinux approach for having your favorite tools at hand
on a Windows PC.

Recently, I tried to create a coLinux filesystem image with the current
Ubuntu 9.10, which failed to boot due to some kernel issues. I have made
some small advancements with the help of the coLinux community, but I still
cannot get it working. I documented the steps I have taken so far in the
coLinux wiki and would like anybody who is interested to review the page,
share their ideas and probably come up with a solution some day.

The wiki page is: http://colinux.wikia.com/wiki/UbuntuKarmic

Best regards,
Andreas

[coLinux-users] Problems with private communication link on Vista32/colinux 0.75

[Olaf S. <ca...@gm...>]

Hiya

I decided to get back to this wondrous piece of software, that i used last
time around 0.73. I had the original disk image as well as conf file, though
i havent got any idea how wrong the comeback would fare.

I planned to use the same layout i used before, two interfaces:

eth0 - pcap-bridged 11.0.0.7/255.255.255.0/broadcast 11.0.0.255/wasnt sure
about gateway -> bridged to Microsoft Loopback adapter set to
11.0.0.1/255.255.255.0
both static - as a private link for telnet/xming access;

eth1 - pcap-bridged, dhcp, bridged to ethernet adapter - used for guest
internet access.

Host runs winpcap 4.1.1 (with no problems, wireshark works fine).

First discrepancy: http://colinux.wikia.com/wiki/Network > WinPcap > The
WinPcap driver > regarding colinux conf, bolded:
"Make sure the mac-address is different from the mac of your regular network
interface. If you want to read why, read up on layer 2 networking."

after doing so, i get the following error on colinux boot:

SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth0.

same error for eth1.

My next step was to pass exactly the same mac address as the one on host
side i was bridging to. Miraculously, it worked. Both eth0 and 1 got up,
eth1 also got ip from dhcp server (router box my whole local network is
connected to) and i was able to access internet via eth1.

Unfortunately, same trick didnt work for eth0. I cannot set up the private
link. Wireshark on host, when i ping from guest, sees the incoming guest
ARP`s (where is 11.0.0.1, asks 11.0.0.7) without any answer. Windows
Firewall has no effect on this, tried it enabled, disabled, and with
loopback removed from filtering.

I spent hours trying all possible combinations, adding gateways on either
side etc... What is more funny, i can easily access guest from other
machines on my network, via eth1 (at least it responds to ping and can ping
them back) but nothing between host<>guest.

Please help. I will gladly provide all necessary info and respond to any
question regarding this issue. I`m this >< close to drop colinux and add new
vm to virtualbox, (even though the performance will be pathetic compared to
colinux) and waiting for x86-64 version so i could install it on my server
box.

Thanks in advance

Re: [coLinux-users] updatedb sometimes hangs coLinux

[Henry N. <hen...@ar...>]

Am 12.11.2009 04:12, schrieb Frédéric L. W. Meunier:
> Using 2.6.25.20 or 2.6.26.8, updatedb (here, mlocate) sometimes
> hangs coLinux. I guess it has to do with cofs, because it also
> scans the Windows partitions. When I used ^C to kill the VM, the
> following appeared.
>
> fuse_dir_open: host returned error: ffffffff
> fuse_dir_open: host returned error: ffffffff
>    

There errors comes from trying to entering a directory without permission.

Try to simulate the "updatedb" by running such command:

  cd /windows
  find . -name 'Nothing, just scanning all dirs'

If that also stops, then go one directory level deeper and try the same. 
Do this again with all directories from top most. ("System Volume 
Information", C:\Winows, C:\Programm, ...) If you found the hanging 
directory, then change into the failed directoy and do run the check for 
every singe directory there again, ... Up to have the problematic file 
or directoy. Than we can see how we can skip it.

-- 
Henry N.

[coLinux-users] updatedb sometimes hangs coLinux

[Frédéric L. W. M. <lis...@pe...>]

Using 2.6.25.20 or 2.6.26.8, updatedb (here, mlocate) sometimes 
hangs coLinux. I guess it has to do with cofs, because it also 
scans the Windows partitions. When I used ^C to kill the VM, the 
following appeared.

fuse_dir_open: host returned error: ffffffff
fuse_dir_open: host returned error: ffffffff
colinux: Linux VM terminated
colinux: powered off, exiting.

Here, updatedb runs daily at 1:00.

Re: [coLinux-users] How to make the colinux NT console black on white

[Henry N. <hen...@ar...>]

For more you need to change the "terminfo". That would be hardly.

Bashish is perhaps an other interesting for you?
http://bashish.sourceforge.net/
I don't have tested. Not all will work on the colinux console (no 
graphics, and no palette manipulation).

-- 
Henry

enveru wrote:
>     Henry Nestler, thank for the reply!
> I have been told this solution a while ago, but didn't like it because
> it has issue. The background color becomes grey, not white. And also
> after running a fullscreen application like nano or man for example,
> the color is reset to white on black.
>
> On 09.11.2009, Henry Nestler wrote:
>    
>> Henry Nestler wrote:
>>      
>>> Run this in you Linux prompt:
>>>        echo -ne "\022[30;40m"
>>>
>>>        
>    
>> Sorry, not black on black, and wrong ESC code!
>> That does it better:
>>      
>    
>>          echo -ne "\033[30;47m"
>>      

Re: [coLinux-users] How to make the colinux NT console black on white

[Henry N. <hen...@ar...>]

Henry Nestler wrote:
> Run this in you Linux prompt:
>       echo -ne "\022[30;40m"
>    

Sorry, not black on black, and wrong ESC code!
That does it better:

	echo -ne "\033[30;47m"

-- 
Henry N.

Re: [coLinux-users] How to make the colinux NT console black on white

[Henry N. <hen...@ar...>]

enveru wrote:
> I like to use coLinux with colinux-console-nt.exe. How can I change
> the color of it to black on white? I can change the color of cmd.exe
> like this - http://i33.tinypic.com/33nhklt.png But I don't know how to
> do it with coLinux
>    

Run this in you Linux prompt:

     echo -ne "\022[30;40m"
     clear

To have this for all your logins, put this line into your file "~/.profile"
More color code you will see under "ECMA-48 Set Graphics Rendition" in 
"man console_codes"
http://linux.die.net/man/4/console_codes

Remember, you can go back to defaults by running this in your Prompt:

     reset

-- 
Henry N.

[coLinux-users] How to make the colinux NT console black on white

[<en...@in...>]

I like to use coLinux with colinux-console-nt.exe. How can I change
the color of it to black on white? I can change the color of cmd.exe
like this - http://i33.tinypic.com/33nhklt.png But I don't know how to
do it with coLinux

[coLinux-users] Tighter integration with Windows?

[Ferry T. <ft...@te...>]

Some thoughts for tighter integration:

- Windows programs (explorer) should be able to start the associated
application in coLinux

Meaning: double click in explorer on a svg would start Inkscape in
coLinux. This would probably need a file association to an app doing ssh
to the coLinux (plink.exe?). The coLinux needs to have the file system
mounted in a predictable way.

- CoLinux apps should be a able to start the associated application in
Windows

Meaning: opening a link in Evolution should start Firefox on Windows
not, coLinux. I currently would not know how to start a app from remote
in Windows. Using dcom?

- xming is doing a great job, but we could use clipboard translation
from windows types to linux and v.v.

So we can copy graphics from one to another. But this may require a bit
more standardization on the linux side first.

Ferry

[coLinux-users] mac changing between service and standalone modes

[Mike F. <vap...@gm...>]

if i start up coLinux (0.7.5) in stand alone mode (i.e. under my
user), i get one set of randomly generated MACs.  the values seen
match my registry keys:
HKCU\Software\coLinux\monitor\0\eth{0,1}\mac

but when i start up in service mode (i.e. under the system user), i
get a different set of randomly generated MACs.  the values seen match
the default user's registry keys:
HKU\.DEFAULT\Software\coLinux\monitor\0\eth{0,1}\mac

obviously this plays havoc with udev's default behavior of
saving/restoring eth names based on MAC addresses.  my network is
configured by slirp/tuntap:
eth0=slirp
eth1=tuntap

reading the Network wiki page [1] indicates that i could specify the
MAC manually for both modes, but it seems like this randomization
should match by default.  i guess the trouble here would be clashes
between multiple users trying to run their own instance of coLinux --
you wouldnt want them to get the same set of random MACs.  perhaps if
the service install step defaulted to running the coLinux service
under the current user instead of the Local System account ?
-mike

[1] http://colinux.wikia.com/wiki/Network