colinux-users — coLinux users mailing list

[coLinux-users] install colinux-driver without administrator privileges

[Bojtos I. P. <pet...@gm...>]

Dear list-members.

I have a problem, which I can't solve. My idea was put everything belongs to
Colinux to a pendrive and run it everywhere i go. But when I runned coLinux
on windows as a normal user, it failed to start (with no driver installed),
I tried to install it with 'colinux-daemon --install-driver' but it also
failed as a normal user. (not enough privileges to do that)
Is there a solution to install driver without administrator privileges?
thanks for the answers,
Peter

-- 
(\__/)    This is Bunny. Copy and paste Bunny
(O.o)    into your signature to help him gain
(> _< )  world domination.

Re: [coLinux-users] accessing raw disk partitions

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

This texts should help you:
http://colinux.wikia.com/wiki/Partitions
http://colinux.wikia.com/wiki/WindowsDevicePaths

Raw partitions starts with \Device\Harddisk0\Partition1 (mostly drive C:).
Remember, that "extended partition" is not counted by windows.

-- 
Henry

Eric S. Johansson wrote:
> running on a machine that dual boots between Windows 7 and Ubuntu.
>
> I need to share my home partition between a virtual machine and a real machine.
>    Obviously, I will access the home partition from either one machine or the
> other but not both at the same time.  I was trying to use virtual box because I
> need to run multiple virtual machines at times.  Unfortunately, due to Windows
> security features, accessing the raw disk is no longer possible without jumping
> through significant hoops.
>
> According to the documentation, it looks like I should be able to access a raw
> partition from co-linux and everything should be hunky-dory.  Is this a good
> assumption or am I living in a fantasy realm?
>
> Can I also run multiple virtual box instances at the same time or are the two
> systems mutually exclusive?  reason I ask is because I need to produce
> production virtual machine images using virtual box and it would be nice to be
> able to run both at the same time.
>
> Ever so grateful for your feedback.
>
> --- eric

[coLinux-users] accessing raw disk partitions

[Eric S. J. <es...@ha...>]

running on a machine that dual boots between Windows 7 and Ubuntu.

I need to share my home partition between a virtual machine and a real machine. 
  Obviously, I will access the home partition from either one machine or the 
other but not both at the same time.  I was trying to use virtual box because I 
need to run multiple virtual machines at times.  Unfortunately, due to Windows 
security features, accessing the raw disk is no longer possible without jumping 
through significant hoops.

According to the documentation, it looks like I should be able to access a raw 
partition from co-linux and everything should be hunky-dory.  Is this a good 
assumption or am I living in a fantasy realm?

Can I also run multiple virtual box instances at the same time or are the two 
systems mutually exclusive?  reason I ask is because I need to produce 
production virtual machine images using virtual box and it would be nice to be 
able to run both at the same time.

Ever so grateful for your feedback.

--- eric

Re: [coLinux-users] from colinux image to virtualbox

[GuyBrush <guy...@gm...>]

I got it to work.
Booted a native linux live CD, the loop device worked, copied everything 
in to a tar ball then restored it in a new Virtualbox drive.
I don't know if loop device works well on virtualbox when the file being 
mounted is located in a virtual box file share mount.

I can give better/clearer instructions if anyone is interested.

A note for anyone trying this. I use virtual machines for Symfony web 
development and have the web app source in my host Vista 64 HDD.
VirtualBox file share did not work very well, I'm having to use smb.

