From: Henry N. <Henry.Ne@Arcor.de> - 2005-09-15 20:29:37
|
Juergen Hennerich wrote: > [...] > >>>Most crashes seems to be cofs related. It looks like cofs is not in best >>>shape. I get regularly crashes, when I leave a FD open in cofs, run a >>>find in cofs or in most cases if I do a mkswap or a mkfs.... on a file >>>in a cofs. Is there some development planned in the near future? >> >>I would fix this, but I have never seen this bug on my system. >>dd and mkfs on file works for me. find and du works to. >> > > Have you tested a find or maybe a repeatedly find | xargs file over a > complete harddisk? 'find' yes, 'xargs file' no. I w'll try this. ( after sending this mail, and backup my work ;-) ) >>mkswap or swapon on a file on cofs should definitly not use. >>mkswap or swapon should only run, if this drive configured as cobd and >>not in use from cofs. Remember: cofs is async! So some crashes can >>preent, if you waits 1 second after close the file and sync the filesystem. >> > > I tested it only with mkswap on an emtpy file. Of I do not want to put > swap on a cofs. You can create the empty file under cofs. The mkswap should only run on a cobd device. Perhaps with a "sleep 1", so windows can close and unlock the file. This I have tested. dd if=/dev/zero of=/mnt_for_cofs/filename bs=1k count=256k Reboot with a cobdX to "filename" mkswap /dev/cobdX swapon /dev/cobdX Now you can use it via /etc/fstab for next boot. Problem is inside cofs or fuse driver. This is async and the file is locked after close for a while. This can give you some problems, if you try to use cofs files in scripts. Try this and you know, what I mean (it don't crash, but interesting output, the change date 1970-01-01) cd /mnt_for_cofs touch foo; stat foo; sleep 1; stat foo > [...] > >>>Are there plans to make it possible of having different coLinux drivers >>>(linux.sys) installed? (I don't ask for different coLinux versions >>>concurrently running) >> >>No. The daemon can only find linux.sys, if the daemon know the name of >>pipe. The pipe is fix coded in linux.sys and all daemons. >>Why you ask this? You can run different colinux-daemons without >>problems. All running colinux-daemons are separate. You need only >>separate TAP devices, if TAP used. >> >>One linux.sys is a manager for multiple colinux seassions at same time, >>from different images, in separate terminals. >> > > This is a misunderstanding. I know how coLinux works. I wanted to know > if some sort of versioning is planned, so that two different interfaces > could be used at the same time, or if not concurrently but without a > removal and installation of the linux.sys driver. > > On the other side this would be completely wasted, if the interface > would be stable. From version 6.3.x to 7.1.x the interface can't use the same struct. On devel versions (7.1.x) the interface is in working process. You should not use differ daemons on same linux.sys, this risk a blue screen. For that we have a api-version check. Use of differ versions in same time would be to difficould for handling (in the current source today). If you would use newer version in some older images, than should let initrd.gz update your /lib/modules. The initrd checks for new kernel version and updates your rootfs. You can also do that in your booting process with a tar.gz of new modules over the cofs driver. > [...] > >>>Is there an easy way to check if port 22 on Windows is already used? >> >>Grep over "netstat -a -n -p TCP -o" and locking for "0.0.0.0:22" as >>local address. The selected line give you the PID of process (option -o). >> > > I know this. If netstat is available on all NT based systems, this could > work. But I have no grep available inside the installer. netstat is on all W2K, XP and NT. Installer have small scripting inside, I have read. On other side, you say, you run a installation initrd before starts working image. You can put netstat output to a file and grep this in your initrd for configuration? > Btw. Is rsh available per default on all NT based systems? What is 'rsh' on NT? Never seen that on my XP and W2K. > >>If the port 22 is in use, before slirp starts, then slirp does not bind >>the port (still skip over). Any sugestion is to use a alternate port on >>host for forwarding the SSH and TELNET, such as >> eth0=slirp,"",tcp:2222:22/tcp:2323:23 >> > > This would be a good idea: > eth0=slirp,"",tcp:22:22/tcp:333:22 Yes, very good idea. :) Fallback to port 333, if port 22 is inuse. > [...] >>It's something mistaken in the slirp code near the "ouraddr". In >>current version slirp only supports one ipaddres for host. But in the >>real world the host has more ones (see "ipconfig /all", with LAN cable >>and without) >> >>But slirp can never forward all ports from host to linux. >> > > I know, that while slirp could bind on every address in the > 127.xxx.xxx.xxx network the Windows ports are still occupied. > But maybe there is some other trick to this behavior in a userspace > solution. Currently slirp has no user configuration from linux side. The old source of Slirp has a "configurator" on address "10.0.2.0:telnet". This don't exist under colinux. Best idea: If Linux goes to listen on port, it should forward on host ip and port. But this is not in design of slirp. If anybody find the condition, why slirp not transmit or translate (NAT) the incomming packets on 127.0.0.1, then it could work. Sometimes I have a telnet opened from windows to linux on 127.0.0.1, but the packets goes different ways, if I connect a cable on real LAN or unplug the cable. I thing it's the problem, that slirp only supports one actual IP for host. If we correct this, than you can connect from windows the 127.0.0.1 to colinux for ssh. -- Henry Nestler |