colinux-users — coLinux users mailing list

[coLinux-users] Introduction and a few questions

[Zachary K. <zk...@zk...>]

Hello,
     First a few words of introduction on my part: I'm a blind computer
user who has had an interest in Linux ever since I first found out about
it some six or so years back.
The main problem I've had with Linux is that for the most part the
hardware I have doesn't make using speech synthesizers and the like to
do independant installations very easy.
My computer doesn't come with a serial port--and the only synthesizer I
have that would let me do that needs one.  USB to serial doesn't seem to
work, etc.  I settled on using CoLinux and using my existing Windows
screen reader with the NT console--for some reason the FLTK doesn't work
so well with it, I don't know why.
     Now to my questions...I have taken a real liking to ArchLinux: it's
simple, and very useable for what I'd like so far.  
However, the problem comes when upgrading: the latest upgrades recommend
that I use kernel 2.6.17 to take advantage of UDev support.  I can work
around this, but really I wonder if there's an advantage to using it?
If so...Is it possible to use 2.6.18 with CoLinux, and if that's
possible how would I compile it, and patch it?  Would an initrd be
enough?
Thanks in advance,
Zack.

Re: [coLinux-users] yum update causes an error when using slirp (0.7.1)

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

Hello Wim,

Ren=E9 Berber wrote:
> Wim Vander Schelden wrote:
>=20
>> When I use slirp for an internet connection, I can't successfully upda=
te=20
>> my system. When I call "yum update", it causes an exception in the sli=
rp=20
>> deamon after printing "Determining fastest mirror".
>>
>> I'm using the FC5 image available from the coLinux download section.=20
>> This is really annoying, since both other networking systems cause=20
>> conflicts with my router. Is this a known issue? does anyone have a=20
>> solution?
>=20
> I've seen the same problem, there's a Windows panel that comes up sayin=
g that
> the program has failed and Windows has to end it to avoid... bla, bla (=
the usual
> stuff).  CoLinux seems to keep working after that, network and everythi=
ng but
> yum doesn't.
>=20
> My solution was to shutdown FC5, make sure in the Task Manager that it =
was not
> running  (several times it was still running along with the -daemon pro=
cesses),
> and start again.  The second time yum runs fine.

have you the error code from your crash?  I need the message about=20
instruction pointer (see into the Windows EventLogger), and your used=20
coLinux version.

I'm interested, because the 0.8.0 was changed on similarly error.  Would=20
you test the last autobuild please:
http://www.henrynestler.com/colinux/autobuild/devel-20070117/

--=20
Henry Nestler

Re: [coLinux-users] yum update causes an error when using slirp (0.7.1)

[<r.b...@co...>]

Wim Vander Schelden wrote:

> When I use slirp for an internet connection, I can't successfully updat=
e=20
> my system. When I call "yum update", it causes an exception in the slir=
p=20
> deamon after printing "Determining fastest mirror".
>=20
> I'm using the FC5 image available from the coLinux download section.=20
> This is really annoying, since both other networking systems cause=20
> conflicts with my router. Is this a known issue? does anyone have a=20
> solution?

I've seen the same problem, there's a Windows panel that comes up saying =
that
the program has failed and Windows has to end it to avoid... bla, bla (th=
e usual
stuff).  CoLinux seems to keep working after that, network and everything=
 but
yum doesn't.

My solution was to shutdown FC5, make sure in the Task Manager that it wa=
s not
running  (several times it was still running along with the -daemon proce=
sses),
and start again.  The second time yum runs fine.

HTH
--=20
Ren=E9 Berber

[coLinux-users] yum update causes an error when using slirp (0.7.1)

[Wim V. S. <wim...@gm...>]

When I use slirp for an internet connection, I can't successfully update 
my system. When I call "yum update", it causes an exception in the slirp 
deamon after printing "Determining fastest mirror".

I'm using the FC5 image available from the coLinux download section. 
This is really annoying, since both other networking systems cause 
conflicts with my router. Is this a known issue? does anyone have a 
solution?


Thanks,

Wim

Re: [coLinux-users] [SOLVED] Re: Slirp port mapping problem

[<r.b...@co...>]

