Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

December 13, 2024 at 11:17 AM, "Sergey Bugaev" mailto:buga...@gmail.com?to=%22Sergey%20Bugaev%22%20%3Cbugaevc%40gmail.com%3E > wrote: > > On Thu, Dec 12, 2024 at 6:14 PM wrote: > > > > > #stillFriendsRight? > > > Totally! I'm just hoping I didn't offend you or something. > > And please ke

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

On Thu, Dec 12, 2024 at 6:14 PM wrote: > #stillFriendsRight? Totally! I'm just hoping I didn't offend you or something. And please keep up the good work on docs, just... not that way :) Sergey

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

December 12, 2024 at 4:04 AM, "Sergey Bugaev" mailto:buga...@gmail.com?to=%22Sergey%20Bugaev%22%20%3Cbugaevc%40gmail.com%3E > wrote: > > On Wed, Dec 11, 2024 at 11:58 PM Samuel Thibault > wrote: > > > > > jbra...@dismail.de, mailto:jbra...@dismail.de, le mer. 11 déc. 2024 > > 20:46:54 +00

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

On 12/12/24 5:04 PM, Sergey Bugaev wrote: On Wed, Dec 11, 2024 at 11:58 PM Samuel Thibault wrote: jbra...@dismail.de, le mer. 11 déc. 2024 20:46:54 +, a ecrit: Sergey, are you ok with "assigning copyright" to the FSF for this document? Sergey has already assigned copyright for all past&f

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

Sergey Bugaev, le jeu. 12 déc. 2024 12:04:36 +0300, a ecrit: > Again, this _has_ been handled appropriately in this case, so no > complaints here. > > Hope that didn't sound overly negative :) Sure, better say these things than grumble silently :) Samuel

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

On Wed, Dec 11, 2024 at 11:58 PM Samuel Thibault wrote: > jbra...@dismail.de, le mer. 11 déc. 2024 20:46:54 +, a ecrit: > > Sergey, are you ok with "assigning copyright" to the FSF for this document? > > Sergey has already assigned copyright for all past&future hurd > contributions. Uh. I ass

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

Applied with copyright notice addition, thanks! Zhaoming Luo, le mer. 11 déc. 2024 11:29:49 +0800, a ecrit: > * microkernel/mach/mig/documentation.mdwn: add a link pointing to mig-mutate > page > * .../mach/mig/documentation/mig-mutate.mdwn: new file. Introduction to a > mig-m

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

Hello, jbra...@dismail.de, le mer. 11 déc. 2024 20:46:54 +, a ecrit: > Sergey, are you ok with "assigning copyright" to the FSF for this document? Sergey has already assigned copyright for all past&future hurd contributions. Samuel

