src/lib/libc/sys/mknod.2, branch release/4.1.0_cvs

This commit was manufactured by cvs2svn to create tag

2000-07-26T21:12:35+00:00

'RELENG_4_1_0_RELEASE'.

This commit was manufactured to restore the state of the 4.1-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

MFC: introduce .Lb macro to libc manpages

2000-04-22T17:07:11+00:00

$Id$ -> $FreeBSD$

1999-08-28T00:22:10+00:00

Remove a 4.3BSDish anachronism that claimed EPERM for an attempt to

1999-08-27T14:25:00+00:00

mknod() a pathname containg a ``character with the high-order bit
set''.

Add $Id$, to make it simpler for members of the translation teams to

1999-07-12T20:50:10+00:00

track.

The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;

     .\"    $Id$
     .\"

If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.

Approved by:            bde

Mention that you can only create a block or char special file using

1999-04-28T10:04:48+00:00

mknod(2).

Correct the most glaring errors. I have a feeling there are some

1997-04-02T01:42:07+00:00

left.

I was porting something from sysV world and found our cross references

1997-01-27T19:20:05+00:00

not quite as good as I would expect.  So I'm introducing mknod to mkfifo,
and vice-versa.

Remove the EINVAL error from the ERRORS sections that

1997-01-11T23:56:32+00:00

say is means that a pathname had the high-order bit
set, since this is no longer an error.

Correctly use .Fn instead of .Nm to reference function names

1996-08-22T23:31:07+00:00

in a bunch of man pages.

Use the correct .Bx  (BSD UNIX) or .At (AT&T UNIX) macros
instead of explicitly specifying the version in the text
in a bunch of man pages.