Henry Nestler wrote:
> Hey Ren=E9,
>=20
> Ren=E9 Berber wrote:
>> After reading `man dhcpcd` the solution was easy.
>>
>> As Henry pointed out, I was getting the wrong IP address from the DHCP=
 server
>> (slirp-daemon in this case).  The reason is that dhcpdcd asks the serv=
er to
>> reuse the last address the "computer" had, slirp-daemon accepted that =
address
>> wich was 192.168.0.40 (I probably used it as fixed address at some tim=
e).
>>
>> The solution is to delete dhcpdcd's cache (for reference:
>> /var/lib/dhcpc/dhcpcd-eth0.cache), tested with `dhcpdcd -T` and saw, i=
n the
>> .info file same directory, that the new address was OK, rebooted and e=
verything
>> is fine.
>>
>> Thanks Henry, your reply made it easy to fix.
>=20
> think, you found a very old unsolved problem with dhcpcd and slirp.
> Have I understand rigth: Slirp ACKed the older address 192.x.x.x?

Yes, it did.

--=20
Ren=E9 Berber

Re: [coLinux-users] Adding to PATH

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

Simon Crombie schrieb:

> /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games so I guess it is
> picking this up from some setup file. Which file gets run to set the PATH
> environment variable when a non-root user logs in?

That depends on the shell that is used. Usually bash.
Which means you should look at /etc/bash.bashrc or /etc/bash.bashrc.local if that is included in from the first one.

[coLinux-users] Adding to PATH

[Simon C. <sim...@on...>]

Using colinux 0.6.4 and Debian GNU/Linux 3.0, I want to add an item on the
end of the PATH which will be automatically set when I login as a non-root
user, but can't find which file to edit to apply this. The path variable is
set to the default values of
/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games so I guess it is
picking this up from some setup file. Which file gets run to set the PATH
environment variable when a non-root user logs in?

Re: [coLinux-users] [SOLVED] Re: Slirp port mapping problem

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

Hey Ren=E9,

Ren=E9 Berber wrote:
> After reading `man dhcpcd` the solution was easy.
>=20
> As Henry pointed out, I was getting the wrong IP address from the DHCP =
server
> (slirp-daemon in this case).  The reason is that dhcpdcd asks the serve=
r to
> reuse the last address the "computer" had, slirp-daemon accepted that a=
ddress
> wich was 192.168.0.40 (I probably used it as fixed address at some time=
).
>=20
> The solution is to delete dhcpdcd's cache (for reference:
> /var/lib/dhcpc/dhcpcd-eth0.cache), tested with `dhcpdcd -T` and saw, in=
 the
> .info file same directory, that the new address was OK, rebooted and ev=
erything
> is fine.
>=20
> Thanks Henry, your reply made it easy to fix.

think, you found a very old unsolved problem with dhcpcd and slirp.
Have I understand rigth: Slirp ACKed the older address 192.x.x.x?

--=20
Henry Nestler

[coLinux-users] [SOLVED] Re: Slirp port mapping problem

[<r.b...@co...>]

After reading `man dhcpcd` the solution was easy.

As Henry pointed out, I was getting the wrong IP address from the DHCP se=
rver
(slirp-daemon in this case).  The reason is that dhcpdcd asks the server =
to
reuse the last address the "computer" had, slirp-daemon accepted that add=
ress
wich was 192.168.0.40 (I probably used it as fixed address at some time).=


The solution is to delete dhcpdcd's cache (for reference:
/var/lib/dhcpc/dhcpcd-eth0.cache), tested with `dhcpdcd -T` and saw, in t=
he
=2Einfo file same directory, that the new address was OK, rebooted and ev=
erything
is fine.

Thanks Henry, your reply made it easy to fix.
--=20
Ren=E9 Berber

Re: [coLinux-users] Slirp port mapping problem

[<r.b...@co...>]

Henry Nestler wrote:
[snip]
> You know that, inside coLinux sshd is listen on 10.0.2.15 network!=20
> Check it with "netstat -an".  Sshd should listen on all networks=20
> (0.0.0.0:22) or on your slirp network (10.0.2.15:22).  Slirp only works=
=20
> with ipaddress 10.0.2.15, with only the netmask 255.255.255.0, check it=
=2E=20

sshd is listening on 0.0.0.0:22 (by default it also listens on the ipv6 a=
ddress
but I disabled it to see if it helped).