I miss Colinux :o(

Sorry if this msg seems obscure, too much work too little time...
Thanks for the help.

Frank Church wrote:
> Why don't you paste the configuration and instructions you are using?
> That would be a lot more help'
>
> 2009/7/24 GuyBrush <guy...@gm...>:
>   
>> I just got a new laptop with vista 64 and I can't downgrade to XP 32 and
>> run Colinux.
>> Anyone tried to move from Colinux to virtualbox?
>>
>> This is what I have tried so far.
>>
>> * installed kubuntu 9.04 (x86 IIRC) guest in virtualbox using vista 64
>> as host
>> * mounted vista shared host folder
>> * tried to mount ubuntu colinux image located inside the shared folder
>> using loop device.- This does not work,
>> the mount command keeps running and returns no output. After a while I
>> try to kill mount but it also does not work.
>>
>> I'm trying to copy all the colinux files to a virtualbox image so it can
>> boot from virtualbox.
>>
>> Anyone has any ideas?
>>
>> Thank you!
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>     
>
>
>
>   

[coLinux-users] from colinux image to virtualbox

[GuyBrush <guy...@gm...>]

I just got a new laptop with vista 64 and I can't downgrade to XP 32 and 
run Colinux.
Anyone tried to move from Colinux to virtualbox?

This is what I have tried so far.

* installed kubuntu 9.04 (x86 IIRC) guest in virtualbox using vista 64 
as host
* mounted vista shared host folder
* tried to mount ubuntu colinux image located inside the shared folder 
using loop device.- This does not work,
the mount command keeps running and returns no output. After a while I 
try to kill mount but it also does not work.

I'm trying to copy all the colinux files to a virtualbox image so it can 
boot from virtualbox.

Anyone has any ideas?

Thank you!

Re: [coLinux-users] Can I stop Ctrl-C in the Colinux console from exiting?

[Alister H. <ali...@sy...>]

(Sorry David for replying direct, not to the list)
Great, thanks.
So to save from having to start colinux and then a separate terminal, I
write a batch script that checks if it is running and if not starts it
with -d (using the Cygwin `run` command or some other way of suppressing
the now useless terminal), then starts a terminal to connect to the
running Colinux session.  Seems a little complicated :) I still don't
understand the point of having Ctrl-C shut it down if I run without -d
:)

-----Original Message-----
From: David Kaufman [mailto:da...@gi...] 
Sent: Thursday, 23 July 2009 7:59 a.m.
To: col...@li...
Subject: Re: [coLinux-users] Can I stop Ctrl-C in the Colinux console
from exiting?

Hi Alister, Henry:

Henry Nestler wrote:
> On 20.07.2009 04:00, Alister Hood wrote:
>> Does anyone know if it is possible to stop Colinux from exiting when
you
>> press Ctrl-C in the console? Or is there another way to interrupt a
>> program running in the console without shutting Colinux down?
> 
> For me, CTRL-C does not shutting down coLinux. Both consoles (NT and 
> FLTK) have not such effect. Tested with coLinux 0.7.4 on Windows XP.
> 
> Do you perhaps not use the native CMD.EXE?


If I remember correctly Ctrl-C stops coLinux if you ran 
colinux-daemon.exe without the -d option and colInux was running in the 
foreground of your DOS shell.

To run coLinux in the background include, the -d on the command-line.

It's also a good idea to read the whole colinux-daemon.txt file (in your

colinux directory, next to colinux-daemon.exe) from top to bottom!

It also tells you neat tricks like how to make colinux startup 
automatically in the backgrouns as a Windows service at boot time, so 
you dont have to start it each time yourself.

-dave



------------------------------------------------------------------------
------
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Can I stop Ctrl-C in the Colinux console from exiting?

[David K. <da...@gi...>]

Hi Alister, Henry:

Henry Nestler wrote:
> On 20.07.2009 04:00, Alister Hood wrote:
>> Does anyone know if it is possible to stop Colinux from exiting when you
>> press Ctrl-C in the console? Or is there another way to interrupt a
>> program running in the console without shutting Colinux down?
> 
> For me, CTRL-C does not shutting down coLinux. Both consoles (NT and 
> FLTK) have not such effect. Tested with coLinux 0.7.4 on Windows XP.
> 
> Do you perhaps not use the native CMD.EXE?


If I remember correctly Ctrl-C stops coLinux if you ran 
colinux-daemon.exe without the -d option and colInux was running in the 
foreground of your DOS shell.

To run coLinux in the background include, the -d on the command-line.

It's also a good idea to read the whole colinux-daemon.txt file (in your 
colinux directory, next to colinux-daemon.exe) from top to bottom!

It also tells you neat tricks like how to make colinux startup 
automatically in the backgrouns as a Windows service at boot time, so 
you dont have to start it each time yourself.

-dave

Re: [coLinux-users] Can I stop Ctrl-C in the Colinux console from exiting?

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

On 20.07.2009 04:00, Alister Hood wrote:
> Does anyone know if it is possible to stop Colinux from exiting when you
> press Ctrl-C in the console? Or is there another way to interrupt a
> program running in the console without shutting Colinux down?

For me, CTRL-C does not shutting down coLinux. Both consoles (NT and 
FLTK) have not such effect. Tested with coLinux 0.7.4 on Windows XP.

Do you perhaps not use the native CMD.EXE?

-- 
Henry N.

[coLinux-users] Can I stop Ctrl-C in the Colinux console from exiting?

[Alister H. <ali...@sy...>]

Hi,

Does anyone know if it is possible to stop Colinux from exiting when you
press Ctrl-C in the console?  Or is there another way to interrupt a
program running in the console without shutting Colinux down?

 

