Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Hello David, Ping! Thanks, Michael On Fri, 16 Oct 2020 at 08:50, Michael Kerrisk (man-pages) wrote: > > Hi David, > > Another ping for these five patches please! > > Cheers, > > Michael > > On Fri, 11 Sep 2020 at 14:44, Michael Kerrisk (man-pages) > wrote: > > > > Hi David, > > > > A ping for these five patches please! > > > > Cheers, > > > > Michael > > > > On Wed, 2 Sep 2020 at 22:14, Michael Kerrisk (man-pages) > > wrote: > > > > > > On Wed, 2 Sep 2020 at 18:14, David Howells wrote: > > > > > > > > Michael Kerrisk (man-pages) wrote: > > > > > > > > > The term "filesystem configuration context" is introduced, but never > > > > > really explained. I think it would be very helpful to have a sentence > > > > > or three that explains this concept at the start of the page. > > > > > > > > Does that need a .7 manpage? > > > > > > I was hoping a sentence or a paragraph in this page might suffice. Do > > > you think more is required? > > > > > > Cheers, > > > > > > Michael > > > > > > -- > > > Michael Kerrisk > > > Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > > > Linux/UNIX System Programming Training: http://man7.org/training/ > > > > > > > > -- > > Michael Kerrisk > > Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > > Linux/UNIX System Programming Training: http://man7.org/training/ > > > > -- > Michael Kerrisk > Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > Linux/UNIX System Programming Training: http://man7.org/training/ -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Hi David, Another ping for these five patches please! Cheers, Michael On Fri, 11 Sep 2020 at 14:44, Michael Kerrisk (man-pages) wrote: > > Hi David, > > A ping for these five patches please! > > Cheers, > > Michael > > On Wed, 2 Sep 2020 at 22:14, Michael Kerrisk (man-pages) > wrote: > > > > On Wed, 2 Sep 2020 at 18:14, David Howells wrote: > > > > > > Michael Kerrisk (man-pages) wrote: > > > > > > > The term "filesystem configuration context" is introduced, but never > > > > really explained. I think it would be very helpful to have a sentence > > > > or three that explains this concept at the start of the page. > > > > > > Does that need a .7 manpage? > > > > I was hoping a sentence or a paragraph in this page might suffice. Do > > you think more is required? > > > > Cheers, > > > > Michael > > > > -- > > Michael Kerrisk > > Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > > Linux/UNIX System Programming Training: http://man7.org/training/ > > > > -- > Michael Kerrisk > Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > Linux/UNIX System Programming Training: http://man7.org/training/ -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Hi David, A ping for these five patches please! Cheers, Michael On Wed, 2 Sep 2020 at 22:14, Michael Kerrisk (man-pages) wrote: > > On Wed, 2 Sep 2020 at 18:14, David Howells wrote: > > > > Michael Kerrisk (man-pages) wrote: > > > > > The term "filesystem configuration context" is introduced, but never > > > really explained. I think it would be very helpful to have a sentence > > > or three that explains this concept at the start of the page. > > > > Does that need a .7 manpage? > > I was hoping a sentence or a paragraph in this page might suffice. Do > you think more is required? > > Cheers, > > Michael > > -- > Michael Kerrisk > Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > Linux/UNIX System Programming Training: http://man7.org/training/ -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
On Wed, 2 Sep 2020 at 18:14, David Howells wrote: > > Michael Kerrisk (man-pages) wrote: > > > The term "filesystem configuration context" is introduced, but never > > really explained. I think it would be very helpful to have a sentence > > or three that explains this concept at the start of the page. > > Does that need a .7 manpage? I was hoping a sentence or a paragraph in this page might suffice. Do you think more is required? Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Michael Kerrisk (man-pages) wrote: > The term "filesystem configuration context" is introduced, but never > really explained. I think it would be very helpful to have a sentence > or three that explains this concept at the start of the page. Does that need a .7 manpage? David
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Hi David, One further thought... > +++ b/man2/fsopen.2 [...] > +.BR fsopen () > +creates a blank filesystem configuration context within the kernel for the > +filesystem named in the > +.I fsname > +parameter, puts it into creation mode and attaches it to a file descriptor, > +which it then returns. The term "filesystem configuration context" is introduced, but never really explained. I think it would be very helpful to have a sentence or three that explains this concept at the start of the page. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Hello David, On 8/24/20 2:25 PM, David Howells wrote: > Add a manual page to document the fsopen() and fsmount() system calls. > > Signed-off-by: David Howells > --- > > man2/fsmount.2 |1 > man2/fsopen.2 | 245 > > 2 files changed, 246 insertions(+) > create mode 100644 man2/fsmount.2 > create mode 100644 man2/fsopen.2 > > diff --git a/man2/fsmount.2 b/man2/fsmount.2 > new file mode 100644 > index 0..2bf59fc3e > --- /dev/null > +++ b/man2/fsmount.2 > @@ -0,0 +1 @@ > +.so man2/fsopen.2 > diff --git a/man2/fsopen.2 b/man2/fsopen.2 > new file mode 100644 > index 0..1d1bba238 > --- /dev/null > +++ b/man2/fsopen.2 > @@ -0,0 +1,245 @@ > +'\" t > +.\" Copyright (c) 2020 David Howells > +.\" > +.\" %%%LICENSE_START(VERBATIM) > +.\" Permission is granted to make and distribute verbatim copies of this > +.\" manual provided the copyright notice and this permission notice are > +.\" preserved on all copies. > +.\" > +.\" Permission is granted to copy and distribute modified versions of this > +.\" manual under the conditions for verbatim copying, provided that the > +.\" entire resulting derived work is distributed under the terms of a > +.\" permission notice identical to this one. > +.\" > +.\" Since the Linux kernel and libraries are constantly changing, this > +.\" manual page may be incorrect or out-of-date. The author(s) assume no > +.\" responsibility for errors or omissions, or for damages resulting from > +.\" the use of the information contained herein. The author(s) may not > +.\" have taken the same level of care in the production of this manual, > +.\" which is licensed free of charge, as they might when working > +.\" professionally. > +.\" > +.\" Formatted or processed versions of this manual, if unaccompanied by > +.\" the source, must acknowledge the copyright and authors of this work. > +.\" %%%LICENSE_END > +.\" > +.TH FSOPEN 2 2020-08-07 "Linux" "Linux Programmer's Manual" > +.SH NAME > +fsopen, fsmount \- Filesystem parameterisation and mount creation > +.SH SYNOPSIS > +.nf > +.B #include > +.B #include > +.B #include > +.BR "#include" "/* Definition of AT_* constants */" > +.PP > +.BI "int fsopen(const char *" fsname ", unsigned int " flags ); > +.PP > +.BI "int fsmount(int " fd ", unsigned int " flags ", unsigned int " > mount_attrs ); > +.fi > +.PP > +.IR Note : > +There are no glibc wrappers for these system calls. > +.SH DESCRIPTION > +.PP > +.BR fsopen () > +creates a blank filesystem configuration context within the kernel for the > +filesystem named in the > +.I fsname > +parameter, puts it into creation mode and attaches it to a file descriptor, > +which it then returns. In the preceding sentence, "it" is used three times, with two *different* referents. That's quite hard on the reader. How about: [[ .BR fsopen () creates a blank filesystem configuration context within the kernel for the filesystem named in the .I fsname parameter, puts the context into creation mode and attaches it to a file descriptor; .BR fsopen () returns the file descriptor as the function result. ]] > The file descriptor can be marked close-on-exec by > +setting > +.B FSOPEN_CLOEXEC > +in > +.IR flags . > +.PP > +After calling fsopen(), the file descriptor should be passed to the > +.BR fsconfig (2) > +system call, using that to specify the desired filesystem and security > +parameters. > +.PP > +When the parameters are all set, the > +.BR fsconfig () > +system call should then be called again with > +.B FSCONFIG_CMD_CREATE > +as the command argument to effect the creation. > +.RS > +.PP > +.BR "[!]\ NOTE" : > +Depending on the filesystem type and parameters, this may rather share an Please replace "this" with a noun (phrase), since it is a little unclear what "this" refers to. > +existing in-kernel filesystem representation instead of creating a new one. > +In such a case, the parameters specified may be discarded or may overwrite > the > +parameters set by a previous mount - at the filesystem's discretion. > +.RE > +.PP > +The file descriptor also serves as a channel by which more comprehensive > error, > +warning and information messages may be retrieved from the kernel using > +.BR read (2). > +.PP > +Once the creation command has been successfully run on a context, the context > +will not accept further configuration. At > +this point, > +.BR fsmount () > +should be called to create a mount object. > +.PP > +.BR fsmount () > +takes the file descriptor returned by > +.BR fsopen () > +and creates a mount object for the filesystem root specified there. The > +attributes of the mount object are set from the > +.I mount_attrs > +parameter. The attributes specify the propagation and mount restrictions to > +be applied to accesses through this mount. Can we please have a list of the available attributes here, with a description of each attribute. > +.PP > +The mount object is then attached
[PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Add a manual page to document the fsopen() and fsmount() system calls. Signed-off-by: David Howells --- man2/fsmount.2 |1 man2/fsopen.2 | 245 2 files changed, 246 insertions(+) create mode 100644 man2/fsmount.2 create mode 100644 man2/fsopen.2 diff --git a/man2/fsmount.2 b/man2/fsmount.2 new file mode 100644 index 0..2bf59fc3e --- /dev/null +++ b/man2/fsmount.2 @@ -0,0 +1 @@ +.so man2/fsopen.2 diff --git a/man2/fsopen.2 b/man2/fsopen.2 new file mode 100644 index 0..1d1bba238 --- /dev/null +++ b/man2/fsopen.2 @@ -0,0 +1,245 @@ +'\" t +.\" Copyright (c) 2020 David Howells +.\" +.\" %%%LICENSE_START(VERBATIM) +.\" Permission is granted to make and distribute verbatim copies of this +.\" manual provided the copyright notice and this permission notice are +.\" preserved on all copies. +.\" +.\" Permission is granted to copy and distribute modified versions of this +.\" manual under the conditions for verbatim copying, provided that the +.\" entire resulting derived work is distributed under the terms of a +.\" permission notice identical to this one. +.\" +.\" Since the Linux kernel and libraries are constantly changing, this +.\" manual page may be incorrect or out-of-date. The author(s) assume no +.\" responsibility for errors or omissions, or for damages resulting from +.\" the use of the information contained herein. The author(s) may not +.\" have taken the same level of care in the production of this manual, +.\" which is licensed free of charge, as they might when working +.\" professionally. +.\" +.\" Formatted or processed versions of this manual, if unaccompanied by +.\" the source, must acknowledge the copyright and authors of this work. +.\" %%%LICENSE_END +.\" +.TH FSOPEN 2 2020-08-07 "Linux" "Linux Programmer's Manual" +.SH NAME +fsopen, fsmount \- Filesystem parameterisation and mount creation +.SH SYNOPSIS +.nf +.B #include +.B #include +.B #include +.BR "#include" "/* Definition of AT_* constants */" +.PP +.BI "int fsopen(const char *" fsname ", unsigned int " flags ); +.PP +.BI "int fsmount(int " fd ", unsigned int " flags ", unsigned int " mount_attrs ); +.fi +.PP +.IR Note : +There are no glibc wrappers for these system calls. +.SH DESCRIPTION +.PP +.BR fsopen () +creates a blank filesystem configuration context within the kernel for the +filesystem named in the +.I fsname +parameter, puts it into creation mode and attaches it to a file descriptor, +which it then returns. The file descriptor can be marked close-on-exec by +setting +.B FSOPEN_CLOEXEC +in +.IR flags . +.PP +After calling fsopen(), the file descriptor should be passed to the +.BR fsconfig (2) +system call, using that to specify the desired filesystem and security +parameters. +.PP +When the parameters are all set, the +.BR fsconfig () +system call should then be called again with +.B FSCONFIG_CMD_CREATE +as the command argument to effect the creation. +.RS +.PP +.BR "[!]\ NOTE" : +Depending on the filesystem type and parameters, this may rather share an +existing in-kernel filesystem representation instead of creating a new one. +In such a case, the parameters specified may be discarded or may overwrite the +parameters set by a previous mount - at the filesystem's discretion. +.RE +.PP +The file descriptor also serves as a channel by which more comprehensive error, +warning and information messages may be retrieved from the kernel using +.BR read (2). +.PP +Once the creation command has been successfully run on a context, the context +will not accept further configuration. At +this point, +.BR fsmount () +should be called to create a mount object. +.PP +.BR fsmount () +takes the file descriptor returned by +.BR fsopen () +and creates a mount object for the filesystem root specified there. The +attributes of the mount object are set from the +.I mount_attrs +parameter. The attributes specify the propagation and mount restrictions to +be applied to accesses through this mount. +.PP +The mount object is then attached to a new file descriptor that looks like one +created by +.BR open "(2) with " O_PATH " or " open_tree (2). +This can be passed to +.BR move_mount (2) +to attach the mount object to a mountpoint, thereby completing the process. +.PP +The file descriptor returned by fsmount() is marked close-on-exec if +FSMOUNT_CLOEXEC is specified in +.IR flags . +.PP +After fsmount() has completed, the context created by fsopen() is reset and +moved to reconfiguration state, allowing the new superblock to be +reconfigured. See +.BR fspick (2) +for details. +.PP +To use either of these calls, the caller requires the appropriate privilege +(Linux: the +.B CAP_SYS_ADMIN +capability). +.PP +.SS Message Retrieval Interface +The context file descriptor may be queried for message strings at any time by +calling +.BR read (2) +on the file descriptor. This will return formatted messages that are prefixed +to indicate their class:
Re: [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Hi David, On Fri, 7 Aug 2020 at 16:03, David Howells wrote: > > Add a manual page to document the fsopen() and fsmount() system calls. > > Signed-off-by: David Howells > --- > > man2/fsmount.2 |1 > man2/fsopen.2 | 254 > > 2 files changed, 255 insertions(+) > create mode 100644 man2/fsmount.2 > create mode 100644 man2/fsopen.2 > > diff --git a/man2/fsmount.2 b/man2/fsmount.2 > new file mode 100644 > index 0..2bf59fc3e > --- /dev/null > +++ b/man2/fsmount.2 > @@ -0,0 +1 @@ > +.so man2/fsopen.2 > diff --git a/man2/fsopen.2 b/man2/fsopen.2 > new file mode 100644 > index 0..b36ea1609 > --- /dev/null > +++ b/man2/fsopen.2 > @@ -0,0 +1,254 @@ > +'\" t > +.\" Copyright (c) 2020 David Howells > +.\" > +.\" %%%LICENSE_START(VERBATIM) > +.\" Permission is granted to make and distribute verbatim copies of this > +.\" manual provided the copyright notice and this permission notice are > +.\" preserved on all copies. > +.\" > +.\" Permission is granted to copy and distribute modified versions of this > +.\" manual under the conditions for verbatim copying, provided that the > +.\" entire resulting derived work is distributed under the terms of a > +.\" permission notice identical to this one. > +.\" > +.\" Since the Linux kernel and libraries are constantly changing, this > +.\" manual page may be incorrect or out-of-date. The author(s) assume no > +.\" responsibility for errors or omissions, or for damages resulting from > +.\" the use of the information contained herein. The author(s) may not > +.\" have taken the same level of care in the production of this manual, > +.\" which is licensed free of charge, as they might when working > +.\" professionally. > +.\" > +.\" Formatted or processed versions of this manual, if unaccompanied by > +.\" the source, must acknowledge the copyright and authors of this work. > +.\" %%%LICENSE_END > +.\" > +.TH FSOPEN 2 2020-08-07 "Linux" "Linux Programmer's Manual" > +.SH NAME > +fsopen, fsmount \- Filesystem parameterisation and mount creation > +.SH SYNOPSIS > +.nf > +.B #include > +.br > +.B #include > +.br Remove all instances of ".br" here in the SYNOPSIS. They aren't needed (because of the .nf above). > +.B #include > +.br > +.BR "#include" "/* Definition of AT_* constants */" > +.PP > +.BI "int fsopen(const char *" fsname ", unsigned int " flags ); > +.PP > +.BI "int fsmount(int " fd ", unsigned int " flags ", unsigned int " > mount_attrs ); > +.fi > +.PP > +.IR Note : > +There are no glibc wrappers for these system calls. > +.SH DESCRIPTION > +.PP > +.BR fsopen () > +creates a blank filesystem configuration context within the kernel for the > +filesystem named in the > +.I fsname > +parameter, puts it into creation mode and attaches it to a file descriptor, > +which it then returns. The file descriptor can be marked close-on-exec by > +setting > +.B FSOPEN_CLOEXEC > +in > +.IR flags . > +.PP > +After calling fsopen(), the file descriptor should be passed to the > +.BR fsconfig (2) > +system call, using that to specify the desired filesystem and security > +parameters. > +.PP > +When the parameters are all set, the > +.BR fsconfig () > +system call should then be called again with > +.B FSCONFIG_CMD_CREATE > +as the command argument to effect the creation. > +.RS > +.PP > +.BR "[!]\ NOTE" : > +Depending on the filesystem type and parameters, this may rather share an > +existing in-kernel filesystem representation instead of creating a new one. > +In such a case, the parameters specified may be discarded or may overwrite > the > +parameters set by a previous mount - at the filesystem's discretion. > +.RE > +.PP > +The file descriptor also serves as a channel by which more comprehensive > error, > +warning and information messages may be retrieved from the kernel using > +.BR read (2). > + Delete blank line above. > +.PP > +Once the creation command has been successfully run on a context, the context > +is switched into need-mount mode which prevents further configuration. At > +this point, > +.BR fsmount () > +should be called to create a mount object. > +.PP > +.BR fsmount () > +takes the file descriptor returned by > +.BR fsopen () > +and creates a mount object for the filesystem root specified there. The > +attributes of the mount object are set from the > +.I mount_attrs > +parameter. The attributes specify the propagation and mount restrictions to > +be applied to accesses through this mount. > +.PP > +The mount object is then attached to a new file descriptor that looks like > one > +created by > +.BR open "(2) with " O_PATH " or " open_tree (2). > +This can be passed to > +.BR move_mount (2) > +to attach the mount object to a mountpoint, thereby completing the process. > +.PP > +The file descriptor returned by fsmount() is marked close-on-exec if > +FSMOUNT_CLOEXEC is specified in > +.IR flags . > +.PP > +After fsmount() has completed, the context
[PATCH 4/5] Add manpage for fsopen(2) and fsmount(2)
Add a manual page to document the fsopen() and fsmount() system calls. Signed-off-by: David Howells --- man2/fsmount.2 |1 man2/fsopen.2 | 254 2 files changed, 255 insertions(+) create mode 100644 man2/fsmount.2 create mode 100644 man2/fsopen.2 diff --git a/man2/fsmount.2 b/man2/fsmount.2 new file mode 100644 index 0..2bf59fc3e --- /dev/null +++ b/man2/fsmount.2 @@ -0,0 +1 @@ +.so man2/fsopen.2 diff --git a/man2/fsopen.2 b/man2/fsopen.2 new file mode 100644 index 0..b36ea1609 --- /dev/null +++ b/man2/fsopen.2 @@ -0,0 +1,254 @@ +'\" t +.\" Copyright (c) 2020 David Howells +.\" +.\" %%%LICENSE_START(VERBATIM) +.\" Permission is granted to make and distribute verbatim copies of this +.\" manual provided the copyright notice and this permission notice are +.\" preserved on all copies. +.\" +.\" Permission is granted to copy and distribute modified versions of this +.\" manual under the conditions for verbatim copying, provided that the +.\" entire resulting derived work is distributed under the terms of a +.\" permission notice identical to this one. +.\" +.\" Since the Linux kernel and libraries are constantly changing, this +.\" manual page may be incorrect or out-of-date. The author(s) assume no +.\" responsibility for errors or omissions, or for damages resulting from +.\" the use of the information contained herein. The author(s) may not +.\" have taken the same level of care in the production of this manual, +.\" which is licensed free of charge, as they might when working +.\" professionally. +.\" +.\" Formatted or processed versions of this manual, if unaccompanied by +.\" the source, must acknowledge the copyright and authors of this work. +.\" %%%LICENSE_END +.\" +.TH FSOPEN 2 2020-08-07 "Linux" "Linux Programmer's Manual" +.SH NAME +fsopen, fsmount \- Filesystem parameterisation and mount creation +.SH SYNOPSIS +.nf +.B #include +.br +.B #include +.br +.B #include +.br +.BR "#include" "/* Definition of AT_* constants */" +.PP +.BI "int fsopen(const char *" fsname ", unsigned int " flags ); +.PP +.BI "int fsmount(int " fd ", unsigned int " flags ", unsigned int " mount_attrs ); +.fi +.PP +.IR Note : +There are no glibc wrappers for these system calls. +.SH DESCRIPTION +.PP +.BR fsopen () +creates a blank filesystem configuration context within the kernel for the +filesystem named in the +.I fsname +parameter, puts it into creation mode and attaches it to a file descriptor, +which it then returns. The file descriptor can be marked close-on-exec by +setting +.B FSOPEN_CLOEXEC +in +.IR flags . +.PP +After calling fsopen(), the file descriptor should be passed to the +.BR fsconfig (2) +system call, using that to specify the desired filesystem and security +parameters. +.PP +When the parameters are all set, the +.BR fsconfig () +system call should then be called again with +.B FSCONFIG_CMD_CREATE +as the command argument to effect the creation. +.RS +.PP +.BR "[!]\ NOTE" : +Depending on the filesystem type and parameters, this may rather share an +existing in-kernel filesystem representation instead of creating a new one. +In such a case, the parameters specified may be discarded or may overwrite the +parameters set by a previous mount - at the filesystem's discretion. +.RE +.PP +The file descriptor also serves as a channel by which more comprehensive error, +warning and information messages may be retrieved from the kernel using +.BR read (2). + +.PP +Once the creation command has been successfully run on a context, the context +is switched into need-mount mode which prevents further configuration. At +this point, +.BR fsmount () +should be called to create a mount object. +.PP +.BR fsmount () +takes the file descriptor returned by +.BR fsopen () +and creates a mount object for the filesystem root specified there. The +attributes of the mount object are set from the +.I mount_attrs +parameter. The attributes specify the propagation and mount restrictions to +be applied to accesses through this mount. +.PP +The mount object is then attached to a new file descriptor that looks like one +created by +.BR open "(2) with " O_PATH " or " open_tree (2). +This can be passed to +.BR move_mount (2) +to attach the mount object to a mountpoint, thereby completing the process. +.PP +The file descriptor returned by fsmount() is marked close-on-exec if +FSMOUNT_CLOEXEC is specified in +.IR flags . +.PP +After fsmount() has completed, the context created by fsopen() is reset and +moved to reconfiguration state, allowing the new superblock to be +reconfigured. See +.BR fspick (2) +for details. +.PP + +.\" +.SS Message Retrieval Interface +The context file descriptor may be queried for message strings at any time by +calling +.BR read (2) +on the file descriptor. This will return formatted messages that are prefixed +to indicate their class: +.TP +\fB"e