The Linux eth0 address is not the one you mention, it is 192.168.0.40 and=
 it
receives that address from a DHCP server which I guess is the slirp-daemo=
n since
I have only one DHCP server and that one did not give that address.

I don't use that network, but I see in the comments of Gentoo's network
configuration that is seems to be the default Gentoo network.

>   Check the broadcast 10.0.2.255

Yes, broadcast is 10.0.2.255, so networking is set all wrong

> Try "ssh 10.0.2.15" inside coLinux.

ssh connected to my sshd running in Windows.

> SSHD [locks]looks in the DNS or /etc/hosts for the windows side address=
=20
> 10.0.2.2, this was a very long timeout for me.  I wrote this lines into=
=20
> my /etc/hosts, and than sshd runs very fine (SuSE 9.0):
>    10.0.2.2        slirp-router
>    10.0.2.3        slirp-dns
>    10.0.2.15       slirp-client
>=20
> 10.0.2.2 is your default route. Right?  Check the /etc/resolv.conf

Yes, 10.0.2.2 is the default route, and 'slirp-dns' is the DNS server.

> Terminate the sshd daemon and run it in foreground with verbose message=
s=20
> "sshd -D -d"
>=20
> 192.168.0.* I'm afraid, is your TAP driver rigth?

I disabled TAP, I'm not using it.

> If you have tap and=20
> slirp configured: Shutting down the tap by "ifconfig ethX" and try only=
=20
> the slirp.  After slirp is running, enable tap again.  Tap is typical a=
=20
> network only betwen windows and linux (not outgoing).
>=20
> Have you a file /etc/host.allow|deny?  Is there configured right? (I'm =

> not shure with this for sshd)

Yes, I know very well how sshd works with those files (I'm using DenyHost=
s and
fail2ban on some servers).

> On windows side:
> Check, that your ethernet card (192.168.10.2 I think) is listen on port=
=20
> 10022 "netstat.exe -an", or 0.0.0.0 for all networks.

Yes, slirp-daemon is listening on the ports I configured.

> Try SSH connection with putty from Windows to "localhost" port 10022.

The result is what I reported before.

The problem, as you pointed out in your first comment, is that I have an =
IP
address that does not belong to the Linux network.  I have to find out wh=
ich
DHCP server gave that address or from where it comes from.  A quick solut=
ion is
to set a fixed IP address using 10.0.2.15 .

Thanks for your reply, it was very helpful.
--=20
Ren=E9 Berber

Re: [coLinux-users] Slirp port mapping problem

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

Ren=E9 Berber wrote:
> Hi,
>=20
> I'm using coLinux 0.7.1pre with only Slirp as network in the configurat=
ion:
>=20
> 	eth0=3Dslirp,,tcp:10022:22/tcp:15901:5901
>=20
> Linux is Gentoo, the 2005.1 image from Sourceforge, working fine includ=
ing all
> network operations to the outside.
>=20
> My problem is that I cannot connect from Windows, I've tried ssh and vn=
cviewer.
>=20
> Details:
>=20
> - colinux-slirp-net-daemon is working fine, I can see it listening to b=
oth ports
> and spawning (or forking) a process when I try to connect.
>=20
> - sshd in Linux is working fine, it is listening, and I can connect fro=
m Linux
> to 127.0.0.1 and also to 192.168.0.40 which are the local addresses of =
the network.
>=20
> - I can connect to anything (tested http, ssh, rsync) from Linux to out=
side
> (outside being Windows (192.168.10.2 both netmasks are /24), or the Int=
ernet).
>=20
> - I cannot connect from outside to Linux (tested from Windows and from =
another
> computer via mapping the port at the gateway).  The initial connection =
is made,
> for instance ssh -> colinux-slirp-net-daemon port 10022, a process is s=
pawned on
> a new port and ssh changes to that port, then nothing... until ssh clos=
es the
> connection and the slirp daemon answers to that close (I used snoop und=
er
> Solaris to see the traffic).  The result with VNC is similar, just the =
ports change.
>=20
> - there is no firewall at Windows' side, and none I could find at Gento=
o Linux
> side.  I installed syslog-ng in Linux and there are no messages about t=
he failed
> connection, sshd never sees the try.
>=20
> Did I miss something in the configuration?
>=20
> Is anybody using the Gentoo image with slirp port mapping? One solution=
 I'm