Re: [PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

December 10, 2024 at 10:29 PM, "Zhaoming Luo" mailto:zhming...@163.com?to=%22Zhaoming%20Luo%22%20%3Czhmingluo%40163.com%3E > wrote: > > * microkernel/mach/mig/documentation.mdwn: add a link pointing to mig-mutate > page > * .../mach/mig/documentation/mig-mutate.mdw

[PATCH 1/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

* microkernel/mach/mig/documentation.mdwn: add a link pointing to mig-mutate page * .../mach/mig/documentation/mig-mutate.mdwn: new file. Introduction to a mig-mutate.h file Signed-off-by: Zhaoming Luo --- microkernel/mach/mig/documentation.mdwn | 2 +- .../mach/mig/documentation/mig

[PATCH 0/1 Web] Add microkernel/mach/mig/documentation/mig-mutate page

Add the text about a mig-mutate.h file from mail list[0] to wiki with some modifications so it is more friendly after rendered. [0]: https://mail.gnu.org/archive/html/bug-hurd/2024-11/msg00045.html Zhaoming Luo (1): Add microkernel/mach/mig/documentation/mig-mutate page microkernel/mach/mig

[PATCH 3/5] I put all "developer references" on hurd/documentation.

The pages hurd and hurd/documentation both have "documentation sections". That seems a little silly. I am added a link in hurd to "developer documentation" that links to hurd/documentation. * hurd: link to hurd/documentation. * hurd/documentation: combine the documentatio

Re: [PATCH 6/6] added short documentation for some translators.

but also this is contrary to the GNU project official documentation format. Samuel

Re: [PATCH 6/6] added short documentation for some translators.

rnative TCP/IP stack. > > * pflocal:: > > * libpipe:: > > * Socket Interface:: Network communication I/O protocol. > > @@ -4710,6 +4798,55 @@ FIXME: this subsystem is in flux @c Thomas, > > 26-03-1998 > > > > @node pfinet > >

Re: [PATCH 6/6] added short documentation for some translators.

nu > > -* pfinet:: TCP/IP stack. > > +* pfinet:: Default TCP/IP stack. > > +* lwip:: Alternative TCP/IP stack. > > * pflocal:: > > * libpipe:: > > * Socket Interface:: Network communication I/O protocol. > > @@ -4710,6 +4798,55 @@ FIXME: this subsyst

Re: [PATCH 6/6] added short documentation for some translators.

ement > The rump > +TCP/IP stack will most likely be a better option, but no one has > +started on it yet. > + > +@node lwip > +@section lwip > +@cindex lwip > + > +Developers created the @code{lwip} TCP/IP library with the design > +goals of minimalism and portability.

Re: [PATCH 6/6] added short documentation for some translators.

Joshua Branson, le jeu. 21 sept. 2023 12:48:22 -0400, a ecrit: > +Alternatively one can @emph{name} a pipe with the command > +@command{mkfifo }, which will persist until you remove it with > +the command @command{rm }. This lets you use commands that > +interact with the pipe from many different

[PATCH 6/6] added short documentation for some translators.

From: "jbra...@dismail.de" * doc/hurd.texi (fifo): added a short explanation. * doc/hurd.texi (ifsock): added a really short explanation. * doc/hurd.texi (null): added a short explanation. * doc/hurd.texi (devnode): tiny grammer fix. * doc/hurd.texi (Storeio): short explanation. * doc/hurd.texi (

Re: Documentation for lwip-hurd

ages. One just needs to add “ Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Co

Re: Documentation and ideas for related work

On Fri, Apr 19, 2019 at 06:43:41PM +0200, Paul Boddie wrote: > > What's not described, obviously, is external memory managers, but it's > > similar to how kernel memory managers (file systems) interface with > > the VM. > > I don't really follow the distinction between external and kernel memory

Re: Documentation and ideas for related work

e Linux memory management code uses a > mostly similar design), documentation shouldn't lack. I will have to dig around for informative references. > I recommend the NetBSD UVM paper, which extensively describes the BSD > VM, and in turn much of the Mach VM. This did appear to be rather i

Re: Documentation for lwip-hurd

gt; > > > Jasine > > > > On Tue, Apr 16, 2019 at 1:40 AM Joshua Branson > wrote: > > > > Sooraj Tom <111501...@smail.iitpkd.ac.in> writes: > > > > > Hi, > > > > > > I have been developing documentation for the hurd po

Re: Documentation for lwip-hurd

e/hurd/hurd.html > Is it okay to also mention our institute name somewhere in the page, though > the > licensing is free? > > Jasine > > On Tue, Apr 16, 2019 at 1:40 AM Joshua Branson wrote: > > Sooraj Tom <111501...@smail.iitpkd.ac.in> writes: > > > H

Re: Documentation and ideas for related work

organised. That question relates much more to the Mach kernel than to the Hurd. And since the Mach VM is the ancestor of most "modern" operating systems (the BSDs in particular, but the Linux memory management code uses a mostly similar design), documentation shouldn't lack. I

Documentation and ideas for related work

Hello, Since there have been some messages about documentation, I thought I might ask about architectural documentation for the Hurd. I have taken a look at a few of the resources mentioned on this page: https://www.gnu.org/software/hurd/hurd/documentation.html Previously, I tried to get some

Re: Documentation for lwip-hurd

Hello, Jasine Babu, le mar. 16 avril 2019 12:14:22 +0530, a ecrit: > Is it okay to also mention our institute name somewhere in the page, though > the > licensing is free? Sure, free licences don't exclude author information and copyright attribution :) Samuel

Re: Documentation for lwip-hurd

gt; > > > I have been developing documentation for the hurd port of lwIP. So far, > it has brief > > descriptions about all functions, the starting up of the translator and > the journey of a > > packet. We are now planning to add overview for the files and details >

Re: Documentation for lwip-hurd

t; > I have been developing documentation for the hurd port of lwIP. So far, > it has brief > > descriptions about all functions, the starting up of the translator and > the journey of a > > packet. We are now planning to add overview for the files and details > about function > &

Re: Documentation for lwip-hurd

Sooraj Tom <111501...@smail.iitpkd.ac.in> writes: > Hi, > > I have been developing documentation for the hurd port of lwIP. So far, it > has brief > descriptions about all functions, the starting up of the translator and the > journey of a > packet. We are now plann

Re: Documentation for lwip-hurd

Sooraj Tom <111501...@smail.iitpkd.ac.in> writes: > Hi, > > I have been developing documentation for the hurd port of lwIP. So far, it > has brief > descriptions about all functions, the starting up of the translator and the > journey of a > packet. We are now plann

Documentation for lwip-hurd

Hi, I have been developing documentation for the hurd port of lwIP. So far, it has brief descriptions about all functions, the starting up of the translator and the journey of a packet. We are now planning to add overview for the files and details about function parameters. The wiki is

Re: Documentation writer

Hi! Reposting this, so that "evergetis" can actually see the answer, when not (yet?) subscribed to the bug-hurd mailing list. (It's good practice to not strip off recipients when replying.) Thanks for the offer to help with documentation, and thanks Joshua for guidance! For ref

Re: Documentation writer

everge...@csd.auth.gr writes: > Hello! I am interested in helping you write the documentation for The GNU > Hurd. > I am a pre graduate student and it's going to be my project for a class. I > would be more than happy to contribute! Hello! There's several ways that you

Documentation writer

Hello! I am interested in helping you write the documentation for The GNU Hurd. I am a pre graduate student and it's going to be my project for a class. I would be more than happy to contribute!

Re: Documentation severely outdate on gnu.org

/users-guide/using_gnuhurd.html#dir > >> > as documentation for the Hurd, which is just antique. Does anybody know > >> > how to update this? > >> > >> See the bits about “Webpages repository” at > >> <https://savannah.gnu.org/cvs/?group=hurd>.

Re: Documentation severely outdate on gnu.org

Samuel Thibault skribis: > Ludovic Courtès, on dim. 05 nov. 2017 18:37:06 +0100, wrote: >> Samuel Thibault skribis: >> > People find >> > https://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html#dir >> > as documentation for the Hurd, which is just an

Re: Documentation severely outdate on gnu.org

Ludovic Courtès, on dim. 05 nov. 2017 18:37:06 +0100, wrote: > Samuel Thibault skribis: > > People find > > https://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html#dir > > as documentation for the Hurd, which is just antique. Does anybody know > > how to upd

Re: Documentation severely outdate on gnu.org

Hi, Samuel Thibault skribis: > People find > https://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html#dir > as documentation for the Hurd, which is just antique. Does anybody know > how to update this? See the bits about “Webpages repository” at <https://savannah.gnu

Re: Documentation severely outdate on gnu.org

Hello, On Thu, 2 Nov 2017 14:20:32 +0100 Samuel Thibault wrote: > People find > https://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html#dir > as documentation for the Hurd, which is just antique. Does anybody know > how to update this? As far as I remember and understand

Documentation severely outdate on gnu.org

Hello, People find https://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html#dir as documentation for the Hurd, which is just antique. Does anybody know how to update this? Samuel

Documentation work (was: re involved)

Hi James! On Tue, 16 Apr 2013 00:07:14 +0200, Arne Babenhauserheide wrote: > Am Samstag, 13. April 2013, 06:26:57 schrieb James Simko: > > do you still need a technical writer to do documentation? > > Sure. Just take part in improving the wiki. Yep, and welcome! May I ask ho

Re: [PATCH] libps/ps.h: Fix typo in the documentation of _proc_stat_create().

Hi! On Mon, 22 Oct 2012 01:56:08 +0200, Cyril Roelandt wrote: > pc_context_find_proc_stat() does not exist. The right function name is > "ps_context_find_proc_stat". Pushed as 2e22275ea95f4a528f8badf24b833fb1f060f7f6, thanks. Grüße, Thomas pgpiTZ6CO8lF1.pgp Description: PGP signature

[PATCH] libps/ps.h: Fix typo in the documentation of _proc_stat_create().

pc_context_find_proc_stat() does not exist. The right function name is "ps_context_find_proc_stat". Signed-off-by: Cyril Roelandt --- libps/ps.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libps/ps.h b/libps/ps.h index 91fdc70..bcc43f8 100644 --- a/libps/ps.h +++ b/li

Re: Technical Documentation Help

Hallo Lee! On Sat, 9 Jul 2011 12:41:54 -0500, Lee DuBose wrote: > My name is Lee DuBose and I am [...] Thanks for this nice introduction. > I was wondering what I could do to help gnu in > regards to being a technical writer, by helping document code or anything > else that needs to be writte

Technical Documentation Help

Hello, My name is Lee DuBose and I am a junior Computer Science major at the University of Mississippi. I was wondering what I could do to help gnu in regards to being a technical writer, by helping document code or anything else that needs to be written up. I hope you reply as I am very excited

Re: device_set_filter documentation update

Hello, A second draft is sent as reply to this message to address the issues identified by Richard. On Thu, 20 Jan 2011 09:57:32 +0100 Richard Braun wrote: > 3/ > You should probably describe that, when a packet is received by a > listener, the flags are *either* NETF_IN or NETF_OUT, and not a >

Re: device_set_filter documentation update

On Sun, Jan 16, 2011 at 10:20:35PM -0300, Diego Nieto Cid wrote: > Hello, > > Commit 1ca2a1632d7325ee26b2c701b38c1d2e2fcb6f80 in gnumach changed > the interface with the > packet filter and the GNU Mach Reference Manual got outdated. > > Here's the email where the patch wa

Re: device_set_filter documentation update

On Sun, Jan 16, 2011 at 10:20:35PM -0300, Diego Nieto Cid wrote: > Hello, > > Commit 1ca2a1632d7325ee26b2c701b38c1d2e2fcb6f80 in gnumach changed > the interface with the > packet filter and the GNU Mach Reference Manual got outdated. > > Here's the email where the patch wa

device_set_filter documentation update

Hello, Commit 1ca2a1632d7325ee26b2c701b38c1d2e2fcb6f80 in gnumach changed the interface with the packet filter and the GNU Mach Reference Manual got outdated. Here's the email where the patch was submitted: http://lists.gnu.org/archive/html/bug-hurd/2006-04/msg00032.html

Re: MIG documentation

Mary R. Thompson, MIG - THE MACH > > INTERFACE GENERATOR. ps, doc. November 1989. Department of Computer > > Science, Carnegie-Mellon University. > > > > That's the one I've once been reading. > > Shouldn't these be included in the mig package, so

Re: MIG documentation (was: libpager deadlock)

rtment of Computer > Science, Carnegie-Mellon University. > > That's the one I've once been reading. Shouldn't these be included in the mig package, so they can be called "documentation"? Samuel

MIG documentation (was: libpager deadlock)

t; simpleroutine, so a call to mach_msg_trap should only enqueue the > > > message and return immediately. > > > > Is this kind of information documented somewhere? I can't find such > > documentation in MIG's source. > > Humm... must be a paper somewher

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

Hello! On Sat, Oct 24, 2009 at 08:53:35AM +0200, olafbuddenha...@gmx.net wrote: > On Mon, Sep 28, 2009 at 10:16:29AM +0200, Thomas Schwinge wrote: > > On Tue, Sep 08, 2009 at 10:08:23AM +0300, Sergiu Ivanov wrote: > > > Anyway, I hope the solution I suggested above (adding the &

Re: OT: automation (was: News 2009-08-31, documentation, wiki)

Am Samstag, 24. Oktober 2009 09:03:10 schrieb olafbuddenha...@gmx.net: > Hi, > > On Tue, Sep 29, 2009 at 08:27:37AM +0200, Arne Babenhauserheide wrote: > > Am Montag, 28. September 2009 10:16:29 schrieb Thomas Schwinge: > > > Even that (usually) is not hard at all if you know your Unix shell > > >

nsmux on / (was: nsmux Documentation)

Hi, On Wed, Sep 30, 2009 at 09:45:32PM +0200, Arne Babenhauserheide wrote: > Am Mittwoch, 30. September 2009 18:36:34 schrieb Sergiu Ivanov: > > > It reads nice, but I miss an info: How can I activate nsmux, so I > > > can use the magic filenames? > > Can I also put it "on /"? That way I could a

temporary branches (was: News 2009-08-31, documentation, wiki)

Hi, On Wed, Sep 30, 2009 at 04:19:41PM +0300, Sergiu Ivanov wrote: > So, personal branches in the Hurd wiki repository are fine for > temporary changes, right? Yes. -antrik-

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

Hi, On Mon, Sep 28, 2009 at 10:16:29AM +0200, Thomas Schwinge wrote: > On Tue, Sep 08, 2009 at 10:08:23AM +0300, Sergiu Ivanov wrote: > > Anyway, I hope the solution I suggested above (adding the > > documentation to my hurd-web page) should be good. > > There's no n

OT: automation (was: News 2009-08-31, documentation, wiki)

Hi, On Tue, Sep 29, 2009 at 08:27:37AM +0200, Arne Babenhauserheide wrote: > Am Montag, 28. September 2009 10:16:29 schrieb Thomas Schwinge: > > Even that (usually) is not hard at all if you know your Unix shell > > scripting: find / grep / sed / ... > > That's true... I think I even wrote a sma

nsmux on / (was: nsmux Documentation)

Hi, On Fri, Oct 02, 2009 at 09:16:38AM +0200, Carl Fredrik Hammar wrote: > A secure way to use it on the entire filesystem would be to make use > of settrans -C flag, to start a shell chrooted to nsmux but not > actually set on /. This way only programs started from the shell > would be affected

default features (was: nsmux Documentation)

Hi, On Fri, Oct 02, 2009 at 08:23:24AM +0200, Arne Babenhauserheide wrote: > PS: I think that to get people to do some more testing, a few easy to > use examples (and one complex and powerful example) would be efficient > - especially if they directly contain the shell commands to use (copy > pas

Re: nsmux Documentation

Am Sonntag, 4. Oktober 2009 20:36:16 schrieb Sergiu Ivanov: > Thank you for the idea! :-) I will add such examples, but only after I > have fixed the ugly bugs concerning the behaviour of nsmux run as > normal user. These bugs are top priority now, because it is my > enormous blunder to have teste

Re: nsmux Documentation

Hello, On Fri, Oct 02, 2009 at 09:16:38AM +0200, Carl Fredrik Hammar wrote: > On Thu, Oct 01, 2009 at 07:52:57PM +0300, Sergiu Ivanov wrote: > > On Wed, Sep 30, 2009 at 09:45:32PM +0200, Arne Babenhauserheide wrote: > > > > Can I also put it "on /"? > > > That way I could activate it systemwide :

Re: nsmux Documentation

Hello, On Fri, Oct 02, 2009 at 08:23:24AM +0200, Arne Babenhauserheide wrote: > PS: I think that to get people to do some more testing, a few easy > to use examples (and one complex and powerful example) would be > efficient - especially if they directly contain the shell commands > to use (copy p

Re: nsmux Documentation

Hi, On Thu, Oct 01, 2009 at 07:52:57PM +0300, Sergiu Ivanov wrote: > On Wed, Sep 30, 2009 at 09:45:32PM +0200, Arne Babenhauserheide wrote: > > Am Mittwoch, 30. September 2009 18:36:34 schrieb Sergiu Ivanov: > > > > It reads nice, but I miss an info: How can I activate nsmux, so I > > > > can use

Re: nsmux Documentation

Am Donnerstag, 1. Oktober 2009 18:52:57 schrieb Sergiu Ivanov: > Yes, this is the long-term goal, though I definitely won't advise you > trying this out ATM -- one of the most important issues is security, > about which nsmux does nothing but standard procedures, but it is > possible that something

Re: nsmux Documentation

Hello, On Wed, Sep 30, 2009 at 09:45:32PM +0200, Arne Babenhauserheide wrote: > Am Mittwoch, 30. September 2009 18:36:34 schrieb Sergiu Ivanov: > > > It reads nice, but I miss an info: How can I activate nsmux, so I > > > can use the magic filenames? > > > > Thank you for pointing out! :-) > >

Re: nsmux Documentation

Am Mittwoch, 30. September 2009 18:36:34 schrieb Sergiu Ivanov: > > It reads nice, but I miss an info: How can I activate nsmux, so I > > can use the magic filenames? > > Thank you for pointing out! :-) Can I also put it "on /"? That way I could activate it systemwide :) > I've added short us

Re: nsmux Documentation

, I came to the > > conclusion that that README is really useless :-( It stresses wrong > > points and describes yet non-existent features. That's why I > > concocted a brand new piece of documentation and added it to the wiki. > > Great! > > It reads nice, but I miss an

Re: nsmux Documentation

escribes yet non-existent features. That's why I > concocted a brand new piece of documentation and added it to the wiki. Great! It reads nice, but I miss an info: How can I activate nsmux, so I can use the magic filenames?

Re: nsmux Documentation

ncocted a brand new piece of documentation and added it to the wiki. Regards, scolobb

Re: nsmux Documentation

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

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

explanation on some Hurd > > > > > wiki page. > > [...] > > > There is a small problem though: I'm not sure on which page to create > > > the documentation. There is hurd-web/hurd/translator/unionmount.mdwn, > > > but it's the description of the

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

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

Re: nsmux Documentation

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: nsmux Documentation

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

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

IIRC hurd-devel was a private list, so if you shut it down just shut it down completely rather than making it forward anywhere.

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

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: nsmux Documentation

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/scolob

Re: nsmux Documentation

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

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

This way we can't mess up anymore with the > detail of how many days every months has. (I don't care strongly about > that one, though.) My reason for using the last day was mainly that it can strengthen the pretext that the month is always a look _back_ whi

News 2009-08-31, documentation, wiki

required) I can provide a short explanation on some Hurd > > > > wiki page. > [...] > > There is a small problem though: I'm not sure on which page to create > > the documentation. There is hurd-web/hurd/translator/unionmount.mdwn, > > but it's the descri

Re: unionfs Documentation

On Fri, Aug 28, 2009 at 2:37 AM, wrote: > On Wed, Aug 26, 2009 at 01:07:27AM +0200, Gianluca Guida wrote: >> > This is a non-trivial problem. Other unionfs implementations >> > probably spent considerable time figuring out how to do it best. I >> > entreated Gianluca to check what over implementat

Re: unionfs Documentation

Hi Gianluca, On Wed, Aug 26, 2009 at 01:07:27AM +0200, Gianluca Guida wrote: > Hm, funny things happens while grepping past mail. Hehe... Nice to see you here :-) > > This is a non-trivial problem. Other unionfs implementations > > probably spent considerable time figuring out how to do it best

