summaryrefslogtreecommitdiff
path: root/lib/libutil/fmt_scaled.3
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2003-06-02 11:37:28 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2003-06-02 11:37:28 +0000
commitffbc2b20d6f53275f7df6b2dcd2b699ee239fefd (patch)
tree18b233451d712295c943998edc6ef758b7ceafd0 /lib/libutil/fmt_scaled.3
parent6f0d19accbba4a1917d5f114b590cbc8adcb0cff (diff)
- section reorder
- clean up .Xr's
Diffstat (limited to 'lib/libutil/fmt_scaled.3')
-rw-r--r--lib/libutil/fmt_scaled.328
1 files changed, 14 insertions, 14 deletions
diff --git a/lib/libutil/fmt_scaled.3 b/lib/libutil/fmt_scaled.3
index 3ca96fe9f54..6a63675d28a 100644
--- a/lib/libutil/fmt_scaled.3
+++ b/lib/libutil/fmt_scaled.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: fmt_scaled.3,v 1.1 2003/05/15 01:26:26 ian Exp $
+.\" $OpenBSD: fmt_scaled.3,v 1.2 2003/06/02 11:37:27 jmc Exp $
.\" Copyright (c) 2001, 2003 Ian Darwin. All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@@ -103,17 +103,6 @@ else
.Sh SEE ALSO
.Xr printf 3 ,
.Xr scanf 3
-.Sh BUGS
-Some of the scale factors have misleading meanings in lower case
-(p for P is incorrect; p should be pico- and P for Peta-).
-However, we bend the SI rules in favor of common sense here.
-A person creating a disk partition of "100m" is unlikely to require
-100 millibytes (i.e., 0.1 byte) of storage in the partition;
-100 megabytes is the only reasonable interpretation.
-.Pp
-Cannot represent the larger scale factors on all architectures.
-.Pp
-Ignores the current locale.
.Sh HISTORY
The functions
.Fn fmt_scaled
@@ -123,10 +112,21 @@ first appeared in
.Ox 3.4 .
.Sh AUTHORS
Ken Stailey wrote the first version of the code that became
-.Xr fmt_scaled 3 ,
+.Fn fmt_scaled ,
originally inside
.Ox
.Xr df 1 .
Ian Darwin excerpted this and made it into a library routine
(with significant help from Paul Janzen), and wrote
-.Xr scan_scaled 3 .
+.Fn scan_scaled .
+.Sh BUGS
+Some of the scale factors have misleading meanings in lower case
+(p for P is incorrect; p should be pico- and P for Peta-).
+However, we bend the SI rules in favor of common sense here.
+A person creating a disk partition of "100m" is unlikely to require
+100 millibytes (i.e., 0.1 byte) of storage in the partition;
+100 megabytes is the only reasonable interpretation.
+.Pp
+Cannot represent the larger scale factors on all architectures.
+.Pp
+Ignores the current locale.