> willing to try is installing Gentoo 2006.1 to another root filesystem.
>=20
> Any ideas/help will be appreciated.

You know that, inside coLinux sshd is listen on 10.0.2.15 network!=20
Check it with "netstat -an".  Sshd should listen on all networks=20
(0.0.0.0:22) or on your slirp network (10.0.2.15:22).  Slirp only works=20
with ipaddress 10.0.2.15, with only the netmask 255.255.255.0, check it.=20
  Check the broadcast 10.0.2.255

Try "ssh 10.0.2.15" inside coLinux.

SSHD locks in the DNS or /etc/hosts for the windows side address=20
10.0.2.2, this was a very long timeout for me.  I wrote this lines into=20
my /etc/hosts, and than sshd runs very fine (SuSE 9.0):
   10.0.2.2        slirp-router
   10.0.2.3        slirp-dns
   10.0.2.15       slirp-client

10.0.2.2 is your default route. Right?  Check the /etc/resolv.conf

Terminate the sshd daemon and run it in foreground with verbose messages=20
"sshd -D -d"

192.168.0.* I'm afraid, is your TAP driver rigth?  If you have tap and=20
slirp configured: Shutting down the tap by "ifconfig ethX" and try only=20
the slirp.  After slirp is running, enable tap again.  Tap is typical a=20
network only betwen windows and linux (not outgoing).

Have you a file /etc/host.allow|deny?  Is there configured right? (I'm=20
not shure with this for sshd)

On windows side:
Check, that your ethernet card (192.168.10.2 I think) is listen on port=20
10022 "netstat.exe -an", or 0.0.0.0 for all networks.
Try SSH connection with putty from Windows to "localhost" port 10022.

--=20
Henry Nestler

Re: [coLinux-users] increase memory

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

Simon Crombie wrote:
> Try a programme called TopoResize from
> http://www.henrynestler.com/colinux/tools/
> 
> You can get information about it at
> http://colinux.wikia.com/wiki/ColinuxImageTools
> 
> but don't follow the link from this page because it leads to a porn site.

Follow this short step guide:
http://colinux.wikia.com/wiki/CoLinuxFAQ#Q28._How_can_I_increase_the_size_of_a_coLinux_block_device_image.3F

Instead the fsutil, you can use the tool mkFile to create an empty file
http://www.henrynestler.com/colinux/tools/file-utils-mingw-bin-stripped.zip

-- 
Henry Nestler

Re: [coLinux-users] Differences between 0.6.4 and 0.7.1

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

Mark G. Woodruff wrote:
> Is there a summary somewhere of the differences between 0.6.4 and 0.7.1?

yes nin the NEWS file, or changelog:
http://sourceforge.net/project/shownotes.php?release_id=476227&group_id=98788
http://www.henrynestler.com/colinux/source/0.7.1-doc/NEWS.txt

-- 
Henry Nestler

[coLinux-users] Yet Another Dan Aloni

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

http://www.imdb.com/name/nm0022090/

          --- Okajima, Jun. Tokyo, Japan.

Re: [coLinux-users] increase memory

[Simon C. <sim...@on...>]

Try a programme called TopoResize from
http://www.henrynestler.com/colinux/tools/

You can get information about it at
http://colinux.wikia.com/wiki/ColinuxImageTools

but don't follow the link from this page because it leads to a porn site.

Re: [coLinux-users] increase memory

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

Mathias Uebelacker schrieb:
> well okay my mistake. Okay where can i increase my space. I need to install more packages and coud do this because i have no more free space. On my harddisk is enough free space but i found no configuration file where i could increase this param.

There is no entry in a configuration file to achieve this.
You have to enlarge the existing file containing your filesystem (and the filesystem contained within) or create another file and mount it and format it to the desired filesystem.

Re: [coLinux-users] increase memory

[Mathias U. <m.u...@go...>]