Hurd Interfaces Documentation

Hello, Ruffling through the pieces of data in my head, I came to the conclusion that I'd like to add some documentation about the io interface and fshelp and iohelp librabries. In connection with this I have several questions: 1. Should fshelp and iohelp libraries go on the hurd/interface

Re: unionfs Documentation

Hm, funny things happens while grepping past mail. > This is a non-trivial problem. Other unionfs implementations probably > spent considerable time figuring out how to do it best. I entreated > Gianluca to check what over implementations do, instead of trying to > reinvent the wheel -- but he wou

Re: unionfs Documentation

or the file should I chose? unionfs already has a README, so something different (like ``DOCUMENTATION'' or ``README.LONG'') is required. > > > @item -u > > > @itemx --underlying > > > Add the underlying file system to the list of union mounted file >

Re: unionfs Documentation

ergiu Ivanov wrote: > > > > I'm sending in my attempt to compile a unionfs documentation. It > > > > is formatted as a stand-alone Texinfo file for now, so that I am > > > > able to build and view .info files from it. > [...] > > > put it in th

Re: unionfs Documentation

Hi, On Tue, Aug 04, 2009 at 01:00:10AM +0200, Thomas Schwinge wrote: > On Fri, Jul 17, 2009 at 05:08:28AM +0200, olafbuddenha...@gmx.net wrote: > > On Sat, Jun 13, 2009 at 09:23:23AM +0300, Sergiu Ivanov wrote: > > > I'm sending in my attempt to compile a unionfs doc

