From 772c53a1b079cc66365707622866d045715beeb6 Mon Sep 17 00:00:00 2001
From: Ingo Schwarze <schwarze@cvs.openbsd.org>
Date: Thu, 29 Dec 2022 14:56:49 +0000
Subject: HISTORY: clarify that unmount(2) used to be called umount(2) from v1
 to Tahoe; joint work with and OK jsg@

---
 lib/libc/sys/mount.2 | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/lib/libc/sys/mount.2 b/lib/libc/sys/mount.2
index 9d448571a67..1dea9935cc9 100644
--- a/lib/libc/sys/mount.2
+++ b/lib/libc/sys/mount.2
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mount.2,v 1.50 2021/01/03 18:10:27 rob Exp $
+.\"	$OpenBSD: mount.2,v 1.51 2022/12/29 14:56:48 schwarze Exp $
 .\"	$NetBSD: mount.2,v 1.12 1996/02/29 23:47:48 jtc Exp $
 .\"
 .\" Copyright (c) 1980, 1989, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)mount.2	8.2 (Berkeley) 12/11/93
 .\"
-.Dd $Mdocdate: January 3 2021 $
+.Dd $Mdocdate: December 29 2022 $
 .Dt MOUNT 2
 .Os
 .Sh NAME
@@ -404,9 +404,15 @@ points outside the process's allocated address space.
 The
 .Fn mount
 and
-.Fn unmount
+.Fn umount
 system calls first appeared in
-.At v1 .
+.At v1 ;
+.Fn umount
+was renamed to
+.Fn unmount
+in
+.Bx 4.3 Reno .
+.Pp
 The
 .Fa flags
 argument is supported by
-- 
cgit v1.2.3