d2VsbCBva2F5IG15IG1pc3Rha2UuIE9rYXkgd2hlcmUgY2FuIGkgaW5jcmVhc2UgbXkgc3BhY2Uu
IEkgbmVlZCB0byBpbnN0YWxsIG1vcmUgcGFja2FnZXMgYW5kIGNvdWQgZG8gdGhpcyBiZWNhdXNl
IGkgaGF2ZSBubyBtb3JlIGZyZWUgc3BhY2UuIE9uIG15IGhhcmRkaXNrIGlzIGVub3VnaCBmcmVl
IHNwYWNlIGJ1dCBpIGZvdW5kIG5vIGNvbmZpZ3VyYXRpb24gZmlsZSB3aGVyZSBpIGNvdWxkIGlu
Y3JlYXNlIHRoaXMgcGFyYW0uDQoNCmJyDQpNYXRoaWFzDQotLS0tLSBVcnNwcsO8bmdsaWNoZSBN
aXR0ZWlsdW5nIC0tLS0tDQpWb246IEhvbGdlciBLcnVsbCA8aG9sZ2VyLmtydWxsQGdteC5kZT4N
CkFuOiBjb2xpbnV4LXVzZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KR2VzZW5kZXQ6IFNhLiwg
MTMuIEphbi4gMjAwNyAxMzowNjo1NyBDRVQNCkJldHJlZmY6IFJlOiBbY29MaW51eC11c2Vyc10g
aW5jcmVhc2UgbWVtb3J5DQpNYXRoaWFzIFVlYmVsYWNrZXIgc2NocmllYjoNCg0KPiBpIHVzZSBj
b2xpbnV4IHVuZGVyIHdpbmRvd3MgeHAuIE15IGluaXRyZCBjcmVhdGVzIDIgR0Igc3BhY2UuIE5v
dyBpDQo+IHdvdWxkIGxpa2UgdG8gaW5jcmVhc2UgdGhpcyBzcGFjZS4gSG93IGNhbiBpIGRvIHRo
aXM/IENhbiBhbnlvbmUgcG9pbnQNCj4gbWUgdG8gYSBiaWdnZXIgaW5pdHJkPw0KDQpJIGNhbid0
LiBCdXQgd2hhdCBpbiBoZWF2ZW5zIG5hbWUgbmVlZHMgYSBpbml0cmQgb2Ygb3ZlciAyR0I/DQoN
ClRoZSBpbml0cmQgbWVjaGFuaXNtIHdhcyBtZWFudCBmb3IgdGhlIGJvb3RpbmcgcHJvY2VzcyBv
bmx5LiBJdCBpcyB1c2VkIHRvIGdldCBhY2Nlc3MgdG8gbmVlZGVkIGZpbGVzIGJlZm9yZSB0aGUg
cmVndWxhciBmaWxlc3lzdGVtIG1vdW50cyBleGlzdC4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGFr
ZSBTdXJ2ZXlzLiBFYXJuIENhc2guIEluZmx1ZW5jZSB0aGUgRnV0dXJlIG9mIElUDQpKb2luIFNv
dXJjZUZvcmdlLm5ldCdzIFRlY2hzYXkgcGFuZWwgYW5kIHlvdSdsbCBnZXQgdGhlIGNoYW5jZSB0
byBzaGFyZSB5b3VyDQpvcGluaW9ucyBvbiBJVCAmIGJ1c2luZXNzIHRvcGljcyB0aHJvdWdoIGJy
aWVmIHN1cnZleXMgLSBhbmQgZWFybiBjYXNoDQpodHRwOi8vd3d3LnRlY2hzYXkuY29tL2RlZmF1
bHQucGhwP3BhZ2U9am9pbi5waHAmcD1zb3VyY2Vmb3JnZSZDSUQ9REVWREVWDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KY29MaW51eC11c2VycyBtYWls
aW5nIGxpc3QNCmNvTGludXgtdXNlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0DQpodHRwczovL2xp
c3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9jb2xpbnV4LXVzZXJzDQoNCg==

Re: [coLinux-users] increase memory

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

Mathias Uebelacker schrieb:

> i use colinux under windows xp. My initrd creates 2 GB space. Now i
> would like to increase this space. How can i do this? Can anyone point
> me to a bigger initrd?

I can't. But what in heavens name needs a initrd of over 2GB?

The initrd mechanism was meant for the booting process only. It is used to get access to needed files before the regular filesystem mounts exist.

[coLinux-users] increase memory

[Mathias U. <m.u...@go...>]

Hello,

i use colinux under windows xp. My initrd creates 2 GB space. Now i would like to increase this space. How can i do this? Can anyone point me to a bigger initrd?

