I'm having a real strange issue with filesystem access in hurd 0.2 ....
I'm an extreme newbie (hours old) so any pointers would be appreciated:
I'm running the debian/hurd 0.2 install within a vmware 2.0 VM. I
installed this by first running a RedHat 6.1 install into a VM (I needed
one anyway), getting what I thought to be the correct *.deb files on
ftp.debian.org, running cross-install to a new virtual disk, then using
that disk in a new VM to run hurd with grub floppy image
grub-floppy-19991023.
I had a hell of a time installing it .... failed many times. Finally got
it going, and now I'm seeing some really strange filesystem handling
issues. (I think my install issues were a symptom of this problem I'm
having).
Basically, if I log in as root and do:
find / -name "*.something" -print
I can hang hurd just about every time. A few times I was able to hang it
up by simply trying to install new deb files.
I tried to find something which would hang it every time, but no luck.
However one time I experienced something very strange: I did a find on
/share, and it came back with a few "file not found" errors. At that
point, if I did "ls /share", I got a file listing like you would expect.
If I did "cd /share; ls", I got a listing of what I believe was
/share/timezone. Repeated that several times with same results. Very
strange ... feels like some sort of incore vfs inode corruption (not sure
how that maps into hurd terminology). I then attempted to do a "sync", and
hung up hurd again.
Any hints? Maybe I have a bad install ... or perhaps vmware is not the
best place to be running this? Is there anything I can stick anywhere to
print debugging messages so I can trace this down?
Thanks,
-- jim
