Subject: misc/19678: NetBSD on-line manual should be consistent with RFC1060
To: None <>
From: None <>
List: netbsd-bugs
Date: 01/04/2003 08:46:57
>Number:         19678
>Category:       misc
>Synopsis:       NetBSD on-line manual should be consistent with RFC1060
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 04 08:47:00 PST 2003
>Originator:     Igor Sobrado
>Release:        1.6
University of Oviedo
NetBSD ns1.localnet 1.6 NetBSD 1.6 (GENERIC) #0: Sun Sep  8 19:43:40 UTC 2002 i386

The Internet Engineering Task Force (IETF) RFC1060 has some
recommendations about naming machines and operating system.
Those naming conventions can make NetBSD on-line manual more
consistent [*] [**]:

  mkstr(1)         - PDP 11 family (PDP-11 family)
  sail(6)          - PDP 11/70 (PDP-11/70)
  gcc(1)           - Vax (VAX, in four lines)
  gunzip(1)        - Vax/VMS (VAX/VMS)
  objdump(1)       - Vax (VAX)
  RMD160Data(3)    - vax (VAX)
  SHA1Data(3)      - vax (VAX)
  options(4)       - vax (VAX), Ultrix (ULTRIX), Mips (MIPS),
                     alpha (Alpha)
  hier(7)          - Vax (VAX), Ultrix (ULTRIX), Mips (MIPS)
  compat_ultrix(8) - vax (VAX), Vax (VAX), Ultrix (ULTRIX),
                     mips (MIPS), alpha (Alpha)
  disklabel(8)     - vax (VAX)
  installboot(8)   - vax (VAX, for example in NetBSD/VAX),
  bba(4)           - Ultrix (ULTRIX)
  bpf(4)           - Ultrix (ULTRIX)
  scc(4)           - Ultrix (ULTRIX)
  pppd(8)          - Ultrix (ULTRIX)
  tcpdump(8)       - Ultrix (ULTRIX)
  traceroute(8)    - Ultrix (ULTRIX), HPUX (HP-UX)
  cpio(1)          - HPUX (HP-UX), hpux (HP-UX)
  bad144(8)        - dec (DEC)
  pckbd(4)         - alpha (Alpha)
  wsdisplay(4)     - alpha (Alpha)
  compat_osf1(8)   - alpha (Alpha)

 [*] except when applied to labels or command-line arguments,
of course!

[**] I prefer avoiding references to Unix vs. UNIX by now.
"UNIX" is the word commonly accepted and the first used; it
appears, for example, in the next article:

  Dennis M. Ritchie, Ken Thompson.  The UNIX Time-Sharing System
  CACM, 17(7):365-375

But Dennis M. Ritchie observed that he personally likes "Unix",
because this word is not an acronymic.  Any suggestion?
Reading the IETF RFCs 1010 and 1060, the NetBSD on-line documentation,
and the documentation provided by the developers.  All those words
were matched with the documentation of the developers.
Patching the NetBSD man pages.  These changes only applies to
the vendors and operating systems, not to the options provided
to utilities or stored in configuration files.