br
Mathias

Re: [coLinux-users] Slirp port mapping problem

[<r.b...@co...>]

Just a couple further details:

- The problem is not tcp-wrappers related (I know how that works with ssh=
d);

- Testing with the Fedora Core 5 image the connection is made to Linux, i=
t has
other problems (with PAM auth) but not the network.

So, it is a Gentoo image problem.
--=20
Ren=E9 Berber

[coLinux-users] Differences between 0.6.4 and 0.7.1

[Mark G. W. <mar...@ya...>]

Is there a summary somewhere of the differences between 0.6.4 and 0.7.1?


 
____________________________________________________________________________________
No need to miss a message. Get email on-the-go 
with Yahoo! Mail for Mobile. Get started.
http://mobile.yahoo.com/mail 

[coLinux-users] Slirp port mapping problem

[<r.b...@co...>]

Hi,

I'm using coLinux 0.7.1pre with only Slirp as network in the configuratio=
n:

	eth0=3Dslirp,,tcp:10022:22/tcp:15901:5901

Linux is Gentoo, the 2005.1 image from Sourceforge, working fine includin=
g all
network operations to the outside.

My problem is that I cannot connect from Windows, I've tried ssh and vncv=
iewer.

Details:

- colinux-slirp-net-daemon is working fine, I can see it listening to bot=
h ports
and spawning (or forking) a process when I try to connect.

- sshd in Linux is working fine, it is listening, and I can connect from =
Linux
to 127.0.0.1 and also to 192.168.0.40 which are the local addresses of th=
e network.

- I can connect to anything (tested http, ssh, rsync) from Linux to outsi=
de
(outside being Windows (192.168.10.2 both netmasks are /24), or the Inter=
net).

- I cannot connect from outside to Linux (tested from Windows and from an=
other
computer via mapping the port at the gateway).  The initial connection is=
 made,
for instance ssh -> colinux-slirp-net-daemon port 10022, a process is spa=
wned on
a new port and ssh changes to that port, then nothing... until ssh closes=
 the
connection and the slirp daemon answers to that close (I used snoop under=

Solaris to see the traffic).  The result with VNC is similar, just the po=
rts change.

- there is no firewall at Windows' side, and none I could find at Gentoo =
Linux
side.  I installed syslog-ng in Linux and there are no messages about the=
 failed
connection, sshd never sees the try.

Did I miss something in the configuration?

Is anybody using the Gentoo image with slirp port mapping? One solution I=
'm
willing to try is installing Gentoo 2006.1 to another root filesystem.

Any ideas/help will be appreciated.
--=20
Ren=E9 Berber

Re: [coLinux-users] Problem running colinux

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

Hello Michael,

Michael Brechlin wrote:
> This is my first time writing to the list so I hope I am providing 
> enough information.

Thanks for your full comment here.  Very good.  ;-)

> I have installed colinux 6.4 and 7.1. they are installed in separate 
> directories. (c:\colinux and c:\colinux71)
> I am running Windows XP SP2 (MCE) with all current security updates.
> My boot.ini contains an entry for /NoExecute=AlwaysOff /NOPAE.
> My System specs are: AMD Athlon 64 mobile 4000+ (1.6ghz), 1GB RAM.

Think, "/NoExecute=AlwaysOff /NOPAE" is not need for AMD.  In such error 
cases your machine would be crash with a reboot directly befror see any 
kernel messages.  But, thanks for your full comment here.  ;-)

> In my config file i have only one drive set, initrd default, vmlinux 
> default, memory=256, network=TAP or disabled, no swap.
> I try --driver-remove and --driver-install before I try to run colinux, 
> and status-driver says the driver is running with the correct version 
> listed.

Yes, linux driver is running.
These messages comes from linux kernel:

