Running '/hurd/mtab /some/mountpoint/' correctly outputs the mount details.
However trying with a non-mountpoint still emits a result:
~:/hurd/mtab /any/dir/
/dev/hd0s2 /any/dir ext2fs
where /dev/hd0s2 is '/'. This is probably not intended behaviour.
There's also a less important issue: when
Roland McGrath, le Thu 28 Aug 2014 13:04:14 -0700, a écrit :
> > This is what I had put, is some information still missing?
>
> Oh, was that in the message? I must have missed it because I didn't see a
> ChangeLog header.
Ah, probably, indeed.
> (though it's ok to omit " (__fork)" in a libc fil
> This is what I had put, is some information still missing?
Oh, was that in the message? I must have missed it because I didn't see a
ChangeLog header.
> * sysdeps/mach/hurd/fork.c (__fork): Lock SS->lock around __proc_dostop()
> call.
Don't use () as if it were part of a function name. Othe
Roland McGrath, le Thu 28 Aug 2014 11:21:08 -0700, a écrit :
> Fix comment formatting, put space before paren,
Right, I really need to teach my editor to do the comments properly
automatically...
> write a ChangeLog entry.
This is what I had put, is some information still missing?
* sysdeps/mac
Fix comment formatting, put space before paren, write a ChangeLog entry.
Justus Winter, le Thu 28 Aug 2014 12:04:24 +0200, a écrit :
> Quoting Samuel Thibault (2014-08-27 21:53:39)
> > Justus Winter, le Mon 05 May 2014 14:10:48 +0200, a écrit :
> > > I believe I have found two problems in the glibc.
> > >
> > > 1. hurd_check_cancel takes 'lock', and then asserts that
>
Quoting Samuel Thibault (2014-08-27 21:53:39)
> Hello,
>
> Justus Winter, le Mon 05 May 2014 14:10:48 +0200, a écrit :
> > I believe I have found two problems in the glibc.
> >
> > 1. hurd_check_cancel takes 'lock', and then asserts that
> >'critical_section_lock' is not taken. However, hurd
