Hi, On Sat, Jan 02, 2010 at 12:54:33PM +0800, Da Zheng wrote: > On 09-12-31 ??????11:04, olafbuddenha...@gmx.net wrote:
> >> But it always worked before. I can also mount /dev/hd1 to my file > >> system. 'settrans -a subhurd /hurd/ext2fs /dev/hd1' works on my > >> system. > > > > Have you put a filesystem on /dev/hd1 without partitioning it? > > That's certainly unusual... But if it is so, I guess that's not the > > reason for the failure. > I have used fdisk to create only one partition on that disk. But then you still have a boot sector and probably a few empty sectors before the start of the actual partition -- I don't see how ext2fs could ever have mounted this... Unless you actually did "mke2fs /dev/hd1" after partitioning -- which *overwrote* the partition table you created with fdisk, and instead put the filesystem directly on the unpartitioned disk. > I tried to create /dev/hd1s1, but it doesn't work. Err... What do you mean? You can't mke2fs /dev/hd1s1? Well, if indeed you overwrote the partition table as described above, that's no wonder :-) > I finally got a working subhurd Let us know what the problem was, and how you got around it :-) > and I tested my modified subhurd with samuel's patch to auth. It seems > working. I run subhurd for so many times, but didn't see subhurd hang > in login. That's great news! :-) > But it does hang somewhere else. Maybe there are some other bugs in > subhurd. I see... Still, progress. > I wonder if it's because the proc server in subhurd cannot run in a > higher priority. Doesn't seem too likely to me... If some protocol relies on proc being scheduled before other processes, that would be *extremely* fragile. Of course you could still test what happens if you set the higher priority with some backdoor or a debugger or something. Perhaps the lower priority indeed uncovers some kind of race condition... Though I must say that other race conditions (like the auth one) seem more likely. -antrik-