> Linux version 2.6.12-co-0.7.1 (george@CoDebianDevel) (gcc version 3.4.4 
> 20050314
>  (prerelease) (Debian 3.4.3-13sarge1)) #256MB LOWMEM available.
> initrd enabled: start: 0xcff9a000  size: 0x00065ef7)
> On node 0 totalpages: 65536
>   DMA zone: 0 pages, LIFO batch:1
>   Normal zone: 65536 pages, LIFO batch:31
>   HighMem zone: 0 pages, LIFO batch:1
> Built 1 zonelists
> Kernel command line: root=/dev/cobd0
> Initializing CPU#0
> Setting proxy interrupt vectors
> PID hash table entries: 2048 (order: 11, 32768 bytes)
> Using cooperative for high-res timesource
> Console: colour CoCON 80x25

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
colinux-net-daemon: auto selecting TAP
Memory: 255360k/262144k available (1535k kernel code, 0k reserved, 531k 
data, 112k init, 0k highmem)

... should the next lines from kernel boots.  I'm afraid something 
problem with memory detection, or with cache settings.

Try follow steps:
* Is live CDROM runing on this machine?   Try a Knoppix and compair the 
missing boot messages near "cache hash table".

* Use the smalest config, you have.
For sample this command line with initrd only:
   colinux-daemon.exe mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0

* Open a second command prompt and run the debugger:
   colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml
Than starting the colinux-daemon.
After your colinux-daemon is stopping, stop the debugger with CTRL-C, 
and grep in the file debug.xml for the text "Console: colour CoCON 
80x25".  Is there any more information about your problem?

* Debug the memory (many more outputs).  Run the debugger with output 
about 'allocations'
   colinux-debug-daemon.exe -d -p -s prints=31,misc=31,allocations=15 -f 
allocs.xml
   Run colinux-daemon, stop the debugger and check the output.

* Incrase the memory from 32 up to 250, but not values with power of 2 
(not the 256, not 128 ,...), and check with the "initrd only".

* Try the 20061210-Snapshot.  That was build with differ compiler:
   http://henrynestler.com/colinux/testing/stable-0.7.1/

* Check the task manager: Is colinux-daemon.exe doing anything?  Is it 
idle or polling for any?

> The TAP adapter gives itself a 169.x IP address and claims to be 
> connected, but refuses any ssh attempts.

The network is not setted up. The init process was not running, you 
staning on the memory detection.

> # Slirp for internet connection (outgoing)
> # Inside running coLinux configure eth0 with this static settings:
> # ipaddress 10.0.2.15 <http://10.0.2.15>   broadcast  10.0.2.255 
> <http://10.0.2.255>   netmask 255.255.255.0 <http://255.255.255.0>
> # gateway   10.0.2.2 <http://10.0.2.2>    nameserver 10.0.2.3 
> <http://10.0.2.3>
> #eth0=slirp
> 
> # Networking (tuntap as private network between gust and host)
> eth1=tuntap

If you don't use SLiRP, than set the first network (index 0) to TAP
eth0=tuntap

You can see typical full boot with mem=256 eth0=slirp eth1=tap here:
http://www.henrynestler.com/colinux/screenshoots/typical-boot-0.7.1-256MB.txt

-- 
Henry Nestler

[coLinux-users] Vacantes, Trabajo. de 3hs desde su casa disponible.

[Deon <Mi...@c2...>]

   Estamos buscando gente responsable, hombres honestos interesados en un
   trabajo bien pago utilizando solo unas pocas horas al día..

   Por  largo  tiempo  "DI  GENARO  Ltd."  ha  sido una compañía familiar
   especializados en varias operaciones con joyas antiguas y antigüedades en
   general. Esta compañía esta buscando gente responsable para ser parte de su
   proyecto.

   No te pierdas esta oportunidad - Es exacto lo que estabas buscando!

   Ganar mas de $2500 al mes suena bien? Utilizando solo 4-5 horas por día
   suena mejor? Bueno...con "DI GENARO Ltd." es posible!

   Esta no es una compañía que hará que pagues un cargo de inscripción o te
   inscribirá en una lista de correo. Esta compañía no te pedirá ningún dinero,
   te hará ganar dinero!. Este negocio tomara solo unos momentos de tu tiempo.


   Se te pagara la primera semana como empleado.

   No requerimos ninguna experiencia o habilidad especial. Puedes trabajar
   desde tu casa como un contratado independiente.

   Si estas interesado, por favor siéntete libre de pedir información adicional
   y las provisiones generales.


   Escríbenos ahora, te responderemos lo antes posible.

   Por favor responde a este mail: [1]su...@ch...

References

   1. mailto:su...@ch...

[coLinux-users] Problem running colinux

