Date: Mon, 16 Jul 2001 13:52:49 -0700 (PDT) From: Chern Lee <chern@meow.osd.bsdi.com> To: <freebsd-doc@freebsd.org> Subject: UNIX vs Unix Message-ID: <Pine.BSF.4.31.0107161348180.71896-200000@meow.osd.bsdi.com>
index | next in thread | raw e-mail
[-- Attachment #1 --]
According to O'Reilly's word list:
Unix (UNIX in many books, esp. older ones)
UNIX appears about 10 to 1 to Unix in the handbook. At first, I resorted
to changing all instances of Unix to UNIX to make our document more
standard, but then realized Unix looks a lot more aesthetically pleasing.
According to O'Reilly, are we a new document or an old book?
Attached is a patch changing all relevant instances of Unix -> UNIX.
I'd like it the other way around.
Ideas?
- chern
[-- Attachment #2 --]
Index: advanced-networking/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v
retrieving revision 1.56
diff -u -r1.56 chapter.sgml
--- advanced-networking/chapter.sgml 2001/07/14 23:40:27 1.56
+++ advanced-networking/chapter.sgml 2001/07/16 20:46:14
@@ -1434,7 +1434,7 @@
<indexterm><primary>NetBSD</primary></indexterm>
<indexterm><primary>OpenBSD</primary></indexterm>
<para>NIS, which stands for Network Information Services, was
- developed by Sun Microsystems to centralize administration of Unix
+ developed by Sun Microsystems to centralize administration of UNIX
(originally SunOS) systems. It has now essentially become an
industry standard; all major Unices (Solaris, HP-UX, AIX, Linux,
NetBSD, OpenBSD, FreeBSD, etc) support NIS.</para>
@@ -3519,13 +3519,13 @@
<filename>sandbox/var/run</filename></para>
</listitem>
<listitem>
- <para>The Unix socket used for communication by the &man.ndc.8;
+ <para>The UNIX socket used for communication by the &man.ndc.8;
utility will be created in
<filename>sandbox/var/run</filename></para>
</listitem>
<listitem>
<para>When using the ndc utility you need to specify the
- location of the Unix socket created in the sandbox, by
+ location of the UNIX socket created in the sandbox, by
&man.named.8;, by using the -c switch:
<command>&prompt.root; ndc -c /etc/namedb/sandbox/var/run/ndc</command>
</para>
Index: backups/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v
retrieving revision 1.34
diff -u -r1.34 chapter.sgml
--- backups/chapter.sgml 2001/06/26 20:10:23 1.34
+++ backups/chapter.sgml 2001/07/16 20:46:14
@@ -249,7 +249,7 @@
<indexterm><primary>dump</primary></indexterm>
<indexterm><primary>restore</primary></indexterm>
- <para>&man.dump.8; and &man.restore.8; are the traditional Unix backup
+ <para>&man.dump.8; and &man.restore.8; are the traditional UNIX backup
programs. They operate on the drive as a collection of disk blocks,
below the abstractions of files, links and directories that are
created by the filesystems. &man.dump.8; backs up devices, entire
@@ -316,7 +316,7 @@
<secondary>cpio</secondary>
</indexterm>
- <para>&man.cpio.1; is the original Unix file interchange tape program
+ <para>&man.cpio.1; is the original UNIX file interchange tape program
for magnetic media. &man.cpio.1; has options (among many others) to
perform byte-swapping, write a number of different archives format,
and pipe the data to other programs. This last feature makes
@@ -401,7 +401,7 @@
<para>If your time and your data is worth little to nothing, then
<quote>Do nothing</quote> is the most suitable backup program for your
- computer. But beware, Unix is a useful tool, you may find that within
+ computer. But beware, UNIX is a useful tool, you may find that within
six months you have a collection of files that are valuable to
you.</para>
@@ -420,7 +420,7 @@
<para>&man.dump.8; <emphasis>Period.</emphasis> Elizabeth D. Zwicky
torture tested all the backup programs discussed here. The clear
- choice for preserving all your data and all the peculiarities of Unix
+ choice for preserving all your data and all the peculiarities of UNIX
filesystems is &man.dump.8;. Elizabeth created filesystems containing
a large variety of unusual conditions (and some not so unusual ones)
and tested each program by doing a backup and restore of that
Index: basics/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v
retrieving revision 1.27
diff -u -r1.27 chapter.sgml
--- basics/chapter.sgml 2001/07/13 21:22:49 1.27
+++ basics/chapter.sgml 2001/07/16 20:46:14
@@ -5,7 +5,7 @@
-->
<chapter id="basics">
- <title>Unix Basics</title>
+ <title>UNIX Basics</title>
<sect1>
<title>Synopsis</title>
Index: eresources/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v
retrieving revision 1.59
diff -u -r1.59 chapter.sgml
--- eresources/chapter.sgml 2001/07/08 01:13:22 1.59
+++ eresources/chapter.sgml 2001/07/16 20:46:14
@@ -1101,7 +1101,7 @@
</sect2>
<sect2>
- <title>Other Unix Newsgroups of Interest</title>
+ <title>Other UNIX Newsgroups of Interest</title>
<itemizedlist>
<listitem>
Index: install/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v
retrieving revision 1.73
diff -u -r1.73 chapter.sgml
--- install/chapter.sgml 2001/07/14 23:40:28 1.73
+++ install/chapter.sgml 2001/07/16 20:46:14
@@ -170,7 +170,7 @@
the <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename>tools</filename>; directory</ulink> on the FreeBSD FTP site.</para>
- <para>If you are writing the floppies on a Unix system (such as
+ <para>If you are writing the floppies on a UNIX system (such as
another FreeBSD system) you can use the &man.dd.1; command to
write the image files directly to disk. On FreeBSD you would
run:</para>
@@ -180,7 +180,7 @@
<para>On FreeBSD <filename>/dev/fd0</filename> refers to the
first floppy disk (the <devicename>A:</devicename> drive).
<filename>/dev/rfd1</filename> would be the
- <devicename>B:</devicename> drive, and so on. Other Unix
+ <devicename>B:</devicename> drive, and so on. Other UNIX
variants might have different names for the floppy disk
devices, and you will need to check the documentation for the
system as necessary.</para>
@@ -1934,7 +1934,7 @@
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename>tools</filename>;
directory</ulink> on the FreeBSD FTP site.</para>
- <para>If you are writing the floppies on a Unix system (such
+ <para>If you are writing the floppies on a UNIX system (such
as another FreeBSD system) you can use the &man.dd.1;
command to write the image files directly to disk. On
FreeBSD you would run:</para>
@@ -1944,7 +1944,7 @@
<para>On FreeBSD <filename>/dev/fd0</filename> refers to
the first floppy disk (the <devicename>A:</devicename>
drive). <filename>/dev/rfd1</filename> would be the
- <devicename>B:</devicename> drive, and so on. Other Unix
+ <devicename>B:</devicename> drive, and so on. Other UNIX
variants might have different names for the floppy disk
devices, and you will need to check the documentation for
the system as necessary.</para>
Index: introduction/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v
retrieving revision 1.45
diff -u -r1.45 chapter.sgml
--- introduction/chapter.sgml 2001/07/15 00:28:40 1.45
+++ introduction/chapter.sgml 2001/07/16 20:46:14
@@ -196,7 +196,7 @@
<para>Thousands of additional and
<emphasis>easy-to-port</emphasis> applications are available
on the Internet. FreeBSD is source code compatible with most
- popular commercial Unix systems and thus most applications
+ popular commercial UNIX systems and thus most applications
require few, if any, changes to compile.</para>
</listitem>
Index: ports/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v
retrieving revision 1.124
diff -u -r1.124 chapter.sgml
--- ports/chapter.sgml 2001/07/16 15:12:18 1.124
+++ ports/chapter.sgml 2001/07/16 20:46:14
@@ -17,7 +17,7 @@
software—perhaps a web server, or a mail reader, or a graphical
environment such as KDE or GNOME.</para>
- <para>If you have used a Unix system before you will know that the typical
+ <para>If you have used a UNIX system before you will know that the typical
procedure for installing third party software goes something like
this:</para>
Index: ppp-and-slip/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v
retrieving revision 1.37
diff -u -r1.37 chapter.sgml
--- ppp-and-slip/chapter.sgml 2001/06/25 22:05:25 1.37
+++ ppp-and-slip/chapter.sgml 2001/07/16 20:46:15
@@ -75,7 +75,7 @@
<indexterm><primary>PAP</primary></indexterm>
<indexterm><primary>CHAP</primary></indexterm>
- <indexterm><primary>Unix</primary></indexterm>
+ <indexterm><primary>UNIX</primary></indexterm>
<indexterm><primary>login name</primary></indexterm>
<indexterm><primary>password</primary></indexterm>
<listitem>
Index: serialcomms/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v
retrieving revision 1.29
diff -u -r1.29 chapter.sgml
--- serialcomms/chapter.sgml 2001/07/14 23:40:28 1.29
+++ serialcomms/chapter.sgml 2001/07/16 20:46:15
@@ -79,7 +79,7 @@
<sect2 id="term-uses">
<title>Uses and Types of Terminals</title>
- <para>The original Unix systems did not have consoles. Instead, people
+ <para>The original UNIX systems did not have consoles. Instead, people
logged in and ran programs through terminals that were connected to
the computer's serial ports. It is quite similar to using a modem and
some terminal software to dial into a remote system to do text-only
@@ -87,7 +87,7 @@
<para>Today's PCs have consoles capable of high quality graphics, but
the ability to establish a login session on a serial port still exists
- in nearly every Unix-style operating system today; FreeBSD is no
+ in nearly every UNIX-style operating system today; FreeBSD is no
exception. By using a terminal attached to a unused serial port, you
can log in and run any text program that you would normally run on the
console or in an <command>xterm</command> window in the X Window
Index: users/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v
retrieving revision 1.12
diff -u -r1.12 chapter.sgml
--- users/chapter.sgml 2001/07/08 22:53:33 1.12
+++ users/chapter.sgml 2001/07/16 20:46:15
@@ -631,7 +631,7 @@
<title>Groups</title>
<para>A group is simply a list of users. Groups are identified by
- their group name and gid (group ID). In FreeBSD (and most other Unix
+ their group name and gid (group ID). In FreeBSD (and most other UNIX
systems), the two factors the kernel uses to decide whether a process
is allowed to do something is its user ID and list of groups it
belongs to. Unlike a user ID, a process has a list of groups
Index: x11/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v
retrieving revision 1.29
diff -u -r1.29 chapter.sgml
--- x11/chapter.sgml 2001/07/14 23:40:29 1.29
+++ x11/chapter.sgml 2001/07/16 20:46:16
@@ -1616,7 +1616,7 @@
(e.g. <filename>/usr/X11R6/lib/X11/fonts/TrueType</filename>)
and copy all of your TrueType fonts into this directory. Keep in
mind that you can not take TrueType fonts directly from a
- Macintosh; they must be in Unix/DOS/Windows format for use by
+ Macintosh; they must be in UNIX/DOS/Windows format for use by
<application>XFree86</application>. Once you have copied the
files into this directory you need to use
<application>ttmkfdir</application> to create a
@@ -2048,7 +2048,7 @@
presentation application, an organizer, a news client and
more. KDE is also comes with a web browser called Konqeuror,
which represents already a solid competitor to other
- existing web browsers on Unix systems. More information on
+ existing web browsers on UNIX systems. More information on
KDE can be found on the <ulink url="http://www.kde.org">KDE
website</ulink></para>
</sect3>
@@ -2222,7 +2222,7 @@
much more lightweight and meant for those who want a simple,
efficient desktop which is nevertheless easy to use and
configure. Visually, it looks very much like CDE, found on
- commercial Unix systems.
+ commercial UNIX systems.
Some of XFCE's features are:</para>
<itemizedlist>
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.31.0107161348180.71896-200000>