Re: unionfs Documentation

Hello! On Fri, Jul 17, 2009 at 05:08:28AM +0200, olafbuddenha...@gmx.net wrote: > On Sat, Jun 13, 2009 at 09:23:23AM +0300, Sergiu Ivanov wrote: > > I'm sending in my attempt to compile a unionfs documentation. It is > > formatted as a stand-alone Texinfo file for now,

Re: unionfs Documentation

Hi, On Sat, Jun 13, 2009 at 09:23:23AM +0300, Sergiu Ivanov wrote: > I'm sending in my attempt to compile a unionfs documentation. It is > formatted as a stand-alone Texinfo file for now, so that I am able to > build and view .info files from it. I don't understand -- why c

unionfs Documentation

Hello, I'm sending in my attempt to compile a unionfs documentation. It is formatted as a stand-alone Texinfo file for now, so that I am able to build and view .info files from it. However, according to http://preview.tinyurl.com/lfy436, I will be able to add this document to the

Re: Viengoos build documentation

2008/10/8 Shakthi Kannan <[EMAIL PROTECTED]> > Hi, > > I have documented the Viengoos build process here: > http://www.bddebian.com/~wiki/microkernel/building/ I believe the correct link is http://www.bddebian.com/~wiki/microkernel/viengoos/

Re: Viengoos build documentation