[Michael B. <mic...@gm...>]

HI,
This is my first time writing to the list so I hope I am providing enough
information.

I have installed colinux 6.4 and 7.1. they are installed in separate
directories. (c:\colinux and c:\colinux71)
I am running Windows XP SP2 (MCE) with all current security updates.
My boot.ini contains an entry for /NoExecute=AlwaysOff /NOPAE.
My System specs are: AMD Athlon 64 mobile 4000+ (1.6ghz), 1GB RAM.

In my config file i have only one drive set, initrd default, vmlinux
default, memory=256, network=TAP or disabled, no swap.
I try --driver-remove and --driver-install before I try to run colinux, and
status-driver says the driver is running with the correct version listed.

I have read and followed the steps in the getting started wiki article.

When I run colinux from the dosprompt, It stops at Console and does nothing.
I don't get any errors, nor do I get a login prompt.
Here is the output:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\coLinux71>colinux-daemon.exe @example.conf
Cooperative Linux Daemon, 0.7.1
Compiled on Mon Jan  1 03:59:29 2007

using 'vmlinux' as kernel image
configuring 256 MB of virtual RAM
mapping cobd0 to \??\c:\coLinux71\Debian-3.0r2.ext3-mit-backports.1gb
configured TAP at '' device as eth1
using 'initrd.gz' as initrd image
mapping cofs31 to \??\C:\coLinux71
kernel boot parameters: 'root=/dev/cobd0'

PID: 4056
colinux: launching console
colinux: booting
colinux-net-daemon: auto selecting TAP
colinux-net-daemon: found TAP device named "TAP"
colinux-net-daemon: opening TAP: "TAP"
colinux-net-daemon: TAP driver version 8.4
colinux-net-daemon: enabling TAP...
Linux version 2.6.12-co-0.7.1 (george@CoDebianDevel) (gcc version 3.4.420050314
 (prerelease) (Debian 3.4.3-13sarge1)) #256MB LOWMEM available.
initrd enabled: start: 0xcff9a000  size: 0x00065ef7)
On node 0 totalpages: 65536
  DMA zone: 0 pages, LIFO batch:1
  Normal zone: 65536 pages, LIFO batch:31
  HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/cobd0
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 2048 (order: 11, 32768 bytes)
Using cooperative for high-res timesource
Console: colour CoCON 80x25


The TAP adapter gives itself a 169.x IP address and claims to be connected,
but refuses any ssh attempts.

How do I get colinux to get past the Console: line?
It exhibits the exact same behavior whether I run it with -t nt or let it
run the default console.
It also runs like this for both 6.4 (with the daemon updates), and for 7.1.

here is my config (7.1):
#
# This is an example for a configuration file that can
# be passed to colinux-daemon in this manner:
#
#    colinux-daemon @example.conf
#
# Note that you can still prepend or append configuration and
# boot parameters before and after '@', or you can use more
# that one '@ to load several settings one after another.
#
#    colinux-daemon @example.conf @overrider.conf mem=32
#

# The default kernel
kernel=vmlinux

# File contains the root file system.
# Download and extract preconfigured file from SF "Images for 2.6".
cobd0=c:\coLinux71\Debian-3.0r2.ext3-mit-backports.1gb

# Swap device, should be an empty file with 128..512MB.
#cobd1=c:\coLinux71\swap_device

# Tell kernel the name of root device (mostly /dev/cobd0,
# /dev/cobd/0 on Gentoo)
# This parameter will be forward to Linux kernel.
root=/dev/cobd0

# Initrd installs modules into the root file system.
# Need only on first boot.
initrd=initrd.gz

# Maximal memory for linux guest
mem=256

# Slirp for internet connection (outgoing) on second linux adapter.
# Inside running coLinux configure eth0 with this static settings:
# ipaddress 10.0.2.15   broadcast  10.0.2.255   netmask 255.255.255.0
# gateway   10.0.2.2    nameserver 10.0.2.3
#eth0=slirp

# Networking (tuntap as private network between gust and host)
eth1=tuntap

# Setup for serial device
#ttys0=COM1,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"

# Run an application on colinux start (Sample Xming, a Xserver)
#exec0=C:\Programs\Xming\Xming.exe,":0 -clipboard -multiwindow -ac"


--Mike