mcp-redhat-manpage-data 0.1.0 → 0.1.1

package/.github/workflows/extract.yml

@@ -9,15 +9,21 @@ on:
 jobs:
   extract:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      id-token: write
 
     steps:
       - uses: actions/checkout@v4
 
       - uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '22'
           registry-url: 'https://registry.npmjs.org'
 
+      - name: Upgrade npm
+        run: npm install -g npm@latest
+
       - name: Extract man pages
         run: bash scripts/extract.sh
 
@@ -42,13 +48,12 @@ jobs:
             git diff --cached --stat
           fi
 
-      - name: Bump version and publish
+      - name: Commit, bump version, and publish
         if: steps.changes.outputs.changed == 'true'
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
-          npm version patch -m "Update man pages from latest UBI images"
-          npm publish
+          git commit -m "Update man pages from latest UBI images"
+          npm version patch -m "v%s"
+          npm publish --provenance --access public
           git push --follow-tags

package/manpages/rhel10/groff.1.txt

@@ -330,8 +330,8 @@ Usage
               to s; see groff_mm(7).  It can be specified on the command line as -mm.
 
        om     (invariably called “mom”) is a modern package written by Peter Schaffter  specifically  for  GNU  roff.
-              Consult  the  mom  HTML manual ⟨file:///usr/share/doc/groff/html/mom/toc.html⟩ for extensive documenta‐
-              tion.  She—for mom takes the female pronoun—can be specified on the command line as -mom.
+              Consult  the  mom HTML manual for extensive documentation.  She—for mom takes the female pronoun—can be
+              specified on the command line as -mom.
 
        s      is the original AT&T general-purpose document format; see groff_ms(7).  It can be specified on the com‐
               mand line as -ms.
@@ -634,18 +634,17 @@ Installation directories
 
 Availability
        Obtain links to groff releases for download, its source repository, discussion mailing lists, a support ticket
-       tracker, and further information from the groff page of the GNU website ⟨http://www.gnu.org/software/groff⟩.
+       tracker, and further information from the groff page of the GNU website.
 
-       A free implementation of the grap preprocessor, written by Ted Faber ⟨faber@lunabase.org⟩, can be found at the
-       grap website ⟨http://www.lunabase.org/~faber/Vault/software/grap/⟩.  groff supports only this grap.
+       A free implementation of the grap preprocessor, written by Ted Faber, can be found at the grap website.  groff
+       supports only this grap.
 
 Authors
-       groff  (both  the  front-end  command and the overall system) was primarily written by James Clark ⟨jjc@jclark
-       .com⟩.  Contributors to this document include Clark, Trent  A.  Fisher,  Werner  Lemberg  ⟨wl@gnu.org⟩,  Bernd
-       Warken ⟨groff-bernd.warken-72@web.de⟩, and G. Branden Robinson ⟨g.branden.robinson@gmail.com⟩.
+       groff  (both the front-end command and the overall system) was primarily written by James Clark.  Contributors
+       to this document include Clark, Trent A. Fisher, Werner Lemberg, Bernd Warken, and G. Branden Robinson.
 
 See also
-       Groff:  The  GNU  Implementation of troff, by Trent A. Fisher and Werner Lemberg, is the primary groff manual.
+       Groff: The GNU Implementation of troff, by Trent A. Fisher and Werner Lemberg, is the  primary  groff  manual.
        You can browse it interactively with “info groff”.
 
        Introduction, history, and further reading:
@@ -655,11 +654,11 @@ See also
               gxditview(1)
 
        Preprocessors:
-              chem(1), eqn(1), neqn(1), glilypond(1), grn(1), preconv(1),  gperl(1),  pic(1),  gpinyin(1),  refer(1),
+              chem(1),  eqn(1),  neqn(1),  glilypond(1),  grn(1), preconv(1), gperl(1), pic(1), gpinyin(1), refer(1),
               soelim(1), tbl(1)
 
        Macro packages and package-specific utilities:
-              groff_hdtbl(7),    groff_man(7),    groff_man_style(7),    groff_mdoc(7),   groff_me(7),   groff_mm(7),
+              groff_hdtbl(7),   groff_man(7),   groff_man_style(7),    groff_mdoc(7),    groff_me(7),    groff_mm(7),
               groff_mmse(7),  mmroff(1),  groff_mom(7),  pdfmom(1),  groff_ms(7),  groff_rfc1345(7),  groff_trace(7),
               groff_www(7)
 

package/manpages/rhel10/grops.1.txt

@@ -316,9 +316,9 @@ Usage
        the PFA format described in pfbtops(1).  Several methods exist to generate a Type 42 wrapper; some of them in‐
        volve the use of a PostScript interpreter such as Ghostscript—see gs(1).
 
-       One approach is to use FontForge ⟨https://fontforge.org/⟩, a font editor that can convert  most  outline  font
-       formats.   Here's  an  example  of using the Roboto Slab Serif font with groff.  Several variables are used so
-       that you can more easily adapt it into your own script.
+       One approach is to use FontForge, a font editor that can convert most outline font formats.  Here's an example
+       of using the Roboto Slab Serif font with groff.  Several variables are used so that you can more easily  adapt
+       it into your own script.
 
            MAP=/usr/share/groff/1.23.0/font/devps/generate/text.map
            TTF=/usr/share/fonts/truetype/roboto/slab/RobotoSlab-Regular.ttf
@@ -334,13 +334,13 @@ Usage
            afmtodit "$DIR/devps/$AFM" "$MAP" "$DIR/devps/$GFN"
            printf "$BASE\t$PFA\n" >> "$DIR/devps/download"
 
-       fontforge and afmtodit may generate warnings depending on the attributes of the font.  The test  procedure  is
+       fontforge  and  afmtodit may generate warnings depending on the attributes of the font.  The test procedure is
        simple.
 
            printf ".ft RSR\nHello, world!\n" | groff -F "$DIR" > hello.ps
 
-       Once  you're  satisfied  that  the  font works, you may want to generate any available related styles (for in‐
-       stance, Roboto Slab also has “Bold”, “Light”, and “Thin” styles) and set up GROFF_FONT_PATH in  your  environ‐
+       Once you're satisfied that the font works, you may want to generate any  available  related  styles  (for  in‐
+       stance,  Roboto  Slab also has “Bold”, “Light”, and “Thin” styles) and set up GROFF_FONT_PATH in your environ‐
        ment to include the directory you keep the generated fonts in so that you don't have to use the -F option.
 
 Font installation
@@ -349,35 +349,35 @@ Font installation
        • Convert your font to something groff understands.  This is a PostScript Type 1 font in PFA format or a Post‐
          Script Type 42 font, together with an AFM file.  A PFA file begins as follows.
                 %!PS-AdobeFont-1.0:
-         A  PFB  file contains this string as well, preceded by some non-printing bytes.  If your font is in PFB for‐
+         A PFB file contains this string as well, preceded by some non-printing bytes.  If your font is in  PFB  for‐
          mat, use groff's pfbtops(1) program to convert it to PFA.  For TrueType and other font formats, we recommend
          fontforge, which can convert most outline font formats.  A Type 42 font file begins as follows.
                 %!PS-TrueTypeFont
-         This is a wrapper format for TrueType fonts.  Old PostScript printers might not support them (that is,  they
-         might  not  have a built-in TrueType font interpreter).  In the following steps, we will consider the use of
-         CTAN's BrushScriptX-Italic ⟨https://ctan.org/tex-archive/fonts/brushscr⟩ font in PFA format.
+         This  is a wrapper format for TrueType fonts.  Old PostScript printers might not support them (that is, they
+         might not have a built-in TrueType font interpreter).  In the following steps, we will consider the  use  of
+         CTAN's BrushScriptX-Italic font in PFA format.
 
        • Convert the AFM file to a groff font description file with the afmtodit(1) program.  For instance,
                 $ afmtodit BrushScriptX-Italic.afm text.map BSI
          converts the Adobe Font Metric file BrushScriptX-Italic.afm to the groff font description file BSI.
 
-         If you have a font family which provides regular upright  (roman),  bold,  italic,  and  bold-italic  styles
-         (where  “italic”  may  be  “oblique”  or “slanted”), we recommend using the letters R, B, I, and BI, respec‐
-         tively, as suffixes to the groff font family name to enable groff's font family  and  style  selection  fea‐
-         tures.   An example is groff's built-in support for Times: the font family name is abbreviated as T, and the
-         groff font names are therefore TR, TB, TI, and TBI.  In our  example,  however,  the  BrushScriptX  font  is
+         If  you  have  a  font  family  which provides regular upright (roman), bold, italic, and bold-italic styles
+         (where “italic” may be “oblique” or “slanted”), we recommend using the letters R,  B,  I,  and  BI,  respec‐
+         tively,  as  suffixes  to  the groff font family name to enable groff's font family and style selection fea‐
+         tures.  An example is groff's built-in support for Times: the font family name is abbreviated as T, and  the
+         groff  font  names  are  therefore  TR,  TB, TI, and TBI.  In our example, however, the BrushScriptX font is
          available in a single style only, italic.
 
-       • Install  the  groff  font description file(s) in a devps subdirectory in the search path that groff uses for
-         device and font file descriptions.  See the GROFF_FONT_PATH entry in section “Environment” of  troff(1)  for
+       • Install the groff font description file(s) in a devps subdirectory in the search path that  groff  uses  for
+         device  and  font file descriptions.  See the GROFF_FONT_PATH entry in section “Environment” of troff(1) for
          the current value of the font search path.  While groff doesn't directly use AFM files, it is a good idea to
          store them alongside its font description files.
 
-       • Register  fonts  in  the  devps/download file so they can be located for embedding in PostScript files grops
+       • Register fonts in the devps/download file so they can be located for embedding  in  PostScript  files  grops
          generates.  Only the first download file encountered in the font search path is read.  If in doubt, copy the
