Re: [PATCH 5/6] trivial hurd manual changes.

Applied, thanks! Joshua Branson, le jeu. 21 sept. 2023 12:48:21 -0400, a ecrit: > From: "jbra...@dismail.de" > > * doc/hurd.texi (Special Files): added a reference to the zero store. > * doc/hurd.texi (Translators): added a sentence about /dev/random. > * doc/hurd.texi (Invoking 'mount'): added

Re: [PATCH 4/6] add a FAT FS section to the hurd manual.

Applied, thanks! Joshua Branson, le jeu. 21 sept. 2023 12:48:20 -0400, a ecrit: > From: "jbra...@dismail.de" > > * doc/hurd.texi (FAT FS): new section. > --- > doc/hurd.texi | 9 + > 1 file changed, 9 insertions(+) > > diff --git a/doc/hurd.texi b/doc/hurd.texi > index 21118bb3..eb9946

Re: [PATCH 3/6] describe the ISO-9960 filesystem in the hurd manual.

Applied, thanks! Joshua Branson, le jeu. 21 sept. 2023 12:48:19 -0400, a ecrit: > From: "jbra...@dismail.de" > > * doc/hurd.texi (ISO-9960): I added in a short explanation. > --- > doc/hurd.texi | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/doc/hurd.texi b/doc/hu

Re: [PATCH 2/6] add a short ext2fs description to the hurd manual.

Applied, thanks! Joshua Branson, le jeu. 21 sept. 2023 12:48:18 -0400, a ecrit: > From: "jbra...@dismail.de" > > * doc/hurd.texi (Linux Extended 2 FS): added a short description. > --- > doc/hurd.texi | 14 -- > 1 file changed, 12 insertions(+), 2 deletions(-) > > diff --git a/doc/

Re: [PATCH 1/6] describe fixing filesystem corruption in the hurd manual.

Applied, thanks! Joshua Branson, le jeu. 21 sept. 2023 12:48:17 -0400, a ecrit: > From: "jbra...@dismail.de" > > * doc/hurd.texi (Repairing Filesystems): described fixing filesystem > corruption. > * doc/hurd.texi (Shutdown): added the hurd specific halt-hurd command. > --- > doc/hurd.texi | 53

Re: [PATCH 5/6] trivial hurd manual changes.

Joshua Branson, le jeu. 21 sept. 2023 12:48:21 -0400, a ecrit: > @@ -2110,6 +2110,15 @@ Only display files that have translators. > @node Invoking mount > @subsection Invoking @code{mount} > > +One does not mount filesystem partitions on the Hurd. Instead one > +sets a translator, which transl

[PATCH 3/6] describe the ISO-9960 filesystem in the hurd manual.

From: "jbra...@dismail.de" * doc/hurd.texi (ISO-9960): I added in a short explanation. --- doc/hurd.texi | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/hurd.texi b/doc/hurd.texi index 25b55ae7..21118bb3 100644 --- a/doc/hurd.texi +++ b/doc/hurd.texi @@ -3698,7 +3698,

[PATCH 5/6] trivial hurd manual changes.

From: "jbra...@dismail.de" * doc/hurd.texi (Special Files): added a reference to the zero store. * doc/hurd.texi (Translators): added a sentence about /dev/random. * doc/hurd.texi (Invoking 'mount'): added a short explanation. * doc/hurd.texi (Trivfs Callbacks): added @code{FSTYPE_MISC}. --- doc

[PATCH 2/6] add a short ext2fs description to the hurd manual.

From: "jbra...@dismail.de" * doc/hurd.texi (Linux Extended 2 FS): added a short description. --- doc/hurd.texi | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/doc/hurd.texi b/doc/hurd.texi index ccad3228..25b55ae7 100644 --- a/doc/hurd.texi +++ b/doc/hurd.texi

[PATCH 4/6] add a FAT FS section to the hurd manual.

From: "jbra...@dismail.de" * doc/hurd.texi (FAT FS): new section. --- doc/hurd.texi | 9 + 1 file changed, 9 insertions(+) diff --git a/doc/hurd.texi b/doc/hurd.texi index 21118bb3..eb994656 100644 --- a/doc/hurd.texi +++ b/doc/hurd.texi @@ -3627,6 +3627,7 @@ workstations, as well. * R

