Re: News 2009-08-31, documentation, wiki

2009-09-29 Thread Arne Babenhauserheide
Hi, Am Montag, 28. September 2009 10:16:29 schrieb Thomas Schwinge: > > The only thing which is hard to fix are pages which have > > very many manual backlinks. > > Even that (usually) is not hard at all if you know your Unix shell > scripting: find / grep / sed / ... That's true... I think I e

Re: nsmux Documentation

2009-09-29 Thread Sergiu Ivanov
Hello, On Tue, Sep 29, 2009 at 08:27:37AM +0200, Arne Babenhauserheide wrote: > By the way: Do we already have documentation about nsmux on the website? I haven't yet written any documentation about nsmux (save for a simple README which resides nsmux directory) :-( I'm not sure whether that READ

Re: hurd-web/hurd/translator/unionmount.mdwn

2009-09-29 Thread Sergiu Ivanov
Hello, On Tue, Sep 29, 2009 at 08:37:25AM +0200, Arne Babenhauserheide wrote: > Am Montag, 28. September 2009 17:16:01 schrieb Sergiu Ivanov: > > I have finally run into a period of time which I could dedicate to the > > Hurd: I have just updated my own page, have put the information from > > hurd

[task #9686] implement readlinkat

2009-09-29 Thread Thomas Schwinge
Follow-up Comment #1, task #9686 (project hurd): insserv is now working around this by also detecting whether __stub_readlinkat is defined or not, and resorting to alternative code if it is. Nevertheless, readlinkat, as well as other functions should be implemented. See /usr/include/gnu/stubs-3

[task #9686] implement readlinkat

2009-09-29 Thread anonymous
Follow-up Comment #2, task #9686 (project hurd): Ugh, how horrible hack in insserv... Anyway, see http://sources.redhat.com/ml/libc-alpha/2009-09/msg00058.html and later, hopefully Roland will accept something :) ___ Reply to this item a

[task #9686] implement functions missing in the Hurd port of glibc

2009-09-29 Thread Thomas Schwinge
Update of task #9686 (project hurd): Summary:implement readlinkat => implement functions missing in the Hurd port of glibc ___ Follow-up Comment #3: That's what I told them to use instead of the * && !defined(__gnu_hu

Re: nsmux Documentation

2009-09-29 Thread Arne Babenhauserheide
Am Dienstag, 29. September 2009 20:02:10 schrieb Sergiu Ivanov: > I haven't yet written any documentation about nsmux (save for a simple > README which resides nsmux directory) :-( I'm not sure whether that > README is useful, but you can find it at > http://github.com/scolobb/nsmux . I'd say the

Shutting down some Hurd mailing lists? (was: News 2009-08-31, documentation, wiki)

2009-09-29 Thread Thomas Schwinge
Hello! This was about off-topic discussions on bug-hurd. On Tue, Sep 29, 2009 at 08:27:37AM +0200, Arne Babenhauserheide wrote: > Am Montag, 28. September 2009 10:16:29 schrieb Thomas Schwinge: > > A bit of off-topicness is always > > needed and tolerable, but you have to know when to stop. Else

Re: Shutting down some Hurd mailing lists? (was: News 2009-08-31, documentation, wiki)

2009-09-29 Thread Roland McGrath
IIRC hurd-devel was a private list, so if you shut it down just shut it down completely rather than making it forward anywhere.

Re: nsmux Documentation

2009-09-29 Thread Sergiu Ivanov
Hello, On Tue, Sep 29, 2009 at 09:30:15PM +0200, Arne Babenhauserheide wrote: > Am Dienstag, 29. September 2009 20:02:10 schrieb Sergiu Ivanov: > > I haven't yet written any documentation about nsmux (save for a simple > > README which resides nsmux directory) :-( I'm not sure whether that > > REA

Re: nsmux Documentation

2009-09-29 Thread Arne Babenhauserheide
Hi, Am Dienstag, 29. September 2009 22:51:14 schrieb Sergiu Ivanov: > Great :-) I wasn't sure *this* README was useful. It describes what the translator does and how to use it, so it looks very useful to me :) Best wishes, Arne signature.asc Description: This is a digitally signed message p

Re: Shutting down some Hurd mailing lists? (was: News 2009-08-31, documentation, wiki)

2009-09-29 Thread Arne Babenhauserheide
Am Dienstag, 29. September 2009 21:32:51 schrieb Thomas Schwinge: > > And adding another list will make the Hurd lists less accessible. > > Which brings us (back?) to another topic: should we shut down some Hurd > mailing lists? web-hurd and hurd-devel aren't being used at all; > help-hurd hardly