Thanks,

Alister

Re: [coLinux-users] Ubuntu 9.04 image

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

Shiv Shankar Dayal wrote:
> I have bootstrapped a minimal Ubuntu 9.04 image. If somebody wants it
> please tell me. Image is 80MB approximately. I can upload it or put it
> in a torrent site.

Thanks.

Have tuned it a little like the steps in Wubi 
(http://colinux.wikia.com/wiki/Wubi#Fine_tune), and removed modules from 
/lib/modules.

The file is on https://sourceforge.net/projects/colinux/files/ now.

-- 
Henry N.

Re: [coLinux-users] Warning: unable to open an initial console.

[Alister H. <ali...@sy...>]

> Please check the image, that the file /sbin/init exist, is executable 
and that it is an "ELF" file for 32 bit systems.

It is a link to /bin/busybox, which is that.

> Alternatively use "init=/bin/sh" to get a shell directly.

Even that way I still get the same message.

-----Original Message-----
From: Henry Nestler [mailto:hen...@ar...] 
Sent: Tuesday, 7 July 2009 8:53 p.m.
To: Alister Hood; col...@li...
Subject: Re: [coLinux-users] Warning: unable to open an initial console.

H. Nestler wrote:
> Alister Hood wrote:
>> Warning: unable to open an initial console.
>
> This means your directory "/dev" is empty.
>
> Mount your image from any other running Linux (for example Knoppix),
mount the image as loop, and create this devices:
>
> # mknod -m 600 dev/console c 5 1
> # mknod -m 666 dev/null c 1 3
> # mknod -m 666 dev/zero c 1 5
>
> Or try to use "initrd=initrd.gz". Our initrd does this also for you.
>

Oh, sorry, have not seen your mail completely. :-( You had that checked 
alright.

Please check the image, that the file /sbin/init exist, is executable 
and that it is an "ELF" file for 32 bit systems.

   mount -o loop,ro YourImageName /mnt
   file /mnt/sbin/init

That should be an ELF 32-bit LSB executable, and a statically linked 
file. *NOT* 64 bit.

Alternatively use "init=/bin/sh" to get a shell directly.

-- 
Henry N.

Re: [coLinux-users] Warning: unable to open an initial console.

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

H. Nestler wrote:
> Alister Hood wrote:
>> Warning: unable to open an initial console.
>
> This means your directory "/dev" is empty.
>
> Mount your image from any other running Linux (for example Knoppix),  mount the image as loop, and create this devices:
>
> # mknod -m 600 dev/console c 5 1
> # mknod -m 666 dev/null c 1 3
> # mknod -m 666 dev/zero c 1 5
>
> Or try to use "initrd=initrd.gz". Our initrd does this also for you.
>

Oh, sorry, have not seen your mail completely. :-( You had that checked 
alright.

Please check the image, that the file /sbin/init exist, is executable 
and that it is an "ELF" file for 32 bit systems.

   mount -o loop,ro YourImageName /mnt
   file /mnt/sbin/init

That should be an ELF 32-bit LSB executable, and a statically linked 
file. *NOT* 64 bit.

Alternatively use "init=/bin/sh" to get a shell directly.

-- 
Henry N.

Re: [coLinux-users] Warning: unable to open an initial console.

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

Alister Hood wrote:
> Warning: unable to open an initial console.

This means your directory "/dev" is empty.

Mount your image from any other running Linux (for example Knoppix),  mount the image as loop, and create this devices:

# mknod -m 600 dev/console c 5 1
# mknod -m 666 dev/null c 1 3
# mknod -m 666 dev/zero c 1 5

Or try to use "initrd=initrd.gz". Our initrd does this also for you.



-- 
Henry N.

---------------------------------------------------------
... Es folgt Arcor Werbung | Ads follows by Arcor ...


Jetzt neu: Arcor- Online Butler 5.0 als kostenfreier Download!
Der Arcor-Online Butler loggt Sie automatisch in unsere Online-Dienste ein und Sie kommen mit einem Klick zu Ihren E-Mails, zum Chat und vielem mehr.
www.arcor.de/rd/butler

[coLinux-users] Warning: unable to open an initial console.

[Alister H. <ali...@sy...>]

Hi, I'm trying to set up Puppy Linux with Colinux, and the boot is
failing like this:

 

VFS: Mounted root (ext2 filesystem).

Freeing unused kernel memory: 136k freed

Warning: unable to open an initial console.

Failed to execute /sbin/init.  Attempting defaults...

Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

 

I've googled quite extensively and been unable to find a solution.
Various people suggested running this, which looked promising:

 

mknod -m 600 dev/console c 5 1

mknod -m 666 dev/null c 1 3

mknod -m 666 dev/zero c 1 5

 

I have those nodes, but it doesn't seem to help me.  Can anyone point me
in the right direction?

 

 

Thanks,

Alister

[coLinux-users] Slow x over ssh

[Shiv S. D. <shi...@gm...>]

Hi,

With my new ubuntu image I am using putty as SSH client and xming as X
server on Windows. But X applications run too slow. Compression is
enabled in putty for ssh. Can somebody explain me why it is so slow?
xming is running in Multi-Window mode.

-- 
Best regards,
Shiv Shankar Dayal

[coLinux-users] Ubuntu 9.04 image

[Shiv S. D. <shi...@gm...>]

Hi,

I have bootstrapped a minimal Ubuntu 9.04 image. If somebody wants it
please tell me. Image is 80MB approximately. I can upload it or put it
in a torrent site.

-- 
Best regards,
Shiv Shankar Dayal

[coLinux-users] BSOD problem

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

> yes it is 32-bit windows.
> Unfortunately When I try to uninstall Colinux, I get the BSOD again.
> I have recorded the minidump of this BSOD, but i can't figure out how to attach the file here.

Ok.
Please try to to the followings :

remove driver with colinux-daemon --remove-driver

Then try to download the latest version.
My advice is to try both  0.8.0 and the stable 0.7.4.

To install a new version the steps are always the same :
1. remove driver with colinux-daemon --remove-driver
2. enter in your new colinux distribution
3. install the new driver colinux-daemon --install-driver
4. Try to launch it.

Do you get the usual BSOD ?
When exactly ? at the startuop of colinux ?
Do you see the first kernel boot messages ?

Please post your colinux configuration file and the version you are using.

Remember : the more information you give , the more easy (less
diffucult :=) ) is to understand the problem !

Good luck !

Paolo

Re: [coLinux-users] Can not get slirp to work after upgrade to devel-coLinux-20090520

[Steve W. <li...@la...>]

Thanks very much Henry, ive didnt noticed this part of the README. Works
now.

Henry Nestler schrieb:
> Steve Wagner wrote:
>> Hi, ive upgraded to devel-coLinux-20090520 because i often start
>> VirtualBox and dose not want to run into bluescreens.
>>
>> My problem is that i can not get slirp to work with this version.
>>
>> ####configuration#####
>> kernel=vmlinux
>> mem=128
>> cobd0=C:\CoLinux\root
>> cobd1=C:\CoLinux\swap
>> cobd2=C:\CoLinux\user
>> cofs0=C:\
>> eth0=slirp
>> eth1=tuntap,"CoLinux"
>> root=/dev/cobd0
>>
>> #####/etc/network/interfaces#####
>> auto lo
>> iface lo inet loopback
>>
>> allow-hotplug eth0
>> iface eth0 inet dhcp
>>
>> auto eth1
>> iface eth1 inet static
>>          address 192.168.1.2
>>          netmask 255.255.255.0
>>
>> #####on ifup eth0 ive get######
>> Internet Systems Consortium DHCP Client V3.1.1
>> Copyright 2004-2008 Internet Systems Consortium.
>> All rights reserved.
>> For info, please visit http://www.isc.org/sw/dhcp/
>>
>> 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.
> 
> udev renames the interfaces based on different MAC numbers.
> 
> Please follow the notes for upgrading, and remove all entries from 
> /etc/udev/rules.d/z25_persistent-net.rules, than reboot coLinux.
> 
> All details about this problen found in Bug #1861876
> http://sourceforge.net/tracker/?func=detail&aid=1861876&group_id=98788&atid=622063
> 

Re: [coLinux-users] can not launch Xming

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

Ken Perl wrote:
> I have Xming installed in the default location in which path there is
> a space, I'm not sure if this is the cause, but I can not launch Xming
> after coLinux is started. I have to start it manually from the program
> menu.
>
> exec0=C:\Program Files\Xming\Xming.exe,":0 -clipboard -multiwindow -ac"

Hm. Its's a bug, that quotation marks not works, like this:
exec0="C:\Program Files\Xming\Xming.exe",":0 -clipboard -multiwindow -ac"

Please use the alternate 8.3-names for paths with spaces, for example:
exec0="C:\PROGRA~1\Xming\Xming.exe",":0 -clipboard -multiwindow -ac"

Check on command line with a "DIR C:\ /X" the name for "Program Files" 
on your system.

-- 
Henry N.

Re: [coLinux-users] Can not get slirp to work after upgrade to devel-coLinux-20090520

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

Steve Wagner wrote:
> Hi, ive upgraded to devel-coLinux-20090520 because i often start
> VirtualBox and dose not want to run into bluescreens.
>
> My problem is that i can not get slirp to work with this version.
>
> ####configuration#####
> kernel=vmlinux
> mem=128
> cobd0=C:\CoLinux\root
> cobd1=C:\CoLinux\swap
> cobd2=C:\CoLinux\user
> cofs0=C:\
> eth0=slirp
> eth1=tuntap,"CoLinux"
> root=/dev/cobd0
>
> #####/etc/network/interfaces#####
> auto lo
> iface lo inet loopback
>
> allow-hotplug eth0
> iface eth0 inet dhcp
>
> auto eth1
> iface eth1 inet static
>          address 192.168.1.2
>          netmask 255.255.255.0
>
> #####on ifup eth0 ive get######
> Internet Systems Consortium DHCP Client V3.1.1
> Copyright 2004-2008 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> 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.

udev renames the interfaces based on different MAC numbers.

Please follow the notes for upgrading, and remove all entries from 
/etc/udev/rules.d/z25_persistent-net.rules, than reboot coLinux.

All details about this problen found in Bug #1861876
http://sourceforge.net/tracker/?func=detail&aid=1861876&group_id=98788&atid=622063

-- 
Henry N.

[coLinux-users] Can not get slirp to work after upgrade to devel-coLinux-20090520

[Steve W. <li...@la...>]

Hi, ive upgraded to devel-coLinux-20090520 because i often start
VirtualBox and dose not want to run into bluescreens.

My problem is that i can not get slirp to work with this version.

####configuration#####
kernel=vmlinux
mem=128
cobd0=C:\CoLinux\root
cobd1=C:\CoLinux\swap
cobd2=C:\CoLinux\user
cofs0=C:\
eth0=slirp
eth1=tuntap,"CoLinux"
root=/dev/cobd0

#####/etc/network/interfaces#####
auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
        address 192.168.1.2
        netmask 255.255.255.0

#####on ifup eth0 ive get######
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

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.

colinux-slirp-net-daemon.exe is running.
Host OS is Vista SP2

Dose someone has an idea?

Steve

Re: [coLinux-users] can not copy/paste from xvt term to windows

[Ken P. <ke...@gm...>]

I guess the issue is a bug in xvt, because after I use rxvt instead,
everything works fine now, I can copy/paste linux to windows.

On Thu, Jun 18, 2009 at 10:53 AM, Ken Perl<ke...@gm...> wrote:
> I have coLinux and Xming installed on my XP with default options, and
> I'm using the small terminal xvt.
>
> Below is how I am using it,
>
> - launch the colinux console, export the DISPLAY=10.0.2.2:0.0 and then
> start the xvt terminal, I've tested copy/paste from windows to xvt is
> ok, but I can not copy/paste text from xvt to a windows application
> such as notepad, etc.
>
> I can not find a Xming user list so I'm asking if anyone is using
> coLinux and Xming knows how to resolve the issue.
>
> --
> perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
> ")'
>



-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'

[coLinux-users] can not copy/paste from xvt term to windows

[Ken P. <ke...@gm...>]

I have coLinux and Xming installed on my XP with default options, and
I'm using the small terminal xvt.

Below is how I am using it,

- launch the colinux console, export the DISPLAY=10.0.2.2:0.0 and then
start the xvt terminal, I've tested copy/paste from windows to xvt is
ok, but I can not copy/paste text from xvt to a windows application
such as notepad, etc.

I can not find a Xming user list so I'm asking if anyone is using
coLinux and Xming knows how to resolve the issue.

-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'

[coLinux-users] can not launch Xming

[Ken P. <ke...@gm...>]

Hi,

I have Xming installed in the default location in which path there is
a space, I'm not sure if this is the cause, but I can not launch Xming
after coLinux is started. I have to start it manually from the program
menu.

exec0=C:\Program Files\Xming\Xming.exe,":0 -clipboard -multiwindow -ac"

-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'

[coLinux-users] Could Elive run with CoLinux?

[<hkl...@si...>]

 hi, all
    I am very like Elive Linux distribution(www.elivecd.org) .  And do you know if Elive could run with CoLinux? 
    If so, do you know how to do it?
    Thanks!

BRs,
Koo