[PATCH 1/6] describe fixing filesystem corruption in the hurd manual.

From: "jbra...@dismail.de" * doc/hurd.texi (Repairing Filesystems): described fixing filesystem corruption. * doc/hurd.texi (Shutdown): added the hurd specific halt-hurd command. --- doc/hurd.texi | 53 +-- 1 file changed, 51 insertions(+), 2 delet

[PATCH v2 1/6] describe fixing filesystem corruption in the hurd manual.

* doc/hurd.texi (Repairing Filesystems): described fixing filesystem corruption. * doc/hurd.texi (Shutdown): added the hurd specific halt-hurd command. --- doc/hurd.texi | 53 +-- 1 file changed, 51 insertions(+), 2 deletions(-) diff --git a/doc/hur

[PATCH 1/6] describe fixing filesystem corruption in the hurd manual.

I would have documented how to make /etc/fstab auto-fsck /home, but reading /etc/fstab, I think I already did that on my /etc/fstab, and I always have to manually fsck /home. Also there have been times, that I HAD to manually fsck /. So it's good to show users how to fsck their partitions. E

Re: A small patch for the Hurd Reference Manual

Hello, Thanks for your fixes. Joshua Branson, le Fri 25 Sep 2015 13:52:25 -0400, a écrit : > This might be a significant enough change to require me assigning > copyright to the FSF. I don't think so for these changes: most of the wording was already in the documentation, so in the end you b

Re: A small patch for the Hurd Reference Manual

Hello Olaf, I've modified my patch.diff to fix the problems you had with the first draft. Namely I, 1) Added my .gitignore back to the diff. BUT that means that I've added some lines to the .gitignore, because I ran texi2pdf inside the hurd/doc directory. If it is not advisable to add more

Re: A small patch for the Hurd Reference Manual

Hi, On Fri, Sep 25, 2015 at 01:52:25PM -0400, Joshua Branson wrote: > diff --git a/.gitignore b/.gitignore > deleted file mode 100644 Not sure what happened to your .gitignore -- but you definitely don't want this in the patch :-) > +Note that it is impossible to share microkernel devices betwe

A small patch for the Hurd Reference Manual

Hello, My name is Joshua Branson, and I've recently made some small changes to the hurd reference manual in hurd/doc/hurd.texi. My changes in patch.diff are as follows: 1) I made a tiny grammatical fix. 2) I changed the "don't get any funny ideas" to be m

[PATCH gnumach 3/6] ipc: undo manual inlining of `ipc_entry_X' functions

Today we can rely on the compiler to inline functions. Undoing this manual optimization is a first step to replace the IPC tables. * ipc/mach_msg.c (mach_msg_trap): Undo the manual inlining of `ipc_entry_lookup', `ipc_entry_dealloc', and `ipc_entry_get'. * ipc/ipc_kmsg.c (ipc_kms

manual photo editing Gimp Image Editor 2.8

Dear Sir, I would love to edit photos with Gimp 2.8 Greetings, Hans Louwenhoven

[Bug manual/3665] errno 118 assigned twice (ECANCELED and ENOTSUP)

--- Additional Comments From tschwinge at gnu dot org 2007-07-22 12:46 --- This patch has been applied; now `mach/hurd/bits/errno.h' has to be regenerated. A patch has been posted in . -- http://sourceware.org/bugzilla/show

[Bug manual/3665] errno 118 assigned twice (ECANCELED and ENOTSUP)

--- Additional Comments From samuel dot thibault at ens-lyon dot org 2007-07-12 23:51 --- So, what do you think of this? This is currently blocking building kdelibs on Debian, I'd like to know how this should be fixed before submitting a patch to debian's glibc package. -- http:/

Re: adding bootstrap information to the manual

Hello! On Fri, Mar 09, 2007 at 03:53:59PM -0500, Ben Asselstine wrote: > I have found that the bootstrapping section of the manual is sorely lacking. True. Amongst other things... > Attached is a patch that adds more information to the manual regarding > the bootstrap procedure on

Re: adding bootstrap information to the manual

