BSD 3 development

Work on file usr/man/man1/mesg.1
Work on file usr/man/man1/mkdir.1
Work on file usr/man/man4/mem.4

Synthesized-from: 3bsd

diff --git a/usr/man/man1/mesg.1 b/usr/man/man1/mesg.1
new file mode 100644 (file)
index 0000000..66e57ed
--- /dev/null
+++ b/usr/man/man1/mesg.1
@@ -0,0 +1,34 @@
+.TH MESG 1 
+.SH NAME
+mesg \- permit or deny messages
+.SH SYNOPSIS
+.B mesg
+[
+.B n
+] [
+.B y
+]
+.SH DESCRIPTION
+.I Mesg
+with argument
+.B n
+forbids messages via
+.IR  write (1)
+by revoking non-user
+write permission on the user's terminal.
+.I Mesg
+with argument
+.B y
+reinstates permission.
+All by itself,
+.I mesg
+reports the current state without changing it.
+.SH FILES
+/dev/tty*
+.br
+/dev
+.SH "SEE ALSO"
+write(1)
+.SH DIAGNOSTICS
+Exit status is 0 if messages are receivable,
+1 if not, 2 on error.

diff --git a/usr/man/man1/mkdir.1 b/usr/man/man1/mkdir.1
new file mode 100644 (file)
index 0000000..f970b41
--- /dev/null
+++ b/usr/man/man1/mkdir.1
@@ -0,0 +1,25 @@
+.TH MKDIR 1 
+.SH NAME
+mkdir \- make a directory
+.SH SYNOPSIS
+.B mkdir
+dirname ...
+.SH DESCRIPTION
+.I Mkdir
+creates specified directories
+in mode 777.
+Standard entries,
+.RB ` . ',
+for the directory itself,
+and 
+.BR ` .. '
+for its parent, are made automatically.
+.PP
+.I Mkdir
+requires write permission in the parent directory.
+.SH "SEE ALSO"
+rm(1)
+.SH DIAGNOSTICS
+.I Mkdir
+returns exit code 0 if all directories were successfully made.
+Otherwise it prints a diagnostic and returns nonzero.

diff --git a/usr/man/man4/mem.4 b/usr/man/man4/mem.4
new file mode 100644 (file)
index 0000000..ff8b0e7
--- /dev/null
+++ b/usr/man/man4/mem.4
@@ -0,0 +1,40 @@
+.TH MEM 4 
+.SH NAME
+mem, kmem \- main memory
+.SH DESCRIPTION
+.I Mem
+is a special file that is an image of the main memory
+of the computer.
+It may be used, for example, to examine
+(and even to patch) the system.
+.PP
+Byte addresses in
+.I mem
+are interpreted as physical memory addresses.
+References to non-existent locations cause errors to be returned.
+.PP
+Examining and patching device registers is likely
+to lead to unexpected results when read-only or write-only
+bits are present.
+.PP
+The file
+.I kmem
+is the same as 
+.I mem
+except that kernel virtual memory
+rather than physical memory is accessed.
+.PP
+On PDP11's, the I/O page
+begins at location 0160000 of
+.I kmem
+and per-process data for the current process
+begins at 0140000.
+On VAX11's the I/O space begins at physical address 20000000(16)
+and per-process data for the current process is at virtual 80020000(16).
+.SH FILES
+/dev/mem,
+/dev/kmem
+.SH BUGS
+On PDP11's and VAX11's, memory files are accessed one byte
+at a time, an inapproriate method for some
+device registers.