Re: Questions on the interoperability between libc, gnumach and hurd servers

[Samuel Thibault]

Svante Signell, le Sun 16 Sep 2012 21:33:43 +0200, a écrit :
> On Sun, 2012-09-16 at 18:16 +0200, Samuel Thibault wrote:
> > Svante Signell, le Sun 16 Sep 2012 17:53:19 +0200, a écrit :
> > > What are the powerful features compared to a monolithic kernel.
> > 
> > Using your (as a user) own pflocal instead of the system-provided one,
> > using gdb/valgrind on it, etc. See the wiki pages about the benefits of
> > the Hurd.
> 
> Sorry, valgrind is not yet ported to Hurd.

*yet*.

> > > Sorry, I cannot see them. I only find tons of not implemented things
> > > and nasty bugs.
> > 
> > I'm speechless.
> > 
> > Linux also has tons of not implemented things and nasty bugs. It doesn't
> > make it a too bad kernel. Not for all situations.
> 
> Still, I've not yet seen any killer application for Hurd, have you?

Mounting images as a user is already a killer app for me, for
instance. Not being able to do it on remote Linux servers where fuse is
not enable (and I doubt will ever be) is really a problem in quite a few
situations.

> > > Sad case for Linux too if that is true :(
> > 
> > That's life. You have to understand that you won't always have
> > documentation and people taking time to explain you things. The more you
> > get into the core of the system, the less documentation you'll find. It
> > has been so in all systems I've seen.
> 
> Nevertheless, it's always easier to learn things top-down than bottom-up
> for most people. And reading (unknown) source code is definitely _not_
> top-down.

But it's all you'll have at some point. You'll have to get used to it.

> > > Why not adding to hurd.texi or creating some overview document
> > > describing the overall picture.
> > 
> > That's what I have added as rpc.mdwn
> 
> Have you added that to hurd.texi too?

No. I'm not sure whether it belongs there. Perhaps the introduction, and
still.

Samuel