Hi, On Sat, Mar 10, 2007 at 02:20:40AM +0100, [EMAIL PROTECTED] wrote: > > I have also removed some of the deprecated serverboot documentation. > > Actually, I think a considerable part of the stuff you want to remove > also applies to the "boot" command used for subhurds, so is really > useful,

Re: adding bootstrap information to the manual

Hi, On Fri, Mar 09, 2007 at 03:53:59PM -0500, Ben Asselstine wrote: > I have found that the bootstrapping section of the manual is sorely > lacking. > > Attached is a patch that adds more information to the manual regarding > the bootstrap procedure on the Hurd. I have also remo

adding bootstrap information to the manual

Hello, I have found that the bootstrapping section of the manual is sorely lacking. Attached is a patch that adds more information to the manual regarding the bootstrap procedure on the Hurd. I have also removed some of the deprecated serverboot documentation. If I have missed anything, let

[Bug manual/3665] errno 118 assigned twice (ECANCELED and ENOTSUP)

--- Additional Comments From samuel dot thibault at ens-lyon dot org 2007-01-21 23:19 --- Created an attachment (id=1510) --> (http://sourceware.org/bugzilla/attachment.cgi?id=1510&action=view) proposed patch Here is a proposed patch. ECANCELED is only supported for aio functions, whi

Re: typos in gnumach manual

At Sun, 21 Jan 2007 15:24:09 +0100, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > Hello there, > > here's a bunch of typo fixes for the gnumach manual. > (You didn't mean "netword", right?) Thanks for these fixes. I put

typos in gnumach manual

Hello there, here's a bunch of typo fixes for the gnumach manual. (You didn't mean "netword", right?) Cheers, Ralf 2007-01-20 Ralf Wildenhues <[EMAIL PROTECTED]> * doc/mach.texi: Fix some ty

[Bug manual/3665] errno 118 assigned twice (ECANCELED and ENOTSUP)

-- What|Removed |Added CC||bug-hurd at gnu dot org http://sourceware.org/bugzilla/show_bug.cgi?id=3665 --- You are receiving this ma

Re: manual