Working link: - http://www.bddebian.com/~wiki/microkernel/viengoos/building/ Best wishes, Arne PS: Just checked the wiki repo. Am Mittwoch 08 Oktober 2008 09:27:09 schrieb Shakthi Kannan: > I have documented the Viengoos build process here: > http://www.bddebian.com/~wiki/microkernel/building

Viengoos build documentation

Hi, I have documented the Viengoos build process here: http://www.bddebian.com/~wiki/microkernel/building/ Please feel free to add/delete/update the same, SK -- Shakthi Kannan http://www.shakthimaan.com

Re: Library/function documentation

Hi, - On Dec 16, 2007 11:38 PM, <[EMAIL PROTECTED]> wrote: | any normal comments in the code -- doxygen can link every function to | the corresponding location in the source code. \-- Here is a customized doxygen config file which I am satisfied with (for reference, if others would like to t

Re: Library/function documentation

ing ctags extensively, which works out quite nice with vim most of the time. > Wouldn't it be useful for newbies if all functions can have comments > to generate gtk-doc style documentation? > http://library.gnome.org/devel/glib/unstable/index.html > > It will be helpful to sk

Re: Library/function documentation

Hi, - On Dec 17, 2007 5:37 PM, Samuel Thibault <[EMAIL PROTECTED]> wrote: | I guess there is some texinfo2html tool somewhere. \-- The following works: texi2html hurd.texi Regards, SK -- Shakthi Kannan http://www.shakthimaan.com ___ Bug-h

Re: Library/function documentation

you get a > | mess :) > \-- > > True. I shall have a look at the info pages. An intuitive web > documentation is my preference. I guess there is some texinfo2html tool somewhere. Samuel ___ Bug-hurd mailing list Bug-hurd@gnu.org http://l

Re: Library/function documentation

ve web documentation is my preference. I shall work on it and revert back. Thanks for your help and replies. SK -- Shakthi Kannan http://www.shakthimaan.com ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: Library/function documentation

Hi, Shakthi Kannan, le Mon 17 Dec 2007 11:35:14 +0530, a écrit : > - On Dec 16, 2007 7:40 PM, Carl Fredrik Hammar <[EMAIL PROTECTED]> wrote: > | The consensus seem to be that proper overview documentation belongs in > | info pages were it can be handled more appropriate. >

  1   2   >