[coLinux-devel] yust an other installation report

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi coLinux-Hackers,

here is just an other installation report. I started with the latest (and
only) coLinux binary and added the colinux-daemon-replacement1. My System
in win2000 SP4. I installed the system as described in the README file and
started the colinux-daemon from a MSDOS window:
...
Cooperative Linux daemon
Installing kernel driver
Creating monitor
Monitor is running
...
Ok, this is fine. I then started the colinux-console and connect .... YES!
I'll see Linux running. Amazing! Excellent work!

So far so good. But I also can confirm some errors reported on this list.

First is the fsck reports a error message, so I disabled the rootcheck for
the further steps.
Then started with the basic system configuration and yes there are little
display problems with the colinux-console but its good enough to setup the
first basic steps and I later switched to ssh (putty).

So I setup networking. I just enabled "Internet Connection Sharing" in the
configuration of my LAN and that was all.
IP-Host:    192.168.0.1 (Connection Sharing)
IP-coLinux: 192.168.0.40

I then installed ssh with apt-get and I can confirm the network problems
reported on this list. Sometimes it takes 5-6 times to get a package
without md5sum errors. If I transfer larger files this problem appears
more often. But this errors happens also with files < 1MB and sometimes I
can transfer files larger the 1MB. I tried to install locales package but
this is 3.3MB and with this size I get always md5sum errors. Maybe I
should try this other TAB-Win32 driver that was discussed on the list. Any
success with this driver?

One other thing I see while installing with apt-get is that tar sends
warnings abount date/time. System date is 1-jan-1970 = 0. Ok maybe I have
to setup here something that the unix date/time is set by the host
date/time or maybe this is still missing in this early stage of the
colinux development. If I'll find no other solution I will try to get the
current date/time from the network.

I then tryed to attach a swap device as an extra cobd1 device. This works
without a problem.

I connected with putty and get the login prompt. Then a long pause (10-20
sec.) and then the password prompt. Is this long pause normal?

I then tried to shutdown system with command "shutdown -h now". The
terminal  gets closed but the daemon is still running. I din't know what
to do know, because I can't reconnect, so I just closed the MSDOS window I
used to run the daemon. That was not a good idea I shortly receive a blue
screen and some error messages about linux.sys. Because this is such a
miracle that linux can run such easy within windows that I expected this
kind of error much earlier.
So I read again in this list and found command "shutdown -g0 -y -i0" and
this works without problem... putty window gets closed and the daemon
reports:

Monitor shutting down
Closing monitor
Removing kernel driver
Stopping driver service
Removing driver service

Conclusion:
Very good work for the first release. Amazing what is possible.
The biggest problem (for me) so far is the network issue because this is
holding me back to install more packages.
Next importend is the fsck problem. There is a workaround but to disable
the check could only be a temporary solution. Less importend are the
date/time, shutdown and terminal problems.

Thanks to all the coLinux hackers that made this possible!

Thanks and kind regards,
 Thomas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAI9iWnwJBIFTVIqwRAvbIAJ0aFHTk2wPpyZOFEZn7J90xG5UlNgCfRfNN
J5K8TJycJOSIR+b948mrui0=
=8nXx
-----END PGP SIGNATURE-----