mirror of
https://github.com/openbsd/src.git
synced 2024-12-22 07:27:59 -08:00
Avoid gendered language in man pages when not referring to a specific
person. Rewrite or use singular they. ok thfr@ sthen@ daniel@ ian@ job@ kmos@ jcs@ ratchov@ phessler@ and others I'm likely missing on an earlier version. feedback tj@, feedback and ok jmc@
This commit is contained in:
jsg
parent
5c5d853c4b
commit
25a24f0b58
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: atc.6,v 1.24 2020/12/13 15:47:32 jmc Exp $
|
||||
.\" $OpenBSD: atc.6,v 1.25 2022/02/18 23:17:13 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1990, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
@ -34,7 +34,7 @@
|
||||
.\"
|
||||
.\" Copyright (c) 1986 Ed James. All rights reserved.
|
||||
.\"
|
||||
.Dd $Mdocdate: December 13 2020 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt ATC 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -488,7 +488,7 @@ The
|
||||
file lists the currently available play fields.
|
||||
New field description file names must be placed in this file to be
|
||||
playable.
|
||||
If a player specifies a game not in this file, his score will not be logged.
|
||||
If a player specifies a game not in this file, the score will not be logged.
|
||||
.Pp
|
||||
The game field description files are broken into two parts.
|
||||
The first part is the definition section.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: bs.6,v 1.15 2014/09/08 01:27:54 schwarze Exp $
|
||||
.\" $OpenBSD: bs.6,v 1.16 2022/02/18 23:17:13 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1997, Jason Downs. All rights reserved.
|
||||
.\"
|
||||
@ -23,7 +23,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: September 8 2014 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt BS 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -72,7 +72,7 @@ This disables that check and allows them to close-pack.
|
||||
Selects a
|
||||
.Sq salvo
|
||||
variant.
|
||||
This allows a player one shot per turn for each of his/her
|
||||
This allows players one shot per turn for each of their
|
||||
ships still afloat.
|
||||
This puts a premium on scoring hits early and knocking out
|
||||
some ships and also makes it much harder, for example, when you face a superior
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: canfield.6,v 1.11 2016/03/02 17:51:28 tim Exp $
|
||||
.\" $OpenBSD: canfield.6,v 1.12 2022/02/18 23:17:13 jsg Exp $
|
||||
.\" $NetBSD: canfield.6,v 1.4 1995/03/21 15:08:30 cgd Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1983, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)canfield.6 8.1 (Berkeley) 5/31/93
|
||||
.\"
|
||||
.Dd $Mdocdate: March 2 2016 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt CANFIELD 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -53,15 +53,15 @@ Spaces must be filled from the stock.
|
||||
The top card of the stock also is available to be played on foundations or
|
||||
built on tableau piles.
|
||||
After the stock is exhausted,
|
||||
tableau spaces may be filled from the talon and the player may
|
||||
keep them open until he wishes to use them.
|
||||
tableau spaces may be filled from the talon.
|
||||
Players may keep tableau spaces open until they wish to use them.
|
||||
.Pp
|
||||
Cards are dealt from the hand to the talon by threes
|
||||
and this repeats until there are no more cards in the hand
|
||||
or the player quits.
|
||||
To have cards dealt onto the talon the player types
|
||||
To have cards dealt onto the talon players type
|
||||
.Sq Ic ht
|
||||
for his move.
|
||||
for their move.
|
||||
Foundation base cards are also automatically moved to the foundation when
|
||||
they become available.
|
||||
.Pp
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: cribbage.6,v 1.15 2015/03/12 02:19:10 bentley Exp $
|
||||
.\" $OpenBSD: cribbage.6,v 1.16 2022/02/18 23:17:13 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
@ -29,7 +29,7 @@
|
||||
.\"
|
||||
.\" @(#)cribbage.6 8.1 (Berkeley) 5/31/93
|
||||
.\"
|
||||
.Dd $Mdocdate: March 12 2015 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt CRIBBAGE 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -50,7 +50,7 @@ are needed \(en if so, it will print out the appropriate section from
|
||||
options include:
|
||||
.Bl -tag -width indent
|
||||
.It Fl e
|
||||
When the player makes a mistake scoring his hand or crib, provide an
|
||||
When players make a mistake scoring their hand or crib, provide an
|
||||
explanation of the correct score.
|
||||
.Po
|
||||
This is especially useful for beginning players.
|
||||
@ -64,12 +64,12 @@ the opponent may claim the overlooked points.
|
||||
Print a shorter form of all messages \(en this is only recommended for
|
||||
users who have played the game without specifying this option.
|
||||
.It Fl r
|
||||
Instead of asking the player to cut the deck, the program will randomly
|
||||
Instead of asking players to cut the deck, the program will randomly
|
||||
cut the deck.
|
||||
.El
|
||||
.Pp
|
||||
.Nm
|
||||
first asks the player whether he wishes to play a short game
|
||||
first asks whether to play a short game
|
||||
.Po
|
||||
.Dq once around ,
|
||||
to 61
|
||||
@ -116,8 +116,8 @@ The program keeps track of the scoring of all points and the total of
|
||||
the cards on the table.
|
||||
.Pp
|
||||
After play, the hands are scored.
|
||||
The program requests the player to score his hand
|
||||
.Pq and the crib, if it is his
|
||||
The program requests players to score their hand
|
||||
.Pq and the crib, if it is theirs
|
||||
by printing out the appropriate cards.
|
||||
Play continues until one player reaches the game limit
|
||||
.Pq 61 or 121 .
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: hack.6,v 1.22 2019/04/08 17:49:07 jmc Exp $
|
||||
.\" $OpenBSD: hack.6,v 1.23 2022/02/18 23:17:14 jsg Exp $
|
||||
.\" $NetBSD: hack.6,v 1.5 1995/07/03 19:44:30 jtc Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1985, Stichting Centrum voor Wiskunde en Informatica,
|
||||
@ -59,7 +59,7 @@
|
||||
.\" OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
|
||||
.\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: April 8 2019 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt HACK 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -91,8 +91,8 @@ will identify the things you see on the screen.
|
||||
To win the game (as opposed to merely playing to beat other people's high
|
||||
scores) you must locate the Amulet of Yendor which is somewhere below
|
||||
the 20th level of the dungeon and get it out.
|
||||
Nobody has achieved this yet and if somebody does,
|
||||
he will probably go down in history as a hero among heroes.
|
||||
Nobody has achieved this yet and whoever does
|
||||
will probably go down in history as a hero among heroes.
|
||||
.Pp
|
||||
When the game ends, either by your death, when you quit, or if you escape
|
||||
from the caves,
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
.\" $NetBSD: hunt.6,v 1.3 1997/10/10 16:32:30 lukem Exp $
|
||||
.\" $OpenBSD: hunt.6,v 1.22 2014/09/28 07:53:02 schwarze Exp $
|
||||
.\" $OpenBSD: hunt.6,v 1.23 2022/02/18 23:17:14 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1985 Conrad C. Huang, Gregory S. Couch, Kenneth C.R.C. Arnold
|
||||
.\" San Francisco, California
|
||||
@ -31,7 +31,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: September 28 2014 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt HUNT 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -350,16 +350,15 @@ Slime goes around walls, not through them.
|
||||
.It
|
||||
Walls regenerate, reappearing in the order they were destroyed.
|
||||
One percent of the regenerated walls will be diagonal walls or doors.
|
||||
When a wall is generated directly beneath a player, he is thrown in
|
||||
When a wall is generated directly beneath a player, they are thrown in
|
||||
a random direction for a random period of time.
|
||||
When he lands, he
|
||||
sustains damage
|
||||
When the player lands, they sustain damage
|
||||
.Po
|
||||
up to 20 percent of the amount of damage already sustained
|
||||
.Pc ;
|
||||
i.e.,
|
||||
the less damage he had, the more nimble he is and
|
||||
therefore less likely to hurt himself on landing.
|
||||
the less damage the player had, the more nimble they are and
|
||||
therefore less likely to hurt themselves on landing.
|
||||
.\"It
|
||||
.\"There is a volcano close to the center of the maze which goes off
|
||||
.\"close to every 30 deaths.
|
||||
@ -465,7 +464,7 @@ how many times player died
|
||||
.It Still
|
||||
how many times player died without typing in any commands
|
||||
.It Saved
|
||||
how many times a shot/bomb would have killed player if he hadn't
|
||||
how many times a shot/bomb would have killed player if they hadn't
|
||||
ducked or absorbed it
|
||||
.It Connect
|
||||
current connection state(s) of player:
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: mille.6,v 1.13 2014/09/08 01:27:54 schwarze Exp $
|
||||
.\" $OpenBSD: mille.6,v 1.14 2022/02/18 23:17:14 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1983, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
@ -29,7 +29,7 @@
|
||||
.\"
|
||||
.\" @(#)mille.6 8.3 (Berkeley) 6/1/94
|
||||
.\"
|
||||
.Dd $Mdocdate: September 8 2014 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt MILLE 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -324,7 +324,7 @@ except that
|
||||
.Em "you cannot play more than two 200 mile cards in one hand" .
|
||||
A hand ends whenever one player gets exactly 700 miles or the deck runs out.
|
||||
In that case, play continues until either someone reaches 700,
|
||||
or neither player can use any cards in his hand.
|
||||
or neither player can use any cards in their hand.
|
||||
If the trip is completed after the deck runs out, this is called
|
||||
.Em Delayed Action .
|
||||
.Ss Coup Fourre
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: monop.6,v 1.16 2017/06/09 15:32:40 fcambus Exp $
|
||||
.\" $OpenBSD: monop.6,v 1.17 2022/02/18 23:17:14 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980 The Regents of the University of California.
|
||||
.\" All rights reserved.
|
||||
@ -29,7 +29,7 @@
|
||||
.\"
|
||||
.\" @(#)monop.6 6.5 (Berkeley) 3/25/93
|
||||
.\"
|
||||
.Dd $Mdocdate: June 9 2017 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt MONOP 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -49,11 +49,11 @@ no auction is held and the property remains unowned.
|
||||
.Pp
|
||||
The game, in effect, lends the player money,
|
||||
so it is possible to buy something which you cannot afford.
|
||||
However, as soon as a person goes into debt,
|
||||
he must
|
||||
However, as soon as players go into debt,
|
||||
they must
|
||||
.Dq fix the problem ,
|
||||
i.e., make himself solvent, before play can continue.
|
||||
If this is not possible, the player's property reverts to his debtee,
|
||||
i.e., make themselves solvent, before play can continue.
|
||||
If this is not possible, the player's property reverts to their debtee,
|
||||
either a player or the bank.
|
||||
A player can resign at any time to any person or the bank,
|
||||
which puts the property back on the board, unowned.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
.\" $OpenBSD: phantasia.6tbl,v 1.10 2016/09/09 15:32:28 tb Exp $
|
||||
.\" $OpenBSD: phantasia.6tbl,v 1.11 2022/02/18 23:17:14 jsg Exp $
|
||||
.\" $NetBSD: phantasia.6,v 1.9 2002/09/26 18:32:03 wiz Exp $
|
||||
.\"
|
||||
.Dd $Mdocdate: September 9 2016 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt PHANTASIA 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -196,7 +196,7 @@ Paralyzed monsters wake up very fast when nicked.
|
||||
This is essentially a battle of wits with the monster.
|
||||
Success is based upon the player's and the monster's
|
||||
.Em brains .
|
||||
The player gets credit for slaying the monster if he/she succeeds.
|
||||
If successful, the player gets credit for slaying the monster.
|
||||
Otherwise, nothing happens, and the chance to
|
||||
.Ic luckout
|
||||
is lost.
|
||||
@ -339,8 +339,7 @@ can overcome the player, and how much
|
||||
.Em poison
|
||||
the player can withstand.
|
||||
.Ss Spells
|
||||
During the course of the game, the player may exercise his/her
|
||||
magic powers.
|
||||
During the course of the game, the player may use magic powers.
|
||||
These cases are described below.
|
||||
.Bl -tag -width "all or nothing" -offset indent
|
||||
.It Ic cloak
|
||||
@ -353,7 +352,7 @@ These cases are described below.
|
||||
Used during normal play.
|
||||
Prevents monsters from finding the character,
|
||||
as well as hiding the player from other players.
|
||||
His/her coordinates show up as '?' in the
|
||||
The player's coordinates show up as '?' in the
|
||||
.Ic players
|
||||
option.
|
||||
Players cannot collect
|
||||
@ -861,7 +860,8 @@ and
|
||||
They come in four different flavors.
|
||||
All
|
||||
.Em rings
|
||||
rest the player to maximum and cause him/her to hit much harder
|
||||
rest the player to maximum,
|
||||
and cause them to hit much harder
|
||||
in battle with monsters (assuming the
|
||||
.Em ring
|
||||
is being used for battle.)
|
||||
@ -876,8 +876,8 @@ After a few times of using these types, the player falls
|
||||
under the control of the
|
||||
.Em ring ,
|
||||
and strange, random things will occur.
|
||||
Eventually, the player dies, and gives his/her name to a monster
|
||||
on the file.
|
||||
Eventually, the player dies,
|
||||
and the player's name is given to a monster on the file.
|
||||
Dying before the
|
||||
.Em ring
|
||||
is used up also renames the monster.
|
||||
@ -888,7 +888,7 @@ are much more benign.
|
||||
The one from a
|
||||
.Em nazgul
|
||||
is good for a limited number of battle rounds, and will save
|
||||
the player from death if it was being used when he/she died.
|
||||
the player from death if it was being used.
|
||||
The one from
|
||||
.Em Dark Lord
|
||||
is the same, except that it never is used up.
|
||||
@ -920,7 +920,7 @@ reaches
|
||||
are converted to
|
||||
.Em gold .
|
||||
.Pp
|
||||
Once a player is king, he/she may do certain things while in
|
||||
Once a player is king, they may do certain things while in
|
||||
the Lord's Chamber (0,0).
|
||||
These are exercised with the
|
||||
.Ic decree
|
||||
@ -947,17 +947,16 @@ A
|
||||
protects from king's curses.
|
||||
.It Ic energy void
|
||||
The king may put a number of these scattered about
|
||||
his/her kingdom as he/she pleases.
|
||||
If a player hits one, he/she loses
|
||||
the kingdom.
|
||||
If a player hits one, they lose
|
||||
.Em mana , energy ,
|
||||
and
|
||||
.Em gold .
|
||||
The energy void disappears after being hit.
|
||||
.It Ic bestow
|
||||
This is also done to another player.
|
||||
The king may wish to reward one or more loyal subjects by sharing his/her
|
||||
riches
|
||||
.Em ( gold ) .
|
||||
The king may wish to reward one or more loyal subjects by sharing
|
||||
.Em gold .
|
||||
Or it is a convenient way to dispose of some unwanted deadweight.
|
||||
.It Ic collect taxes
|
||||
Everyone pays 7% tax on all
|
||||
@ -1013,9 +1012,9 @@ may
|
||||
.Ic teleport
|
||||
with greater ease.
|
||||
.Pp
|
||||
Upon finding the grail, the player advances to position of
|
||||
Upon finding the grail, players advance to position of
|
||||
.Em valar .
|
||||
He/she may then exercise more and niftier options under
|
||||
They may then exercise more and niftier options under
|
||||
.Ic intervention .
|
||||
These include all of the council members' options plus the
|
||||
ability to move other players about, bless them, and throw monsters at
|
||||
@ -1024,7 +1023,7 @@ A
|
||||
.Em valar Ns 's
|
||||
blessing has the same effect as the treasure
|
||||
.Em blessing ,
|
||||
except that the affected player does not get his/her
|
||||
except that the affected player does not get the
|
||||
.Em blessing
|
||||
flag set.
|
||||
All
|
||||
@ -1043,11 +1042,13 @@ or call monsters.
|
||||
.Em valar
|
||||
finds a
|
||||
.Em transporter . )
|
||||
This is to allow him/her to dispose of excess
|
||||
This is to allow the
|
||||
.Em valar
|
||||
to dispose of excess
|
||||
.Em gold .
|
||||
Any monsters which a
|
||||
.Em valar
|
||||
encounters are based upon his/her size.
|
||||
encounters are based upon the valar's size.
|
||||
Only one valar may exist at a time.
|
||||
The current valar is replaced when another player finds the grail.
|
||||
The valar is then bumped back to the council of the wise.
|
||||
@ -1097,8 +1098,8 @@ from the other character types.
|
||||
.El
|
||||
.Ss Special Places
|
||||
Certain regions of the playing grid have different names.
|
||||
In general, this is only to give the player some idea of
|
||||
his/her present location.
|
||||
In general, this is only to give players some idea of
|
||||
their present location.
|
||||
Some special places do exist.
|
||||
.Bl -tag -width "Trading Posts"
|
||||
.It Em Trading Posts
|
||||
@ -1206,8 +1207,8 @@ One-time chance to try to win against the foe.
|
||||
Has a 10% chance of working.
|
||||
.El
|
||||
.Pp
|
||||
Sometimes waits for the other player may be excessive, because
|
||||
he/she may be battling a monster.
|
||||
Sometimes waits for other players may be excessive, because
|
||||
they may be battling a monster.
|
||||
Upon slaying a player in battle the winner gets the other's
|
||||
.Em experience
|
||||
and treasures.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: sail.6,v 1.23 2016/09/09 15:32:28 tb Exp $
|
||||
.\" $OpenBSD: sail.6,v 1.24 2022/02/18 23:17:14 jsg Exp $
|
||||
.\" $NetBSD: sail.6,v 1.4 1995/04/22 10:37:24 cgd Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1988, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)sail.6 8.2 (Berkeley) 12/30/93
|
||||
.\"
|
||||
.Dd $Mdocdate: September 9 2016 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt SAIL 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -60,13 +60,13 @@ players or the computer.
|
||||
They may re-enact one of the many historical sea battles recorded
|
||||
in the game, or they can choose a fictional battle.
|
||||
.Pp
|
||||
As a sea captain in the
|
||||
As sea captains in the
|
||||
.Nm
|
||||
Navy, the player has complete control over the workings of his ship.
|
||||
He must order every maneuver, change the set of his sails, and judge the
|
||||
right moment to let loose the terrible destruction of his broadsides.
|
||||
In addition to fighting the enemy, he must harness the powers of the wind
|
||||
and sea to make them work for him.
|
||||
Navy, players have complete control over the workings of their ship.
|
||||
They must order every maneuver, change the set of their sails, and judge the
|
||||
right moments to let loose the terrible destruction of their broadsides.
|
||||
In addition to fighting their enemies,
|
||||
they must harness the powers of the wind and sea.
|
||||
The outcome of many battles during the age of sail was decided by the
|
||||
ability of one captain to hold the
|
||||
.Sq weather gage .
|
||||
@ -87,7 +87,7 @@ Play the first available ship instead of prompting for a choice.
|
||||
.Sh IMPLEMENTATION
|
||||
.Nm
|
||||
is really two programs in one.
|
||||
Each player starts up a process which runs his own ship.
|
||||
All players start a process which runs their ship.
|
||||
In addition, a
|
||||
.Em driver
|
||||
process is forked
|
||||
@ -97,10 +97,10 @@ to run the computer ships and take care of global bookkeeping.
|
||||
Because the driver must calculate moves for each ship it controls, the
|
||||
more ships the computer is playing, the slower the game will appear.
|
||||
.Pp
|
||||
If a player joins a game in progress, he will synchronize
|
||||
Players who join a game in progress will synchronize
|
||||
with the other players
|
||||
.Pq a rather slow process for everyone ,
|
||||
and then he may play along with the rest.
|
||||
and then they may play along with the rest.
|
||||
.Pp
|
||||
To implement a multi-user game in
|
||||
.Ux
|
||||
@ -145,8 +145,8 @@ that succeeds in linking will have exclusive access to the temporary file.
|
||||
.Ss "CONSEQUENCES OF SEPARATE PLAYER AND DRIVER PROCESSES"
|
||||
When players do something of global interest, such as moving or firing,
|
||||
the driver must coordinate the action with the other ships in the game.
|
||||
For example, if a player wants to move in a certain direction, he writes a
|
||||
message into the temporary file requesting that the driver move his ship.
|
||||
For example, players who want to move in a certain direction, write a
|
||||
message into the temporary file requesting that the driver move their ship.
|
||||
Each
|
||||
.Dq turn ,
|
||||
the driver reads all the messages sent from the players and
|
||||
@ -155,7 +155,7 @@ It then writes back into the temporary file new values of variables, etc.
|
||||
.Pp
|
||||
The most noticeable effect this communication has on the game is the
|
||||
delay in moving.
|
||||
Suppose a player types a move for his ship and hits return.
|
||||
Suppose a player types a move and hits return.
|
||||
What happens then?
|
||||
The player process saves up messages to
|
||||
be written to the temporary file in a buffer.
|
||||
@ -168,7 +168,7 @@ Finally, when the player process gets around to doing another 7-second update,
|
||||
the results of the move are displayed on the screen.
|
||||
Hence, every movement requires four
|
||||
exclusive accesses to the temporary file (anywhere from 7 to 21 seconds
|
||||
depending upon asynchrony) before the player sees the results of his moves.
|
||||
depending upon asynchrony) before players see the results of their moves.
|
||||
.Pp
|
||||
In practice, the delays are not as annoying as they would appear.
|
||||
There is room for
|
||||
@ -997,7 +997,7 @@ tricky.
|
||||
Ed Wang rewrote the
|
||||
.Fn angle
|
||||
routine in 1981 to be less incorrect, and he added code to let a player
|
||||
select which ship he wanted at the start of the game.
|
||||
select a ship at the start of the game.
|
||||
.\"instead of the first one available).
|
||||
.Pp
|
||||
Captain Happy (Craig Leres) is responsible for making
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: snake.6,v 1.14 2015/11/29 15:58:38 jmc Exp $
|
||||
.\" $OpenBSD: snake.6,v 1.15 2022/02/18 23:17:14 jsg Exp $
|
||||
.\" $NetBSD: snake.6,v 1.5 1995/04/22 08:34:35 cgd Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)snake.6 8.1 (Berkeley) 5/31/93
|
||||
.\"
|
||||
.Dd $Mdocdate: November 29 2015 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt SNAKE 6
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -84,7 +84,7 @@ This does
|
||||
.Em not
|
||||
let you jump away from the snake, but rather saves you from having
|
||||
to type a key repeatedly.
|
||||
The snake still gets all his turns.
|
||||
The snake still gets all its turns.
|
||||
.It Ic SEFC
|
||||
Likewise for the upper case versions on the left.
|
||||
.It Ic ATPB
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: chown.2,v 1.26 2015/09/10 17:55:21 schwarze Exp $
|
||||
.\" $OpenBSD: chown.2,v 1.27 2022/02/18 23:17:14 jsg Exp $
|
||||
.\" $NetBSD: chown.2,v 1.10 1995/10/12 15:40:47 jtc Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1991, 1993, 1994
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)chown.2 8.4 (Berkeley) 4/19/94
|
||||
.\"
|
||||
.Dd $Mdocdate: September 10 2015 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt CHOWN 2
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -60,9 +60,10 @@ is changed as specified by the arguments
|
||||
.Fa owner
|
||||
and
|
||||
.Fa group .
|
||||
The owner of a file may change the
|
||||
The owner of a file may change its
|
||||
.Fa group
|
||||
to a group of which he or she is a member, but the change
|
||||
to one the owner is a member of.
|
||||
The change
|
||||
.Fa owner
|
||||
capability is restricted to the superuser.
|
||||
.Pp
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: umask.2,v 1.12 2015/10/12 17:51:55 millert Exp $
|
||||
.\" $OpenBSD: umask.2,v 1.13 2022/02/18 23:17:14 jsg Exp $
|
||||
.\" $NetBSD: umask.2,v 1.6 1995/02/27 12:39:06 cgd Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1991, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)umask.2 8.1 (Berkeley) 6/4/93
|
||||
.\"
|
||||
.Dd $Mdocdate: October 12 2015 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt UMASK 2
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -65,7 +65,7 @@ and
|
||||
system calls to turn off corresponding bits requested in the file mode
|
||||
(see
|
||||
.Xr chmod 2 ) .
|
||||
This clearing allows each user to restrict the default access to his files.
|
||||
This clearing allows users to restrict the default access to their files.
|
||||
.Pp
|
||||
The default mask value is S_IWGRP|S_IWOTH (022, write access for the
|
||||
owner only).
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: SSL_CTX_set_tmp_dh_callback.3,v 1.8 2020/03/30 10:28:59 schwarze Exp $
|
||||
.\" $OpenBSD: SSL_CTX_set_tmp_dh_callback.3,v 1.9 2022/02/18 23:17:15 jsg Exp $
|
||||
.\" OpenSSL b97fdb57 Nov 11 09:33:09 2016 +0100
|
||||
.\"
|
||||
.\" This file was written by Lutz Jaenicke <jaenicke@openssl.org>.
|
||||
@ -48,7 +48,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
|
||||
.\" OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: March 30 2020 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt SSL_CTX_SET_TMP_DH_CALLBACK 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -113,8 +113,8 @@ Anonymous ciphers (without a permanent server key) also use ephemeral DH keys.
|
||||
Using ephemeral DH key exchange yields forward secrecy,
|
||||
as the connection can only be decrypted when the DH key is known.
|
||||
By generating a temporary DH key inside the server application that is lost
|
||||
when the application is left, it becomes impossible for an attacker to decrypt
|
||||
past sessions, even if he gets hold of the normal (certified) key,
|
||||
when the application is left, it becomes impossible for attackers to decrypt
|
||||
past sessions, even if they get hold of the normal (certified) key,
|
||||
as this key was only used for signing.
|
||||
.Pp
|
||||
In order to perform a DH key exchange the server must use a DH group
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: pw_init.3,v 1.14 2016/08/14 14:57:16 tb Exp $
|
||||
.\" $OpenBSD: pw_init.3,v 1.15 2022/02/18 23:17:15 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1995
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
@ -31,7 +31,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: August 14 2016 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt PW_INIT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -114,7 +114,7 @@ before running the editor.
|
||||
.Pp
|
||||
The
|
||||
.Fn pw_prompt
|
||||
function asks the user whether he or she wants to re-edit the password
|
||||
function asks the user whether they want to re-edit the password
|
||||
file; if the answer is no,
|
||||
.Fn pw_prompt
|
||||
deletes the lock file and exits the process.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: mount_tmpfs.8,v 1.4 2014/11/16 02:22:10 brad Exp $
|
||||
.\" $OpenBSD: mount_tmpfs.8,v 1.5 2022/02/18 23:17:15 jsg Exp $
|
||||
.\" $NetBSD: mount_tmpfs.8,v 1.14 2008/04/30 13:10:53 martin Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2005, 2006 The NetBSD Foundation, Inc.
|
||||
@ -29,7 +29,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: November 16 2014 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt MOUNT_TMPFS 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -141,7 +141,7 @@ File system meta-data is not pageable.
|
||||
If there is not enough main memory to hold this information, the system may
|
||||
become unstable or very unresponsive because it will not be able to allocate
|
||||
required memory.
|
||||
A malicious user could trigger this condition if he could create lots of
|
||||
A malicious user could trigger this condition by creating lots of
|
||||
files inside a size-unbounded tmpfs file system.
|
||||
Limiting the number of nodes per file system
|
||||
.Pq Fl n
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: ipsec.4,v 1.86 2022/02/17 12:24:08 jsg Exp $
|
||||
.\" $OpenBSD: ipsec.4,v 1.87 2022/02/18 23:17:15 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright 1997 Niels Provos <provos@physnet.uni-hamburg.de>
|
||||
.\" All rights reserved.
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" Manual page, using -mandoc macros
|
||||
.\"
|
||||
.Dd $Mdocdate: February 17 2022 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt IPSEC 4
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -118,9 +118,9 @@ data, some of the IP header data, and a certain secret value
|
||||
(the authentication key).
|
||||
This value is then sent with the rest of each packet.
|
||||
The receiver performs the same computation, and if the value matches,
|
||||
he knows no one tampered with the data (integrity), the address information
|
||||
it knows no one tampered with the data (integrity), the address information
|
||||
(authenticity) or a sequence number (replay protection).
|
||||
He knows this because the secret authentication key makes sure no
|
||||
It knows this because the secret authentication key makes sure no
|
||||
active attacker (man-in-the-middle) can recompute the correct value after
|
||||
altering the packet.
|
||||
The algorithms used to compute these values are called hash algorithms and are
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: tty.4,v 1.54 2022/02/06 00:29:02 jsg Exp $
|
||||
.\" $OpenBSD: tty.4,v 1.55 2022/02/18 23:17:15 jsg Exp $
|
||||
.\" $NetBSD: tty.4,v 1.4 1996/03/19 04:26:01 paulus Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1991, 1992, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)tty.4 8.3 (Berkeley) 4/19/94
|
||||
.\"
|
||||
.Dd $Mdocdate: February 6 2022 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt TTY 4
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -107,14 +107,13 @@ For more information on dial-out, see
|
||||
When an interactive user logs in, the system prepares the line to
|
||||
behave in a certain way (called a
|
||||
.Em "line discipline" ) ,
|
||||
the particular details of which are described in
|
||||
described in
|
||||
.Xr stty 1
|
||||
at the command level, and in
|
||||
.Xr termios 4
|
||||
at the programming level.
|
||||
A user may be concerned with changing settings associated with his particular
|
||||
login terminal and should refer to the preceding man pages for the common
|
||||
cases.
|
||||
To change settings associated with a login terminal,
|
||||
refer to the preceding man pages for the common cases.
|
||||
The remainder of this man page is concerned with describing details of using
|
||||
and controlling terminal devices at a low level, such as that possibly
|
||||
required by a program wishing to provide features similar to those provided
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: bsd.port.mk.5,v 1.555 2022/02/11 17:19:59 sthen Exp $
|
||||
.\" $OpenBSD: bsd.port.mk.5,v 1.556 2022/02/18 23:17:15 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2000-2008 Marc Espie
|
||||
.\"
|
||||
@ -24,7 +24,7 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: February 11 2022 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt BSD.PORT.MK 5
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -4366,7 +4366,7 @@ instead.
|
||||
.It Ev IGNOREFILES
|
||||
Set to the list of files that can't be checksummed.
|
||||
All uses of it have led to postponing the correct action: talking
|
||||
to the software author and getting him to provide versioned archives.
|
||||
to the software authors and getting them to provide versioned archives.
|
||||
.It Ev MANn
|
||||
List of unformatted manpages, per section.
|
||||
.It Ev MANPREFIX
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: pf.conf.5,v 1.590 2021/12/26 01:00:32 sashan Exp $
|
||||
.\" $OpenBSD: pf.conf.5,v 1.591 2022/02/18 23:17:15 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2002, Daniel Hartmeier
|
||||
.\" Copyright (c) 2003 - 2013 Henning Brauer <henning@openbsd.org>
|
||||
@ -28,7 +28,7 @@
|
||||
.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: December 26 2021 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt PF.CONF 5
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -2536,8 +2536,8 @@ This means that it will not work on other protocols and will not match
|
||||
a currently established connection.
|
||||
.Pp
|
||||
Caveat: operating system fingerprints are occasionally wrong.
|
||||
There are three problems: an attacker can trivially craft his packets to
|
||||
appear as any operating system he chooses;
|
||||
There are three problems: an attacker can trivially craft packets to
|
||||
appear as any operating system;
|
||||
an operating system patch could change the stack behavior and no fingerprints
|
||||
will match it until the database is updated;
|
||||
and multiple operating systems may have the same fingerprint.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: mail.1,v 1.81 2021/03/08 02:47:28 jsg Exp $
|
||||
.\" $OpenBSD: mail.1,v 1.82 2022/02/18 23:17:15 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1990, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
@ -29,7 +29,7 @@
|
||||
.\"
|
||||
.\" @(#)mail.1 8.8 (Berkeley) 4/28/95
|
||||
.\"
|
||||
.Dd $Mdocdate: March 8 2021 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt MAIL 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -456,9 +456,9 @@ On return from the editor, the message is read back in.
|
||||
or
|
||||
.Ic x )
|
||||
Effects an immediate return to the shell without
|
||||
modifying the user's system mailbox, his
|
||||
modifying the user's system mailbox,
|
||||
.Ar mbox
|
||||
file, or his edit file in
|
||||
file, or edit file in
|
||||
.Fl f .
|
||||
.It Ic file
|
||||
.Pq Ic fi
|
||||
@ -581,16 +581,14 @@ and
|
||||
Takes a message list and types out each message on the user's terminal.
|
||||
.It Ic quit
|
||||
.Pq Ic q
|
||||
Terminates the session, saving all undeleted, unsaved messages in
|
||||
the user's
|
||||
Terminates the session, saving all undeleted, unsaved messages in the
|
||||
.Ar mbox
|
||||
file in his login directory, preserving all messages marked with
|
||||
file in the user's login directory, preserving all messages marked with
|
||||
.Ic hold
|
||||
or
|
||||
.Ic preserve
|
||||
or never referenced
|
||||
in his system mailbox, and removing all other messages from his system
|
||||
mailbox.
|
||||
or never referenced in the user's system mailbox,
|
||||
and removing all other messages from the user's system mailbox.
|
||||
If new mail has arrived during the session, the message
|
||||
.Dq Li "You have new mail"
|
||||
is given.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: patch.1,v 1.34 2021/12/21 08:07:20 schwarze Exp $
|
||||
.\" $OpenBSD: patch.1,v 1.35 2022/02/18 23:17:15 jsg Exp $
|
||||
.\" Copyright 1986, Larry Wall
|
||||
.\"
|
||||
.\" Redistribution and use in source and binary forms, with or without
|
||||
@ -19,7 +19,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: December 21 2021 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt PATCH 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -153,7 +153,7 @@ the number of lines of context in the context diff, ordinarily 3.
|
||||
.It Fl f , Fl Fl force
|
||||
Forces
|
||||
.Nm
|
||||
to assume that the user knows exactly what he or she is doing, and to not
|
||||
to assume that the user knows exactly what they are doing, and to not
|
||||
ask any questions.
|
||||
It assumes the following:
|
||||
skip patches for which a file to patch can't be found;
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: sndiod.8,v 1.14 2021/12/25 16:15:53 ratchov Exp $
|
||||
.\" $OpenBSD: sndiod.8,v 1.15 2022/02/18 23:17:16 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2006-2012 Alexandre Ratchov <alex@caoua.org>
|
||||
.\"
|
||||
@ -14,7 +14,7 @@
|
||||
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
|
||||
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
||||
.\"
|
||||
.Dd $Mdocdate: December 25 2021 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt SNDIOD 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -595,4 +595,4 @@ Technically, this allows
|
||||
to attempt to use one of the sub-devices it exposes as an audio device,
|
||||
creating a deadlock.
|
||||
There's nothing to prevent the user
|
||||
from shooting himself in the foot by creating such a deadlock.
|
||||
from shooting themselves in the foot by creating such a deadlock.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: top.1,v 1.79 2021/03/12 05:18:01 jsg Exp $
|
||||
.\" $OpenBSD: top.1,v 1.80 2022/02/18 23:17:16 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1997, Jason Downs. All rights reserved.
|
||||
.\"
|
||||
@ -23,7 +23,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: March 12 2021 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt TOP 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -228,7 +228,7 @@ on an intelligent terminal is, in fact,
|
||||
The environment variable
|
||||
.Ev TOP
|
||||
is examined for options before the command line is scanned.
|
||||
This enables a user to set his or her own defaults.
|
||||
This enables users to set their own defaults.
|
||||
The number of processes to display
|
||||
can also be specified in the environment variable
|
||||
.Ev TOP .
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: adduser.8,v 1.47 2021/12/04 07:31:38 jmc Exp $
|
||||
.\" $OpenBSD: adduser.8,v 1.48 2022/02/18 23:17:16 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1995-1996 Wolfram Schneider <wosch@FreeBSD.org>. Berlin.
|
||||
.\" All rights reserved.
|
||||
@ -25,7 +25,7 @@
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $From: adduser.8,v 1.12 1996/08/28 17:54:13 adam Exp $
|
||||
.Dd $Mdocdate: December 4 2021 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt ADDUSER 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -280,7 +280,7 @@ access to it.
|
||||
.El
|
||||
.\" .Sh UNIQUE GROUP
|
||||
.\" Perhaps you're missing what *can* be done with this scheme that falls apart
|
||||
.\" with most other schemes. With each user in his/her own group the user can
|
||||
.\" with most other schemes. With each user in their own group the user can
|
||||
.\" safely run with a umask of 002 and have files created in their home
|
||||
.\" directory and not worry about others being able to read them.
|
||||
.\"
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: authpf.8,v 1.55 2020/04/05 10:11:07 jmc Exp $
|
||||
.\" $OpenBSD: authpf.8,v 1.56 2022/02/18 23:17:16 jsg Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1998-2007 Bob Beck (beck@openbsd.org>. All rights reserved.
|
||||
.\"
|
||||
@ -14,7 +14,7 @@
|
||||
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
|
||||
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
||||
.\"
|
||||
.Dd $Mdocdate: April 5 2020 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt AUTHPF 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -179,7 +179,7 @@ name instead of "authpf_users".
|
||||
.Sh USER MESSAGES
|
||||
On successful invocation,
|
||||
.Nm
|
||||
displays a message telling the user he or she has been authenticated.
|
||||
displays a message telling the user they have been authenticated.
|
||||
It will additionally display the contents of the file called
|
||||
.Pa authpf.message .
|
||||
This file will first be searched for in
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: lprm.1,v 1.12 2020/04/23 21:28:10 jmc Exp $
|
||||
.\" $OpenBSD: lprm.1,v 1.13 2022/02/18 23:17:16 jsg Exp $
|
||||
.\" $NetBSD: lprm.1,v 1.10 2002/01/19 03:23:47 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1983, 1990, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)lprm.1 8.1 (Berkeley) 6/6/93
|
||||
.\"
|
||||
.Dd $Mdocdate: April 23 2020 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt LPRM 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -133,7 +133,7 @@ daemon and the job number of the currently active job.
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -tag -width Ds
|
||||
.It Sy Permission denied
|
||||
Printed if the user tries to remove files other than his own.
|
||||
File to remove was owned by another user.
|
||||
.El
|
||||
.Sh SEE ALSO
|
||||
.Xr lpq 1 ,
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: mtree.8,v 1.41 2019/09/02 21:18:41 deraadt Exp $
|
||||
.\" $OpenBSD: mtree.8,v 1.42 2022/02/18 23:17:16 jsg Exp $
|
||||
.\" $NetBSD: mtree.8,v 1.4 1995/03/07 21:26:25 cgd Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1989, 1990, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)mtree.8 8.2 (Berkeley) 12/11/93
|
||||
.\"
|
||||
.Dd $Mdocdate: September 2 2019 $
|
||||
.Dd $Mdocdate: February 18 2022 $
|
||||
.Dt MTREE 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -318,7 +318,7 @@ Then, periodically,
|
||||
and
|
||||
.Xr sha256 1
|
||||
should be run against the on-line specifications.
|
||||
While it is possible for the bad guys to change the on-line specifications
|
||||
While it is possible for attackers to change the on-line specifications
|
||||
to conform to their modified binaries, it is believed to be
|
||||
impractical for them to create a modified specification which has
|
||||
the same SHA-256 digest as the original.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user