bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Svante Signell
Subject: Re: Questions on the interoperability between libc, gnumach and hurd servers
Date: Sun, 16 Sep 2012 21:33:43 +0200

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.

> > 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?

> > 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.
 
> > 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?

> > The wiki is good, but at least me appreciate written manuals too.
> 
> Why?

Well reading web pages assumes you have to have access to a computer/a
pad/whatever and internet access, that is not needed with things written
on paper.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]