Note that the ufs filesystem has not been used much at all in a long time and has not gotten nearly as much real-world testing as ext2fs, so there may be more bugs.
As to the uid of the root dir, that seems reasonable enough. On the Hurd it seems most sane to have mkfs.ufs do whatever mke2fs does, so I changed it to match. As to the SIGLOST crash, that is kind of strange. That error is supposed to indicate that the RPC server appeared to die, in this case the storeio or filesystem. But you might have noticed that, especially if it was just the normal filesystem. Can you ascertain whether storeio is dying? (i.e., ls -l /dev/hd0s8, then find its storeio with ps, then get your SIGLOST and check if that process died.) If this happens when the server is not dying, can you figure out what's going on? First you can try "trap '' SIGLOST" to ignore the signal and see if it just shows you an error from lseek. You can also get a libc.so.0.2 with debug symbols, go to the lseek frame and see what made it decide to send the signal (or run it with a bkpt at _hurd_raise_signal). Thanks, Roland _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