If the tex formatting of those lines now looks reasonably sane, then fine. Looked good in info. Commited (and why didn't anyone tell me that the ChangeLog was wrong, doc/hurd.texi my ass...). 2005-01-21 Alfred M. Szmidt <[EMAIL PROTECTED]> * doc/hurd.texi: Doc fixes. _

Re: manual

If the tex formatting of those lines now looks reasonably sane, then fine. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

manual

This fixes a bunch of unbalanced parens, ok to commit? 2005-01-21 Alfred M. Szmidt <[EMAIL PROTECTED]> * doc/hurd.texi: Doc fixes. --- doc/hurd.texi 01 Feb 2004 23:04:51 +0100 1.26 +++ doc/hurd.texi 21 Jan 2005 17:37:19 +0100 @@ -1097,7 +1097,7 @@ The rest of the

Re: The Hurd Reference Manual - overhaul

Marco Gerards <[EMAIL PROTECTED]> writes: > Added to that, if anyone has a patch, just send it in. I am willing > to proof read every patch that makes sense. And I am sure a lot of > people will do the same. I would be happy to. I am possibly going to have a small patch for the

Re: The Hurd Reference Manual - overhaul

no one is interested in working on the Hurd Reference Guide. I am. I can not remember a single patch for it sent to the mailinglists as long as I am subscribed (almost 3 years). Then you have utterly crappy memory. James has sent patches for it on occassions during these 3 years you n

Re: The Hurd Reference Manual - overhaul

Yaakov Nemoy <[EMAIL PROTECTED]> writes: >> It can be better than one Wiki, but I think that we need a on-line >> version that the people can read the newest modifications. Because >> If only a group, or one person, works in this job the manual could >> turn boring

Re: The Hurd Reference Manual - overhaul

Why oh why won't you two shutup and start writting documentation instead? :-) You _will_ have to send a patch here no matter what, you _will_ have convert it from the wiki format to texinfo and back again-- waste of time, IMHO. Why not skip those extra steps and just do it the way it was meant to

Re: The Hurd Reference Manual - overhaul

> > > It can be better than one Wiki, but I think that we need a on-line version that > > > the people can read the newest modifications. Because If only a group, or one > > > person, works in this job the manual could turn boring and discourage people to > > &

Re: The Hurd Reference Manual - overhaul

> > > > It can be better than one Wiki, but I think that we need a on-line version that > > the people can read the newest modifications. Because If only a group, or one > > person, works in this job the manual could turn boring and discourage people to > > se

Re: The Hurd Reference Manual - overhaul

> > It can be better than one Wiki, but I think that we need a on-line version that the > people can read the newest modifications. Because If only a group, or one person, > works in this job the manual could turn boring and discourage people to send fixes. > I think that we n

Re: The Hurd Reference Manual - overhaul

> "Leonardo Pereira" <[EMAIL PROTECTED]> writes: > > > I had said that frow Wiki one person can get the texts, confer they and write the > > others kind of manual. This can be used only to create the new manual, because > > it's faster, after you ca

Re: The Hurd Reference Manual - overhaul

I had said that frow Wiki one person can get the texts, confer they and write the others kind of manual. This can be used only to create the new manual, because it's faster, after you can get the new manual and update it how do you want. -- __

Re: The Hurd Reference Manual - overhaul

GNU manuals have always been intended to serve as both good introductions that can be read straight through, and as reference manuals. You don't have to give a manual a meaningless structure to make it easy to find things by name. Good indexes and good menus can do that.

Re: The Hurd Reference Manual - overhaul

I think this is a good idea. We need updates for detailed information, and cosmetic. People will benefit a lot more from a "well" written manual of great detail and easy usage. hde ___ Bug-hurd mailing list [EMAIL PROTECTED] http://lis

Re: The Hurd Reference Manual - overhaul

Why do you not do the Hurd Reference Manual in something like a Wiki, Because of the following: * You can't read it offline * You can't make it into a book (the FSF makes money by selling books, a good thing) * You can't print it (a subset of the above) * You can'

Re: Re: The Hurd Reference Manual - overhaul

Why do you not do the Hurd Reference Manual in something like a Wiki, it's faster, It's easy to remodel, it's more simple to update, it's exciting to who will edit. To do official versions you can put a person to read the

Re: The Hurd Reference Manual - overhaul

plete can reorganize the manual however they like. ___ Bug-hurd mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: The Hurd Reference Manual - overhaul

GNU manuals have always been intended to serve as both good introductions that can be read straight through, and as reference manuals. You don't have to give a manual a meaningless structure to make it easy to find things by name. Good indexes and good menus can do that.

Re: The Hurd Reference Manual - overhaul

GNU manuals have always been intended to serve as both good introductions that can be read straight through, and as reference manuals. You don't have to give a manual a meaningless structure to make it easy to find things by name. Good indexes and good menus can do

The Hurd Reference Manual - overhaul

Allways during my late night hacking sessions I try to find something useful todo while waiting for compile jobs, this is tonights task. Doing a overhaul of the Hurd Reference manual. The major grief I have with it is that it is organised in a stupid way. The following "list" is how

Re: Hurd Reference Manual: installation section

Thanks. ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

Re: Hurd Reference Manual: installation section

Yeah, I agree what's there is useless. If there are more useful things to write about those subjects, we might resurrect it later. ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

Hurd Reference Manual: installation section

Hi, Would anyone mind if we ditched the install section in the Hurd Reference Manual (from here on I will call it HRM)? It is very outdated, and how to install a GNU/Hurd system should be documented with the actual system, not the Hurd. For cross-compilation, such things should live in INSTALL

Re: Hurd server manual (first chunk)

Marcus, Marcus Brinkmann wrote: Hi, I started to document the Hurd server interfaces in the style of a reference manual. The Hurd server interfaces are currently only documented in the .defs files, which is a bit short on detail. I wanted a place where I could put all the lengthy explanations

Hurd server manual (first chunk)

Hi, I started to document the Hurd server interfaces in the style of a reference manual. The Hurd server interfaces are currently only documented in the .defs files, which is a bit short on detail. I wanted a place where I could put all the lengthy explanations and rationale and protocols, and