-         default download file (see section “Files” below) to the first directory in the font  search  path  and  add
-         your  fonts  there.  The PostScript font name used by grops is stored in the internalname field in the groff
-         font description file.  (This name does not necessarily resemble the font's file name.)  We add the  follow‐
+         default  download  file  (see  section “Files” below) to the first directory in the font search path and add
+         your fonts there.  The PostScript font name used by grops is stored in the internalname field in  the  groff
+         font  description file.  (This name does not necessarily resemble the font's file name.)  We add the follow‐
          ing line to download.
                 BrushScriptX-Italic→BrushScriptX-Italic.pfa
          A tab character, depicted as →, separates the fields.
@@ -392,7 +392,7 @@ Old fonts
        has 314 glyphs and includes the Euro glyph.  For backwards compatibility, these old font descriptions are also
        installed in the /usr/share/groff/1.23.0/oldfont/devps directory.
 
-       To  use  them, make sure that grops finds the fonts before the default system fonts (with the same names): ei‐
+       To use them, make sure that grops finds the fonts before the default system fonts (with the same  names):  ei‐
        ther give grops the -F command-line option,
               $ groff -Tps -P-F -P/usr/share/groff/1.23.0/oldfont ...
        or add the directory to groff's font and device description search path environment variable,
@@ -402,15 +402,15 @@ Old fonts
 
 Environment
        GROFF_FONT_PATH
-              A list of directories in which to seek the selected output device's directory of device  and  font  de‐
+              A  list  of  directories in which to seek the selected output device's directory of device and font de‐
               scription files.  See troff(1) and groff_font(5).
 
        GROPS_PROLOGUE
-              If  this is set to foo, then grops uses the file foo (in the font path) instead of the default prologue
+              If this is set to foo, then grops uses the file foo (in the font path) instead of the default  prologue
               file prologue.  The option -P overrides this environment variable.
 
        SOURCE_DATE_EPOCH
-              A timestamp (expressed as seconds since the Unix epoch) to use as  the  output  creation  timestamp  in
+              A  timestamp  (expressed  as  seconds  since the Unix epoch) to use as the output creation timestamp in
               place of the current time.  The time is converted to human-readable form using ctime(3) and recorded in
               a PostScript comment.
 
@@ -431,28 +431,27 @@ Files
               is the default PostScript prologue prefixed to every output file.
 
        /usr/share/groff/1.23.0/font/devps/text.enc
-              describes  the encoding scheme used by most PostScript Type 1 fonts; the encoding directive of font de‐
+              describes the encoding scheme used by most PostScript Type 1 fonts; the encoding directive of font  de‐
               scription files for the ps device refers to it.
 
        /usr/share/groff/1.23.0/tmac/ps.tmac
-              defines macros for use with the ps output device.  It is automatically loaded by troffrc  when  the  ps
+              defines  macros  for  use with the ps output device.  It is automatically loaded by troffrc when the ps
               output device is selected.
 
        /usr/share/groff/1.23.0/tmac/pspic.tmac
-              defines  the  PSPIC  macro  for embedding images in a document; see groff_tmac(5).  It is automatically
+              defines the PSPIC macro for embedding images in a document; see  groff_tmac(5).   It  is  automatically
               loaded by troffrc.
 
        /usr/share/groff/1.23.0/tmac/psold.tmac
-              provides replacement glyphs for text fonts that lack complete coverage of  the  ISO  Latin-1  character
-              set;  using  it,  groff can produce glyphs like eth (ð) and thorn (þ) that older PostScript printers do
+              provides  replacement  glyphs  for  text fonts that lack complete coverage of the ISO Latin-1 character
+              set; using it, groff can produce glyphs like eth (ð) and thorn (þ) that older  PostScript  printers  do
               not natively support.
 
-       grops creates temporary files using the template “gropsXXXXXX”; see groff(1) for details on their storage  lo‐
+       grops  creates temporary files using the template “gropsXXXXXX”; see groff(1) for details on their storage lo‐
        cation.
 
 See also
-       PostScript   Language   Document   Structuring  Conventions  Specification  ⟨http://partners.adobe.com/public/
-       developer/en/ps/5001.DSC_Spec.pdf⟩
+       PostScript Language Document Structuring Conventions Specification
 
        afmtodit(1), groff(1), troff(1), pfbtops(1), groff_char(7), groff_font(5), groff_out(5), groff_tmac(5)
 

package/manpages/rhel10/grotty.1.txt

@@ -188,10 +188,9 @@ Examples
 See also
        “Control Functions for Coded Character Sets” (ECMA-48) 5th edition, Ecma International, June 1991.   A  gratis
        version  of  ISO  6429,  this document includes a normative description of SGR escape sequences.  Available at
-       ⟨http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-048.pdf⟩.
+       http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-048.pdf.
 
-       “Hyperlinks  in  Terminal   Emulators”   ⟨https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda⟩,
-       Egmont Koblinger.
+       “Hyperlinks in Terminal Emulators”, Egmont Koblinger.
 
        groff(1), troff(1), groff_out(5), groff_font(5), groff_char(7), ul(1), more(1), less(1), man(1)
 

package/manpages/rhel10/pic.1.txt

@@ -395,11 +395,11 @@ See also
        “PIC—A Graphics Language for Typesetting: User Manual”, by Brian W. Kernighan, 1984 (revised 1991), AT&T  Bell
        Laboratories Computing Science Technical Report No. 116
 
-       ps2eps is available from CTAN mirrors, e.g., ⟨ftp://ftp.dante.de/tex-archive/support/ps2eps/⟩
+       ps2eps is available from CTAN mirrors, e.g., ftp://ftp.dante.de/tex-archive/support/ps2eps/
 
-       W. Richard Stevens, Turning PIC into HTML ⟨http://www.kohala.com/start/troff/pic2html.html⟩
+       W. Richard Stevens, Turning PIC into HTML
 
-       W. Richard Stevens, Examples of pic Macros ⟨http://www.kohala.com/start/troff/pic.examples.ps⟩
+       W. Richard Stevens, Examples of pic Macros
 
        troff(1), groff_out(5), tex(1), gs(1), ps2eps(1), pstopnm(1), ps2epsi(1), pnm(5)
 

package/manpages/rhel10/tbl.1.txt

@@ -538,8 +538,7 @@ See also
        “Tbl—A Program to Format Tables”, by M. E. Lesk, 1976 (revised 16 January 1979), AT&T Bell  Laboratories  Com‐
        puting Science Technical Report No. 49.
 
-       The   spanning   example   above   was   taken   from   mandoc's   man   page   for   its  tbl  implementation
-       ⟨https://man.openbsd.org/tbl.7⟩.
+       The spanning example above was taken from mandoc's man page for its tbl implementation.
 
        groff(1), troff(1)
 

package/manpages/rhel10/troff.1.txt

@@ -262,11 +262,10 @@ Files
 
 Authors
        The GNU version of troff was originally written by James Clark; he also wrote the  original  version  of  this
-       document,  which  was updated by Werner Lemberg ⟨wl@gnu.org⟩, Bernd Warken ⟨groff-bernd.warken-72@web.de⟩, and
-       G. Branden Robinson ⟨g.branden.robinson@gmail.com⟩.
+       document, which was updated by Werner Lemberg, Bernd Warken, and G. Branden Robinson.
 
 See also
-       Groff: The GNU Implementation of troff, by Trent A. Fisher and Werner Lemberg, is the  primary  groff  manual.
+       Groff:  The  GNU  Implementation of troff, by Trent A. Fisher and Werner Lemberg, is the primary groff manual.
        You can browse it interactively with “info groff”.
 
        groff(1)
@@ -277,7 +276,7 @@ See also
               ters, and escape sequences.
 
        groff_char(7)
-              explains  the syntax of groff special character escape sequences, and lists all special characters pre‐
+              explains the syntax of groff special character escape sequences, and lists all special characters  pre‐
               defined by the language.
 
        groff_diff(7)

package/manpages/rhel8/groff.1.txt

@@ -12,7 +12,7 @@ SYNOPSIS
 DESCRIPTION
        This  document  describes the groff program, the main front-end for the groff document formatting system.  The
        groff program and macro suite is the implementation of a roff(7) system within the  free  software  collection
-       GNU ⟨http://www.gnu.org⟩.  The groff system has all features of the classical roff, but adds many extensions.
+       GNU.  The groff system has all features of the classical roff, but adds many extensions.
 
        The groff program allows to control the whole groff system by command line options.  This is a great simplifi‐
        cation in comparison to the classical case (which uses pipes only).
@@ -493,8 +493,8 @@ BUGS
        On EBCDIC hosts (e.g., OS/390 Unix), output devices ascii and latin1 aren't available.  Similarly, output  for
        EBCDIC code page cp1047 is not available on ASCII based operating systems.
 
-       Report  bugs  to  the groff mailing list ⟨bug-groff@gnu.org⟩.  Include a complete, self-contained example that
-       allows the bug to be reproduced, and say which version of groff you are using.
+       Report  bugs  to the groff mailing list.  Include a complete, self-contained example that allows the bug to be
+       reproduced, and say which version of groff you are using.
 
 POSITIONS FROM INSTALLATION
        There are some directories in which groff installs all of its  data  files.   Due  to  different  installation
@@ -583,24 +583,21 @@ POSITIONS FROM INSTALLATION
               Font file for font F of device name.
 
 AVAILABILITY
-       Information  on  how  to  get  groff  and  related  information is available at the groff GNU website ⟨http://
-       www.gnu.org/software/groff⟩.
+       Information on how to get groff and related information is available at the groff GNU website.
 
        Three groff mailing lists are available:
 
-              for reporting bugs ⟨bug-groff@gnu.org⟩.
+              for reporting bugs.
 
-              for general discussion of groff, ⟨groff@gnu.org⟩.
+              for general discussion of groff,.
 
-              the groff commit list ⟨groff-commit@ffii.org⟩, a read-only list showing  logs  of  commitments  to  the
-              groff repository.
+              the groff commit list, a read-only list showing logs of commitments to the groff repository.
 
        Details  on  repository access and much more can be found in the file README at the top directory of the groff
        source package.
 
-       There is a free implementation of the grap preprocessor, written by Ted Faber ⟨faber@lunabase.org⟩.   The  ac‐
-       tual  version can be found at the grap website ⟨http://www.lunabase.org/~faber/Vault/software/grap/⟩.  This is
-       the only grap version supported by groff.
+       There is a free implementation of the grap preprocessor, written by Ted Faber.   The  actual  version  can  be
+       found at the grap website.  This is the only grap version supported by groff.
 
 SEE ALSO
        The groff info file contains all information on the groff system within a single document, providing many ex‐
@@ -641,12 +638,12 @@ SEE ALSO
               grodvi(1), grohtml(1), grolbp(1), grolj4(1), lj4_font(5), grops(1), gropdf(1), grotty(1).
 
        Groff macro packages and macro-specific utilities:
-              groff_tmac(5), groff_man(7),  groff_mdoc(7),  groff_me(7),  groff_mm(7),  groff_mmse(7),  groff_mom(7),
+              groff_tmac(5),  groff_man(7),  groff_mdoc(7),  groff_me(7),  groff_mm(7),  groff_mmse(7), groff_mom(7),
               groff_ms(7), groff_www(7), groff_trace(7), mmroff(7).
 
        The following utilities are available:
-              addftinfo(1),   afmtodit(1),   eqn2graph(1),   gdiffmk(1),   grap2graph(1),  groffer(1),  gxditview(1),
-              hpftodit(1), indxbib(1),  lkbib(1),  lookbib(1),  pdfroff(1),  pfbtops(1),  pic2graph(1),  tfmtodit(1),
+              addftinfo(1),  afmtodit(1),  eqn2graph(1),   gdiffmk(1),   grap2graph(1),   groffer(1),   gxditview(1),
+              hpftodit(1),  indxbib(1),  lkbib(1),  lookbib(1),  pdfroff(1),  pfbtops(1),  pic2graph(1), tfmtodit(1),
               xtotroff(1).
 
 COPYING (LICENSE)
@@ -660,14 +657,13 @@ COPYING (LICENSE)
        tation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant
        Sections being the macro definition or .co and .au, with no Front-Cover Texts, and with no Back-Cover Texts.
 
-       A  copy  of the Free Documentation License is included as a file called FDL in the main directory of the groff
+       A copy of the Free Documentation License is included as a file called FDL in the main directory of  the  groff
        source package.
 
-       It is also available in the internet at the GNU copyleft site ⟨http://www.gnu.org/copyleft/fdl.html⟩.
+       It is also available in the internet at the GNU copyleft site.
 
 AUTHORS
-       This document is based on the original groff man page written by James Clark ⟨jjc@jclark.com⟩.  It was rewrit‐
-       ten, enhanced, and put under the FDL license by Bernd Warken <groff-bernd.warken-72@web.de>.  It is maintained
-       by Werner Lemberg ⟨wl@gnu.org⟩.
+       This document is based on the original groff man page written by James Clark.  It was rewritten, enhanced, and
+       put under the FDL license by Bernd Warken <groff-bernd.warken-72@web.de>.  It is maintained by Werner Lemberg.
 
 Groff Version 1.22.3                               4 November 2014                                           GROFF(1)

package/manpages/rhel8/grops.1.txt

@@ -348,17 +348,16 @@ USAGE
        Yet, the easiest method involves the use of the application ttftot42(1).  This program uses freetype(3)  (ver‐
        sion  1.3.1)  to  generate  type42  font wrappers and well-formed AFM files that can be fed to the afmtodit(1)
        script to create appropriate metric files.  The resulting font wrappers should be added to the download  file.
-       ttftot42  source code can be downloaded from ftp://www.giga.or.at/pub/nih/ttftot42/ ⟨ftp://www.giga.or.at/pub/
-       nih/ttftot42/⟩.
+       ttftot42 source code can be downloaded from ftp://www.giga.or.at/pub/nih/ttftot42/.
 
-       Another solution for creating type42 wrappers is to  use  FontForge,  available  from  http://fontforge.sf.net
-       ⟨http://fontforge.sf.net⟩.  This font editor can convert most outline font formats.
+       Another  solution  for  creating  type42 wrappers is to use FontForge, available from http://fontforge.sf.net.
+       This font editor can convert most outline font formats.
 
 FONT INSTALLATION
        This section gives a summary of the above explanations; it can serve as a step-by-step font installation guide
        for grops.
 
-        •  Convert  your  font to something groff understands.  This is either a PostScript Type 1 font in PFA format
+        •  Convert your font to something groff understands.  This is either a PostScript Type 1 font in  PFA  format
            or a PostScript Type 42 font, together with an AFM file.
 
            The very first characters in a PFA file look like this:
@@ -371,37 +370,37 @@ FONT INSTALLATION
 
                   %!PS-TrueTypeFont
 
-           This is a wrapper format for TrueType fonts.  Old PS printers might not support it (this  is,  they  don't
+           This  is  a  wrapper format for TrueType fonts.  Old PS printers might not support it (this is, they don't
            have a built-in TrueType font interpreter).
 
-           If  your  font  is  in  PFB  format (such fonts normally have ‘.pfb’ as the file extension), you might use
-           groff's pfbtops(1) program to convert it to PFA.  For TrueType fonts, try ttftot42 or fontforge.  For  all
+           If your font is in PFB format (such fonts normally have ‘.pfb’ as  the  file  extension),  you  might  use
+           groff's  pfbtops(1) program to convert it to PFA.  For TrueType fonts, try ttftot42 or fontforge.  For all
            other font formats use fontforge which can convert most outline font formats.
 
         •  Convert the AFM file to a groff font description file with the afmtodit(1) program.  An example call is
 
                   afmtodit Foo-Bar-Bold.afm textmap FBB
 
-           which  converts  the  metric  file  ‘Foo-Bar-Bold.afm’ to the groff font ‘FBB’.  If you have a font family
-           which comes with normal, bold, italic, and bold italic faces, it is recommended to use the letters  R,  B,
+           which converts the metric file ‘Foo-Bar-Bold.afm’ to the groff font ‘FBB’.  If  you  have  a  font  family
+           which  comes  with normal, bold, italic, and bold italic faces, it is recommended to use the letters R, B,
            I, and BI, respectively, as postfixes in the groff font names to make groff's ‘.fam’ request work.  An ex‐
-           ample  is  groff's  built-in Times-Roman font: The font family name is T, and the groff font names are TR,
+           ample is groff's built-in Times-Roman font: The font family name is T, and the groff font  names  are  TR,
            TB, TI, and TBI.
 
-        •  Install both the groff font description files and the fonts in a ‘devps’ subdirectory  of  the  font  path
-           which  groff  finds.  See the ENVIRONMENT section in the troff(1) man page which lists the actual value of
+        •  Install  both  the  groff  font description files and the fonts in a ‘devps’ subdirectory of the font path
+           which groff finds.  See the ENVIRONMENT section in the troff(1) man page which lists the actual  value  of
            the font path.  Note that groff doesn't use the AFM files (but it is a good idea to store them anyway).
 
-        •  Register all fonts which must be downloaded to the printer in the ‘devps/download’ file.  Only  the  first
-           occurrence  of this file in the font path is read.  This means that you should copy the default ‘download’
-           file to the first directory in your font path and add your fonts there.  To continue the above example  we
-           assume  that the PS font name for Foo-Bar-Bold.pfa is ‘XY-Foo-Bar-Bold’ (the PS font name is stored in the
+        •  Register  all  fonts which must be downloaded to the printer in the ‘devps/download’ file.  Only the first
+           occurrence of this file in the font path is read.  This means that you should copy the default  ‘download’
+           file  to the first directory in your font path and add your fonts there.  To continue the above example we
+           assume that the PS font name for Foo-Bar-Bold.pfa is ‘XY-Foo-Bar-Bold’ (the PS font name is stored in  the
            internalname field in the ‘FBB’ file), thus the following line should be added to ’download’.
 
                   XY-Foo-Bar-Bold Foo-Bar-Bold.pfa
 
 OLD FONTS
-       groff versions 1.19.2 and earlier contain a slightly different set of the 35 Adobe core fonts; the  difference
+       groff  versions 1.19.2 and earlier contain a slightly different set of the 35 Adobe core fonts; the difference
        is mainly the lack of the ‘Euro’ glyph and a reduced set of kerning pairs.  For backwards compatibility, these
        old fonts are installed also in the
 
@@ -409,7 +408,7 @@ OLD FONTS
 
        directory.
 
-       To  use  them, make sure that grops finds the fonts before the default system fonts (with the same names): Ei‐
+       To use them, make sure that grops finds the fonts before the default system fonts (with the same  names):  Ei‐
        ther add command line option -F to grops
 
               groff -Tps -P-F -P/usr/share/groff/1.22.3/oldfont ...
@@ -420,11 +419,11 @@ OLD FONTS
 
 ENVIRONMENT
        GROPS_PROLOGUE
-              If this is set to foo, then grops uses the file foo (in the font path) instead of the default  prologue
+              If  this is set to foo, then grops uses the file foo (in the font path) instead of the default prologue
               file prologue.  The option -P overrides this environment variable.
 
        GROFF_FONT_PATH
-              A  list  of  directories  in which to search for the devname directory in addition to the default ones.
+              A list of directories in which to search for the devname directory in addition  to  the  default  ones.
               See troff(1) and groff_font(5) for more details.
 
 FILES
@@ -440,7 +439,7 @@ FILES
 
        /usr/share/groff/1.22.3/tmac/pspic.tmac      Definition of PSPIC macro, automatically loaded by ps.tmac.
 
-       /usr/share/groff/1.22.3/tmac/psold.tmac      Macros to disable use of characters not present  in  older  Post‐
+       /usr/share/groff/1.22.3/tmac/psold.tmac      Macros  to  disable  use of characters not present in older Post‐
                                                     Script printers (e.g., ‘eth’ or ‘thorn’).
 
        /tmp/gropsXXXXXX                             Temporary file.  See groff(1) for details on the location of tem‐
@@ -449,8 +448,7 @@ FILES
 SEE ALSO
        afmtodit(1), groff(1), troff(1), pfbtops(1), groff_out(5), groff_font(5), groff_char(7), groff_tmac(5)
 
-       PostScript   Language   Document   Structuring  Conventions  Specification  ⟨http://partners.adobe.com/public/
-       developer/en/ps/5001.DSC_Spec.pdf⟩
+       PostScript Language Document Structuring Conventions Specification
 
 COPYING
        Copyright © 1989-2014 Free Software Foundation, Inc.

package/manpages/rhel8/troff.1.txt

@@ -232,7 +232,6 @@ COPYING
        source package.
 
 AUTHORS
-       This file was originally written by James Clark, it was modified by  Werner  Lemberg  ⟨wl@gnu.org⟩  and  Bernd
-       Warken ⟨groff-bernd.warken-72@web.de⟩.
+       This file was originally written by James Clark, it was modified by Werner Lemberg and Bernd Warken.
 
 Groff Version 1.22.3                               4 November 2014                                           TROFF(1)

package/manpages/rhel9/groff.1.txt

@@ -16,7 +16,7 @@ SYNOPSIS
 DESCRIPTION
        This  document  describes the groff program, the main front-end for the groff document formatting system.  The
        groff program and macro suite is the implementation of a roff(7) system within the  free  software  collection
-       GNU ⟨http://www.gnu.org⟩.  The groff system has all features of the classical roff, but adds many extensions.
+       GNU.  The groff system has all features of the classical roff, but adds many extensions.
 
        The groff program allows control of the whole groff system by command-line options.  This is a great simplifi‐
        cation in comparison to the classical case (which uses pipes only).
@@ -578,27 +578,25 @@ INSTALLATION DIRECTORIES
               Font file for font F of device name.
 
 AVAILABILITY
-       Information on how to get groff and related information is available at the groff  page  of  the  GNU  website
-       ⟨http://www.gnu.org/software/groff⟩.
+       Information on how to get groff and related information is available at the groff page of the GNU website.
 
        Three groff mailing lists are available:
 
-              bug tracker activity (read-only) ⟨bug-groff@gnu.org⟩;
+              bug tracker activity (read-only);
 
-              general discussion ⟨groff@gnu.org⟩; and
+              general discussion; and
 
-              commit activity (read-only) ⟨groff-commit@gnu.org⟩, which reports changes to groff's source code repos‐
-              itory by its developers.
+              commit activity (read-only), which reports changes to groff's source code repository by its developers.
 
-       Details  on  repository access and much more can be found in the file README at the top directory of the groff
+       Details on repository access and much more can be found in the file README at the top directory of  the  groff
        source package.
 
-       A free implementation of the grap preprocessor, written by Ted Faber ⟨faber@lunabase.org⟩, can be found at the
-       grap website ⟨http://www.lunabase.org/~faber/Vault/software/grap/⟩.  This is the only grap supported by groff.
+       A  free implementation of the grap preprocessor, written by Ted Faber, can be found at the grap website.  This
+       is the only grap supported by groff.
 
 AUTHORS
-       groff was written by James Clark ⟨jjc@jclark.com⟩.  This document was rewritten, enhanced, and put  under  the
-       FDL license in 2002 by Bernd Warken ⟨groff-bernd.warken-72@web.de⟩.
+       groff was written by James Clark.  This document was rewritten, enhanced, and put under  the  FDL  license  in
+       2002 by Bernd Warken.
 
 SEE ALSO
        Groff:  The  GNU  Implementation of troff, by Trent A. Fisher and Werner Lemberg, is the primary groff manual.

package/manpages/rhel9/grops.1.txt

@@ -348,17 +348,16 @@ USAGE
        Yet,  the easiest method involves the use of the application ttftot42(1).  This program uses freetype(3) (ver‐
        sion 1.3.1) to generate type42 font wrappers and well-formed AFM files that can  be  fed  to  the  afmtodit(1)
        script  to create appropriate metric files.  The resulting font wrappers should be added to the download file.
-       ttftot42 source code can be downloaded from ftp://www.giga.or.at/pub/nih/ttftot42/  ⟨ftp://www.giga.or.at/pub/
-       nih/ttftot42/⟩.
+       ttftot42 source code can be downloaded from ftp://www.giga.or.at/pub/nih/ttftot42/.
 
-       Another  solution  for  creating  type42  wrappers is to use FontForge, available from http://fontforge.sf.net
-       ⟨http://fontforge.sf.net⟩.  This font editor can convert most outline font formats.
+       Another solution for creating type42 wrappers is to use  FontForge,  available  from  http://fontforge.sf.net.
+       This font editor can convert most outline font formats.
 
 FONT INSTALLATION
        This section gives a summary of the above explanations; it can serve as a step-by-step font installation guide
        for grops.
 
-        •  Convert your font to something groff understands.  This is either a PostScript Type 1 font in  PFA  format
+        •  Convert  your  font to something groff understands.  This is either a PostScript Type 1 font in PFA format
            or a PostScript Type 42 font, together with an AFM file.
 
            The very first characters in a PFA file look like this:
@@ -371,37 +370,37 @@ FONT INSTALLATION
 
                   %!PS-TrueTypeFont
 
-           This  is  a  wrapper format for TrueType fonts.  Old PS printers might not support it (this is, they don't
+           This is a wrapper format for TrueType fonts.  Old PS printers might not support it (this  is,  they  don't
            have a built-in TrueType font interpreter).
 
            If your font is in PFB format (such fonts normally have .pfb as the file extension), you might use groff's
-           pfbtops(1) program to convert it to PFA.  For TrueType fonts, try ttftot42 or fontforge.   For  all  other
+           pfbtops(1)  program  to  convert it to PFA.  For TrueType fonts, try ttftot42 or fontforge.  For all other
            font formats use fontforge which can convert most outline font formats.
 
         •  Convert the AFM file to a groff font description file with the afmtodit(1) program.  An example call is
 
                   afmtodit Foo-Bar-Bold.afm textmap FBB
 
-           which  converts  the  metric file Foo-Bar-Bold.afm to the groff font FBB.  If you have a font family which
-           comes with normal, bold, italic, and bold italic faces, it is recommended to use the letters R, B, I,  and
+           which converts the metric file Foo-Bar-Bold.afm to the groff font FBB.  If you have a  font  family  which
+           comes  with normal, bold, italic, and bold italic faces, it is recommended to use the letters R, B, I, and
            BI, respectively, as postfixes in the groff font names to make groff's ‘.fam’ request work.  An example is
            groff's built-in Times-Roman font: The font family name is T, and the groff font names are TR, TB, TI, and
            TBI.
 
         •  Install both the groff font description files and the fonts in a devps subdirectory of the font path which
-           groff  finds.   See  section  “Environment”  in troff(1) for the actual value of the font path.  Note that
+           groff finds.  See section “Environment” in troff(1) for the actual value of  the  font  path.   Note  that
            groff doesn't use the AFM files (but it is a good idea to store them anyway).
 
         •  Register all fonts which must be downloaded to the printer in the devps/download file.  Only the first oc‐
            currence of this file in the font path is read.  This means that you should copy the default download file
-           to the first directory in your font path and add your fonts there.  To continue the above example  we  as‐
-           sume  that  the  PS font name for Foo-Bar-Bold.pfa is ‘XY-Foo-Bar-Bold’ (the PS font name is stored in the
+           to  the  first directory in your font path and add your fonts there.  To continue the above example we as‐
+           sume that the PS font name for Foo-Bar-Bold.pfa is ‘XY-Foo-Bar-Bold’ (the PS font name is  stored  in  the
            internalname field in the FBB file), thus the following line should be added to download.
 
                   XY-Foo-Bar-Bold Foo-Bar-Bold.pfa
 
 OLD FONTS
-       groff versions 1.19.2 and earlier contain a slightly different set of the 35 Adobe core fonts; the  difference
+       groff  versions 1.19.2 and earlier contain a slightly different set of the 35 Adobe core fonts; the difference
        is mainly the lack of the ‘Euro’ glyph and a reduced set of kerning pairs.  For backwards compatibility, these
        old fonts are installed also in the
 
@@ -409,7 +408,7 @@ OLD FONTS
 
        directory.
 
-       To  use  them, make sure that grops finds the fonts before the default system fonts (with the same names): Ei‐
+       To use them, make sure that grops finds the fonts before the default system fonts (with the same  names):  Ei‐
        ther add command-line option -F to grops
 
               groff -Tps -P-F -P/usr/share/groff/1.22.4/oldfont ...
@@ -420,15 +419,15 @@ OLD FONTS
 
 ENVIRONMENT
        GROPS_PROLOGUE
-              If this is set to foo, then grops uses the file foo (in the font path) instead of the default  prologue
+              If  this is set to foo, then grops uses the file foo (in the font path) instead of the default prologue
               file prologue.  The option -P overrides this environment variable.
 
        GROFF_FONT_PATH
-              A  list  of  directories  in which to search for the devname directory in addition to the default ones.
+              A list of directories in which to search for the devname directory in addition  to  the  default  ones.
               See troff(1) and groff_font(5) for more details.
 
        SOURCE_DATE_EPOCH
-              A timestamp (expressed as seconds since the Unix epoch) to use as the creation timestamp  in  place  of
+              A  timestamp  (expressed  as seconds since the Unix epoch) to use as the creation timestamp in place of
               the current time.
 
 FILES
@@ -459,7 +458,6 @@ FILES
 SEE ALSO
        afmtodit(1), groff(1), troff(1), pfbtops(1), groff_out(5), groff_font(5), groff_char(7), groff_tmac(5)
 
-       PostScript   Language   Document   Structuring  Conventions  Specification  ⟨http://partners.adobe.com/public/
-       developer/en/ps/5001.DSC_Spec.pdf⟩
+       PostScript Language Document Structuring Conventions Specification
 
 groff 1.22.4                                       11 October 2021                                           GROPS(1)

package/manpages/rhel9/pic.1.txt

@@ -403,14 +403,14 @@ SEE ALSO
 
        Tpic: Pic for TeX
 
-       Brian W. Kernighan, PIC — A Graphics Language for Typesetting  (User  Manual)  ⟨http://cm.bell-labs.com/cm/cs/
-       cstr/116.ps.gz⟩.  AT&T Bell Laboratories, Computing Science Technical Report No. 116 (revised May, 1991).
+       Brian W. Kernighan, PIC — A Graphics Language for Typesetting (User Manual).  AT&T Bell Laboratories,  Comput‐
+       ing Science Technical Report No. 116 (revised May, 1991).
 
-       ps2eps is available from CTAN mirrors, e.g. ⟨ftp://ftp.dante.de/tex-archive/support/ps2eps/⟩
+       ps2eps is available from CTAN mirrors, e.g. ftp://ftp.dante.de/tex-archive/support/ps2eps/
 
-       W. Richard Stevens, Turning PIC into HTML ⟨http://www.kohala.com/start/troff/pic2html.html⟩
+       W. Richard Stevens, Turning PIC into HTML
 
-       W. Richard Stevens, Examples of pic Macros ⟨http://www.kohala.com/start/troff/pic.examples.ps⟩
+       W. Richard Stevens, Examples of pic Macros
 
 BUGS
        Input  characters  that are invalid for groff (i.e., those with ASCII code 0, or 013 octal, or between 015 and

package/manpages/rhel9/troff.1.txt

@@ -205,7 +205,7 @@ FILES
 
 AUTHORS
        The GNU version of troff was originally written by James Clark; he also wrote the  original  version  of  this
-       document, which was modified by Werner Lemberg ⟨wl@gnu.org⟩ and Bernd Warken ⟨groff-bernd.warken-72@web.de⟩.
+       document, which was modified by Werner Lemberg and Bernd Warken.
 
 SEE ALSO
        groff(1)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-redhat-manpage-data",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Pre-extracted RHEL man pages for mcp-redhat-manpage (RHEL 8, 9, 10)",
   "main": "index.js",
   "scripts": {
@@ -21,5 +21,9 @@
   "homepage": "https://github.com/shonstephens/mcp-redhat-manpage-data#readme",
   "bugs": {
     "url": "https://github.com/shonstephens/mcp-redhat-manpage-data/issues"
+  },
+  "publishConfig": {
+    "provenance": true,
+    "access": "public"
   }
 }

package/manpages/rhel10/.k5identity.5.txt

@@ -1,50 +0,0 @@
-K5IDENTITY(5)                                        MIT Kerberos                                       K5IDENTITY(5)
-
-NAME
-       k5identity - Kerberos V5 client principal selection rules
-
-DESCRIPTION
-       The  .k5identity  file,  which  resides  in  a user's home directory, contains a list of rules for selecting a
-       client principals based on the server being accessed.  These rules are  used  to  choose  a  credential  cache
-       within the cache collection when possible.
-
-       Blank lines and lines beginning with # are ignored.  Each line has the form:
-          principal field=value ...
-
-       If  the server principal meets all of the field constraints, then principal is chosen as the client principal.
-       The following fields are recognized:
-
-       realm  If the realm of the server principal is known, it is matched against value, which may be a pattern  us‐
-              ing shell wildcards.  For host-based server principals, the realm will generally only be known if there
-              is a [domain_realm] section in krb5.conf with a mapping for the hostname.
-
-       service
-              If  the  server  principal  is  a host-based principal, its service component is matched against value,
-              which may be a pattern using shell wildcards.
-
-       host   If the server principal is a host-based principal, its hostname component is converted  to  lower  case
-              and matched against value, which may be a pattern using shell wildcards.
-
-              If  the server principal matches the constraints of multiple lines in the .k5identity file, the princi‐
-              pal from the first matching line is used.  If no line matches, credentials will be selected some  other
-              way, such as the realm heuristic or the current primary cache.
-
-EXAMPLE
-       The  following example .k5identity file selects the client principal alice@KRBTEST.COM if the server principal
-       is within that realm, the principal alice/root@EXAMPLE.COM if the server host is within a  servers  subdomain,
-       and the principal alice/mail@EXAMPLE.COM when accessing the IMAP service on mail.example.com:
-
-          alice@KRBTEST.COM       realm=KRBTEST.COM
-          alice/root@EXAMPLE.COM  host=*.servers.example.com
-          alice/mail@EXAMPLE.COM  host=mail.example.com service=imap
-
-SEE ALSO
-       kerberos(1), krb5.conf
-
-AUTHOR
-       MIT
-
-COPYRIGHT
-       1985-2025, MIT
-
-1.21.3                                                                                                  K5IDENTITY(5)

package/manpages/rhel10/.k5login.5.txt

@@ -1,44 +0,0 @@
-K5LOGIN(5)                                           MIT Kerberos                                          K5LOGIN(5)
-
-NAME
-       k5login - Kerberos V5 acl file for host access
-
-DESCRIPTION
-       The .k5login file, which resides in a user's home directory, contains a list of the Kerberos principals.  Any‐
-       one  with  valid  tickets for a principal in the file is allowed host access with the UID of the user in whose
-       home directory the file resides.  One common use is to place a .k5login file in root's home directory, thereby
-       granting system administrators remote root access to the host via Kerberos.
-
-EXAMPLES
-       Suppose the user alice had a .k5login file in her home directory containing just the following line:
-
-          bob@FOOBAR.ORG
-
-       This would allow bob to use Kerberos network applications, such as ssh(1), to access  alice's  account,  using
-       bob's  Kerberos  tickets.   In  a default configuration (with k5login_authoritative set to true in krb5.conf),
-       this .k5login file would not let alice use those network applications to access her account, since she is  not
-       listed!   With  no  .k5login file, or with k5login_authoritative set to false, a default rule would permit the
-       principal alice in the machine's default realm to access the alice account.
-
-       Let us further suppose that alice is a system administrator.  Alice and the other system administrators  would
-       have their principals in root's .k5login file on each host:
-
-          alice@BLEEP.COM
-
-          joeadmin/root@BLEEP.COM
-
-       This  would allow either system administrator to log in to these hosts using their Kerberos tickets instead of
-       having to type the root password.  Note that because bob retains the Kerberos tickets for his  own  principal,
-       bob@FOOBAR.ORG,  he  would not have any of the privileges that require alice's tickets, such as root access to
-       any of the site's hosts, or the ability to change alice's password.
-
-SEE ALSO
-       kerberos(1)
-
-AUTHOR
-       MIT
-
-COPYRIGHT
-       1985-2025, MIT
-
-1.21.3                                                                                                     K5LOGIN(5)

package/manpages/rhel8/.k5identity.5.txt

@@ -1,50 +0,0 @@
-K5IDENTITY(5)                                        MIT Kerberos                                       K5IDENTITY(5)
-
-NAME
-       k5identity - Kerberos V5 client principal selection rules
-
-DESCRIPTION
-       The  .k5identity  file,  which  resides  in  a user's home directory, contains a list of rules for selecting a
-       client principals based on the server being accessed.  These rules are  used  to  choose  a  credential  cache
-       within the cache collection when possible.
-
-       Blank lines and lines beginning with # are ignored.  Each line has the form:
-          principal field=value ...
-
-       If  the server principal meets all of the field constraints, then principal is chosen as the client principal.
-       The following fields are recognized:
-
-       realm  If the realm of the server principal is known, it is matched against value, which may be a pattern  us‐
-              ing shell wildcards.  For host-based server principals, the realm will generally only be known if there
-              is a [domain_realm] section in krb5.conf with a mapping for the hostname.
-
-       service
-              If  the  server  principal  is  a host-based principal, its service component is matched against value,
-              which may be a pattern using shell wildcards.
-
-       host   If the server principal is a host-based principal, its hostname component is converted  to  lower  case
-              and matched against value, which may be a pattern using shell wildcards.
-
-              If  the server principal matches the constraints of multiple lines in the .k5identity file, the princi‐
-              pal from the first matching line is used.  If no line matches, credentials will be selected some  other
-              way, such as the realm heuristic or the current primary cache.
-
-EXAMPLE
-       The  following example .k5identity file selects the client principal alice@KRBTEST.COM if the server principal
-       is within that realm, the principal alice/root@EXAMPLE.COM if the server host is within a  servers  subdomain,
-       and the principal alice/mail@EXAMPLE.COM when accessing the IMAP service on mail.example.com:
-
-          alice@KRBTEST.COM       realm=KRBTEST.COM
-          alice/root@EXAMPLE.COM  host=*.servers.example.com
-          alice/mail@EXAMPLE.COM  host=mail.example.com service=imap
-
-SEE ALSO
-       kerberos(1), krb5.conf
-
-AUTHOR
-       MIT
-
-COPYRIGHT
-       1985-2025, MIT
-
-1.21.3                                                                                                  K5IDENTITY(5)

package/manpages/rhel8/.k5login.5.txt

@@ -1,44 +0,0 @@
-K5LOGIN(5)                                           MIT Kerberos                                          K5LOGIN(5)
-
-NAME
-       k5login - Kerberos V5 acl file for host access
-
-DESCRIPTION
-       The .k5login file, which resides in a user's home directory, contains a list of the Kerberos principals.  Any‐
-       one  with  valid  tickets for a principal in the file is allowed host access with the UID of the user in whose
-       home directory the file resides.  One common use is to place a .k5login file in root's home directory, thereby
-       granting system administrators remote root access to the host via Kerberos.
-
-EXAMPLES
-       Suppose the user alice had a .k5login file in her home directory containing just the following line:
-
-          bob@FOOBAR.ORG
-
-       This would allow bob to use Kerberos network applications, such as ssh(1), to access  alice's  account,  using
-       bob's  Kerberos  tickets.   In  a default configuration (with k5login_authoritative set to true in krb5.conf),
-       this .k5login file would not let alice use those network applications to access her account, since she is  not
-       listed!   With  no  .k5login file, or with k5login_authoritative set to false, a default rule would permit the
-       principal alice in the machine's default realm to access the alice account.
-
-       Let us further suppose that alice is a system administrator.  Alice and the other system administrators  would
-       have their principals in root's .k5login file on each host:
-
-          alice@BLEEP.COM
-
-          joeadmin/root@BLEEP.COM
-
-       This  would allow either system administrator to log in to these hosts using their Kerberos tickets instead of
-       having to type the root password.  Note that because bob retains the Kerberos tickets for his  own  principal,
-       bob@FOOBAR.ORG,  he  would not have any of the privileges that require alice's tickets, such as root access to
-       any of the site's hosts, or the ability to change alice's password.
-
-SEE ALSO
-       kerberos(1)
-
-AUTHOR
-       MIT
-
-COPYRIGHT
-       1985-2025, MIT
-
-1.21.3                                                                                                     K5LOGIN(5)

package/manpages/rhel9/.k5identity.5.txt

@@ -1,50 +0,0 @@
-K5IDENTITY(5)                                        MIT Kerberos                                       K5IDENTITY(5)
-
-NAME
-       k5identity - Kerberos V5 client principal selection rules
-
-DESCRIPTION
-       The  .k5identity  file,  which  resides  in  a user's home directory, contains a list of rules for selecting a
-       client principals based on the server being accessed.  These rules are  used  to  choose  a  credential  cache
-       within the cache collection when possible.
-
-       Blank lines and lines beginning with # are ignored.  Each line has the form:
-          principal field=value ...
-
-       If  the server principal meets all of the field constraints, then principal is chosen as the client principal.
-       The following fields are recognized:
-
-       realm  If the realm of the server principal is known, it is matched against value, which may be a pattern  us‐
-              ing shell wildcards.  For host-based server principals, the realm will generally only be known if there
-              is a [domain_realm] section in krb5.conf with a mapping for the hostname.
-
-       service
-              If  the  server  principal  is  a host-based principal, its service component is matched against value,
-              which may be a pattern using shell wildcards.
-
-       host   If the server principal is a host-based principal, its hostname component is converted  to  lower  case
-              and matched against value, which may be a pattern using shell wildcards.
-
-              If  the server principal matches the constraints of multiple lines in the .k5identity file, the princi‐
-              pal from the first matching line is used.  If no line matches, credentials will be selected some  other
-              way, such as the realm heuristic or the current primary cache.
-
-EXAMPLE
-       The  following example .k5identity file selects the client principal alice@KRBTEST.COM if the server principal
-       is within that realm, the principal alice/root@EXAMPLE.COM if the server host is within a  servers  subdomain,
-       and the principal alice/mail@EXAMPLE.COM when accessing the IMAP service on mail.example.com:
-
-          alice@KRBTEST.COM       realm=KRBTEST.COM
-          alice/root@EXAMPLE.COM  host=*.servers.example.com
-          alice/mail@EXAMPLE.COM  host=mail.example.com service=imap
-
-SEE ALSO
-       kerberos(1), krb5.conf
-
-AUTHOR
-       MIT
-
-COPYRIGHT
-       1985-2025, MIT
-
-1.21.3                                                                                                  K5IDENTITY(5)

package/manpages/rhel9/.k5login.5.txt

@@ -1,44 +0,0 @@
-K5LOGIN(5)                                           MIT Kerberos                                          K5LOGIN(5)
-
-NAME
-       k5login - Kerberos V5 acl file for host access
-
-DESCRIPTION
-       The .k5login file, which resides in a user's home directory, contains a list of the Kerberos principals.  Any‐
-       one  with  valid  tickets for a principal in the file is allowed host access with the UID of the user in whose
-       home directory the file resides.  One common use is to place a .k5login file in root's home directory, thereby
-       granting system administrators remote root access to the host via Kerberos.
-
-EXAMPLES
-       Suppose the user alice had a .k5login file in her home directory containing just the following line:
-
-          bob@FOOBAR.ORG
-
-       This would allow bob to use Kerberos network applications, such as ssh(1), to access  alice's  account,  using
-       bob's  Kerberos  tickets.   In  a default configuration (with k5login_authoritative set to true in krb5.conf),
-       this .k5login file would not let alice use those network applications to access her account, since she is  not
-       listed!   With  no  .k5login file, or with k5login_authoritative set to false, a default rule would permit the
-       principal alice in the machine's default realm to access the alice account.
-
-       Let us further suppose that alice is a system administrator.  Alice and the other system administrators  would
-       have their principals in root's .k5login file on each host:
-
-          alice@BLEEP.COM
-
-          joeadmin/root@BLEEP.COM
-
-       This  would allow either system administrator to log in to these hosts using their Kerberos tickets instead of
-       having to type the root password.  Note that because bob retains the Kerberos tickets for his  own  principal,
-       bob@FOOBAR.ORG,  he  would not have any of the privileges that require alice's tickets, such as root access to
-       any of the site's hosts, or the ability to change alice's password.
-
-SEE ALSO
-       kerberos(1)
-
-AUTHOR
-       MIT
-
-COPYRIGHT
-       1985-2025, MIT
-
-1.21.3                                                                                                     K5LOGIN(5)