Usenet 1994 October/usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso/std_unix/volume.14

Internet Message Format | 1989-01-07 | 268KB

From uucp  Sun Apr 17 16:12:37 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA10780; Sun, 17 Apr 88 16:12:37 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: comp.std.unix Volume 14
Message-Id: <[e-mail]>
Expires: 15 May 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 17 Apr 88 19:53:40 GMT
Apparently-To: std-unix-archive
Status: RO

This is the first article in Volume 14 of comp.std.unix.
These volumes are purely for administrative convenience.
Feel free to continue any previous discussion or start new ones.

The USENET newsgroup comp.std.unix is also known as the ARPA Internet
mailing list [e-mail].  It is for discussions of UNIX
standards, particularly of IEEE 1003, or POSIX.  The moderator is
John S. Quarterman, who is also the institutional representative of
the USENIX Association to the IEEE P1003 Portable Operating System
Interface for Computer Environments Committee (commonly known as
the UNIX Standards Committee).

Submissions-To:    uunet!std-unix        or [e-mail]
Comments-To: uunet!std-unix-request    or [e-mail]
Postings from the moderator may also originate from longway.tic.com.

Permission to post to the newsgroup is assumed for mail to std-unix.
Permission to post is not assumed for mail to std-unix-request,
unless explicitly granted in the mail.  Mail to my personal addresses
will be treated like mail to std-unix-request if it obviously refers
to the newsgroup.

Archives may be found on uunet.uu.net.  The current volume may
be retrieved by anonymous ftp (login anonymous, password guest)
over the ARPA Internet as
    ~ftp/comp.std.unix/archive
or
    ~ftp/comp.std.unix/volume.14
The previous volume may be retrieved as
    ~ftp/comp.std.unix/volume.13
For hosts with direct UUCP connections to the uunet machine,
UUCP transfer should work with, for example,
    uucp uunet!comp.std.unix/archive archive

Volumes 1-10 are filed under the former newsgroup name, mod.std.unix,
as ~ftp/pub/mod.std.unix.v1, ~ftp/pub/mod.std.unix.v2, etc., through
~ftp/pub/mod.std.unix.v10.  Volume 3 contains the AT&T public domain
getopt(3).  Volume 10 is a special index volume that catalogs Volumes 1-9.

These volumes are strictly for administrative convenience.
Several members of the committee follow the newsgroup on-line.

Finally, remember that any remarks by any committee member (especially
including me) in this newsgroup do not represent any position (including
any draft, proposed or actual, of a standard) of the committee as a
whole or of any subcommittee unless explicitly stated otherwise
in such remarks.

UNIX is a Registered Trademark of AT&T.
IEEE is a Trademark of the Institute of Electrical and Electronics
    Engineers, Inc.

Volume-Number: Volume 14, Number 1

From uucp  Sun Apr 17 16:13:39 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA10817; Sun, 17 Apr 88 16:13:39 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Access to UNIX-Related Standards
Message-Id: <[e-mail]>
Expires: 15 May 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 17 Apr 88 19:59:33 GMT
Apparently-To: std-unix-archive
Status: RO

This is the latest in a series of similar comp.std.unix articles.
Corrections and additions to this article are solicited.

There are two companion articles, posted at the same time as this one
and with subjects ``Access to UNIX User Groups and Publications'' and
``Calendar of UNIX-related Events.''

Also note that Shane McCarron now writes a quarterly summary report for
USENIX soon after each IEEE 1003 meeting for posting in comp.std.unix
and in ;login:, the Newsletter of the USENIX Association.

Changes from last posting:
The July IEEE 1003 meeting has moved to Denver from Colorado Springs,
and the June 1989 Monterey meeting is now the July 1989 San Francisco one.
The later meetings have sprouted tentative dates and a new one in Montreal.
The October 1988 ISO SC22 and WG15 meetings have changed dates (again).

Access information is given in this article for the following standards:
IEEE 1003.1 (operating system interface), 1003.2 (shell and tools),
    1003.3 (testing and verification), 1003.4 (real time),
    1003.5 (ADA binding), 1003.6 (security), 1003.0 (POSIX guide).
NBS FIPS.
/usr/group Technical Committee Subcommittees on distributed file system,
    network interface, graphics/windows, database, internationalization,
    performance measurements, realtime, security, and super computing.
X3H3.6 (display committee)
X3J11 (C language)
/usr/group 1984 Standard
System V Interface Definition (SVID, or The Purple Book)
X/OPEN PORTABILITY GUIDE (The Green Book)
4.3BSD Manuals


UNIX is a Registered Trademark of AT&T.
IEEE is a trademark of the Institute of Electrical and Electronic Engineers,
    Inc.:  POSIX is no longer a trademark.
X/OPEN is a licensed trademark of the X/OPEN Group Members.


The IEEE P1003 Portable Operating System Interface for Computer
Environments Committee is sometimes known colloquially as the UNIX
Standards Committee.  They published the 1003.1 "POSIX" Trial Use
Standard in April 1986.  According to its Foreword:

    The purpose of this document is to define a standard
    operating system interface and environment based on the
    UNIX Operating System documentation to support application
    portability at the source level.  This is intended for
    systems implementors and applications software developers.

Published copies are available at $19.95, with bulk purchasing discounts
available.  Call the IEEE Computer Society in Los Angeles

        714-821-8380

and ask for Book #967.  Unfortunately, this only works for multiple copies.
But the following mail address works for single copies:

        IEEE Computer Society
        P.O. Box 80452
        Worldway Postal Center
        Los Angeles, Ca. 90080

Include a check for $19.95 + $4 for shipping and handling.  For UPS
shipping, add another $4.  Or contact:

        IEEE Service Center
        445 Hoes Ln.
        Piscataway, NJ 08854

and ask for "IEEE 1003.1 Trial Use Standard" - stock number SH10546.

The Trial Use Standard will be available for comments for a period such
as a year.  The current target for a Full Use Standard is Summer 1988.
Initial balloting is completed, and ballot resolution is in progress:
it's too late to ballot if you haven't already.


IEEE has brought the 1003.1 effort brought into the International
Organization for Standardization (ISO) arena.  IEEE 1003.1 Draft 12
is also a ``Draft Proposed International Standard (ISO DP)'' under
SC22 WG15.  The convenor is Jim Isaak:  see below for his address.
There is a U.S. Technical Advisory Group (TAG) to ISO SC22 WG15:
the chair is Donn Terry of HP.

The National Bureau of Standards is producing a Federal Information
Processing Standard (FIPS) based on IEEE 1003.1.  It will probably
be available before the Full Use Standard, and may reflect Draft 12,
rather than the final 1003.1 standard.  For information, contact:

        Roger Martin
        National Bureau of Standards
        Building 225
        Room B266
        Gaithersburg, MD  20899
        [phone]

NBS is also producing a FIPS based on IEEE 1003.2, probably from
the draft made by 1003.2 at their March meeting.


Machine readable copies of the IEEE 1003.1 Trial Use Standard are not
and will not be available.  The same applies to copies of later drafts.

There is a paper mailing list by which interested parties may get
copies of drafts of the standard.  To get on it, or to submit comments
directly to the committee, mail to:

        James Isaak
        Chairperson, IEEE/CS P1003
        Tel.: [phone]
        Fax.: [phone]
        decvax!isaak
        [e-mail]
        Digital Equipment
        ZK03-3/Y25
        110 Spit Brook Rd.
        Nashua, NH  03062-2698

Sufficiently interested parties may join the working group.

The term POSIX actually applies to all of the P1003 subcommittees:
group    subject                co-chairs
1003.0    POSIX Guide            Al Hankinson (NBS), Kevin Lewis (DEC)
1003.1    Systems Interface        Jim Isaak (DEC), Donn Terry (HP)
1003.2    Shell and Tools Interface    Hal Jespersen (UniSoft), Don Cragun (Sun)
1003.3    Verification and Testing     Roger Martin (NBS), Carol Raye (AT&T)
1003.4    Real Time             Bill Corwin (Intel)
1003.5    Ada Binding for POSIX        Terry Fong (USArmy), Stowe Boyd(Compass)
1003.6    Security            Dennis Steinauer (NBS), Ron Elliot (IBM)

Inquiries regarding any of the subcommittees should go to the same address
as for 1003.1.


The next scheduled meetings of the P1003 working groups are:

1988 June 20-24        IEEE 1003.6 at USENIX, in San Francisco, CA
1988 July 11-15        Tech Center Hyatt, Denver, CO
1988 October 17-19,20-21 ISO SC22 Advisory Group & WG15 - Tokyo, Japan
1988 October 24-28    Hawaii

1989 January 9-13    Embassy Suites, Ft. Lauderdale, FL
1989 April 17(29?)    Minneapolis-St. Paul, MN
1989 July 10-14        San Francisco, CA
1989 October 16-20    Brussels (or Amsterdam) (Thought: EC host)

1990 January 29        New Orleans, LA
1990 April        Montreal, Quebec

Here are some details from Hal Jespersen regarding P1003.2:

The IEEE P1003.2 "Shell and Utilities" Working Group is developing a
proposed standard to complement the 1003.1 POSIX standard.  It will
consist of

    a shell command language (currently planned to be based on the
    Bourne Shell),

    groups of utility programs, or commands,

    programmatic interfaces to the shell (system(), popen()) and
    related facilities (regular expressions, file name expansion,
    etc.)

    defined environments (variables, file hierarchies, etc) that
    applications may rely upon

    utilities for installing application programs onto conforming
    systems

which will allow application programs to be developed out of existing
pieces, in the UNIX tradition.  The scope of the standard emphasizes
commands and features that are more typically used by shell scripts or
C language programs than those that are oriented to the terminal user
with windows, mice, visual shells, and so forth.

There has been some controversy in the Working Group about clarifying
the scope of the 1003.2 standard in regard to its relationship with
1003.1.  The Working Group is attempting to produce a standard that
will assume the structure and philosophy of a POSIX system is
available, but it will not require a fully conforming implementation as
a base.  For example, it should be feasible to eventually produce a
1003.2 interface on a V7 system, or on a system very close to POSIX,
but missing a few crucial features (as long as the shell and utilities
didn't need them).  However, the proposed standard will *not* be
unnecessarily watered down simply to allow non-POSIX systems to conform.

The group is currently seeking proposals for groupings of commands that
may be offered by implementors.  As groups are identified, command
descriptions will be solicited.  There is no requirement that the commands
be in System V or BSD today, but they should realistically be commands
that are commonly found in most existing implementations.


There are three Institutional Representatives to P1003:  John Quarterman
from USENIX, Heinz Lycklama from /usr/group, and Mike Lambert from X/OPEN.
The two from USENIX and /usr/group are also representatives to the U.S.
TAG to ISO SC22 WG15.

As the one from USENIX, one of my functions is to get comments from the
USENIX membership and the general public to the committee.  One of the
ways I try to do that is by moderating this newsgroup, comp.std.unix
An article related to this one appeared in the September/October 1986
;login: (The USENIX Association Newsletter).  I'm also currently on the
USENIX Board of Directors.  Comments, suggestions, etc., may be sent to

        John S. Quarterman
        Texas Internet Consulting
        701 Brazos, Suite 500
        Austin TX 78701-3243
        [phone]
        uunet!usenix!jsq
        [e-mail]

For comp.std.unix:
Comments:    uunet!std-unix-request [e-mail]
Submissions:    uunet!std-unix        [e-mail]

The November/December 1987 issue of CommUNIXations (the /usr/group magazine)
contains a report by Heinz Lycklama on the /usr/group Technical Committee
working groups which met in June 1987.

If you are interested in starting another /usr/group working group, contact
Heinz Lycklama:

        Heinz Lycklama
        Interactive Systems Corp.
        2401 Colorado Ave., 3rd Floor
        Santa Monica, CA 90404
        [phone]
        decvax!cca!ima!heinz


Here is contact information for /usr/group working groups as taken from
the CommUNIXations article mentioned above.

/usr/group Working Group on Distributed File System:
    Art Sabsevitz            Frederick Glover
    AT&T Information Systems    MK02-1/H10
    190 River Road            Digital Equipment Corporation
    Summit, NJ  07933        Continental Boulevard
    201-522-6248            Merrimack, NH  03054-0430
    attunix!bump            603-884-5111
                    decvax!fglover

/usr/group Working Group on Network Interface:
    Steve Albert
    AT&T Information Systems
    190 River Road, Rm. A-114
    Summit, NJ  07901
    [phone]
    attunix!ssa

/usr/group Working Group on Internationalization:
    John Wu                Laurie Goudie
    Charles River Data Systems    Santa Cruz Operation
    983 Concord St.,        400 Encinal
    Framingham, MA 01701        Santa Cruz, CA 95060
    617-626-1000            408-458-1422

/usr/group Working Group on Graphics/Windows:
    Tom Greene
    Apollo Computer, Inc.
    330 Billerica Road
    Chelmsford, MA  01824
    [phone], ext. 7581

/usr/group Working Group on Realtime:
    Bill Corwin
    Intel Corp.
    5200 Elam Young Pkwy
    Hillsboro, OR 97123
    [phone]

/usr/group Working Group on Database:
    Val Skalabrin
    Unify Corp.
    1111 Howe Ave.
    Sacramento, CA 95825
    [phone]


/usr/group Working Group on Performance Measurements:
    Ram Chelluri            Dave Hinnant
    AT&T Computer Systems        SCI Systems, Inc.
    Room E15B            Ste 325, Pamlico Bldg
    4513 Western Ave.        Research Triangle Pk, NC 27709
    Lisle, IL 60532            [phone]
    [phone]

/usr/group Working Group on Security:
    Steve Sutton            Ms. Jeanne Baccash
    Consultant, Addamax        AT&T UNIX Systems Engineering
    1107 S. Orchard            190 River Road
    Urbana, IL  61801        Summit, NJ  07901
    217-344-0996            201-522-6028
                    attunix!jeanne

/usr/group Working Group on Super Computing:
    Karen Sheaffer            Robin O'Neill
    Sandia National Laboratory    Lawrence Livermore Laboratory
    P.O. Box 969            P.O. Box 5509, L560
    Livermore, CA  94550        Livermore, CA  94550
    415-422-3431            415-422-0973
                    oneill#[e-mail]


The X3H3.6 display management committee has recently formed to develop
a model to support current and future window management systems, yet
is not based directly on any existing system.  The chair solicits
help and participation:

        Georges Grinstein
        wanginst!ulowell!grinstein


The Abstract of the 1003.1 Trial Use Standard adds:

    This interface is a complement to the C Programming Language
    in the C Information Bulletin prepared by Technical Committee X3J11
    of the Accredited Standards Committee X3, Information Processing
    Systems, further specifying an environment for portable application
    software.

X3J11 is sometimes known as the C Standards Committee.  Their liaison to
P1003 is

        Don Kretsch
        AT&T
        190 River Road
        Summit, NJ 07901

A contact for information regarding publications and working groups is

        Thomas Plum
        Vice Chair, X3J11 Committee
        Plum Hall Inc.
        1 Spruce Avenue
        Cardiff, New Jersey 08232

The current document may be ordered from

        Global Engineering Documents
        2805 McGaw
        Irvine, CA 92714
        USA
        [phone]
        [phone]

Ask for the X3.159 draft standard.  The price is $65.


The /usr/group Standard is a principal ancestor of P1003.1, X/OPEN,
and X3J11.  It may be ordered for $15.00 from:

        /usr/group Standards Committee
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        Tel: [phone]
        Fax: [phone]

/usr/group also publishes an eight page document, ``Your Guide to POSIX,''
explaining what IEEE 1003 is, and a nineteen page document, ``POSIX Explored,''
about technical aspects of IEEE 1003.1, and its relations to other standards
and historical implementations.  Contact /usr/group at the above address
for details.


The System V Interface Definition (The Purple Book, or SVID).
This is the AT&T standard and is one of the most frequently-used
references of the IEEE 1003 committee.

        AT&T Customer Information Center
        Attn:  Customer Service Representative
        P.O. Box 19901
        Indianapolis, IN 46219
        U.S.A.

        800-432-6600 (Inside U.S.A.)
        800-255-1242 (Inside Canada)
        317-352-8557 (Outside U.S.A. and Canada)

    System V Interface Definition, Issue 2
    should be ordered by the following select codes:

    Select Code:    Volume:        Topics:
    320-011        Volume I    Base System
                    Kernel Extension
    320-012        Volume II    Basic Utilities Extension
                    Advanced Utilities Extension
                    Software Development Extension
                    Administered System Extension
                    Terminal Volume Interface Extension
    320-013        Volume III    Base System Addendum
                    Terminal Interface Extension
                    Network Services Extension
    307-131        I, II, III    (all three volumes)

The price is about 37 U.S. dollars for each volume or $84 for all three.
Major credit cards are accepted for telephone orders:  mail orders
should include a check or money order, payable to AT&T.


The X/OPEN PORTABILITY GUIDE (The Green Book)
is another reference frequently used by IEEE 1003.

The X/OPEN Group is "Ten of the world's major information system
suppliers" (at time of publication, Bull, DEC, Ericsson, Hewlett-Packard,
ICL, NIXDORF, Olivetti, Philips, Siemens and Unisys and subsequently
augmented by AT&T) who have produced a document intended to promote
the writing of portable applications.  They closely follow both SVID
and POSIX, and cite the /usr/group standard as contributing, but
X/OPEN's books cover a wider area than any of those.

The book is published by

        Elsevier Science Publishers B.V.
        Book Order Department
        P.O. Box 1991
        1000 BZ Amsterdam
        The Netherlands

and distributed in the U.S.A. and Canada by:

        Elsevier Science Publishing Company, Inc.
        52 Vanderbilt Avenue
        New York, NY 10017
        U.S.A.

There are currently five volumes:
    1) System V Specification Commands and Utilities
    2) System V Specification System Calls and Libraries
    3) System V Specification Supplementary Definitions
    4) Programming Languages
    5) Data Management

They take a large number of credit cards and other forms of payment.

Comments, suggestions, error reports, etc., for Issue 2 of the Green Book
may be mailed directly to:

        [e-mail]
        uunet!mcvax!inset!xopen!xpg2

Information about X/OPEN can be requested from:

        Mike Lambert
        Technical Director
        X/OPEN Ltd
        c/o ICL BRA01
        Lovelace Road
        Bracknell
        Berkshire
        England
        [phone]
        [e-mail]
        uunet!mcvax!inset!xopen!mgl


Finally, 4.2BSD and 4.3BSD have influenced POSIX in a number of areas.
The best reference on them is the 4.3BSD manuals, published by USENIX.
An order form may be obtained from:

        Howard Press
        c/o USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710

        415-528-8649
        {ucbvax,decvax}!usenix!office

4.3BSD User's Manual Set (3 volumes)        $25.00
    User's Reference Manual
    User's Supplementary Documents
    Master Index

4.3BSD Programmer's Manual Set (3 volumes)    $25.00
    Programmer's Reference Maual
    Programmer's Supplementary Documents, Volume 1
    Programmer's Supplementary Documents, Volume 2

4.3BSD System Manager's Manual (1 volume)    $10.00

Unfortunately, there are some license restrictions.
Contact the USENIX office for details.

Volume-Number: Volume 14, Number 2

From uucp  Sun Apr 17 16:15:01 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA10843; Sun, 17 Apr 88 16:15:01 EDT
From: <[e-mail]>
Newsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
Subject: Access to UNIX User Groups and Publications
Message-Id: <[e-mail]>
Expires: 15 May 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 17 Apr 88 20:06:00 GMT
Apparently-To: std-unix-archive
Status: RO

This is the latest in a series of similar comp.std.unix articles,
intended to give summary information about UNIX User groups
and publications; to be accurate, but not exhaustive.
I'm cross-posting it to comp.org.usenix and comp.unix.questions
because there might be interest there.

There are two related articles, posted at the same time as this one,
and with subjects ``Calendar of UNIX-related Events'' and ``Access to
UNIX-Related Standards.''  The latter is posted only to comp.std.unix.

Corrections and additions to this article are solicited.  I keep track
of the conferences, groups, and publications that I attend, am a member
of, or subscribe to.  All others (the majority of the listings) I derive
either from listings elsewhere, or from contributions by readers.
In particular, the meeting schedules and descriptions of most of the
groups are provided by their members.  If a group doesn't have a
meeting schedule listed, it's because nobody has sent me one.  This is
a low-budget operation:  I publish what I have on hand when the time
comes (approximately monthly).

Recent additions:  AT&T Technical Journal, Byte, The C Users Journal, Unique.


Access information is given in this article for the following:
user groups:    USENIX, /usr/group, EUUG, AUUG, NZUSUGI, JUS, KUUG, AMIX,
        DECUS UNIX SIG, Sun User Group, Apollo DOMAIN Users' Society
newsletters:    ;login:, /usr/digest, EUUGN, AUUGN, NUZ
journal:    Computing Systems
magazines:    CommUNIXations, UNIX REVIEW, UNIX/WORLD,
        Multi-User Computing Magazine, UNIX Systems, UNIX Magazine

Telephone numbers are given in international format, i.e., +n at
the beginning for the country code, e.g., +44 is England, +81 Japan,
+82 Korea, +61 Australia, +64 New Zealand, and +1 is U.S.A. or Canada.

UNIX is a Registered Trademark of AT&T.


USENIX is ``The Professional and Technical UNIX(R) Association.''

        USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710
        U.S.A.
        [phone]
        {uunet,ucbvax,decvax}!usenix!office
        [e-mail]

USENIX sponsors two USENIX Conferences a year, featuring technical papers,
as well as tutorials, and with vendor exhibits at the summer conferences:

    Jun 20-24 1988    Hilton Hotel, San Francisco, CA
    Jan 31-Feb 3 1989 Town & Country Inn, San Diego, CA
    Jun 12-16 1989    Hyatt Regency, Baltimore, MD
    Jan 23-26 1990    Washington, DC
    Jun 11-15 1990    Marriott Hotel, Anaheim, CA
    Jan 22-25 1991    Dallas, TX
    Jun 10-14 1991    Opryland, Nashville, TN

They also sponsor workshops, such as
    May 12-13 1988    Omni Shoreham Hotel, Washington, DC
        Fifth Workshop on Real-Time Software and Operating Systems
        IEEE Computer Society and USENIX Association
    Aug 29-30 1988    UNIX Security, Portland, OR
    Sep 26-27 1988    UNIX & Supercomputing, Pittsburgh, PA
    Oct 17-20 1988    C++ Conference (tentative), Denver, CO
    Nov 17-18 1988    Large Installation System Administration II, Monterey,CA

Proceedings for all conferences and workshops are available at
the door and by mail later.

USENIX publishes ``;login:  The USENIX Association Newsletter''
bimonthly.  It is sent free of charge to all their members and
includes technical papers.  There is a USENET newsgroup,
comp.org.usenix, for discussion of USENIX-related matters.

In 1988, USENIX started publishing a new refereed quarterly
technical journal, ``Computing Systems:  The Journal of the USENIX
Association,'' in cooperation with University of California Press.

They also publish an edition of the 4.3BSD manuals, and they
occasionally sponsor experiments, such as methods of improving the
USENET and UUCP networks (e.g., uunet), that are of interest and use to
the membership.  They distribute tapes of contributed software and are
pursuing expanding that activity.

There is a USENIX Institutional Representative on the IEEE P1003
Portable Operating System Interface for Computer Environments Committee.
That representative also moderates the USENET newsgroup comp.std.unix,
which is for discussion of UNIX-related standards, especially P1003.
For more details, see the posting in comp.std.unix, ``Access to
UNIX-Related Standards.''


/usr/group is a non-profit trade association dedicated to the promotion
of products and services based on the UNIX operating system.

        /usr/group
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        U.S.A.
        tel: [phone]
        fax: [phone]

The annual UniForum Conference and Trade Show is sponsored by /usr/group
and features vendor exhibits, as well as tutorials and technical sessions.

    Feb 28-Mar 3 1989 Moscone Center, San Francisco, CA
    Jan 23-26 1990    Washington Hilton, Washington, DC
    Jan 22-25 1991    Infomart, Dallas, TX
    Jan 21-24 1992    Moscone Center, San Francisco CA (tentative)

They also sponsor a regional show, UniForum D.C.:

    Aug 2-4 1988    Washington Hilton Hotel, Washington, D.C.

Proceedings for all conferences are available at the shows and later
by mail.

/usr/group publishes ``CommUNIXations,'' a member magazine that
features articles by industry leaders and observers, technical issues,
standards coverage, and new product announcements.

/usr/group also publishes the ``UNIX Products Directory,'' which lists
products and services developed specifically for the UNIX operating system.
``/usr/digest'' is also published by /usr/group.  This newsletter covers
product announcements and industry projections, and is sent biweekly
to General members of /usr/group and to non-member subscribers.

/usr/group has long been deeply involved in UNIX standardization,
having sponsored the ``/usr/group 1984 Standard,'' providing an Institutional
Representative to the IEEE P1003 Portable Operating System for Computer
Environments Committee, and sponsoring the /usr/group Technical Committee
on areas that P1003 has not yet addressed.  They have recently produced
an executive summary, ``Your Guide to POSIX,'' and a technical overview
``POSIX Explored,'' and funded production of a draft of a ``Rationale and
Notes'' appendix for IEEE 1003.1.


EUUG is the European UNIX systems Users Group, which is currently
celebrating its tenth anniversary.  EUUG is closely coordinated with
national groups in Europe, and with the European UNIX network, EUnet.

        EUUG secretariat
        Owles Hall
        Buntingford
        Herts SG9 9PL
        England
        Telephone [phone]
        Telefax [phone]
        uunet!mcvax!inset!euug
        [e-mail]

They have a newsletter, EUUGN (a previous version of this article
appeared in the latest one), and hold two conferences a year:
    3-7 October 1988, Lisbon, Portugal
    April 1989, Brussels, Belgium


AUUG is the Australian UNIX systems Users Group.

        AUUG
        P.O. Box 366
        Kensington
        N.S.W.    2033
        Australia
        uunet!munnari!auug
        [e-mail]

Phone contact can occasionally be made at [phone]

AUUG holds at least one conference a year, usually in the spring
(August or September).  The next one will be in Melbourne on 13-15
September 1988, will be the first three day meeting, will have a larger
equipment exhibition than any before, and will be professionally
organized for the first time.

They publish a newsletter (AUUGN) at a frequency defined to be every 2 months.


The New Zealand UNIX Systems User Group, Inc. (NZUSUGI) has an annual meeting
and publishes a newsletter, ``NUZ.''

        New Zealand UNIX Systems User Group
        P.O. Box 585
        Hamilton
        New Zealand
        [phone]

The next and fifth annual meeting is the New Zealand UNIX Systems User Group
(NZUSUGI) 1988 Conference, June 9-11 1988, in Wellington, New Zealand.

If you wish to present a paper, acceptance of which entitles you to a free
conference registration, please contact the local speakers organiser,
Dr Dick Cooper, ADATA, PO Box 2555, Christchurch, New Zealand,
[e-mail]   or ...uunet!vuwcomp!cantuar!dick

If you would just like to attend, please respond to Ray Brownrigg, including
a postal address for the delivery of further information as it becomes
available.  Registration forms are expected to be available in February.

        UUCP: {utai!calgary,uunet}!vuwcomp!dsiramd!ray
        ACSnet:    [e-mail][@munnari]
        Ray Brownrigg
        Applied Maths Div, DSIR
        PO Box 1335
        Wellington
        New Zealand


The Korean UNIX User Group (KUUG) has a software distribution service
and a newsletter.

        Korean UNIX User Group
        ETRI
        P.O. Box 8
        Daedug Science Town
        Chungnam 300-32
        Republic of Korea
        [phone]


The Japan UNIX Society has two meetings a year, and a newsletter.

        Japan UNIX Society
        #505 Towa-Hanzomon Corp. Bldg.
        2-12 Hayabusa-cho
        Chiyoda-ku, Tokyo 102
        Japan
        [phone]


AMIX - the Israeli UNIX user group, is a S.I.G. of the Israeli Processing
Association (IPA). AMIX has a yearly conference (next one on 4-6 July 1988)
and a yearly workshop (last one was in November).

        AMIX, c/o IPA
        P.O. Box 919
        Ramat-Gan
        Israel, 52109
        Tel: [phone],715772
        [e-mail]
        [e-mail]


There are similar groups in other parts of the world.  If such a group
wishes to be included in later versions of this access list, they
should please send me information.

There is a partial list of national organizations in the November/December
1987 CommUNIXations.



DECUS, the Digital Equipment Computer Users Society,
has a UNIX SIG (Special Interest Group) that participates
in its general meetings, which are held twice a year.

        DECUS U.S. Chapter
        219 Boston Post Road, BP02
        Marlboro, Massachusetts  01752-1850
        U.S.A.
        [phone]

The next two DECUS Symposia are:

    May 16-20, 1988        Cincinnati, Ohio
    Oct 17-21, 1988        Anaheim, California

See also the USENET newsgroup comp.org.decus.


The Sun User Group (SUG) is an international organization that promotes
communication among Sun users, OEMs, third party vendors, and Sun
Microsystems, Inc.  SUG sponsors conferences, collects and distributes
software, produces the README newsletter and T-shirts, sponsors local
user groups, and communicates members' problems to Sun employees and
management.

    Sun Microsystems User Group, Inc.
    2550 Garcia Avenue
    Mountain View, CA  94043
    U.S.A.
    [phone]
    [e-mail]
    sun!users

They have not set a date/location for the 1988 conference yet, but are
actively looking for a hotel (with good pricing and lots of room).
They've narrowed it down to several locations - Miami/Tampa Florida,
Houston/Dallas Texas, and New Orleans LA.  The date will probably be
very early December, 1988.


ADUS is the Apollo DOMAIN Users' Society:

    Apollo DOMAIN Users' Society
    c/o Andrea Woloski, ADUS Coordinator
    Apollo Computer Inc.
    330 Billerica Rd.
    Chelmsford, MA 01824
    [phone], x4448


The main general circulation (more than 10,000 copies per issue) magazines
specifically about the UNIX system are:

    UNIX REVIEW            UNIX/WORLD
    Miller Freeman Publications Co.    Tech Valley Publishing
    500 Howard Street        444 Castro St.
    San Francisco, CA 94105        Mountain View, CA 94041
    U.S.A.                U.S.A.
    monthly                monthly
    [phone]            [phone]

    Multi-User Computing magazine    UNIX Systems
    Storyplace Ltd.            Eaglehead Publishing Ltd.
    42 Colebrook Row        Maybury Road
    London  N1 8AF            Woking, Surrey GU21 5HX
    England                England
    [phone]            [phone]

    UNIX Magazine
    Jouji Ohkubo
    c/o ASCII Corp.
    [e-mail]
    [phone]
    fax: [phone]
    telex: 242-6875 ASCIIJ

Some of the above information about magazines was taken from the
November/December 1987 issue of CommUNIXations, which also lists
some smaller-circulation magazines and newsletters.

In addition, there is the Journal of the USENIX Association and
the /usr/group member magazine:

    Computing Systems        CommUNIXations
    USENIX Association        /usr/group
    P.O. Box 2299            4655 Old Ironsides Drive, Suite 200
    Berkeley, CA 94710        Santa Clara, California 95054
    U.S.A.                U.S.A.
    quarterly            bimonthly
    [phone]            [phone]


Finally, Dominic Dunlop <[e-mail]> has pointed out several
publications that frequently include articles about the UNIX system or
the C language.  I've listed them below; the comments after each entry
are his.  I have excluded listings of magazines about specific hardware.

    AT&T Technical Journal
    AT&T Bell Laboratories
    Circulation Dept.
    Room 1K-424
    101 J F Kennedy Parkway
    Short Hills, NJ 07078
    Bimonthly
    $40/yr (US); $50/yr (overseas)
    [phone]
    While few issues are devoted to UNIX,
    most turn out to mention its applications.

    Byte
    McGraw-Hill Inc.
    Phoenix Mill Lane
    Peterborough, NH 03458
    Monthly
    $22/yr (US); $25/yr(Mex,Can); $37/yr (surface); $69/yr (air,Europe)
    [phone]
    Concentrates mainly on personal computers,
    but covers low end of UNIX market in some depth.

    The C Users Journal
    ``A service of the C Users Group.''
    R&D Publications Inc
    PO Box 97
    McPherson, KS 67460
    Eight issues per year
    $20/yr (US/Mex/Can); $30/yr (overseas)
    [phone]
    Mainly DOS-oriented; some UNIX.

    Unique
    ``The UNIX System Information Source.''
    Infopro Systems
    PO Box 220
    Rescue, CA 95672
    Monthly
    $79/yr (US,overseas); $99/yr (air)
    [phone]
    High-quality industry newsletter.
    Emphasis on marketing implications of technical developments.


The following information about bookstores was taken from the
November/December 1987 issue of CommUNIXations.  In the interests of
space, I have arbitrarily limited the selection listed here to those
bookstores or suppliers specifically dedicated to computer books, and
not part of other organizations.

    Computer Literacy Bookshop    UNIX Book Service
    2590 No. First St.        35 Bermuda Terrace
    San Jose, CA 95131        Cambridge, CB4 3LD
    U.S.A.                England
    [phone]        [phone]

    Cucumber Bookshop        Jim Joyce's UNIX Book Store
    5611 Kraft Ave.            47 Potomac St.
    Rockville, MD 20852        San Francisco, CA 94117
    U.S.A.                U.S.A.
    [phone]            [phone]

Volume-Number: Volume 14, Number 3

From uucp  Sun Apr 17 16:16:14 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA10881; Sun, 17 Apr 88 16:16:14 EDT
From: [e-mail] (comp.std.unix moderator, John S. Quarterman)
Newsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
Subject: Calendar of UNIX-related Events
Message-Id: <[e-mail]>
Expires: 15 May 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail] (comp.std.unix moderator, John S. Quarterman)
Date: 17 Apr 88 20:11:10 GMT
Apparently-To: std-unix-archive
Status: RO

Here is a combined calendar of planned conferences, workshops, or
standards meetings by various organizations.  I compiled it for
my own use and thought it might be of some public interest.  Most
of this information came from the various conference organizers,
although some was taken from ;login: (USENIX), 13, 1, Jan/Feb
1988 and CommUNIXations (/usr/group), VII, 6, Nov/Dec 1987.

If your favorite meeting is not listed, it's probably because I
don't know about it.  If you send me information on it, I will
probably list it both here and in the companion article, ``Access
to UNIX User Groups and Publications.'' There is also another
companion article, ``Access to UNIX-Related Standards,'' that
appears only in comp.std.unix.

Abbreviations: U for UNIX, W for Workshop, S for Symposium, C for
Center.  The sponsors of the USENIX, EUUG, AUUG and DECUS
conferences are the organizations of the same names, and the
sponsor of UniForum is /usr/group.  Dates and places for IEEE
1003 after Oct 1988 are tentative, and also for the 1992
UniForum.

Changes since last posting: The July IEEE 1003 meeting has moved
to Denver from Colorado Springs, and the June 1989 Monterey
meeting is now the July 1989 San Francisco one.  Their later
meetings have sprouted tentative dates and a new one in Montreal.
The October 1988 ISO SC22 and WG15 meetings have changed dates
(again).

year mon days          conference        (sponsor,) (hotel,) location

1988 May 3-5           U Exposition      AFUU, Palais des Congress, Paris
1988 May 12-13         Real-Time W       USENIX/IEEE, Omni Shoreham, Washington
1988 May 16-20         DECUS S           Cincinnati, Ohio
1988 May 17-19         UNIX 88/etc.      /usr/group/cdn, Convention C, Toronto
1988 Jun 7-9           COMUNIX           /usr/group/UK, Alexandra Palace, London
1988 Jun 9-11          NZSUGI            Wellington, New Zealand
1988 Jun 20-24         USENIX            Hilton, San Francisco, CA
1988 Jun 20-24         IEEE 1003.6       at USENIX, in San Francisco, CA

1988 Jul               U Symposium       JUS, Tokyo, Japan
1988 Jul 4-6           AMIX              Israel
1988 Jul 11-15         IEEE 1003         Tech Center Hyatt, Denver, CO
1988 Aug 2-4           UniForum/DC       Washington Hilton, Washington, DC
1988 Aug 29-30         U Security W      USENIX, Portland, OR
1988 Sep 13-15         AUUG              Melbourne, Australia
1988 Sep 26-27         U&Supercomp. W    USENIX, Pittsburgh, PA
1988 Oct 3-7           EUUG              Lisbon, Portugal
1988 Oct 17-21         DECUS S           Anaheim, California
1988 Oct 17-21         C++ Conference    USENIX, Denver, CO
1988 Oct 17-19,20-21   ISO SC22 & WG15   Tokyo, Japan
1988 Oct 24-28         IEEE 1003         Hawaii
1988 Oct               UNIX Expo         New York, NY
1988 Nov 17-18         Large Install.    Syst. Adm. W II, USENIX, Monterey, CA
1988 Nov               U Symposium       JUS, Osaka, Japan
1988 Dec               Sun User Group    southern U.S.A.
1988 Dec               UNIX Fair         JUS, Tokyo, Japan

1989 Jan 9-13          IEEE 1003         Embassy Suites, Ft. Lauderdale, FL
1989 Jan 31-Feb 3      USENIX            Town and Country, San Diego, CA
1989 Feb 28-Mar 3      UniForum          Moscone Center, San Francisco, CA
1989 Apr 17(29?)       IEEE 1003         Minneapolis-St. Paul, MN
1989 Apr               EUUG              Brussels, Belgium
1989 Jun 12-16         USENIX            Hyatt Regency, Baltimore, MD
1989 Jul 10-14         IEEE 1003         San Francisco, CA
1989 Oct 16-20         IEEE 1003         Brussels (or Amsterdam)
1989 Oct               UNIX Expo         New York, NY

1990 Jan 23-26         USENIX            Washington, DC
1990 Jan 23-26         UniForum          Washington Hilton, Washington, DC
1990 Jan 29            IEEE 1003         New Orleans, LA
1990 Apr               IEEE 1003         Montreal, Quebec
1990 Jun 11-15         USENIX            Marriott, Anaheim, CA

1991 Jan 22-25         USENIX            Dallas, TX
1991 Jan 22-25         UniForum          Infomart, Dallas, TX
1991 Jun 10-14         USENIX            Opryland, Nashville, TN

1992 Jan 21-24         UniForum (?)      Moscone Center, San Francisco CA

Volume-Number: Volume 14, Number 4

From uucp  Mon Apr 18 01:05:16 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA08718; Mon, 18 Apr 88 01:05:16 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Standards Update (1: P1003.1 Final Balloting)
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 18 Apr 88 03:55:11 GMT
Apparently-To: std-unix-archive
Status: RO


                      Standards Update
           An update on UNIX Standards Activities

                       April 17, 1988

             Written for the USENIX Association
              by Shane P. McCarron, NAPS Inc.

[This report was written at the request of the Board of
Directors of the USENIX Association.  In the interests of
reducing article sizes and making followups easier to
manage, I am posting it in three parts, divided according to
the following topics:
     P1003.1 Final Balloting?
     NBS POSIX FIPS
     IEEE P1003 Activities
-mod]

This is the second in a series of reports on the UNIX
standards community.  In this article I will give you a
summary of what happened at the March meeting of the POSIX
committees.  I will also explain what happened during the
IEEE P1003.1 balloting, and why there is going to be another
round of review and comment during May.  In addition I will
discuss what is going on with the National Bureau of
Standards (NBS) Federal Information Processing Standards
(FIPS), and how this will effect both implementors and
programmers in the short and long term.  Those of you who
saw the first article in this series will remember that the
title was "An update on UNIX and C Standards Activities."
That changed this time because the ANSI X3J11 meeting isn't
until mid-April, and there hasn't been too much going on
between meetings (other than a public review).  Next quarter
I will return to the C arena as well.

P1003.1 Final Ballot?

Those of you who saw the first issue of this column may
remember that I reported on the status of the P1003.1
balloting.  At that time I stated that the standards would
be fully ratified in March...  Well, I was wrong.  Although
the IEEE review board gave the standard conditional
approval, it did not pass in it's first round of balloting,
nor did it pass in the first recirculation for review and
comment.  Needless to say, I was a little surprised, but
there were many factors that figured into the problem, and
it just wasn't to be.

P1003.1 Balloting?, April 17, 198S8hane P. McCarron, NAPS Inc.


Standards Update           - 2 -          USENIX Association

I have been asked by many people exactly what went on.  In
the interest of clearing the air, below you will find a
chronological account of the balloting procedure.  I have
also outlined what the IEEE requirements for balloting are,
and how P1003.1 worked within these constraints.  Even
though you many finish reading the summary with an uneasy
feeling about the standards process, please keep in mind
that until recently there have been no large IEEE standards.
The procedures were designed for 4 page documents describing
the characteristics of three-phase power, not for 400 page
documents specifying all the characteristics of an operating
system.

On November 15th the Standard went out to the balloting
group.  The balloting group consists of IEEE or IEEE
Computer Society members who have indicated an interest in
voting on this standard.  When a balloter votes no, they
must return a document which states their specific
objections, and what can be done to resolve them.  Although
specific wording is not required, it is encouraged.

On December 15th (actually, a little after) balloting on the
standard closed.  The official IEEE length of a balloting
period is 30 days, or until 75% of the balloting group
members have returned a ballot, whichever is later.  When
75% of the ballots had been returned, the standard did not
have the necessary percentage of yes votes (75%) for
approval.  At this point the standard and the ballots were
turned over to the Technical Reviewers for resolution.

On January 15th (or so) the committee chair started to
assemble the ballot resolution documents for recirculation
to the balloting group.  The resulting document was a
summary of all the changes made to the standard to resolve
balloting objections or comments.  In all there were 140
pages of changes, and (unfortunately) they were poorly
organized and formatted.  In my own defense (as a Technical
Reviewer) I can only say that the process was rushed a
little, and I procrastinated a little.  Also, communication
between the Technical Reviewers was a little lacking, and
the guidelines for reviewing and acting on ballots were
unclear.  This is all kind of tragic, but it was certainly
an educational experience for all concerned.

On February 5th the resolution document was resubmitted to
the balloting group for a 10 day review period that was to
start on the 15th.  Unfortunately the mail was held up until
the 15th (or in some cases the 17th) and many balloting
group members did not receive the recirculation document
until the 20th or later, for return to the IEEE Standards
office by the 25th.  Worse yet, the IEEE balloting

P1003.1 Balloting?, April 17, 198S8hane P. McCarron, NAPS Inc.


Standards Update           - 3 -          USENIX Association

procedures state that if the technical reviewers have
resolved all objections in a ballot, that ballot
automatically becomes a yes.  The balloter must specifically
indicate that his/her ballot is still negative.  This was
not made very clear to the balloting group, and many people
did not resubmit a ballot.

Fortunately many people did complain about the short review
period and the problems with the recirculation document.
Eventually it was discovered that the 10 day period that
IEEE stipulates for reviews is a minimum, not a maximum.
There was a lot of finger pointing and complaining on all
sides, and in the end it was decided that even though the
standard had the necessary 75% approval, there would be a
second recirculation.

During the week of March 7th the IEEE Standards Board met.
In spite of all the problems with the standard, and all of
the letters of protest that they received (including one
from each of the Institutional Representatives, if I am not
mistaken), the board conditionally approved the standard.
[You're not mistaken: the Institutional Representatives of
all three of USENIX, /usr/group, and X/OPEN sent letters of
protest to the Standards Board; I also spoke to the
Standards Activities Group directly about the time limit
problem.  -jsq] This conditional approval is an
unprecedented event (as far as I can tell) and means that
the standard can become fully ratified before the next
meeting of the standards board once the second recirculation
has been completed and it has sufficient positive ballots.
There was a lot of screaming about this as well, but somehow
it happened.

During the week of March 14th the POSIX committees met in
Washington D.C.  Throughout the meetings the co-chair of
P1003.1 met with each of the Technical Reviewers and very
carefully went through their sections of the document,
making sure that all objections and comments had been
considered, processed, and responded to.  This was an
incredibly time consuming and painful process, but I believe
that it resulted in a much better standard.  During the last
few weeks the Technical Reviewers have continued to work
closely with the co-chair to get the second recirculation
document put together.  It should be completed and sent to
the Technical Reviewers (as a safety check) in mid-April.
Once the Reviewers think that it is clean enough, it will be
sent out to the balloting group for a second review and
comment period.

The second recirculation will be handled quite a bit
differently than the first.  All members of the balloting

P1003.1 Balloting?, April 17, 198S8hane P. McCarron, NAPS Inc.


Standards Update           - 4 -          USENIX Association

group will receive a new copy of the standard (Draft 12.3)
that will have change bars only in those places where
changes have been made as a result of balloting objections
or comments.  In addition, each balloter will receive a
document detailing all of the unresolved objections, what
their nature is, and why they were not resolved.  The
balloting group will have a longer period to respond to this
document (> 10 days), but they shouldn't need much more
time, as most of the changes in the document were already
detailed in the first recirculation document (although they
were not made in context - that is to say they were not in a
new draft, but rather listed as changes to draft 12).  At
the end of this recirculation and balloting period it is
believed by most members of the committee that the standards
will be complete.

The time frame for all of this is late April/early May.

I apologize for the length of this summary, but I think it
is important that everyone know just what happened.  Of
course, this is just one man's perspective, but I think that
it is a fair one.  I believe that the completed standard
will be one which was carefully considered and designed,
even if it won't make everyone happy.

P1003.1 Balloting?, April 17, 198S8hane P. McCarron, NAPS Inc.

Volume-Number: Volume 14, Number 5

From uucp  Mon Apr 18 01:06:49 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA08909; Mon, 18 Apr 88 01:06:49 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Standards Update (2:  NBS POSIX FIPS)
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 18 Apr 88 03:56:54 GMT
Apparently-To: std-unix-archive
Status: RO


                      Standards Update
           An update on UNIX Standards Activities

                       April 17, 1988

             Written for the USENIX Association
              by Shane P. McCarron, NAPS Inc.

NBS POSIX FIPS

As I reported last quarter, the National Bureau of Standards
has specified an Federal Information Processing Standard for
POSIX.  This FIPS has now been called an Interim FIPS, and
is based on Draft 12 of the POSIX standard (the draft that
went to the balloting group).  This is unfortunate, since
the post balloting draft is significantly different in a
number of areas.  Also, the NBS has made some changes in
their requirements for the FIPS since I last reported them.
As of this writing the POSIX Interim FIPS for the System
Services Interface is not official.  It is going through the
government signature maze within the Department of Commerce,
and is expected to emerge sometime in April.

This Interim FIPS will remain the standard until the P1003.1
standard is completed.  Sometime after that the NBS will put
together a final FIPS based on .1.  Unfortunately, this may
not be for several months after .1 is completed.  In the
mean time government agencies will be generating Requests
for Procurement (RFPs) which stipulate the Interim FIPS.

What this means for systems implementors is not entirely
clear.  The government will be requiring (at least for a
little while) a standard that is in many ways incompatible
with the final P1003.1 document.  Obviously implementors
have two options: 1) put together POSIX conforming systems
and wait until the final FIPS is complete before selling any
systems, or 2) put together a FIPS conforming system and be
able to start selling immediately.  Fortunately implementors
have an out here - many of them have release cycles lasting
anywhere from 6 to 18 months.  By the time there is a POSIX
standard and they get their implementation ready to be
released, the FIPS will have changed to reflect the final
standard...  Maybe.

What it means to application developers is a little more
obvious.  Software that is in development today is probably
too far along to consider making it POSIX conformant - or
worse yet, ANSI C conformant.  Software that is not yet in
programming is going to take quite a while to get to market,
so it can be made POSIX conformant without having to worry
about the Interim FIPS.

NBS POSIX FIPS, April 17, 1988  Shane P. McCarron, NAPS Inc.


Standards Update           - 2 -          USENIX Association

In addition to this first FIPS, the NBS has stated that it
is going to be releasing several more Interim FIPS based on
some of the other POSIX work in progress, as well as the
work of other groups (like AT&T and the SVID).  During the
POSIX meetings in Washington, Roger Martin from the NBS (and
also chair of P1003.3 - Testing and Verification) made
presentations to the various committees, explaining what the
NBS intends to do in the next year with Interim FIPS:

In May or June an Interim FIPS for the Shell and Tools
interface (POSIX P1003.2) will be proposed.  It will be
based on Draft 6 of the .2 document, and will contain (at
least) the command set from that document.  It may also
contain text from that document, or in cases where the text
is felt to be immature, will contain text from the SVID or
some other source.  This Interim FIPS will be based on Draft
6 until the final standard is completed sometime in later
1989.

In addition, the NBS will be releasing several other FIPS.
These will be in the areas of Terminal Interface Extensions,
System Administration, and Advanced Utilities.  These are
all terms from the SVID, and relate to just the things that
you think they do.  The Advanced Utilities FIPS may be
rolled into the P1003.2 FIPS, since .2 encompasses most of
those items that they wanted in there.  The others will be
based directly on the SVID (as far as I know).  These are
all to be in place by the end of 1988.  This is an ambitious
schedule, even for NBS.  However if they meet it, it will
mean that by the end of this year the government will have
standards on most aspects of the UNIX operation system, and
system implementors and application developers will have to
conform.

NBS POSIX FIPS, April 17, 1988  Shane P. McCarron, NAPS Inc.

Volume-Number: Volume 14, Number 6

From uucp  Mon Apr 18 01:07:50 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA09021; Mon, 18 Apr 88 01:07:50 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Standards Update (3: IEEE P1003 Activities)
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 18 Apr 88 03:59:48 GMT
Apparently-To: std-unix-archive
Status: RO


                      Standards Update
           An update on UNIX Standards Activities

                       April 17, 1988

             Written for the USENIX Association
              by Shane P. McCarron, NAPS Inc.

IEEE P1003 Activities:

As I mentioned above, the POSIX committees met in Washington
D.C. in March.  For the first time, all 7 of the committees
met.  As you can imagine, it was pretty difficult to catch
all of what went on, but here are the highlights:

P1003.0 - POSIX Guide Project:

This group met for the first time in Washington.  Although
they didn't get a lot of tangible work done, they did
establish what their goals were, as well as starting to put
together a timetable for production of their guide document.
I don't have the details of this yet, but I will next
quarter.

P1003.1 - System Services Interface:

This group met to decide what we are going to be working on
in the future.  We have a few items that must be handled by
the .1 group, and some that could be.  Currently there are
three projects being worked on by members of the committee:

   - Language Independent Description

     The ISO POSIX Working Group has requested that a
     language independent version of the .1 standard be
     produced as soon as possible after completion of the
     standard.  Language bindings (like the current
     descriptions that are in the standard and the work
     being done by the .5 group) would be placed in
     supplements to the main standard, or in chapters within
     the standard itself.

   - Improved Archive Format

     Although the ISO community agrees that CPIO and USTAR
     are fine for the first cut of the standard, they have
     requested that .1 work on a more robust archive format
     that doesn't have the technical drawbacks of either, as
     well as one that takes into account the security
     features needed for trusted systems.

IEEE P1003 Activities, April 17,S1h9a8n8e P. McCarron, NAPS Inc.


Standards Update           - 2 -          USENIX Association

   - Terminal Interface Extensions

     Yes - we mean curses/Terminfo.  Well, not really, but
     something very much like that.  It will have to be
     something that resembles current practice (I imagine),
     but it could be improved in little ways.  There was a
     lot of sentiment in the group for throwing out all of
     the Terminfo stuff and starting from scratch, but I
     don't think it will happen.  We will probably get some
     proposals that are wildly different from existing
     practice, but it is outside the group's charter to
     totally supplant existing practice.

P1003.2 - Shell and Tools Interface:

The .2 Group got a lot of work done in Washington.  They
went in with a 400 page draft 5, and by end of May a 450+
page draft 6 should be completed.  This draft 6 will be used
as the basis of the interim FIPS that the NBS will be using
for their Interim FIPS on POSIX (see above).

The most significant developments in .2 were:

   - Source Code Control

     The committee felt that source code control was outside
     the scope of the standard, and it was removed (it had
     been added at the last meeting).  A number of people
     still feel that some form of source code control should
     be in there, so the committee left a place in the
     document where it could be put back in later.  The real
     danger here is that the RCS people and the SCCS people
     will get into a religious war similar to the one that
     erupted between the TAR and CPIO factions in the .1
     group.

   - Basic Shell Changes

     There were many features of the Bourne shell that had
     been included in .2 for historic reasons.  At this
     meeting the shell subcommittee agreed to remove some of
     those anachronisms.  This will make way for (possibly)
     more enhancements to the basic shell mechanism in the
     future (e.g., substring manipulation).

   - Software Installation

     Two drafts past there was a very complex system in the
     standard that allowed software installation in a
     portable way.  This was removed in the December
     meeting, and replaced at the March meeting by a very

IEEE P1003 Activities, April 17,S1h9a8n8e P. McCarron, NAPS Inc.


Standards Update           - 3 -          USENIX Association

     simple interface that should be acceptable to everyone.
     Although the details are not all clear, it looks like
     this will consist of an implementation defined command
     that will read the first file off of a POSIX conforming
     archive (tape) and execute it.  Anyway, something about
     that difficult.

   - Electronic Mail Interface

     Mailx was added in Draft 5 as a proposed way to
     portably transmit mail.  Some committee members felt
     that the way in which it was described was too
     restrictive, while others felt that it was too liberal.
     In a compromise move, another interface was defined
     that allows very simple mail transmission in a portable
     manner.  It also has a name that doesn't conflict with
     existing utilities.

P1003.3 - Testing and Verification:

At the March meeting the chair announced that they were on
target for completing the assertion lists for P1003.1, and
that the .3 standard for .1 would be ready to ballot just as
soon as the .1 standard was ratified.  He also stated pretty
clearly that P1003.3 didn't want to work as hard when
generating verification standards for the other POSIX
committees.  He asked that in the future the standards be
written in a way that makes it easier to develop assertion
lists.  The .3 committee will be working closely with the .2
effort (which is a little too far along to fix now), but the
other committees will be changing their documents to reflect
what assertion tests can be made about each function or
command being defined.  This should make it easier to
produce verification documents for those standards.

P1003.4 - Real Time:

This committee made a lot of progress in the March meeting.
However, they have a long road ahead of them, and I don't
know that anything earth shattering happened - certainly
nothing that I heard about.  However, they have stated a
target of 1990 for completion, and at this point it is a
little early to draw any sort of conclusions.

P1003.5 - Ada Binding for the System Services Interface:

The Ada group is still a very young committee, but they are
moving right along.  At the very least they are generating a
lot of paper, but it has some excellent stuff on it.
Although they haven't been a working group long, I expect to
see a draft from them in the next six months, and a standard

IEEE P1003 Activities, April 17,S1h9a8n8e P. McCarron, NAPS Inc.


Standards Update           - 4 -          USENIX Association

being balloted in a year.  Although this may seem like a
long time, it is really short work for a standards
committee.  Unfortunately, their work is very dependent on
.1 getting a language independent description of the System
Services Interface put together as quickly as possible.
They have already looked into ways of describing POSIX
independent of any language, and they will be helping .1 get
this firmed up.

P1003.6 - Security:

This was the first meeting of .6 as a real IEEE committee.
They defined their scope and objectives, set a tentative
production schedule, and defined the format of their
document.  As a /usr/group technical committee they produced
a number of white papers, and I expect to see drafts coming
out of the group based on those papers shortly.  The only
snag here is that the transition from a /usr/group technical
committee to an IEEE working group wasn't as smooth as
others have been.  To help alleviate some of the tension
this caused, the next .6 meeting will be held in conjunction
with USENIX in San Francisco in June, instead of with the
POSIX committees in July.  After that they will follow the
regular POSIX meeting schedule.

IEEE P1003 Activities, April 17,S1h9a8n8e P. McCarron, NAPS Inc.

Volume-Number: Volume 14, Number 7

From uucp  Fri Apr 22 23:58:59 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA00699; Fri, 22 Apr 88 23:58:59 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: More UNIX Press sources
Message-Id: <[e-mail]>
Reply-To: uunet!pilchuck!ssc!fyl (Phil Hughes)
Date: 20 Apr 88 13:05:05 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!pilchuck!ssc!fyl (Phil Hughes)

Here are a few more places where  UNIX appears in the press:
    UNIX User
    210 S. Helberta Avenue
    Redondo Beach, CA 90277
    213-372-9917
This is a new magazine dedicated to the UNIX beginner.  First real issue
will be out in June.

    MicroSystems Journal
    M&T Publishing, Inc
    501 Galveston Drive
    Redwood City, CA 94063
    [phone]
Primarily for the PC/XT/AT user but 35% of the readers use UNIX.  It has
had a C column and a UNIX column for some time.  The UNIX column was written
by Ian Darwin of SoftQuad.  I will be writing the column in the future.


We publish a whole series of pocket references on UNIX and C.
We publish command summaries for BSD4.2/4.3, System 5.2/5.3, XENIX 5,
and System III.  Our C Library Reference compares ANSI C with the User
Group Standard.
Phil Hughes, SSC, Inc. P.O. Box 55549, Seattle, WA 98155  (206)FOR-UNIX
    uw-beaver!tikal!ssc!fyl or uunet!pilchuck!ssc!fyl or attmail!ssc!fyl


Volume-Number: Volume 14, Number 8

From uucp  Sat Apr 23 18:03:16 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA28552; Sat, 23 Apr 88 18:03:16 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Eth and Thorn characters
Keywords: Icelandic, ISO8859/1
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: uunet!mcvax!rhi.hi.is!magnus (Magnus Gislason)
Organization: University of Iceland
Date: 20 Apr 88 09:40:26 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!mcvax!rhi.hi.is!magnus (Magnus Gislason)

In article <[e-mail]>
> From: [e-mail] (rja)
>
> A recent posting has inquired about what the Eth and Thorn characters
> look like.
>
>     [...long description of the Eth and Thorn characters...]
>
Unfortunately 'rja' doesn't seem to be very familiar with Icelandic or
these special Icelandic characters.

The only character he (she?) described correctly (at least as I could
understand it) was uppercase Eth.

This is what they approximately look like in Icelandic:

     ETH           eth                THORN        thorn

     ----          \ /                |            |
     |   \          \                 |            |
     |    \        / \                |---         |
    ---   |         _ \               |   >        |---
     |    /        / \|               |---         |   \
     |   /        |   |               |            |   /
     ----          \_/                |            |---
                                                   |
                                                   |
                                                   |

For those who don't know which sounds these characters represent, they
both sound like 'th' in English. 'Eth' as in 'this' and 'thorn' as in
'think'.

        Magnus Gislason
        University of Iceland,       Internet:  [e-mail]
        Computing Center (RHI)       Uucp:  ...!mcvax!hafro!rhi!magnus

Volume-Number: Volume 14, Number 9

#!/bin/sh
for f in 3[7-9] 4?
do
    grep -v "Volume-Number:" $f > x.$f
    echo "Volume-Number: Volume 14, Number $f" >> x.$f
    echo "" >> x.$f
    diff $f x.$f
    mv x.$f $f
done
From uucp  Mon Apr 25 23:53:00 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA27751; Mon, 25 Apr 88 23:53:00 EDT
From: dale chayes <lamont![e-mail]>
Newsgroups: comp.std.unix
Subject: Re: Access to UNIX User Groups and Publications
Summary: add us please
Message-Id: <[e-mail]>
References: <[e-mail]>
Sender: [e-mail]
Reply-To: lamont![e-mail] (dale chayes)
Organization: Lamont-Doherty Geological Observatory N.Y.
Date: 24 Apr 88 23:40:55 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!lamont![e-mail] (dale chayes)

Thanks for the summary of Unix User Groups and Pubs. We are small but
growing, so please add the Masscomp Users Society to your list.

    Masscomp Users Society
    One Technology Park
    Westford, MA   01886
    Attn: Laurie Menard

    [phone]

We hold an annual meeting in April. (The 1988 meeting was last week. The
date and location for the 1989 meeting will be posted to comp.sys.masscomp
as soon as it is set.)

We publish a news letter (Musings) quarterly (approximately.)

Information is available from Laurie at the number above, by email or
phone from me, or by posting to comp.sys.masscomp.


--
Dale Chayes Lamont-Doherty Geological Observatory of Columbia University
usmail: Route 9W, Palisades, N.Y.  10964
voice:    [phone] extension 434    fax: [phone]
UUCP:    ...philabs!lamont!dale

Volume-Number: Volume 14, Number 10

From uucp  Tue Apr 26 11:07:51 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA03590; Tue, 26 Apr 88 11:07:51 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Eth and Thorn characters
Summary: Not "special Icelandic characters"
Keywords: Icelandic, ISO8859/1
Message-Id: <[e-mail]>
References: <[e-mail]> <[e-mail]>
Reply-To: uunet!ucbvax.Berkeley.EDU!usenix!peter (Peter Salus)
Date: 25 Apr 88 17:13:06 GMT
Apparently-To: std-unix-archive
Status: O

From: [e-mail] (Peter Salus)


In article <[e-mail]>:
> From: uunet!mcvax!rhi.hi.is!magnus (Magnus Gislason)
>
>         Magnus Gislason
>         University of Iceland,       Internet:  [e-mail]
>         Computing Center (RHI)       Uucp:  ...!mcvax!hafro!rhi!magnus

Despite the statement that edh (which I prefer to eth) and thorn
are special Icelandic characters, it is worth noting that they
occur in Old English as well.  For anyone involved in Germanic
studies or phonetics they are important.

I claim right to input as one who spent a delightful year at the
University of Iceland a quarter century ago.

Peter H. Salus
Executive Director
USENIX Association

Volume-Number: Volume 14, Number 11

From uucp  Mon May  2 16:11:06 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA14540; Mon, 2 May 88 16:11:06 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Postscript def. eth and thorn
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: uunet!mcvax!rhi.hi.is!marius (Marius Olafsson)
Organization: University of Iceland
Date: 28 Apr 88 09:04:26 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!mcvax!rhi.hi.is!marius (Marius Olafsson)

>From article <[e-mail]>, by [e-mail] (David Brooks):
> From: [e-mail] (David Brooks)
>
> Nobody, but nobody, knows how to design eth and thorn.  If any
> Icelanders(?) would post a bitmap AND a PostScript definition of these
> four glyphs, many of us would be grateful.

Following is a small PostScript-program that defines a font
containing only the two ISO8859/1 letters 'eth' and 'thorn', both
in upper and lower case, as they should look like in Times-Roman.
The encoding vector puts them at the their places in the ISO 8859/1
character set. After defining the font the program uses it to print
a few copies of the letters in several sizes.  Note that upper case
'Eth' is defined by using 'D' in the built-in Times-Roman font.

The letters are not typographically perfect, most notably the lower
case 'eth' (which is a very difficult and often badly designed letter),
but should suffice.

All fonts (almost) that Adobe sells, define these letters with the
same names as used below. They are also defined in the built-in fonts
with PostScript 42.2 and later. In that case, all that is needed to use
them is to include them in the 'Encoding'-vector.

--
Marius Olafsson        [e-mail]
University of Iceland    ..!mcvax!hafro!rhi!marius

%%%%%%%%%%%%%%%%%%%%%%%%%% PostScript begins %%%%%%%%%%%%%%%%%%%%%%%%%%

/BuildCharDict 10 dict def

/IceFont 7 dict def

IceFont begin

  /FontType 3 def
  /FontMatrix [.001 0 0 .001 0 0] def
  /FontBBox [-103 -191 1042 822 ]def

  /Encoding 256 array def
  0 1 255 {Encoding exch /.notdef put} for
  Encoding (\320) 0 get /Eth put
  Encoding (\360) 0 get /eth put
  Encoding (\336) 0 get /Thorn put
  Encoding (\376) 0 get /thorn put

  /CharacterDefs 5 dict def
  CharacterDefs begin
   /.notdef {} def
   /Eth    % definition for the upper case 'Eth'. It is implemented
           % as a Times-Roman 'D' with a line through its left side.
    { /Times-Roman findfont 1000 scalefont setfont
      /trD (D) def
      0 0 moveto
      gsave
       trD stringwidth
       trD false charpath flattenpath pathbbox
      grestore
      setcachedevice % width should be like on 'D'

      newpath
        0 0 moveto
        trD show

        13 369 moveto
        313 369 lineto
        313 411 lineto
        13 411 lineto
        13 369 lineto
      fill
    } def
   /eth    % definition for the lower case 'eth'. It should look like
           % an 'o' with a curved ascender from its right side, and
           % a crossline at a 90 degree angle to the ascender. Note that
           % the crossline is not quite right in this case.
    { 522 0 0 -18 540 738 setcachedevice % width should be like on 'o'
      newpath
        0.91 0.91 scale
        261 6 moveto
        50 4 48 445 261 445 curveto
        490 445 490 4 261 4 curveto
        261 -15 moveto
        -44 -15 -44 469 261 469 curveto
        324 469 373 430 403 401 curveto
        420 438 340 563 276 608 curveto
        162 555 lineto
        137.36 582.3 lineto
        248.5 632.3 lineto
        211 666 157 700 110 712 curveto
        130.4 721 lineto
        183.4 710 240.4 681 291.7 651.3 curveto
        404.76 703.3 lineto
        425.4 679 lineto
        323.4 631 lineto
        596 434 543 -15 261 -15 curveto
      eofill
    } def
   /Thorn  % definition for the upper case 'Thorn'. It should look similar
           % to a 'P' but the circle lies lower
    { 594 0 0 0 513 666 setcachedevice % width should be like on 'P'
      newpath
        32 3 moveto
        32 16 lineto
        92 16 129 25 133 65 curveto
        133 600 lineto
        133 639 98 654 32 654 curveto
        32 660 lineto
        307 660 lineto
        307 654 lineto
        246 654 211 636 208 600 curveto
        208 540 lineto
        350 540 lineto
        470 537 548 461 548 360 curveto
        548 261 467 175 309 173 curveto
        276 174 242 176 208 180 curveto
        208 65 lineto
        208 34 243 16 307 16 curveto
        307 3 lineto
        31 3 lineto
        208 224 moveto
        208 475 lineto
        208 496 246 501 298 501 curveto
        438 501 478 413 478 351 curveto
        478 264 435 204 285 204 curveto
        258 203 236 217 208 224 curveto
      eofill
    } def
   /thorn  % definition for the lower case 'thorn'. It should look like
           % a 'p' with an ascender as high as the 'l'.
    { 504 0 0 -234 468 702 setcachedevice % width should be like on 'p'
      newpath
        5 -217 moveto
        5 -202 lineto
        57 -202 95 -185 95 -130 curveto
        95 578 lineto
        95 615 55 628 40 628 curveto
        28 628 11 622 5 619 curveto
        5 631 lineto
        158 689 lineto
        158 387 lineto
        213 441 254 466 294 466 curveto
        410 466 470 337 470 237 curveto
        470 135 389 -18 261 -18 curveto
        224 -18 189 -2 158 26 curveto
        158 -136 lineto
        158 -187 182 -204 234 -204 curveto
        234 -217 lineto
        5 -217 lineto
        158 87 moveto
        158 341 lineto
        176 364 216 404 254 404 curveto
        359 404 393 298 393 206 curveto
        393 140 366 24 258 24 curveto
        212 24 178 50 158 87 curveto
      eofill
    } def
  end

  /BuildChar
    { BuildCharDict begin

        /char exch def
        /fontdict exch def

        /charname fontdict /Encoding get
          char get def

        /charproc fontdict /CharacterDefs get
          charname get def

        gsave charproc grestore
      end
    } def
end

/IceTimes-Roman IceFont definefont pop


/IceTimes-Roman findfont 150 scalefont setfont
30 700 moveto
<D0F0DEFE> show

/IceTimes-Roman findfont 200 scalefont setfont
30 520 moveto
<D0F0DEFE> show

/IceTimes-Roman findfont 250 scalefont setfont
30 320 moveto
<D0F0> show

/IceTimes-Roman findfont 250 scalefont setfont
30 100 moveto
<DEFE> show

showpage

%%%%%%%%%%%%%%%%%%%%%%%%%%% PostScript ends %%%%%%%%%%%%%%%%%%%%%%%%%%%


Volume-Number: Volume 14, Number 12

From uucp  Thu May  5 03:22:22 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA08208; Thu, 5 May 88 03:22:22 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: UUCP protocol definition
Message-Id: <[e-mail]>
Reply-To: uunet!uts.amdahl.com!gam (Gordon Moffett)
Date: 3 May 88 23:49:00 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!uts.amdahl.com!gam (Gordon Moffett)

[ This is Greg Chesson's packet driver protocol (UUCP g protocol) paper
that I posted a year ago.  It originally came from John Gilmore, who has
since appended some useful code, thus this updated reposting.  -mod ]

.\" @(#) packet.driver.ms    Version hoptoad-1.4    88/03/24
.\"
.\" format this with [nt]roff -ms.
.\"
.\" From: [e-mail] (Greg Chesson)
.\" Newsgroups: mod.std.unix
.\" Volume-Number: Volume 9, Number 55
.\" Subject: Packet Driver Protocol
.\" Message-ID: <[e-mail]>
.\" Date: 11 Feb 87 23:44:09 GMT
.\"
.\" This message contains a copy of ``Packet Driver Protocol,''
.\" written by G. L. Chesson while he was at Bell Laboratories.
.\" He remarks that it was approved for public distribution, and that
.\"
.\"     The version of the note that you probably have omits the
.\"     detail that the transmitted checksum is really 0125252
.\"     - the block checksum function.
.\"
.\" [Note that 0125252 is 0xAAAA, which is easier to remember.
.\" I have folded this update into the document. -- hoptoad!gnu]
.\"
.\" [I have also updated the checksum routine to include one that
.\" works regardless of the size of a "short" or an "int". -- hoptoad!gnu]
.ce
.B
Packet Driver Protocol
.R
.sp 1
.ce
G. L. Chesson
.br
.ce
Bell Laboratories
.SH
Abstract
.in +.5i
.PP
These notes describe the packet driver link
protocol that was supplied
with the
Seventh Edition of
.UX
and is used by the UUCP program.
.in -.5i
.SH
General
.PP
Information flow between a pair of machines
may be regulated by
first
representing the data
as sequence-numbered
.I
packets
.R
of data
and then establishing conventions that
govern the use of sequence numbers.
The
.I
PK,
.R
or
.I
packet driver,
.R
protocol
is a particular instance of this type of
flow-control discipline.
The technique depends on the notion of a transmission
.I
window
.R
to determine upper and lower bounds for valid
sequence numbers.
The transmitter is allowed to retransmit packets
having sequence numbers
within the window until the receiver indicates that
packets have been correctly received.
Positive acknowledgement from the receiver moves the
window;
negative acknowledgement or no acknowledgement
causes retransmission.
The receiver must ignore duplicate transmission, detect
the various errors that may occur,
and inform the transmitter when packets are
correctly or incorrectly received.
.PP
The following paragraphs describe the packet formats,
message exchanges,
and framing
used by the protocol as coded
in the UUCP program and the
.UX
kernel.
Although no attempt will be made here to present
internal details of the algorithms that were used,
the checksum routine is supplied
for the benefit of other implementors.
.SH
Packet Formats
.PP
The protocol is defined in terms of message
transmissions of 8-bit bytes.
Each message includes one
.I
control
.R
byte plus a
.I
data segment
.R
of zero or more information bytes.
The allowed data segment sizes range
between 32 and 4096 as determined by the formula
32(2\uk\d) where
k is a 3-bit number.
The packet sequence numbers are likewise constrained
to 3-bits; i.e. counting proceeds modulo-8.
.PP
The control byte is partitioned into three fields as
depicted below.
.bp
.nf
.sp
.in 1i
.ls 1
bit    7    6    5    4    3    2    1    0
    t    t    x    x    x    y    y    y
.ls 1
.in -1i
.fi
.sp
The
.I
t
.R
bits indicate a packet type and
determine the interpretation to be placed on
the
.I
xxx
.R
and
.I
yyy
.R
fields.
The various interpretations are as follows:
.in +1i
.sp
.nf
.ls 1
.I
tt    interpretation
.sp
.R
00    control packet
10    data packet
11    `short' data packet
01    alternate channel
.ls 1
.fi
.sp
.in -1i
A data segment accompanies all non-control packets.
Each transmitter is constrained to observe the maximum
data segment size
established during initial synchronization by the
receiver that it sends to.
Type 10 packets have maximal size data segments.
Type 11, or `short', packets have zero or more data
bytes but less than the maximum.
The first one or two bytes of the data segment of a
short packet are `count' bytes that
indicate the difference between the
maximum size and the number of bytes in the short
segment.
If the difference is less than 127, one count
byte is used.
If the difference exceeds 127,
then the low-order seven bits of the difference
are put in the first data byte and the high-order
bit is set as an indicator that the remaining
bits of the difference are in the second byte.
Type 01 packets are never used by UUCP
and need not be discussed in detail here.
.PP
The sequence number of a non-control packet is
given by the
.I
xxx
.R
field.
Control packets are not sequenced.
The newest sequence number,
excluding duplicate transmissions,
accepted by a receiver is placed in the
.I
yyy
.R
field of non-control packets sent to the
`other' receiver.
.PP
There are no data bytes associated with a control packet,
the
.I
xxx
.R
field is interpreted as a control message,
and the
.I
yyy
.R
field is a value accompanying the control message.
The control messages are listed below in decreasing priority.
That is, if several control messages are to be sent,
the lower-numbered ones are sent first.
.in +1i
.nf
.ls 1
.sp
.I
xxx    name        yyy
.R

1    CLOSE    n/a
2    RJ        last correctly received sequence number
3    SRJ        sequence number to retransmit
4    RR        last correctly received sequence number
5    INITC    window size
6    INITB    data segment size
7    INITA    window size
.in -i
.ls 1
.fi
.sp
.PP
The CLOSE message indicates that the communications channel
is to be shut down.
The RJ, or
.I
reject,
.R
message indicates that the receiver has detected an error
and the sender should retransmit after using the
.I
yyy
.R
field to update the window.
This mode of retransmission is usually
referred to as a
`go-back-N' procedure.
The SRJ, or
.I
selective reject,
.R
message carries with it the sequence number of
a particular packet to be retransmitted.
The RR, or
.I
receiver ready,
.R
message indicates that the receiver has detected
no errors; the
.I
yyy
.R
field updates the sender's window.
The INITA/B/C messages are used
to set window and data segment sizes.
Segment sizes are calculated by the formula
32(2\uyyy\d)
as mentioned above,
and window sizes may range between 1 and 7.
.PP
Measurements of the protocol running on communication
links at rates up to 9600 baud showed that
a window size of 2 is optimal
given a packet size greater than 32 bytes.
This means that the link bandwidth can be fully utilized
by the software.
For this reason the SRJ message is not as important as it
might otherwise be.
Therefore the
.UX
implementations no longer generate or respond to SRJ
messages.
It is mentioned here for historical accuracy only,
and one may assume that SRJ is no longer part of the protocol.
.SH
Message Exchanges
.SH
    Initialization
.PP
Messages are exchanged between four cooperating
entities: two senders and two receivers.
This means that the communication channel is thought of
as two independent half-duplex data paths.
For example the window and segment sizes need not
be the same in each direction.
.PP
Initial synchronization is accomplished
with two 3-way handshakes: two each of
INITA/INITB/INITC.
Each sender transmits INITA messages repeatedly.
When an INITA message is received, INITB is
sent in return.
When an INITB message is received
.I
and
.R
an INITB message has been sent,
an INITC message is sent.
The INITA and INITB messages carry
with them the packet and window size that
each receiver wants to use,
and the senders are supposed to comply.
When a receiver has seen all three
INIT messages, the channel is
considered to be open.
.PP
It is possible to design a protocol that starts up using
fewer messages than the interlocked handshakes described above.
The advantage of the more complicated design lies in its use as
a research vehicle:
the initial handshake sequence is completely symmetric,
a handshake
can be initiated by one side of the link while the
connection is in use, and the software to do this can
utilize code that would ordinarily be used only once
at connection setup time.
These properties were used in experiments with dynamically
adjusted parameters.
That is attempts were made to adapt the window and segment
sizes to changes observed in traffic while a link was in use.
Other experiments used the initial
handshake  in a different way
for restarting the protocol without data loss
after machine crashes.
These experiments never worked well in the packet driver and
basically provided the impetus for other protocol designs.
The result
as far as UUCP is concerned is that initial synchronization
uses the two 3-way handshakes, and the INIT
messages are ignored elsewhere.
.SH
    Data Transport
.PP
After initial synchronization each receiver
sets a modulo-8 incrementing counter R to 0;
each sender sets a similar counter S to 1.
The value of R is always the number of the most recent
correctly received packet.
The value of S is always the first sequence number in
the output window.
Let W denote window size.
Note that the value of W may be different for each sender.
.PP
A sender may transmit packets with sequence numbers
in the range S to (S+W-1)\ mod-8.
At any particular time a receiver expects
arriving packets to have numbers in the range
(R+1)\ mod-8 to (R+W)\ mod-8.
Packets must arrive in sequence number order
are are only acknowledged in order.
That is,
the `next' packet a receiver
will acknowledge must have
sequence number (R+1)\ mod-8.
.PP
A receiver acknowledges receipt of data packets
by arranging for the value of its R counter to be
sent across the channel
where it will be used to update an S counter.
This is done in two ways.
If data is flowing in both directions across a
channel then each receiver's current R value is
carried in the
.I
yyy
.R
field of non-control packets.
Otherwise when there is no bidirectional
data flow,
each receiver's R value is transmitted across the link
as the
.I
yyy
.R
field of an RR control packet.
.PP
Error handling is up to the discretion
of the receiver.
It can ignore all errors in which case
transmitter timeouts must provide for
retransmission.
The receiver may also generate RJ
error control packets.
The
.I
yyy
.R
field of an incoming RJ message replaces
the S value of the local sender and
constitutes a request for retransmission to start
at that sequence number.
The
.I
yyy
.R
field of an incoming SRJ message selects a particular
packet for retransmission.
.PP
The resemblance between the flow control procedure in the
packet driver and that defined for X.25 is no accident.
The packet driver protocol began life as an attempt at
cleaning up X.25.
That is why, for example,
control information is uniform in length (one byte),
there is no RNR message (not needed),
and there is but one timeout defined
in the sender.
.SH
    Termination
.PP
The CLOSE message is used to terminate communications.
Software on either or both ends of the communication
channel may initiate termination.
In any case when one end wants to terminate it sends
CLOSE messages until one is received from the other end
or until a programmable limit on the number of CLOSE
messages is reached.
Receipt of a CLOSE message causes a CLOSE message to be sent.
In the
.UX
environment
it also causes the SIGPIPE or
`broken pipe' signal to be sent to
the local process using the communication channel.
.SH
    Framing
.PP
The term
.I
framing
.R
is used to denote the technique by which the
beginning and end of a message is detected
in a byte stream;
.I
error control
.R
denotes the method by which transmission
errors are detected.
Strategies for framing and error control depend
upon
additional information being transmitted along
with the control byte and data segment,
and the choice of a particular strategy usually
depends on characteristics of input/output
devices and transmission media.
.PP
Several framing techniques are in used in support
of PK protocol implementations,
not all of which can be described in detail here.
The technique used on asynchronous serial lines
will be described.
.PP
A six byte
framing
.I
envelope
.R
is constructed using the control byte
C of a packet and five other bytes as
depicted below.
.in +1i
<DLE><k><c0><c1><C><x>
.in -1i
The <DLE> symbol denotes the ASCII ctrl/P character.
If the envelope is to be followed by a data segment,
<k> has the value
log\d2\u(size)-4;
i.e. 1 \(<= k \(<= 8.
If k is 9, then the envelope represents a control packet.
The <c0> and <c1> bytes are the low-order and high-order
bytes respectively of 0xAAAA minus a 16-bit checksum.
For control packets, this 16-bit checksum is the same
as the control byte C.
For data packets, the checksum is calculated by the
program below.
The <x> byte is the exclusive-or of <k><c0><c1><C>.
Error control is accomplished by checking
a received framing envelope for compliance with the definition,
and comparing a checksum function of the data segment
with <c0><c1>.
.PP
This particular framing strategy assumes data segments
are constant-sized:
the `unused' bytes in a short packet are actually
transmitted.
This creates a certain amount of overhead which
can be eliminated by a more complicated framing technique.
The advantage of this strategy is that i/o
devices can be programmed to take advantage of the
constant-sized framing envelopes and data segments.
.bp
.PP
The checksum calculation is displayed below as a C function.
Note that the code is not truly portable because
the definitions of
.I short
and
.I char
are not necessarily uniform across all machines
that might support this language.
This code assumes that
.I short
and
.I char
are 16 and 8-bits respectively.
.PP
.in +.5i
.nf
.ft CW
.ls 1
/* [Original document's version corrected to actual version] */
chksum(s,n)
register char *s;
register n;
{
    register short sum;
    register unsigned short t;
    register short x;

    sum = -1;
    x = 0;

    do {
        if (sum<0) {
            sum <<= 1;
            sum++;
        } else
            sum <<= 1;
        t = sum;
        sum += (unsigned)*s++ & 0377;
        x += sum^n;
        if ((unsigned short)sum <= t) {
            sum ^= x;
        }
    } while (--n > 0);

    return(sum);
}

.fi
.in -.5i
.ft
The checksum routine used in gnuucp has been updated to avoid depending
on the particular sizes of
.I char
and
.I short
variables.  As long as a
.I char
holds 8 bits or more, and a
.I short
holds 16 bits or more, the code will work.
To test it, uncomment the ``#define short long'' below.
A good compiler produces the same code from this function as from
the less portable version.
.PP
.in +.5i
.nf
.ft CW
.ls 1
#define    HIGHBIT16    0x8000
#define    JUST16BITS    0xFFFF
#define    JUST8BITS    0x00FF
#define    MAGIC        0125252        /* checksum is subtracted from this */

int
pktchksum(msg, bytes)
    unsigned char *msg;
    int bytes;
{
    return (JUST16BITS &
        (MAGIC - (chksum(&msg[6], bytes) ^ (JUST8BITS & msg[4]))));

}


int
chksum(s,n)
register unsigned char *s;
register n;
{
/* #define short long    /* To make sure it works with shorts > 16 bits */
    register short sum;
    register unsigned short t;
    register short x;

    sum = (-1) & JUST16BITS;
    x = 0;
    do {
        /* Rotate "sum" left by 1 bit, in a 16-bit barrel */
        if (sum & HIGHBIT16)
        {
            sum = (1 + (sum << 1)) & JUST16BITS;
        }
        else
            sum <<= 1;
        t = sum;
        sum = (sum + (*s++ & JUST8BITS)) & JUST16BITS;
        x += sum ^ n;
        if ((unsigned short)sum <= t)
            sum = (sum ^ x) & JUST16BITS;
    } while (--n > 0);

    return(sum);
#undef short        /* End of debugging check */
}
.fi
.in -.5i
.ft

Volume-Number: Volume 14, Number 13

From usenet  Tue May 17 22:37:26 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA18802; Tue, 17 May 88 22:37:26 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Access to UNIX-Related Standards
Message-Id: <[e-mail]>
Expires: 19 Jun 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 17 May 88 22:03:26 GMT
Apparently-To: std-unix-archive
Status: O

This is the latest in a series of similar comp.std.unix articles.
Corrections and additions to this article are solicited.

There are two companion articles, posted at the same time as this one
and with subjects ``Access to UNIX User Groups and Publications'' and
``Calendar of UNIX-related Events.''

Also note that Shane McCarron now writes a quarterly summary report for
USENIX soon after each IEEE 1003 meeting for posting in comp.std.unix
and in ;login:, the Newsletter of the USENIX Association.

Changes from last posting:
Dates for ANSI X3J11 and ISO TC97/SC22/WG14 added from an article
by Cornelia Boldyreff in the EUUG Newsletter, Vol. 7, No. 4, Winter 1987.

Access information is given in this article for the following standards:
IEEE 1003.1 (operating system interface), 1003.2 (shell and tools),
    1003.3 (testing and verification), 1003.4 (real time),
    1003.5 (ADA binding), 1003.6 (security), 1003.0 (POSIX guide).
NBS FIPS.
/usr/group Technical Committee Subcommittees on distributed file system,
    network interface, graphics/windows, database, internationalization,
    performance measurements, realtime, security, and super computing.
X3H3.6 (display committee)
X3J11 (C language)
/usr/group 1984 Standard
System V Interface Definition (SVID, or The Purple Book)
X/OPEN PORTABILITY GUIDE (The Green Book)
4.3BSD Manuals


UNIX is a Registered Trademark of AT&T.
IEEE is a trademark of the Institute of Electrical and Electronic Engineers,
    Inc.:  POSIX is no longer a trademark.
X/OPEN is a licensed trademark of the X/OPEN Group Members.


The IEEE P1003 Portable Operating System Interface for Computer
Environments Committee is sometimes known colloquially as the UNIX
Standards Committee.  They published the 1003.1 "POSIX" Trial Use
Standard in April 1986.  According to its Foreword:

    The purpose of this document is to define a standard
    operating system interface and environment based on the
    UNIX Operating System documentation to support application
    portability at the source level.  This is intended for
    systems implementors and applications software developers.

Published copies are available at $19.95, with bulk purchasing discounts
available.  Call the IEEE Computer Society in Los Angeles

        714-821-8380

and ask for Book #967.  Unfortunately, this only works for multiple copies.
But the following mail address works for single copies:

        IEEE Computer Society
        P.O. Box 80452
        Worldway Postal Center
        Los Angeles, Ca. 90080

Include a check for $19.95 + $4 for shipping and handling.  For UPS
shipping, add another $4.  Or contact:

        IEEE Service Center
        445 Hoes Ln.
        Piscataway, NJ 08854

and ask for "IEEE 1003.1 Trial Use Standard" - stock number SH10546.

The Trial Use Standard will be available for comments for a period such
as a year.  The current target for a Full Use Standard is Summer 1988.
Initial balloting is completed, and ballot resolution is in progress:
it's too late to ballot if you haven't already.


IEEE has brought the 1003.1 effort brought into the International
Organization for Standardization (ISO) arena.  IEEE 1003.1 Draft 12
is also a ``Draft Proposed International Standard (ISO DP)'' under
SC22 WG15.  The convenor is Jim Isaak:  see below for his address.
There is a U.S. Technical Advisory Group (TAG) to ISO SC22 WG15:
the chair is Donn Terry of HP.

The National Bureau of Standards is producing a Federal Information
Processing Standard (FIPS) based on IEEE 1003.1.  It will probably
be available before the Full Use Standard, and may reflect Draft 12,
rather than the final 1003.1 standard.  For information, contact:

        Roger Martin
        National Bureau of Standards
        Building 225
        Room B266
        Gaithersburg, MD  20899
        [phone]

NBS is also producing a FIPS based on IEEE 1003.2, probably from
the draft made by 1003.2 at their March meeting.


Machine readable copies of the IEEE 1003.1 Trial Use Standard are not
and will not be available.  The same applies to copies of later drafts.

There is a paper mailing list by which interested parties may get
copies of drafts of the standard.  To get on it, or to submit comments
directly to the committee, mail to:

        James Isaak
        Chairperson, IEEE/CS P1003
        Tel.: [phone]
        Fax.: [phone]
        decvax!isaak
        [e-mail]
        Digital Equipment
        ZK03-3/Y25
        110 Spit Brook Rd.
        Nashua, NH  03062-2698

Sufficiently interested parties may join the working group.

The term POSIX actually applies to all of the P1003 subcommittees:
group    subject                co-chairs
1003.0    POSIX Guide            Al Hankinson (NBS), Kevin Lewis (DEC)
1003.1    Systems Interface        Jim Isaak (DEC), Donn Terry (HP)
1003.2    Shell and Tools Interface    Hal Jespersen (UniSoft), Don Cragun (Sun)
1003.3    Verification and Testing     Roger Martin (NBS), Carol Raye (AT&T)
1003.4    Real Time             Bill Corwin (Intel)
1003.5    Ada Binding for POSIX        Terry Fong (USArmy), Stowe Boyd(Compass)
1003.6    Security            Dennis Steinauer (NBS), Ron Elliot (IBM)

Inquiries regarding any of the subcommittees should go to the same address
as for 1003.1.


The next scheduled meetings of the P1003 working groups are:

1988 June 20-24        IEEE 1003.6 at USENIX, in San Francisco, CA
1988 July 11-15        Tech Center Hyatt, Denver, CO
1988 October 17-19,20-21 ISO SC22 Advisory Group & WG15 - Tokyo, Japan
1988 October 24-28    Hawaii

1989 January 9-13    Embassy Suites, Ft. Lauderdale, FL
1989 April 17(29?)    Minneapolis-St. Paul, MN
1989 July 10-14        San Francisco, CA
1989 October 16-20    Brussels (or Amsterdam) (Thought: EC host)

1990 January 29        New Orleans, LA
1990 April        Montreal, Quebec

Here are some details from Hal Jespersen regarding P1003.2:

The IEEE P1003.2 "Shell and Utilities" Working Group is developing a
proposed standard to complement the 1003.1 POSIX standard.  It will
consist of

    a shell command language (currently planned to be based on the
    Bourne Shell),

    groups of utility programs, or commands,

    programmatic interfaces to the shell (system(), popen()) and
    related facilities (regular expressions, file name expansion,
    etc.)

    defined environments (variables, file hierarchies, etc) that
    applications may rely upon

    utilities for installing application programs onto conforming
    systems

which will allow application programs to be developed out of existing
pieces, in the UNIX tradition.  The scope of the standard emphasizes
commands and features that are more typically used by shell scripts or
C language programs than those that are oriented to the terminal user
with windows, mice, visual shells, and so forth.

There has been some controversy in the Working Group about clarifying
the scope of the 1003.2 standard in regard to its relationship with
1003.1.  The Working Group is attempting to produce a standard that
will assume the structure and philosophy of a POSIX system is
available, but it will not require a fully conforming implementation as
a base.  For example, it should be feasible to eventually produce a
1003.2 interface on a V7 system, or on a system very close to POSIX,
but missing a few crucial features (as long as the shell and utilities
didn't need them).  However, the proposed standard will *not* be
unnecessarily watered down simply to allow non-POSIX systems to conform.

The group is currently seeking proposals for groupings of commands that
may be offered by implementors.  As groups are identified, command
descriptions will be solicited.  There is no requirement that the commands
be in System V or BSD today, but they should realistically be commands
that are commonly found in most existing implementations.


There are three Institutional Representatives to P1003:  John Quarterman
from USENIX, Heinz Lycklama from /usr/group, and Mike Lambert from X/OPEN.
The two from USENIX and /usr/group are also representatives to the U.S.
TAG to ISO SC22 WG15.

As the one from USENIX, one of my functions is to get comments from the
USENIX membership and the general public to the committee.  One of the
ways I try to do that is by moderating this newsgroup, comp.std.unix
An article related to this one appeared in the September/October 1986
;login: (The USENIX Association Newsletter).  I'm also currently on the
USENIX Board of Directors.  Comments, suggestions, etc., may be sent to

        John S. Quarterman
        Texas Internet Consulting
        701 Brazos, Suite 500
        Austin TX 78701-3243
        [phone]
        uunet!usenix!jsq
        [e-mail]

For comp.std.unix:
Comments:    uunet!std-unix-request [e-mail]
Submissions:    uunet!std-unix        [e-mail]

The November/December 1987 issue of CommUNIXations (the /usr/group magazine)
contains a report by Heinz Lycklama on the /usr/group Technical Committee
working groups which met in June 1987.

If you are interested in starting another /usr/group working group, contact
Heinz Lycklama:

        Heinz Lycklama
        Interactive Systems Corp.
        2401 Colorado Ave., 3rd Floor
        Santa Monica, CA 90404
        [phone]
        decvax!cca!ima!heinz


Here is contact information for /usr/group working groups as taken from
the CommUNIXations article mentioned above.

/usr/group Working Group on Distributed File System:
    Art Sabsevitz            Frederick Glover
    AT&T Information Systems    MK02-1/H10
    190 River Road            Digital Equipment Corporation
    Summit, NJ  07933        Continental Boulevard
    201-522-6248            Merrimack, NH  03054-0430
    attunix!bump            603-884-5111
                    decvax!fglover

/usr/group Working Group on Network Interface:
    Steve Albert
    AT&T Information Systems
    190 River Road, Rm. A-114
    Summit, NJ  07901
    [phone]
    attunix!ssa

/usr/group Working Group on Internationalization:
    John Wu                Laurie Goudie
    Charles River Data Systems    Santa Cruz Operation
    983 Concord St.,        400 Encinal
    Framingham, MA 01701        Santa Cruz, CA 95060
    617-626-1000            408-458-1422

/usr/group Working Group on Graphics/Windows:
    Tom Greene
    Apollo Computer, Inc.
    330 Billerica Road
    Chelmsford, MA  01824
    [phone], ext. 7581

/usr/group Working Group on Realtime:
    Bill Corwin
    Intel Corp.
    5200 Elam Young Pkwy
    Hillsboro, OR 97123
    [phone]

/usr/group Working Group on Database:
    Val Skalabrin
    Unify Corp.
    1111 Howe Ave.
    Sacramento, CA 95825
    [phone]


/usr/group Working Group on Performance Measurements:
    Ram Chelluri            Dave Hinnant
    AT&T Computer Systems        SCI Systems, Inc.
    Room E15B            Ste 325, Pamlico Bldg
    4513 Western Ave.        Research Triangle Pk, NC 27709
    Lisle, IL 60532            [phone]
    [phone]

/usr/group Working Group on Security:
    Steve Sutton            Ms. Jeanne Baccash
    Consultant, Addamax        AT&T UNIX Systems Engineering
    1107 S. Orchard            190 River Road
    Urbana, IL  61801        Summit, NJ  07901
    217-344-0996            201-522-6028
                    attunix!jeanne

/usr/group Working Group on Super Computing:
    Karen Sheaffer            Robin O'Neill
    Sandia National Laboratory    Lawrence Livermore Laboratory
    P.O. Box 969            P.O. Box 5509, L560
    Livermore, CA  94550        Livermore, CA  94550
    415-422-3431            415-422-0973
                    oneill#[e-mail]


The X3H3.6 display management committee has recently formed to develop
a model to support current and future window management systems, yet
is not based directly on any existing system.  The chair solicits
help and participation:

        Georges Grinstein
        wanginst!ulowell!grinstein


The Abstract of the 1003.1 Trial Use Standard adds:

    This interface is a complement to the C Programming Language
    in the C Information Bulletin prepared by Technical Committee X3J11
    of the Accredited Standards Committee X3, Information Processing
    Systems, further specifying an environment for portable application
    software.

X3J11 is sometimes known as the C Standards Committee.  Their liaison to
P1003 is

        Don Kretsch
        AT&T
        190 River Road
        Summit, NJ 07901

A contact for information regarding publications and working groups is

        Thomas Plum
        Vice Chair, X3J11 Committee
        Plum Hall Inc.
        1 Spruce Avenue
        Cardiff, New Jersey 08232

The current document may be ordered from

        Global Engineering Documents
        2805 McGaw
        Irvine, CA 92714
        USA
        [phone]
        [phone]

Ask for the X3.159 draft standard.  The price is $65.

The current X3J11 meeting schedule is:

1988 June 13-14        London, England        ISO TC97/SC22/WG14
1988 August 15-19    Cupertino, CA
1988 December 12-16    Seattle, WA
1989 April 10-11    Phoenix, AZ


The /usr/group Standard is a principal ancestor of P1003.1, X/OPEN,
and X3J11.  It may be ordered for $15.00 from:

        /usr/group Standards Committee
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        Tel: [phone]
        Fax: [phone]

/usr/group also publishes an eight page document, ``Your Guide to POSIX,''
explaining what IEEE 1003 is, and a nineteen page document, ``POSIX Explored,''
about technical aspects of IEEE 1003.1, and its relations to other standards
and historical implementations.  Contact /usr/group at the above address
for details.


The System V Interface Definition (The Purple Book, or SVID).
This is the AT&T standard and is one of the most frequently-used
references of the IEEE 1003 committee.

        AT&T Customer Information Center
        Attn:  Customer Service Representative
        P.O. Box 19901
        Indianapolis, IN 46219
        U.S.A.

        800-432-6600 (Inside U.S.A.)
        800-255-1242 (Inside Canada)
        317-352-8557 (Outside U.S.A. and Canada)

    System V Interface Definition, Issue 2
    should be ordered by the following select codes:

    Select Code:    Volume:        Topics:
    320-011        Volume I    Base System
                    Kernel Extension
    320-012        Volume II    Basic Utilities Extension
                    Advanced Utilities Extension
                    Software Development Extension
                    Administered System Extension
                    Terminal Volume Interface Extension
    320-013        Volume III    Base System Addendum
                    Terminal Interface Extension
                    Network Services Extension
    307-131        I, II, III    (all three volumes)

The price is about 37 U.S. dollars for each volume or $84 for all three.
Major credit cards are accepted for telephone orders:  mail orders
should include a check or money order, payable to AT&T.


The X/OPEN PORTABILITY GUIDE (The Green Book)
is another reference frequently used by IEEE 1003.

The X/OPEN Group is "Ten of the world's major information system
suppliers" (at time of publication, Bull, DEC, Ericsson, Hewlett-Packard,
ICL, NIXDORF, Olivetti, Philips, Siemens and Unisys and subsequently
augmented by AT&T) who have produced a document intended to promote
the writing of portable applications.  They closely follow both SVID
and POSIX, and cite the /usr/group standard as contributing, but
X/OPEN's books cover a wider area than any of those.

The book is published by

        Elsevier Science Publishers B.V.
        Book Order Department
        P.O. Box 1991
        1000 BZ Amsterdam
        The Netherlands

and distributed in the U.S.A. and Canada by:

        Elsevier Science Publishing Company, Inc.
        52 Vanderbilt Avenue
        New York, NY 10017
        U.S.A.

There are currently five volumes:
    1) System V Specification Commands and Utilities
    2) System V Specification System Calls and Libraries
    3) System V Specification Supplementary Definitions
    4) Programming Languages
    5) Data Management

They take a large number of credit cards and other forms of payment.

Comments, suggestions, error reports, etc., for Issue 2 of the Green Book
may be mailed directly to:

        [e-mail]
        uunet!mcvax!inset!xopen!xpg2

Information about X/OPEN can be requested from:

        Mike Lambert
        Technical Director
        X/OPEN Ltd
        c/o ICL BRA01
        Lovelace Road
        Bracknell
        Berkshire
        England
        [phone]
        [e-mail]
        uunet!mcvax!inset!xopen!mgl


Finally, 4.2BSD and 4.3BSD have influenced POSIX in a number of areas.
The best reference on them is the 4.3BSD manuals, published by USENIX.
An order form may be obtained from:

        Howard Press
        c/o USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710

        415-528-8649
        {ucbvax,decvax}!usenix!office

4.3BSD User's Manual Set (3 volumes)        $25.00
    User's Reference Manual
    User's Supplementary Documents
    Master Index

4.3BSD Programmer's Manual Set (3 volumes)    $25.00
    Programmer's Reference Maual
    Programmer's Supplementary Documents, Volume 1
    Programmer's Supplementary Documents, Volume 2

4.3BSD System Manager's Manual (1 volume)    $10.00

Unfortunately, there are some license restrictions.
Contact the USENIX office for details.

Volume-Number: Volume 14, Number 14

From usenet  Tue May 17 23:13:05 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA21196; Tue, 17 May 88 23:13:05 EDT
From: <[e-mail]>
Newsgroups: comp.std.unix,comp.unix.questions,comp.org.usenix
Subject: Access to UNIX User Groups and Publications
Message-Id: <[e-mail]>
Expires: 19 Jun 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 17 May 88 22:09:18 GMT
Apparently-To: std-unix-archive
Status: O

This is the latest in a series of similar comp.std.unix articles,
intended to give summary information about UNIX User groups
and publications; to be accurate, but not exhaustive.
I'm cross-posting it to comp.org.usenix and comp.unix.questions
because there might be interest there.

There are two related articles, posted at the same time as this one,
and with subjects ``Calendar of UNIX-related Events'' and ``Access to
UNIX-Related Standards.''  The latter is posted only to comp.std.unix.

Corrections and additions to this article are solicited.  I keep track
of the conferences, groups, and publications that I attend, am a member
of, or subscribe to.  All others (the majority of the listings) I derive
either from listings elsewhere, or from contributions by readers.
In particular, the meeting schedules and descriptions of most of the
groups are provided by their members.  If a group doesn't have a
meeting schedule listed, it's because nobody has sent me one.  This is
a low-budget operation:  I publish what I have on hand when the time
comes (approximately monthly).

Recent additions:  AT&T Technical Journal, Byte, The C Users Journal, Unique.


Access information is given in this article for the following:
user groups:    USENIX, /usr/group, EUUG, AUUG, NZUSUGI, JUS, KUUG, AMIX,
        DECUS UNIX SIG, Sun User Group, Apollo DOMAIN Users' Society
newsletters:    ;login:, /usr/digest, EUUGN, AUUGN, NUZ
journal:    Computing Systems
magazines:    CommUNIXations, UNIX REVIEW, UNIX/WORLD,
        Multi-User Computing Magazine, UNIX Systems, UNIX Magazine

Telephone numbers are given in international format, i.e., +n at
the beginning for the country code, e.g., +44 is England, +81 Japan,
+82 Korea, +61 Australia, +64 New Zealand, and +1 is U.S.A. or Canada.

UNIX is a Registered Trademark of AT&T.


USENIX is ``The Professional and Technical UNIX(R) Association.''

        USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710
        U.S.A.
        [phone]
        {uunet,ucbvax,decvax}!usenix!office
        [e-mail]

USENIX sponsors two USENIX Conferences a year, featuring technical papers,
as well as tutorials, and with vendor exhibits at the summer conferences:

    Jun 20-24 1988    Hilton Hotel, San Francisco, CA
    Jan 31-Feb 3 1989 Town & Country Inn, San Diego, CA
    Jun 12-16 1989    Hyatt Regency, Baltimore, MD
    Jan 23-26 1990    Washington, DC
    Jun 11-15 1990    Marriott Hotel, Anaheim, CA
    Jan 22-25 1991    Dallas, TX
    Jun 10-14 1991    Opryland, Nashville, TN

They also sponsor workshops, such as
    May 12-13 1988    Omni Shoreham Hotel, Washington, DC
        Fifth Workshop on Real-Time Software and Operating Systems
        IEEE Computer Society and USENIX Association
    Aug 29-30 1988    UNIX Security, Portland, OR
    Sep 26-27 1988    UNIX & Supercomputing, Pittsburgh, PA
    Oct 17-20 1988    C++ Conference (tentative), Denver, CO
    Nov 17-18 1988    Large Installation System Administration II, Monterey,CA

Proceedings for all conferences and workshops are available at
the door and by mail later.

USENIX publishes ``;login:  The USENIX Association Newsletter''
bimonthly.  It is sent free of charge to all their members and
includes technical papers.  There is a USENET newsgroup,
comp.org.usenix, for discussion of USENIX-related matters.

In 1988, USENIX started publishing a new refereed quarterly
technical journal, ``Computing Systems:  The Journal of the USENIX
Association,'' in cooperation with University of California Press.

They also publish an edition of the 4.3BSD manuals, and they
occasionally sponsor experiments, such as methods of improving the
USENET and UUCP networks (e.g., uunet), that are of interest and use to
the membership.  They distribute tapes of contributed software and are
pursuing expanding that activity.

There is a USENIX Institutional Representative on the IEEE P1003
Portable Operating System Interface for Computer Environments Committee.
That representative also moderates the USENET newsgroup comp.std.unix,
which is for discussion of UNIX-related standards, especially P1003.
For more details, see the posting in comp.std.unix, ``Access to
UNIX-Related Standards.''


/usr/group is a non-profit trade association dedicated to the promotion
of products and services based on the UNIX operating system.

        /usr/group
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        U.S.A.
        tel: [phone]
        fax: [phone]

The annual UniForum Conference and Trade Show is sponsored by /usr/group
and features vendor exhibits, as well as tutorials and technical sessions.

    Feb 28-Mar 3 1989 Moscone Center, San Francisco, CA
    Jan 23-26 1990    Washington Hilton, Washington, DC
    Jan 22-25 1991    Infomart, Dallas, TX
    Jan 21-24 1992    Moscone Center, San Francisco CA (tentative)

They also sponsor a regional show, UniForum D.C.:

    Aug 2-4 1988    Washington Hilton Hotel, Washington, D.C.

Proceedings for all conferences are available at the shows and later
by mail.

/usr/group publishes ``CommUNIXations,'' a member magazine that
features articles by industry leaders and observers, technical issues,
standards coverage, and new product announcements.

/usr/group also publishes the ``UNIX Products Directory,'' which lists
products and services developed specifically for the UNIX operating system.
``/usr/digest'' is also published by /usr/group.  This newsletter covers
product announcements and industry projections, and is sent biweekly
to General members of /usr/group and to non-member subscribers.

/usr/group has long been deeply involved in UNIX standardization,
having sponsored the ``/usr/group 1984 Standard,'' providing an Institutional
Representative to the IEEE P1003 Portable Operating System for Computer
Environments Committee, and sponsoring the /usr/group Technical Committee
on areas that P1003 has not yet addressed.  They have recently produced
an executive summary, ``Your Guide to POSIX,'' and a technical overview
``POSIX Explored,'' and funded production of a draft of a ``Rationale and
Notes'' appendix for IEEE 1003.1.


EUUG is the European UNIX systems Users Group, which is currently
celebrating its tenth anniversary.  EUUG is closely coordinated with
national groups in Europe, and with the European UNIX network, EUnet.

        EUUG secretariat
        Owles Hall
        Buntingford
        Herts SG9 9PL
        England
        Telephone [phone]
        Telefax [phone]
        uunet!mcvax!inset!euug
        [e-mail]

They have a newsletter, EUUGN (a previous version of this article
appeared in the latest one), and hold two conferences a year:
    3-7 October 1988, Lisbon, Portugal
    April 1989, Brussels, Belgium


AUUG is the Australian UNIX systems Users Group.

        AUUG
        P.O. Box 366
        Kensington
        N.S.W.    2033
        Australia
        uunet!munnari!auug
        [e-mail]

Phone contact can occasionally be made at [phone]

AUUG holds at least one conference a year, usually in the spring
(August or September).  The next one will be in Melbourne on 13-15
September 1988, will be the first three day meeting, will have a larger
equipment exhibition than any before, and will be professionally
organized for the first time.

They publish a newsletter (AUUGN) at a frequency defined to be every 2 months.


The New Zealand UNIX Systems User Group, Inc. (NZUSUGI) has an annual meeting
and publishes a newsletter, ``NUZ.''

        New Zealand UNIX Systems User Group
        P.O. Box 585
        Hamilton
        New Zealand
        [phone]

The next and fifth annual meeting is the New Zealand UNIX Systems User Group
(NZUSUGI) 1988 Conference, June 9-11 1988, in Wellington, New Zealand.

If you wish to present a paper, acceptance of which entitles you to a free
conference registration, please contact the local speakers organiser,
Dr Dick Cooper, ADATA, PO Box 2555, Christchurch, New Zealand,
[e-mail]   or ...uunet!vuwcomp!cantuar!dick

If you would just like to attend, please respond to Ray Brownrigg, including
a postal address for the delivery of further information as it becomes
available.  Registration forms are expected to be available in February.

        UUCP: {utai!calgary,uunet}!vuwcomp!dsiramd!ray
        ACSnet:    [e-mail][@munnari]
        Ray Brownrigg
        Applied Maths Div, DSIR
        PO Box 1335
        Wellington
        New Zealand


The Korean UNIX User Group (KUUG) has a software distribution service
and a newsletter.

        Korean UNIX User Group
        ETRI
        P.O. Box 8
        Daedug Science Town
        Chungnam 300-32
        Republic of Korea
        [phone]


The Japan UNIX Society has two meetings a year, and a newsletter.

        Japan UNIX Society
        #505 Towa-Hanzomon Corp. Bldg.
        2-12 Hayabusa-cho
        Chiyoda-ku, Tokyo 102
        Japan
        [phone]


AMIX - the Israeli UNIX user group, is a S.I.G. of the Israeli Processing
Association (IPA). AMIX has a yearly conference (next one on 4-6 July 1988)
and a yearly workshop (last one was in November).

        AMIX, c/o IPA
        P.O. Box 919
        Ramat-Gan
        Israel, 52109
        Tel: [phone],715772
        [e-mail]
        [e-mail]


There are similar groups in other parts of the world.  If such a group
wishes to be included in later versions of this access list, they
should please send me information.

There is a partial list of national organizations in the November/December
1987 CommUNIXations.



DECUS, the Digital Equipment Computer Users Society,
has a UNIX SIG (Special Interest Group) that participates
in its general meetings, which are held twice a year.

        DECUS U.S. Chapter
        219 Boston Post Road, BP02
        Marlboro, Massachusetts  01752-1850
        U.S.A.
        [phone]

The next two DECUS Symposia are:

    May 16-20, 1988        Cincinnati, Ohio
    Oct 17-21, 1988        Anaheim, California

See also the USENET newsgroup comp.org.decus.


The Sun User Group (SUG) is an international organization that promotes
communication among Sun users, OEMs, third party vendors, and Sun
Microsystems, Inc.  SUG sponsors conferences, collects and distributes
software, produces the README newsletter and T-shirts, sponsors local
user groups, and communicates members' problems to Sun employees and
management.

    Sun Microsystems User Group, Inc.
    2550 Garcia Avenue
    Mountain View, CA  94043
    U.S.A.
    [phone]
    [e-mail]
    sun!users

They have not set a date/location for the 1988 conference yet, but are
actively looking for a hotel (with good pricing and lots of room).
They've narrowed it down to several locations - Miami/Tampa Florida,
Houston/Dallas Texas, and New Orleans LA.  The date will probably be
very early December, 1988.


ADUS is the Apollo DOMAIN Users' Society:

    Apollo DOMAIN Users' Society
    c/o Andrea Woloski, ADUS Coordinator
    Apollo Computer Inc.
    330 Billerica Rd.
    Chelmsford, MA 01824
    [phone], x4448


The main general circulation (more than 10,000 copies per issue) magazines
specifically about the UNIX system are:

    UNIX REVIEW            UNIX/WORLD
    Miller Freeman Publications Co.    Tech Valley Publishing
    500 Howard Street        444 Castro St.
    San Francisco, CA 94105        Mountain View, CA 94041
    U.S.A.                U.S.A.
    monthly                monthly
    [phone]            [phone]

    Multi-User Computing magazine    UNIX Systems
    Storyplace Ltd.            Eaglehead Publishing Ltd.
    42 Colebrook Row        Maybury Road
    London  N1 8AF            Woking, Surrey GU21 5HX
    England                England
    [phone]            [phone]

    UNIX Magazine
    Jouji Ohkubo
    c/o ASCII Corp.
    [e-mail]
    [phone]
    fax: [phone]
    telex: 242-6875 ASCIIJ

Some of the above information about magazines was taken from the
November/December 1987 issue of CommUNIXations, which also lists
some smaller-circulation magazines and newsletters.

In addition, there is the Journal of the USENIX Association and
the /usr/group member magazine:

    Computing Systems        CommUNIXations
    USENIX Association        /usr/group
    P.O. Box 2299            4655 Old Ironsides Drive, Suite 200
    Berkeley, CA 94710        Santa Clara, California 95054
    U.S.A.                U.S.A.
    quarterly            bimonthly
    [phone]            [phone]


Finally, Dominic Dunlop <[e-mail]> has pointed out several
publications that frequently include articles about the UNIX system or
the C language.  I've listed them below; the comments after each entry
are his.  I have excluded listings of magazines about specific hardware.

    AT&T Technical Journal
    AT&T Bell Laboratories
    Circulation Dept.
    Room 1K-424
    101 J F Kennedy Parkway
    Short Hills, NJ 07078
    Bimonthly
    $40/yr (US); $50/yr (overseas)
    [phone]
    While few issues are devoted to UNIX,
    most turn out to mention its applications.

    Byte
    McGraw-Hill Inc.
    Phoenix Mill Lane
    Peterborough, NH 03458
    Monthly
    $22/yr (US); $25/yr(Mex,Can); $37/yr (surface); $69/yr (air,Europe)
    [phone]
    Concentrates mainly on personal computers,
    but covers low end of UNIX market in some depth.

    The C Users Journal
    ``A service of the C Users Group.''
    R&D Publications Inc
    PO Box 97
    McPherson, KS 67460
    Eight issues per year
    $20/yr (US/Mex/Can); $30/yr (overseas)
    [phone]
    Mainly DOS-oriented; some UNIX.

    Unique
    ``The UNIX System Information Source.''
    Infopro Systems
    PO Box 220
    Rescue, CA 95672
    Monthly
    $79/yr (US,overseas); $99/yr (air)
    [phone]
    High-quality industry newsletter.
    Emphasis on marketing implications of technical developments.


The following information about bookstores was taken from the
November/December 1987 issue of CommUNIXations.  In the interests of
space, I have arbitrarily limited the selection listed here to those
bookstores or suppliers specifically dedicated to computer books, and
not part of other organizations.

    Computer Literacy Bookshop    UNIX Book Service
    2590 No. First St.        35 Bermuda Terrace
    San Jose, CA 95131        Cambridge, CB4 3LD
    U.S.A.                England
    [phone]        [phone]

    Cucumber Bookshop        Jim Joyce's UNIX Book Store
    5611 Kraft Ave.            47 Potomac St.
    Rockville, MD 20852        San Francisco, CA 94117
    U.S.A.                U.S.A.
    [phone]            [phone]

Volume-Number: Volume 14, Number 15

From usenet  Tue May 17 23:17:15 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA21585; Tue, 17 May 88 23:17:15 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix,comp.unix.questions,comp.org.usenix
Subject: Calendar of UNIX-related Events
Message-Id: <[e-mail]>
Expires: 19 Jun 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail] (Moderator, John S. Quarterman)
Date: 17 May 88 22:17:01 GMT
Apparently-To: std-unix-archive
Status: O

Here is a combined calendar of planned conferences, workshops, or
standards meetings by various organizations.  I compiled it for
my own use and thought it might be of some public interest.  Most
of this information came from the various conference organizers,
although some was taken from ;login: (USENIX), 13, 1, Jan/Feb
1988 and CommUNIXations (/usr/group), VII, 6, Nov/Dec 1987.

If your favorite meeting is not listed, it's probably because I
don't know about it.  If you send me information on it, I will
probably list it both here and in the companion article, ``Access
to UNIX User Groups and Publications.'' There is also another
companion article, ``Access to UNIX-Related Standards,'' that
appears only in comp.std.unix.

Abbreviations: U for UNIX, W for Workshop, S for Symposium, C for
Center.  The sponsors of the USENIX, EUUG, AUUG and DECUS
conferences are the organizations of the same names, and the
sponsor of UniForum is /usr/group.  Dates and places for IEEE
1003 after Oct 1988 are tentative, and also for the 1992 UniForum.

Changes since last posting: Dates for ANSI X3J11 and ISO
TC97/SC22/WG14 added from an article by Cornelia Boldyreff,
in the EUUG Newsletter Vol. 7, No. 4, Winter 1987.

year mon days          conference        (sponsor,) (hotel,) location

1988 May 3-5           U Exposition      AFUU, Palais des Congress, Paris
1988 May 12-13         Real-Time W       USENIX/IEEE, Omni Shoreham, Washington
1988 May 16-20         DECUS S           Cincinnati, Ohio
1988 May 17-19         UNIX 88/etc.      /usr/group/cdn, Convention C, Toronto
1988 Jun 7-9           COMUNIX           /usr/group/UK, Alexandra Palace, London
1988 Jun 9-11          NZSUGI            Wellington, New Zealand
1988 Jun 13-14         C Standard        ISO TC97/SC22/WG14, London, England
1988 Jun 20-24         USENIX            Hilton, San Francisco, CA
1988 Jun 20-24         IEEE 1003.6       at USENIX, in San Francisco, CA

1988 Jul               U Symposium       JUS, Tokyo, Japan
1988 Jul 4-6           AMIX              Israel
1988 Jul 11-15         IEEE 1003         Tech Center Hyatt, Denver, CO
1988 Aug 2-4           UniForum/DC       Washington Hilton, Washington, DC
1988 Aug 15-19         ANSI X3J11        Cupertino, CA
1988 Aug 29-30         U Security W      USENIX, Portland, OR
1988 Sep 13-15         AUUG              Melbourne, Australia
1988 Sep 26-27         U&Supercomp. W    USENIX, Pittsburgh, PA
1988 Oct 3-7           EUUG              Lisbon, Portugal
1988 Oct 17-21         DECUS S           Anaheim, California
1988 Oct 17-21         C++ Conference    USENIX, Denver, CO
1988 Oct 17-19,20-21   ISO SC22 & WG15   Tokyo, Japan
1988 Oct 24-28         IEEE 1003         Hawaii
1988 Oct               UNIX Expo         New York, NY
1988 Nov 17-18         Large Install.    Syst. Adm. W II, USENIX, Monterey, CA
1988 Nov               U Symposium       JUS, Osaka, Japan
1988 Dec               Sun User Group    southern U.S.A.
1988 Dec               UNIX Fair         JUS, Tokyo, Japan
1988 Dec 12-16         ANSI X3J11        Seattle, WA

1989 Jan 9-13          IEEE 1003         Embassy Suites, Ft. Lauderdale, FL
1989 Jan 31-Feb 3      USENIX            Town and Country, San Diego, CA
1989 Feb 28-Mar 3      UniForum          Moscone Center, San Francisco, CA
1989 Apr 10-11         ANSI X3J11        Phoenix, AZ
1989 Apr 17(29?)       IEEE 1003         Minneapolis-St. Paul, MN
1989 Apr               EUUG              Brussels, Belgium
1989 Jun 12-16         USENIX            Hyatt Regency, Baltimore, MD
1989 Jul 10-14         IEEE 1003         San Francisco, CA
1989 Oct 16-20         IEEE 1003         Brussels (or Amsterdam)
1989 Oct               UNIX Expo         New York, NY

1990 Jan 23-26         USENIX            Washington, DC
1990 Jan 23-26         UniForum          Washington Hilton, Washington, DC
1990 Jan 29            IEEE 1003         New Orleans, LA
1990 Apr               IEEE 1003         Montreal, Quebec
1990 Jun 11-15         USENIX            Marriott, Anaheim, CA

1991 Jan 22-25         USENIX            Dallas, TX
1991 Jan 22-25         UniForum          Infomart, Dallas, TX
1991 Jun 10-14         USENIX            Opryland, Nashville, TN

1992 Jan 21-24         UniForum (?)      Moscone Center, San Francisco CA

Volume-Number: Volume 14, Number 16

From usenet  Fri May 20 16:35:31 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA13828; Fri, 20 May 88 16:35:31 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Open Software Foundation
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 18 May 88 21:40:52 GMT
Apparently-To: std-unix-archive
Status: O

[ Someone forwarded this to me.  It looks like a good opener for a discussion
on the Open Software Foundation. -mod ]

In comp.unix.wizards [e-mail] (William Sommerfeld) writes:

This is a typed-in copy of a press release I got this afternoon.
I am not responsible for typing errors, but I think I was fairly
careful.

                    Bill Sommerfeld
                    [e-mail]

FOUNDATION CONTACT: Deborah Siegel
            Cohn & Wolfe
            [phone]
... Apollo, Groupe Bull, Digital Equipment, Hewlett-Packard, IBM,
Nixdorf, Siemens ...

        NEW FOUNDATION TO ADVANCE SOFTWARE STANDARDS,
        DEVELOP AND PROVIDE OPEN SOFTWARE ENVIRONMENT

NEW YORK, N.Y., May 17, 1988---Seven leading computer companies today
announced an international foundation to develop and provide a
completely open software environment to make it easier for customers
to use computers and software from many vendors.

The Open Software Foundation (OSF) will develop a software
environment, including application interfaces, advanced system
extensions, and a new operating system, using X/Open(tm) and POSIX*
specifications as the starting point.  POSIX is an operating system
standard, closely related to the UNIX(tm) system, that specifies how
software should be written to run on computers from different vendors.

Initial funding for OSF is being provided by the following sponsors:
Apollo Computer Inc., Groupe Bull, Digital Equipment Corporation,
Hewlett-Packard Company, International Business Machines Corporation,
Nixdorf Computer AG, and Siemens Aktiengesellschaft.  OSF membership
is available to computer hardware and software suppliers, educational
institutions, and government agencies around the world.

The foundation has a management organization, staff, and a funding
comittment in excess of $90 million to begin immediate operations.
Its initial development will be based on technologies offered by the
members and its own research, to be carried out worldwide.

"The creation of a standard software enviornment is one of the most
important issues facing the computer industry today," said John L.
Doyle, chairman of the foundation board of directors.  "Establishing
this international foundation fulfills the critical need for an open,
rational, and equitable process to help establish the standards our
customers demand and to protect their long-term software investment."

Foundation Principles:

OSF is incorporated as a non-profit, industry-supported research and
development organization.  It will define specifications, develop a
leadership operating system, and promote an open, portable
applications environment.

Principles of the foundation include:

 * Offerings based on relevant industry standards;
 * Open process to actively solicit inputs and technology;
 * Timely, vendor-neutral decision process;
 * Early and equal access to specifications and continuing
   development;
 * Hardware independant applications;
 * Reasonable, stable licensing terms;
 * Technical innovation through university/research participation.

To support its portable application environment, the foundation will
provide software that makes it easier for users to mix and match
computers and appllications from different suppliers by addressing the
following needs:
 * Portability---the ability to use application software on computers
   from multiple vendors.
 * Interoperability---the ability to have computers from different
   vendors work together;
 * Scalability---the ability to use the same software environment on
   many classes of computers, from personal computers to
   supercomputers.

To achieve maximum acceptance for the new software environment, the
foundation will provide all members early and equal access to the
development process.

The foundation will follow a direction consistent with the
international X/Open Common Application Environment, the U.S. National
Bureau of Standards Application Portability Profile, and equivalent
European and international standards.  Where standards do not exist,
the foundation will work with standards groups to help define them.

Membership

Foundation members will contribute ideas on both technical and policy
matters.  They will be informed of foundation activities on a regular
basis and periodically polled on specific issues.  Membership is open
to anyone.

Research Institute

A research institute is being created to fund research for the
advancement of applications portability, interoperability standards,
and other advanced technologies for future foundation use.  An
academic advisory panel will provide guidance and input to the
institute.  The Institute's research will be conducted worldwide.

Software environment guidelines

The foundation's open software environment will allow vendors to add
value through compatible extensions.  To encourage its widespread use,
it will run on a wide range of single- and multi-processor computers.

THe foundation's software environment includes a set of application
programming interfaces to make it easier to write applications for a
variety of systems.  The initial set of interfaces will support POSIX
and X/Open specifications, and will be extended to include areas such
as distributed computing, graphics, and user interfaces.

The foundation will base its development efforts on its own research
as well as on technologies which will be selected and licensed from
member offerings.  Technologies being considered by the foundation
include:

 * Apollo's Network Computing System(tm) (NCS)
 * Bull's UNIX system-based multiprocessor architecture;
 * Digital's user interface tool kit and style guides for the
   X Window System(tm)
 * Hewlett-Packard's Native Language Support (NLS);
 * Nixdorf's relational database technology;
 * Siemens' OSI protocol support.

To provide a clear and easy migration path for application developers
and end users, the foundation's system will include features to
support current System V- and Berkeley-based UNIX applications.  The
operating system will use core technology from a future version of
IBM's AIX(tm) as a development base.

Specifications supported by the foundation will be publicly available,
and a set of verification tests for all appropriate facilities will be
identified or created.  The foundation will license its open system
software internationally.

--------

X/Open is a trademark of X/Open CO. Ltd.
* Institute of Electrical and Electronics Engineers (IEEE) Standard
    1003.
UNIX is a registered trademark of AT&T in the U.S. and other
companies.
Network Computing System is a trademark of Apollo Computer, Inc.
X Window System is a trademark of Massachusetts Institute of
    Technology.
AIX is a trademark of International Business Machines Corporation.

Volume-Number: Volume 14, Number 17

From usenet  Tue May 24 15:32:14 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA12478; Tue, 24 May 88 15:32:14 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Calendar of UNIX-related Events
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: uunet!sally.utexas.edu!ctp (Clyde T. Poole)
Organization: U. Texas CS Dept., Austin, Texas
Date: 23 May 88 17:19:13 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!sally.utexas.edu!ctp (Clyde T. Poole)

The dates of the next few DECUS Symposia are as follows:

Anaheim, CA        October 17-21, 1988
Atlanta, GA        May 8-12, 1989
Anaheim, CA        November 6-10, 1989
New Orleans, LA        May 7-11, 1990

ctp

Volume-Number: Volume 14, Number 18

From usenet  Thu May 26 17:42:45 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA20984; Thu, 26 May 88 17:42:45 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Open Software Foundation
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: John T. Nelson <uunet!potomac.ads.com!jtn>
Date: 25 May 88 19:02:58 GMT
Apparently-To: std-unix-archive
Status: O

From: John T. Nelson <uunet!potomac.ads.com!jtn>

I have mixed feelings about the Open Software Foundation.  On the one
hand I agree with AT&T when they state that the OSF has no track
record in the open software/standards business.  This is true.  The
founders of OSF consist of a handful of large computer companies whose
experience is mostly in marketing hardware and proprietary software,
not designing state-of-the-art operating systems, user interfaces and
environments for the scientist/engineer.

Now the OSF claims that they can pound together a standard which will
appeal to both System V and Berkeley users.  I fear that more than
likely the OSF standard will bind users to a single Unix standard and
thus to a single proprietary product... namely IBM's AIX, and
thus ensure IBM's position in the marketplace.

Making the standard available to everyone does not qualify it as an
"open" standard.  There must be open and equal participation among ALL
users of the system to make both technical and policy decisions when
defining the standard.  The OSF, if it is to live up to its advertised
ideals, must recognize the diverse needs of developers, researchers and
engineers who actually use the system and may prefer a system interface
that is different from what the standard proposes.

There must be diverse community participation.

> Membership
>
> Foundation members will contribute ideas on both technical and policy
> matters.  They will be informed of foundation activities on a regular
> basis and periodically polled on specific issues.  Membership is open
> to anyone.

... for a price...

I note that individual/educational memberships to the OSF cost $5,000.
Corporate memberships cost $25,000.  Worse, simply being a member does
not allow you to make decisions on ALL policy issues.  Apparently the
OSF founders only want partners who have a signicant financial stake
in Unix.  This means that the individuals who will be most affect by
Unix (hackers, scientists) will be those most excluded from
membership if they cannot find an institution to sponsor them.  Even
then it isn't clear how much of a voice they will have in defining
the standard.

> The foundation's software environment includes a set of application
> programming interfaces to make it easier to write applications for a
> variety of systems.  The initial set of interfaces will support POSIX
> and X/Open specifications, and will be extended to include areas such
> as distributed computing, graphics, and user interfaces.

Sounds pretty good so far though.

> To provide a clear and easy migration path for application developers
> and end users, the foundation's system will include features to
> support current System V- and Berkeley-based UNIX applications.  The
> operating system will use core technology from a future version of
> IBM's AIX(tm) as a development base.

If the corner-stone of the OSF Unix standard is IBM's proprietary
product then how flexible can the standard be to user needs?  If the
new standards require massive rewrites to the AIX kernal will IBM
comply with the OSF's findings and completely rewrite their kernal?

> Specifications supported by the foundation will be publicly available,
> and a set of verification tests for all appropriate facilities will be
> identified or created.  The foundation will license its open system
> software internationally.

I would prefer to see an implementation maintained by an independent
university or the user community at large, not by a handful of
mega-marketing computer companies who have vested interests in products
they have already developed.  I would also like to see source code made
available so that the system can be easily maintained and modified at
each individual site.  Much like Berkeley source code licences.

On the other hand, I welcome the OSF as a positive effect on the
market place.  Adoption of standards that facilitate portability will
stimulate a somewhat stagnant and confused computer software industry.
Also, perhaps now Sun will get serious about their windowing systems
(to name just one of my gripes about Sun computers).  Sunview is a
toy.  NeWS is better and I think this will become a good product.

I'm much more interested in seeing Sun develop an entierly new and
integrated user interface... not just something that runs on top of the
shell.  Rather we should see a highly integrated window system/shell
much like the Symbolics LISP machine's windowing environment.  I
realize this is difficult to implement in Unix thanks to Unix's rather
backward way of thinking about the user interface, but hope springs
eternal.

Volume-Number: Volume 14, Number 19

From usenet  Sat May 28 07:00:13 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AB09604; Sat, 28 May 88 07:00:13 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Calendar of UNIX-related Events
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: Kusumoto Hiroyuki <uunet!etl.jp!kusumoto>
Organization: Electrotechnical Laboratory, Tsukuba Science City
Date: 26 May 88 12:36:12 GMT
Apparently-To: std-unix-archive
Status: O

From: Kusumoto Hiroyuki <uunet!etl.jp!kusumoto>

Hi,
I am a member of JUS committee.

In article <[e-mail]> you write:
>year mon days          conference        (sponsor,) (hotel,) location
>1988 Jul               U Symposium       JUS, Tokyo, Japan
>1988 Nov               U Symposium       JUS, Osaka, Japan

Detail schedule:

1988 Jul 6-8            U Symposium       JUS, Tokyo, Japan
1988 Nov 10-11          U Symposium       JUS, Osaka, Japan

KUSUMOTO Hiroyuki (KUSUMOTO is my family name)
[e-mail]

# ETL is ElectroTechnical Laboratory (MITI's Lab.)
# MITI is Ministry of International Trade and Industry

Volume-Number: Volume 14, Number 20

From usenet  Sat Jun  4 14:45:33 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA06705; Sat, 4 Jun 88 14:45:33 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Meetings
Message-Id: <[e-mail]>
Reply-To: George Pajari <uunet!ubc-cs!pajari>
Date: 3 Jun 88 09:20:00 GMT
Apparently-To: std-unix-archive
Status: O

From: George Pajari <uunet!ubc-cs!pajari>

New meetings to add to the list:

AT&T and Sun Microsystems
Software Developer Conferences
on System V Release 4.0

Sep 14-16    New York
Sep 27-29    Los Angeles
Oct 11-13    Tokyo
Oct 25-27    London
Nov  9-11    Boston
Nov 29-Dec 1    Chicago
Dec 13-15    Washington, DC
TBA        Toronto

(all 1988)

For more info, call 1-800-387-6100

Also in Canada every year:
sometime in February    UNIX in Government Conference and Tradeshow  Ottawa
sometime in May        UNIX 8x/etc Conference and Tradeshow     Toronto

I will try to get better dates for these last two and will send them
to you.


Volume-Number: Volume 14, Number 21

From usenet  Sat Jun 11 16:59:27 1988
Received: by uunet.UU.NET (5.54/1.14)
    id AA09439; Sat, 11 Jun 88 16:59:27 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: standards BOF at USENIX
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 11 Jun 88 18:41:48 GMT
Apparently-To: std-unix-archive
Status: O

The usual standards BOF at USENIX will be at 8PM Wednesday, 22 June,
at the Hilton, facilitated by Shane McCarron and John Quarterman.
This usually tends to be an occassion for USENIX attendees to ask
questions about what has been going on in standards lately.  Anyone
who wants to do that, or to provide answers, is invited to attend.

Volume-Number: Volume 14, Number 22

From usenet  Wed Jun 29 11:28:51 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA03923; Wed, 29 Jun 88 11:28:51 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Access to UNIX-Related Standards
Message-Id: <[e-mail]>
Expires: 19 Jul 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 28 Jun 88 01:15:48 GMT
Apparently-To: std-unix-archive
Status: O

This is the latest in a series of similar comp.std.unix articles.
Corrections and additions to this article are solicited.

There are two companion articles, posted at the same time as this one
and with subjects ``Access to UNIX User Groups and Publications'' and
``Calendar of UNIX-related Events.''

Also note that Shane McCarron now writes a quarterly summary report for
USENIX soon after each IEEE 1003 meeting for posting in comp.std.unix
and in ;login:, the Newsletter of the USENIX Association.

Changes from last posting:  None.

Access information is given in this article for the following standards:
IEEE 1003.1 (operating system interface), 1003.2 (shell and tools),
    1003.3 (testing and verification), 1003.4 (real time),
    1003.5 (ADA binding), 1003.6 (security), 1003.0 (POSIX guide).
NBS FIPS.
/usr/group Technical Committee Subcommittees on distributed file system,
    network interface, graphics/windows, database, internationalization,
    performance measurements, realtime, security, and super computing.
X3H3.6 (display committee)
X3J11 (C language)
/usr/group 1984 Standard
System V Interface Definition (SVID, or The Purple Book)
X/OPEN PORTABILITY GUIDE (The Green Book)
4.3BSD Manuals


UNIX is a Registered Trademark of AT&T.
IEEE is a trademark of the Institute of Electrical and Electronic Engineers,
    Inc.:  POSIX is no longer a trademark.
X/OPEN is a licensed trademark of the X/OPEN Group Members.


The IEEE P1003 Portable Operating System Interface for Computer
Environments Committee is sometimes known colloquially as the UNIX
Standards Committee.  They published the 1003.1 "POSIX" Trial Use
Standard in April 1986.  According to its Foreword:

    The purpose of this document is to define a standard
    operating system interface and environment based on the
    UNIX Operating System documentation to support application
    portability at the source level.  This is intended for
    systems implementors and applications software developers.

Published copies are available at $19.95, with bulk purchasing discounts
available.  Call the IEEE Computer Society in Los Angeles

        714-821-8380

and ask for Book #967.  Unfortunately, this only works for multiple copies.
But the following mail address works for single copies:

        IEEE Computer Society
        P.O. Box 80452
        Worldway Postal Center
        Los Angeles, Ca. 90080

Include a check for $19.95 + $4 for shipping and handling.  For UPS
shipping, add another $4.  Or contact:

        IEEE Service Center
        445 Hoes Ln.
        Piscataway, NJ 08854

and ask for "IEEE 1003.1 Trial Use Standard" - stock number SH10546.

The Trial Use Standard will be available for comments for a period such
as a year.  The current target for a Full Use Standard is Summer 1988.
Initial balloting is completed, and ballot resolution is in progress:
it's too late to ballot if you haven't already.


IEEE has brought the 1003.1 effort into the International Organization
for Standardization (ISO) arena.  IEEE 1003.1 Draft 12 is also a
``Draft Proposed International Standard (ISO DP)'' under SC22 WG15.
The convenor is Jim Isaak:  see below for his address.  There is a U.S.
Technical Advisory Group (TAG) to ISO SC22 WG15:  the chair is Donn
Terry of HP.

The National Bureau of Standards is producing a Federal Information
Processing Standard (FIPS) based on IEEE 1003.1.  It will probably
be available before the Full Use Standard, and may reflect Draft 12,
rather than the final 1003.1 standard.  For information, contact:

        Roger Martin
        National Bureau of Standards
        Building 225
        Room B266
        Gaithersburg, MD  20899
        [phone]

NBS is also producing a FIPS based on IEEE 1003.2, probably from
the draft made by 1003.2 at their March meeting.


Machine readable copies of the IEEE 1003.1 Trial Use Standard are not
and will not be available.  The same applies to copies of later drafts.

There is a paper mailing list by which interested parties may get
copies of drafts of the standard.  To get on it, or to submit comments
directly to the committee, mail to:

        James Isaak
        Chairperson, IEEE/CS P1003
        Tel.: [phone]
        Fax.: [phone]
        decvax!isaak
        [e-mail]
        Digital Equipment
        ZK03-3/Y25
        110 Spit Brook Rd.
        Nashua, NH  03062-2698

Sufficiently interested parties may join the working group.

The term POSIX actually applies to all of the P1003 subcommittees:
group    subject                co-chairs
1003.0    POSIX Guide            Al Hankinson (NBS), Kevin Lewis (DEC)
1003.1    Systems Interface        Jim Isaak (DEC), Donn Terry (HP)
1003.2    Shell and Tools Interface    Hal Jespersen (UniSoft), Don Cragun (Sun)
1003.3    Verification and Testing     Roger Martin (NBS), Carol Raye (AT&T)
1003.4    Real Time             Bill Corwin (Intel)
1003.5    Ada Binding for POSIX        Terry Fong (USArmy), Stowe Boyd(Compass)
1003.6    Security            Dennis Steinauer (NBS), Ron Elliot (IBM)

Inquiries regarding any of the subcommittees should go to the same address
as for 1003.1.


The next scheduled meetings of the P1003 working groups are:

1988 July 11-15        Tech Center Hyatt, Denver, CO
1988 October 17-19,20-21 ISO SC22 Advisory Group & WG15 - Tokyo, Japan
1988 October 24-28    Hawaii

1989 January 9-13    Embassy Suites, Ft. Lauderdale, FL
1989 April 17(29?)    Minneapolis-St. Paul, MN
1989 July 10-14        San Francisco, CA
1989 October 16-20    Brussels (or Amsterdam) (Thought: EC host)

1990 January 29        New Orleans, LA
1990 April        Montreal, Quebec

Here are some details from Hal Jespersen regarding P1003.2:

The IEEE P1003.2 "Shell and Utilities" Working Group is developing a
proposed standard to complement the 1003.1 POSIX standard.  It will
consist of

    a shell command language (currently planned to be based on the
    Bourne Shell),

    groups of utility programs, or commands,

    programmatic interfaces to the shell (system(), popen()) and
    related facilities (regular expressions, file name expansion,
    etc.)

    defined environments (variables, file hierarchies, etc) that
    applications may rely upon

    utilities for installing application programs onto conforming
    systems

which will allow application programs to be developed out of existing
pieces, in the UNIX tradition.  The scope of the standard emphasizes
commands and features that are more typically used by shell scripts or
C language programs than those that are oriented to the terminal user
with windows, mice, visual shells, and so forth.

There has been some controversy in the Working Group about clarifying
the scope of the 1003.2 standard in regard to its relationship with
1003.1.  The Working Group is attempting to produce a standard that
will assume the structure and philosophy of a POSIX system is
available, but it will not require a fully conforming implementation as
a base.  For example, it should be feasible to eventually produce a
1003.2 interface on a V7 system, or on a system very close to POSIX,
but missing a few crucial features (as long as the shell and utilities
didn't need them).  However, the proposed standard will *not* be
unnecessarily watered down simply to allow non-POSIX systems to conform.

The group is currently seeking proposals for groupings of commands that
may be offered by implementors.  As groups are identified, command
descriptions will be solicited.  There is no requirement that the commands
be in System V or BSD today, but they should realistically be commands
that are commonly found in most existing implementations.


There are three Institutional Representatives to P1003:  John Quarterman
from USENIX, Heinz Lycklama from /usr/group, and Mike Lambert from X/OPEN.
The two from USENIX and /usr/group are also representatives to the U.S.
TAG to ISO SC22 WG15.

As the one from USENIX, one of my functions is to get comments from the
USENIX membership and the general public to the committee.  One of the
ways I try to do that is by moderating this newsgroup, comp.std.unix
An article related to this one appeared in the September/October 1986
;login: (The USENIX Association Newsletter).  I'm also currently on the
USENIX Board of Directors.  Comments, suggestions, etc., may be sent to

        John S. Quarterman
        Texas Internet Consulting
        701 Brazos, Suite 500
        Austin TX 78701-3243
        [phone]
        uunet!usenix!jsq
        [e-mail]

For comp.std.unix:
Comments:    uunet!std-unix-request [e-mail]
Submissions:    uunet!std-unix        [e-mail]

The November/December 1987 issue of CommUNIXations (the /usr/group magazine)
contains a report by Heinz Lycklama on the /usr/group Technical Committee
working groups which met in June 1987.

If you are interested in starting another /usr/group working group, contact
Heinz Lycklama:

        Heinz Lycklama
        Interactive Systems Corp.
        2401 Colorado Ave., 3rd Floor
        Santa Monica, CA 90404
        [phone]
        decvax!cca!ima!heinz


Here is contact information for /usr/group working groups as taken from
the CommUNIXations article mentioned above.

/usr/group Working Group on Distributed File System:
    Art Sabsevitz            Frederick Glover
    AT&T Information Systems    MK02-1/H10
    190 River Road            Digital Equipment Corporation
    Summit, NJ  07933        Continental Boulevard
    201-522-6248            Merrimack, NH  03054-0430
    attunix!bump            603-884-5111
                    decvax!fglover

/usr/group Working Group on Network Interface:
    Steve Albert
    AT&T Information Systems
    190 River Road, Rm. A-114
    Summit, NJ  07901
    [phone]
    attunix!ssa

/usr/group Working Group on Internationalization:
    John Wu                Laurie Goudie
    Charles River Data Systems    Santa Cruz Operation
    983 Concord St.,        400 Encinal
    Framingham, MA 01701        Santa Cruz, CA 95060
    617-626-1000            408-458-1422

/usr/group Working Group on Graphics/Windows:
    Tom Greene
    Apollo Computer, Inc.
    330 Billerica Road
    Chelmsford, MA  01824
    [phone], ext. 7581

/usr/group Working Group on Realtime:
    Bill Corwin
    Intel Corp.
    5200 Elam Young Pkwy
    Hillsboro, OR 97123
    [phone]

/usr/group Working Group on Database:
    Val Skalabrin
    Unify Corp.
    1111 Howe Ave.
    Sacramento, CA 95825
    [phone]


/usr/group Working Group on Performance Measurements:
    Ram Chelluri        David F. Hinnant
    AT&T Computer Systems    Northern Telecom, Inc.
    Room E15B        Dept. 0226
    4513 Western Ave.    P.O. Box 13010
    Lisle, IL 60532        Research Triangle Park, NC  27709-3010
    [phone]        [phone]
                ...{decvax,akgua}!mcnc!rti!ntirtp!dfh

/usr/group Working Group on Security:
    Steve Sutton            Ms. Jeanne Baccash
    Consultant, Addamax        AT&T UNIX Systems Engineering
    1107 S. Orchard            190 River Road
    Urbana, IL  61801        Summit, NJ  07901
    217-344-0996            201-522-6028
                    attunix!jeanne

/usr/group Working Group on Super Computing:
    Karen Sheaffer            Robin O'Neill
    Sandia National Laboratory    Lawrence Livermore Laboratory
    P.O. Box 969            P.O. Box 5509, L560
    Livermore, CA  94550        Livermore, CA  94550
    415-422-3431            415-422-0973
                    oneill#[e-mail]


The X3H3.6 display management committee has recently formed to develop
a model to support current and future window management systems, yet
is not based directly on any existing system.  The chair solicits
help and participation:

        Georges Grinstein
        wanginst!ulowell!grinstein


The Abstract of the 1003.1 Trial Use Standard adds:

    This interface is a complement to the C Programming Language
    in the C Information Bulletin prepared by Technical Committee X3J11
    of the Accredited Standards Committee X3, Information Processing
    Systems, further specifying an environment for portable application
    software.

X3J11 is sometimes known as the C Standards Committee.  Their liaison to
P1003 is

        Don Kretsch
        AT&T
        190 River Road
        Summit, NJ 07901

A contact for information regarding publications and working groups is

        Thomas Plum
        Vice Chair, X3J11 Committee
        Plum Hall Inc.
        1 Spruce Avenue
        Cardiff, New Jersey 08232

The current document may be ordered from

        Global Engineering Documents
        2805 McGaw
        Irvine, CA 92714
        USA
        [phone]
        [phone]

Ask for the X3.159 draft standard.  The price is $65.

The current X3J11 meeting schedule is:

1988 August 15-19    Cupertino, CA
1988 December 12-16    Seattle, WA
1989 April 10-11    Phoenix, AZ


The /usr/group Standard is a principal ancestor of P1003.1, X/OPEN,
and X3J11.  It may be ordered for $15.00 from:

        /usr/group Standards Committee
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        Tel: [phone]
        Fax: [phone]

/usr/group also publishes an eight page document, ``Your Guide to POSIX,''
explaining what IEEE 1003 is, and a nineteen page document, ``POSIX Explored,''
about technical aspects of IEEE 1003.1, and its relations to other standards
and historical implementations.  Contact /usr/group at the above address
for details.


The System V Interface Definition (The Purple Book, or SVID).
This is the AT&T standard and is one of the most frequently-used
references of the IEEE 1003 committee.

        AT&T Customer Information Center
        Attn:  Customer Service Representative
        P.O. Box 19901
        Indianapolis, IN 46219
        U.S.A.

        800-432-6600 (Inside U.S.A.)
        800-255-1242 (Inside Canada)
        317-352-8557 (Outside U.S.A. and Canada)

    System V Interface Definition, Issue 2
    should be ordered by the following select codes:

    Select Code:    Volume:        Topics:
    320-011        Volume I    Base System
                    Kernel Extension
    320-012        Volume II    Basic Utilities Extension
                    Advanced Utilities Extension
                    Software Development Extension
                    Administered System Extension
                    Terminal Volume Interface Extension
    320-013        Volume III    Base System Addendum
                    Terminal Interface Extension
                    Network Services Extension
    307-131        I, II, III    (all three volumes)

The price is about 37 U.S. dollars for each volume or $84 for all three.
Major credit cards are accepted for telephone orders:  mail orders
should include a check or money order, payable to AT&T.


The X/OPEN PORTABILITY GUIDE (The Green Book)
is another reference frequently used by IEEE 1003.

The X/OPEN Group is "Ten of the world's major information system
suppliers" (at time of publication, Bull, DEC, Ericsson, Hewlett-Packard,
ICL, NIXDORF, Olivetti, Philips, Siemens and Unisys and subsequently
augmented by AT&T) who have produced a document intended to promote
the writing of portable applications.  They closely follow both SVID
and POSIX, and cite the /usr/group standard as contributing, but
X/OPEN's books cover a wider area than any of those.

The book is published by

        Elsevier Science Publishers B.V.
        Book Order Department
        P.O. Box 1991
        1000 BZ Amsterdam
        The Netherlands

and distributed in the U.S.A. and Canada by:

        Elsevier Science Publishing Company, Inc.
        52 Vanderbilt Avenue
        New York, NY 10017
        U.S.A.

There are currently five volumes:
    1) System V Specification Commands and Utilities
    2) System V Specification System Calls and Libraries
    3) System V Specification Supplementary Definitions
    4) Programming Languages
    5) Data Management

They take a large number of credit cards and other forms of payment.

Comments, suggestions, error reports, etc., for Issue 2 of the Green Book
may be mailed directly to:

        [e-mail]
        uunet!mcvax!inset!xopen!xpg2

Information about X/OPEN can be requested from:

        Mike Lambert
        Technical Director
        X/OPEN Ltd
        c/o ICL BRA01
        Lovelace Road
        Bracknell
        Berkshire
        England
        [phone]
        [e-mail]
        uunet!mcvax!inset!xopen!mgl


Finally, 4.2BSD and 4.3BSD have influenced POSIX in a number of areas.
The best reference on them is the 4.3BSD manuals, published by USENIX.
An order form may be obtained from:

        Howard Press
        c/o USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710

        415-528-8649
        {ucbvax,decvax}!usenix!office

4.3BSD User's Manual Set (3 volumes)        $25.00
    User's Reference Manual
    User's Supplementary Documents
    Master Index

4.3BSD Programmer's Manual Set (3 volumes)    $25.00
    Programmer's Reference Maual
    Programmer's Supplementary Documents, Volume 1
    Programmer's Supplementary Documents, Volume 2

4.3BSD System Manager's Manual (1 volume)    $10.00

Unfortunately, there are some license restrictions.
Contact the USENIX office for details.

Volume-Number: Volume 14, Number 14

Volume-Number: Volume 14, Number 23

From usenet  Wed Jun 29 11:47:31 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA04672; Wed, 29 Jun 88 11:47:31 EDT
From: <[e-mail]>
Newsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
Subject: Access to UNIX User Groups and Publications
Message-Id: <[e-mail]>
Expires: 19 Jul 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 28 Jun 88 01:17:59 GMT
Apparently-To: std-unix-archive
Status: O

This is the latest in a series of similar comp.std.unix articles,
intended to give summary information about UNIX User groups
and publications; to be accurate, but not exhaustive.
I'm cross-posting it to comp.org.usenix and comp.unix.questions
because there might be interest there.

There are two related articles, posted at the same time as this one,
and with subjects ``Calendar of UNIX-related Events'' and ``Access to
UNIX-Related Standards.''  The latter is posted only to comp.std.unix.

Corrections and additions to this article are solicited.  I keep track
of the conferences, groups, and publications that I attend, am a member
of, or subscribe to.  All others (the majority of the listings) I derive
either from listings elsewhere, or from contributions by readers.
In particular, the meeting schedules and descriptions of most of the
groups are provided by their members.  If a group doesn't have a
meeting schedule listed, it's because nobody has sent me one.  This is
a low-budget operation:  I publish what I have on hand when the time
comes (approximately monthly).

Recent additions: None.


Access information is given in this article for the following:
user groups:    USENIX, /usr/group, EUUG, AUUG, NZUSUGI, JUS, KUUG, AMIX,
        DECUS UNIX SIG, Sun User Group, Apollo DOMAIN Users' Society,
        AT&T and Sun V.4 Software Developer Conferences,
        Open Software Foundation.
newsletters:    ;login:, /usr/digest, EUUGN, AUUGN, NUZ
journal:    Computing Systems
magazines:    CommUNIXations, UNIX REVIEW, UNIX/WORLD,
        Multi-User Computing Magazine, UNIX Systems, UNIX Magazine

Telephone numbers are given in international format, i.e., +n at
the beginning for the country code, e.g., +44 is England, +81 Japan,
+82 Korea, +61 Australia, +64 New Zealand, and +1 is U.S.A. or Canada.

UNIX is a Registered Trademark of AT&T.


USENIX is ``The Professional and Technical UNIX(R) Association.''

        USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710
        U.S.A.
        [phone]
        {uunet,ucbvax,decvax}!usenix!office
        [e-mail]

USENIX sponsors two USENIX Conferences a year, featuring technical papers,
as well as tutorials, and with vendor exhibits at the summer conferences:

    Jan 31-Feb 3 1989 Town & Country Inn, San Diego, CA
    Jun 12-16 1989    Hyatt Regency, Baltimore, MD
    Jan 23-26 1990    Washington, DC
    Jun 11-15 1990    Marriott Hotel, Anaheim, CA
    Jan 22-25 1991    Dallas, TX
    Jun 10-14 1991    Opryland, Nashville, TN

They also sponsor workshops, such as
    Aug 29-30 1988    UNIX Security, Portland, OR
    Sep 26-27 1988    UNIX & Supercomputing, Pittsburgh, PA
    Oct 17-20 1988    C++ Conference (tentative), Denver, CO
    Nov 17-18 1988    Large Installation System Administration II, Monterey,CA

Proceedings for all conferences and workshops are available at
the door and by mail later.

USENIX publishes ``;login:  The USENIX Association Newsletter''
bimonthly.  It is sent free of charge to all their members and
includes technical papers.  There is a USENET newsgroup,
comp.org.usenix, for discussion of USENIX-related matters.

In 1988, USENIX started publishing a new refereed quarterly
technical journal, ``Computing Systems:  The Journal of the USENIX
Association,'' in cooperation with University of California Press.

They also publish an edition of the 4.3BSD manuals, and they
occasionally sponsor experiments, such as methods of improving the
USENET and UUCP networks (e.g., uunet), that are of interest and use to
the membership.  They distribute tapes of contributed software and are
pursuing expanding that activity.

There is a USENIX Institutional Representative on the IEEE P1003
Portable Operating System Interface for Computer Environments Committee.
That representative also moderates the USENET newsgroup comp.std.unix,
which is for discussion of UNIX-related standards, especially P1003.
For more details, see the posting in comp.std.unix, ``Access to
UNIX-Related Standards.''


/usr/group is a non-profit trade association dedicated to the promotion
of products and services based on the UNIX operating system.

        /usr/group
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        U.S.A.
        tel: [phone]
        fax: [phone]

The annual UniForum Conference and Trade Show is sponsored by /usr/group
and features vendor exhibits, as well as tutorials and technical sessions.

    Feb 28-Mar 3 1989 Moscone Center, San Francisco, CA
    Jan 23-26 1990    Washington Hilton, Washington, DC
    Jan 22-25 1991    Infomart, Dallas, TX
    Jan 21-24 1992    Moscone Center, San Francisco CA (tentative)

They also sponsor a regional show, UniForum D.C.:

    Aug 2-4 1988    Washington Hilton Hotel, Washington, D.C.

Proceedings for all conferences are available at the shows and later
by mail.

/usr/group publishes ``CommUNIXations,'' a member magazine that
features articles by industry leaders and observers, technical issues,
standards coverage, and new product announcements.

/usr/group also publishes the ``UNIX Products Directory,'' which lists
products and services developed specifically for the UNIX operating system.
``/usr/digest'' is also published by /usr/group.  This newsletter covers
product announcements and industry projections, and is sent biweekly
to General members of /usr/group and to non-member subscribers.

/usr/group has long been deeply involved in UNIX standardization,
having sponsored the ``/usr/group 1984 Standard,'' providing an Institutional
Representative to the IEEE P1003 Portable Operating System for Computer
Environments Committee, and sponsoring the /usr/group Technical Committee
on areas that P1003 has not yet addressed.  They have recently produced
an executive summary, ``Your Guide to POSIX,'' and a technical overview
``POSIX Explored,'' and funded production of a draft of a ``Rationale and
Notes'' appendix for IEEE 1003.1.


EUUG is the European UNIX systems Users Group, which is currently
celebrating its tenth anniversary.  EUUG is closely coordinated with
national groups in Europe, and with the European UNIX network, EUnet.

        EUUG secretariat
        Owles Hall
        Buntingford
        Herts SG9 9PL
        England
        Telephone [phone]
        Telefax [phone]
        uunet!mcvax!inset!euug
        [e-mail]

They have a newsletter, EUUGN (a previous version of this article
appeared in the latest one), and hold two conferences a year:
    3-7 October 1988, Lisbon, Portugal
    April 1989, Brussels, Belgium


AUUG is the Australian UNIX systems Users Group.

        AUUG
        P.O. Box 366
        Kensington
        N.S.W.    2033
        Australia
        uunet!munnari!auug
        [e-mail]

Phone contact can occasionally be made at [phone]

AUUG holds at least one conference a year, usually in the spring
(August or September).  The next one will be in Melbourne on 13-15
September 1988, will be the first three day meeting, will have a larger
equipment exhibition than any before, and will be professionally
organized for the first time.

They publish a newsletter (AUUGN) at a frequency defined to be every 2 months.


The New Zealand UNIX Systems User Group, Inc. (NZUSUGI) has an annual meeting
and publishes a newsletter, ``NUZ.''

        New Zealand UNIX Systems User Group
        P.O. Box 585
        Hamilton
        New Zealand
        [phone]

The next and fifth annual meeting is the New Zealand UNIX Systems User Group
(NZUSUGI) 1988 Conference, June 9-11 1988, in Wellington, New Zealand.

If you wish to present a paper, acceptance of which entitles you to a free
conference registration, please contact the local speakers organiser,
Dr Dick Cooper, ADATA, PO Box 2555, Christchurch, New Zealand,
[e-mail]   or ...uunet!vuwcomp!cantuar!dick

If you would just like to attend, please respond to Ray Brownrigg, including
a postal address for the delivery of further information as it becomes
available.  Registration forms are expected to be available in February.

        UUCP: {utai!calgary,uunet}!vuwcomp!dsiramd!ray
        ACSnet:    [e-mail][@munnari]
        Ray Brownrigg
        Applied Maths Div, DSIR
        PO Box 1335
        Wellington
        New Zealand


The Korean UNIX User Group (KUUG) has a software distribution service
and a newsletter.

        Korean UNIX User Group
        ETRI
        P.O. Box 8
        Daedug Science Town
        Chungnam 300-32
        Republic of Korea
        [phone]


The Japan UNIX Society has two meetings a year, and a newsletter.

        Japan UNIX Society (JUS)
        #505 Towa-Hanzomon Corp. Bldg.
        2-12 Hayabusa-cho
        Chiyoda-ku, Tokyo 102
        Japan
        [phone]

1988 Jul 6-8    UNIX Symposium    Tokyo, Japan
1988 Nov 10-11    UNIX Symposium    Osaka, Japan


AMIX - the Israeli UNIX user group, is a S.I.G. of the Israeli Processing
Association (IPA). AMIX has a yearly conference (next one on 4-6 July 1988)
and a yearly workshop (last one was in November).

        AMIX, c/o IPA
        P.O. Box 919
        Ramat-Gan
        Israel, 52109
        Tel: [phone],715772
        [e-mail]
        [e-mail]


There are similar groups in other parts of the world.  If such a group
wishes to be included in later versions of this access list, they
should please send me information.

There is a partial list of national organizations in the November/December
1987 CommUNIXations.



DECUS, the Digital Equipment Computer Users Society,
has a UNIX SIG (Special Interest Group) that participates
in its general meetings, which are held twice a year.

        DECUS U.S. Chapter
        219 Boston Post Road, BP02
        Marlboro, Massachusetts  01752-1850
        U.S.A.
        [phone]

The next two DECUS Symposia are:

    Oct 17-21, 1988        Anaheim, California
    May 8-12, 1989        Atlanta, Georgia
    Nov 6-10, 1989        Anaheim, California
    May 7-11, 1990        New Orleans, Louisiana

See also the USENET newsgroup comp.org.decus.


The Sun User Group (SUG) is an international organization that promotes
communication among Sun users, OEMs, third party vendors, and Sun
Microsystems, Inc.  SUG sponsors conferences, collects and distributes
software, produces the README newsletter and T-shirts, sponsors local
user groups, and communicates members' problems to Sun employees and
management.

    Sun Microsystems User Group, Inc.
    2550 Garcia Avenue
    Mountain View, CA  94043
    U.S.A.
    [phone]
    [e-mail]
    sun!users

They have not set a date/location for the 1988 conference yet, but are
actively looking for a hotel (with good pricing and lots of room).
They've narrowed it down to several locations - Miami/Tampa Florida,
Houston/Dallas Texas, and New Orleans LA.  The date will probably be
very early December, 1988.


ADUS is the Apollo DOMAIN Users' Society:

    Apollo DOMAIN Users' Society
    c/o Andrea Woloski, ADUS Coordinator
    Apollo Computer Inc.
    330 Billerica Rd.
    Chelmsford, MA 01824
    [phone], x4448



AT&T and Sun Microsystems are holding a series of
Software Developer Conferences on System V Release 4.0,
related to the Sun/AT&T Applications Binary Interface (ABI).

1988 Sep 14-16    New York, NY
1988 Sep 27-29    Los Angeles, CA
1988 Oct 11-13    Tokyo, Japan
1988 Oct 25-27    London, England
1988 Nov  9-11    Boston, MA
1988 Nov 29-Dec 1    Chicago, IL
1988 Dec 13-15    Washington, DC
1988 TBA    Toronto, ON

For more information, call 1-800-387-6100.


The Open Software Foundation (OSF) is a vendor group formed 17 May 1988
by Apollo, Bull, DEC, HP, IBM, Nixdorff, and Siemens.  Excerpts from
a press release of that date:

The Open Software Foundation (OSF) will develop a software environment,
including application interfaces, advanced system extensions, and a new
operating system, using X/Open(tm) and POSIX* specifications as the
starting point. ...  OSF membership is available to computer hardware
and software suppliers, educational institutions, and government
agencies around the world.  ...  The foundation has a management
organization, staff, and a funding comittment in excess of $90 million
to begin immediate operations.  Its initial development will be based
on technologies offered by the members and its own research, to be
carried out worldwide.

A research institute is being created to fund research for the
advancement of applications portability, interoperability standards,
and other advanced technologies for future foundation use.  An
academic advisory panel will provide guidance and input to the
institute.  The Institute's research will be conducted worldwide.

For more information, contact:

    Deborah Siegel
    Cohn & Wolfe
    [phone]

or

    Open Software Foundation
    20 Ballard Way
    Lawrence, MA 01843

The main general circulation (more than 10,000 copies per issue) magazines
specifically about the UNIX system are:

    UNIX REVIEW            UNIX/WORLD
    Miller Freeman Publications Co.    Tech Valley Publishing
    500 Howard Street        444 Castro St.
    San Francisco, CA 94105        Mountain View, CA 94041
    U.S.A.                U.S.A.
    monthly                monthly
    [phone]            [phone]

    Multi-User Computing magazine    UNIX Systems
    Storyplace Ltd.            Eaglehead Publishing Ltd.
    42 Colebrook Row        Maybury Road
    London  N1 8AF            Woking, Surrey GU21 5HX
    England                England
    [phone]            [phone]

    UNIX Magazine
    Jouji Ohkubo
    c/o ASCII Corp.
    [e-mail]
    [phone]
    fax: [phone]
    telex: 242-6875 ASCIIJ

Some of the above information about magazines was taken from the
November/December 1987 issue of CommUNIXations, which also lists
some smaller-circulation magazines and newsletters.

In addition, there is the Journal of the USENIX Association and
the /usr/group member magazine:

    Computing Systems        CommUNIXations
    USENIX Association        /usr/group
    P.O. Box 2299            4655 Old Ironsides Drive, Suite 200
    Berkeley, CA 94710        Santa Clara, California 95054
    U.S.A.                U.S.A.
    quarterly            bimonthly
    [phone]            [phone]


Finally, Dominic Dunlop <[e-mail]> has pointed out several
publications that frequently include articles about the UNIX system or
the C language.  I've listed them below; the comments after each entry
are his.  I have excluded listings of magazines about specific hardware.

    AT&T Technical Journal
    AT&T Bell Laboratories
    Circulation Dept.
    Room 1K-424
    101 J F Kennedy Parkway
    Short Hills, NJ 07078
    Bimonthly
    $40/yr (US); $50/yr (overseas)
    [phone]
    While few issues are devoted to UNIX,
    most turn out to mention its applications.

    Byte
    McGraw-Hill Inc.
    Phoenix Mill Lane
    Peterborough, NH 03458
    Monthly
    $22/yr (US); $25/yr(Mex,Can); $37/yr (surface); $69/yr (air,Europe)
    [phone]
    Concentrates mainly on personal computers,
    but covers low end of UNIX market in some depth.

    The C Users Journal
    ``A service of the C Users Group.''
    R&D Publications Inc
    PO Box 97
    McPherson, KS 67460
    Eight issues per year
    $20/yr (US/Mex/Can); $30/yr (overseas)
    [phone]
    Mainly DOS-oriented; some UNIX.

    Unique
    ``The UNIX System Information Source.''
    Infopro Systems
    PO Box 220
    Rescue, CA 95672
    Monthly
    $79/yr (US,overseas); $99/yr (air)
    [phone]
    High-quality industry newsletter.
    Emphasis on marketing implications of technical developments.


The following information about bookstores was taken from the
November/December 1987 issue of CommUNIXations.  In the interests of
space, I have arbitrarily limited the selection listed here to those
bookstores or suppliers specifically dedicated to computer books, and
not part of other organizations.

    Computer Literacy Bookshop    UNIX Book Service
    2590 No. First St.        35 Bermuda Terrace
    San Jose, CA 95131        Cambridge, CB4 3LD
    U.S.A.                England
    [phone]        [phone]

    Cucumber Bookshop        Jim Joyce's UNIX Book Store
    5611 Kraft Ave.            47 Potomac St.
    Rockville, MD 20852        San Francisco, CA 94117
    U.S.A.                U.S.A.
    [phone]            [phone]

Volume-Number: Volume 14, Number 24

From usenet  Wed Jun 29 11:58:40 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA05227; Wed, 29 Jun 88 11:58:40 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Calendar of UNIX-related Events
Message-Id: <[e-mail]>
Expires: 19 Jul 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail] (Moderator, John S. Quarterman)
Date: 28 Jun 88 01:20:23 GMT
Apparently-To: std-unix-archive
Status: O

Here is a combined calendar of planned conferences, workshops, or
standards meetings by various organizations.  I compiled it for
my own use and thought it might be of some public interest.  Most
of this information came from the various conference organizers,
although some was taken from ;login: (USENIX), 13, 1, Jan/Feb
1988 and CommUNIXations (/usr/group), VII, 6, Nov/Dec 1987.

If your favorite meeting is not listed, it's probably because I
don't know about it.  If you send me information on it, I will
probably list it both here and in the companion article, ``Access
to UNIX User Groups and Publications.'' There is also another
companion article, ``Access to UNIX-Related Standards,'' that
appears only in comp.std.unix.

Dates and places for IEEE 1003 after Oct 1988 are tentative, and
also for the 1992 UniForum.

Changes since last posting: None.


88/06/27         Calendar of UNIX-Related Events    comp.std.unix

year mon days        conference      (sponsor,) (hotel,) location

1988 Jul 6-8         U Symposium     JUS, Tokyo, Japan
1988 Jul 4-6         AMIX            Israel
1988 Jul 11-15       IEEE 1003       Tech Center Hyatt, Denver, CO
1988 Aug 2-4         UniForum/DC     Washington Hilton, Washington, DC
1988 Aug 15-19       ANSI X3J11      Cupertino, CA
1988 Aug 29-30       U Security W    USENIX, Portland, OR
1988 Sep 13-15       AUUG            Melbourne, Australia
1988 Sep 14-16       V.4 Soft. Dev.  AT&T and Sun, New York, NY
1988 Sep 26-27       U&Supercomp. W  USENIX, Pittsburgh, PA
1988 Sep 27-29       V.4 Soft. Dev.  AT&T and Sun, Los Angeles, CA
1988 Oct 3-7         EUUG            Lisbon, Portugal
1988 Oct 11-13       V.4 Soft. Dev.  AT&T and Sun, Tokyo, Japan
1988 Oct 17-21       DECUS S         Anaheim, California
1988 Oct 17-21       C++ Conference  USENIX, Denver, CO
1988 Oct 17-19,20-21 ISO SC22 & WG15 Tokyo, Japan
1988 Oct 24-28       IEEE 1003       Hawaii
1988 Oct 25-27       V.4 Soft. Dev.  AT&T and Sun, London, England
1988 Oct             UNIX Expo       New York, NY
1988 Nov  9-11       V.4 Soft. Dev.  AT&T and Sun, Boston, MA
1988 Nov 17-18       Large Install.  Syst. Adm. W II, USENIX, Monterey, CA
1988 Nov 10-11       U Symposium     JUS, Osaka, Japan
1988 Nov 29-Dec 1    V.4 Soft. Dev.  AT&T and Sun, Chicago, IL
1988 Dec             Sun User Group  southern U.S.A.
1988 Dec             UNIX Fair       JUS, Tokyo, Japan
1988 Dec 12-16       ANSI X3J11      Seattle, WA
1988 Dec 13-15       V.4 Soft. Dev.  AT&T and Sun, Washington, DC
1988 TBA             V.4 Soft. Dev.  AT&T and Sun, Toronto, ON

1989 Jan 9-13        IEEE 1003       Embassy Suites, Ft. Lauderdale, FL
1989 Jan 31-Feb 3    USENIX          Town and Country, San Diego, CA
1989 Feb             U in Gov. C&T   Ottawa, ON
1989 Feb 28-Mar 3    UniForum        Moscone Center, San Francisco, CA
1989 Apr 10-11       ANSI X3J11      Phoenix, AZ
1989 Apr 17(29?)     IEEE 1003       Minneapolis-St. Paul, MN
1989 Apr             EUUG            Brussels, Belgium
1989 May 8-12        DECUS S         Atlanta, Georgia
1989 May             U 8x/etc C&T    /usr/group/cdn, Toronto, ON
1989 Jun 12-16       USENIX          Hyatt Regency, Baltimore, MD
1989 Jul 10-14       IEEE 1003       San Francisco, CA
1989 Oct 16-20       IEEE 1003       Brussels (or Amsterdam)
1989 Oct             UNIX Expo       New York, NY
1989 Nov 6-10        DECUS S         Anaheim, California

1990 Jan 23-26       USENIX          Washington, DC
1990 Jan 23-26       UniForum        Washington Hilton, Washington, DC
1990 Jan 29          IEEE 1003       New Orleans, LA
1990 Feb             U in Gov. C&T   Ottawa, ON
1990 Apr             IEEE 1003       Montreal, Quebec
1990 May 7-11        DECUS S         New Orleans, Louisiana
1990 May             U 8x/etc C&T    /usr/group/cdn, Toronto, ON
1990 Jun 11-15       USENIX          Marriott, Anaheim, CA

1991 Jan 22-25 USENIX        Dallas, TX
1991 Jan 22-25 UniForum      Infomart, Dallas, TX
1990 Feb       U in Gov. C&T Ottawa, ON
1990 May       U 8x/etc C&T  Toronto, ON
1991 Jun 10-14 USENIX        Opryland, Nashville, TN

1992 Jan 21-24 UniForum (?)  Moscone Center, San Francisco CA


Abbreviations: C for Conference, S for Symposium, T for
Tradeshow, U for UNIX, V.4 for System V Release 4.0, W for
Workshop.  USENIX, EUUG, AUUG and DECUS sponsor conferences of
the same names; /usr/group sponsors UniForum.  UNIX is a
Registered Trademark of AT&T.

[e-mail]    John S. Quarterman       uunet!longway!jsq

Volume-Number: Volume 14, Number 25

From usenet  Wed Jun 29 12:11:15 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA05730; Wed, 29 Jun 88 12:11:15 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
Subject: calendar.t
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 28 Jun 88 01:27:27 GMT
Apparently-To: std-unix-archive
Status: O

echo calendar.t
sed -e 's/^X//' >calendar.t <<'shar.calendar.t.2301'
XFrom: [e-mail] (Moderator, John S. Quarterman)
XNewsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
XSubject: Calendar of UNIX-related Events
XExpires: 19 Jul 88 21:45:37 GMT
XReply-To: [e-mail] (Moderator, John S. Quarterman)
XApproved: [e-mail] (Moderator, John S. Quarterman)
X.hy 0
XHere is a combined calendar of planned conferences, workshops, or
Xstandards meetings by various organizations.
XI compiled it for my own use and thought it might be of some public interest.
XMost of this information came from the various conference organizers,
Xalthough some was taken from ;login: (USENIX), 13, 1, Jan/Feb 1988
Xand CommUNIXations (/usr/group), VII, 6, Nov/Dec 1987.
XIf your favorite meeting is not listed, it's probably because
XI don't know about it.
XIf you send me information on it, I will probably list it both here and
Xin the companion article, ``Access to UNIX User Groups and Publications.''
XThere is also another companion article,
X``Access to UNIX-Related Standards,'' that appears only in comp.std.unix.
XDates and places for IEEE 1003 after Oct 1988 are
Xtentative, and also for the 1992 UniForum.
XChanges since last posting:
X.if n FormFeed
X.tl '$Date: 88/06/27 20:11:55 $'Calendar of UNIX-Related Events'comp.std.unix'
Xl1 l1 l1 .
Xyear mon days    conference    (sponsor,) (hotel,) location
X1988 Jul 6-8    U Symposium    JUS, Tokyo, Japan
X1988 Jul 4-6    AMIX    Israel
X1988 Jul 11-15    IEEE 1003    Tech Center Hyatt, Denver, CO
X1988 Aug 2-4    UniForum/DC    Washington Hilton, Washington, DC
X1988 Aug 15-19    ANSI X3J11    Cupertino, CA
X1988 Aug 29-30    U Security W    USENIX, Portland, OR
X1988 Sep 13-15    AUUG    Melbourne, Australia
X1988 Sep 14-16    V.4 Soft. Dev.    AT&T and Sun, New York, NY
X1988 Sep 26-27    U&Supercomp. W    USENIX, Pittsburgh, PA
X1988 Sep 27-29    V.4 Soft. Dev.    AT&T and Sun, Los Angeles, CA
X1988 Oct 3-7    EUUG    Lisbon, Portugal
X1988 Oct 11-13    V.4 Soft. Dev.    AT&T and Sun, Tokyo, Japan
X1988 Oct 17-21    DECUS S    Anaheim, California
X1988 Oct 17-21    C++ Conference    USENIX, Denver, CO
X1988 Oct 17-19,20-21    ISO SC22 & WG15    Tokyo, Japan
X1988 Oct 24-28    IEEE 1003    Hawaii
X1988 Oct 25-27    V.4 Soft. Dev.    AT&T and Sun, London, England
X1988 Oct    UNIX Expo    New York, NY
X1988 Nov  9-11    V.4 Soft. Dev.    AT&T and Sun, Boston, MA
X1988 Nov 17-18    Large Install.    Syst. Adm. W II, USENIX, Monterey, CA
X1988 Nov 10-11    U Symposium    JUS, Osaka, Japan
X1988 Nov 29-Dec 1    V.4 Soft. Dev.    AT&T and Sun, Chicago, IL
X1988 Dec    Sun User Group    southern U.S.A.
X1988 Dec    UNIX Fair    JUS, Tokyo, Japan
X1988 Dec 12-16    ANSI X3J11    Seattle, WA
X1988 Dec 13-15    V.4 Soft. Dev.    AT&T and Sun, Washington, DC
X1988 TBA    V.4 Soft. Dev.    AT&T and Sun, Toronto, ON
X1989 Jan 9-13    IEEE 1003    Embassy Suites, Ft. Lauderdale, FL
X1989 Jan 31-Feb 3    USENIX    Town and Country, San Diego, CA
X1989 Feb    U in Gov. C&T    Ottawa, ON
X1989 Feb 28-Mar 3    UniForum    Moscone Center, San Francisco, CA
X1989 Apr 10-11    ANSI X3J11    Phoenix, AZ
X1989 Apr 17(29?)    IEEE 1003    Minneapolis-St. Paul, MN
X1989 Apr    EUUG    Brussels, Belgium
X1989 May 8-12    DECUS S    Atlanta, Georgia
X1989 May    U 8x/etc C&T    /usr/group/cdn, Toronto, ON
X1989 Jun 12-16    USENIX    Hyatt Regency, Baltimore, MD
X1989 Jul 10-14    IEEE 1003    San Francisco, CA
X1989 Oct 16-20    IEEE 1003    Brussels (or Amsterdam)
X1989 Oct    UNIX Expo    New York, NY
X1989 Nov 6-10    DECUS S    Anaheim, California
X1990 Jan 23-26    USENIX    Washington, DC
X1990 Jan 23-26    UniForum    Washington Hilton, Washington, DC
X1990 Jan 29    IEEE 1003    New Orleans, LA
X1990 Feb    U in Gov. C&T    Ottawa, ON
X1990 Apr    IEEE 1003    Montreal, Quebec
X1990 May 7-11    DECUS S    New Orleans, Louisiana
X1990 May    U 8x/etc C&T    /usr/group/cdn, Toronto, ON
X1990 Jun 11-15    USENIX    Marriott, Anaheim, CA
Xl1 l1 l1 .
X1991 Jan 22-25    USENIX    Dallas, TX
X1991 Jan 22-25    UniForum    Infomart, Dallas, TX
X1990 Feb    U in Gov. C&T    Ottawa, ON
X1990 May    U 8x/etc C&T    Toronto, ON
X1991 Jun 10-14    USENIX    Opryland, Nashville, TN
X1992 Jan 21-24    UniForum (?)    Moscone Center, San Francisco CA
X.if n FormFeed
XC for Conference,
XS for Symposium,
XT for Tradeshow,
XU for UNIX,
XV.4 for System V Release 4.0,
XW for Workshop.
XUSENIX, EUUG, AUUG and DECUS sponsor conferences of the same names;
X/usr/group sponsors UniForum.
XUNIX is a Registered Trademark of AT&T.
X.tl '[e-mail]'John S. Quarterman'uunet!longway!jsq'
XVolume-Number: Volume 14, Number 25
shar.calendar.t.2301
echo Makefile
sed -e 's/^X//' >Makefile <<'shar.Makefile.2301'
Xdoc: calendar.doc
Xcalendar.alpha: calendar.t Makefile
X    sed \
X        -e 's/$$Date: \(.*\) ..:..:../\1/' \
X        -e 's/$$Revision: //' \
X        -e '/^\.tl/s/ \$$//g' \
X        calendar.t > $@
Xcalendar.doc: Makefile calendar.alpha
X    tbl calendar.alpha | nroff | col | uniq \
X        | sed -e 's/FormFeed//g' > calendar.doc
Xcalendar.$(PR): calendar.alpha
X    tbl calendar.alpha | troff -t -T$(TYPE) > $@
Xprint:    calendar.$(PR)
X    lpr -P$(PR) -c calendar.$(PR)
shar.Makefile.2301
exit

Volume-Number: Volume 14, Number 26

From news  Wed Jul 13 07:10:28 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA23458; Wed, 13 Jul 88 07:10:28 EDT
From: John S. Quarterman <[e-mail]>
Newsgroups: comp.std.unix,comp.org.usenix
Subject: standard article
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail]
Date: 13 Jul 88 06:27:04 GMT
Apparently-To: std-unix-archive
Status: O

From: John S. Quarterman <[e-mail]>

USENIX and Standards

As a result of the increasing importance of standards in the UNIX
community, the USENIX Association is expanding its involvement in
standards related to the UNIX operating system.  The Association is
interested in promoting technical stability through standards without
limiting technical progress.

Since 1986, the Association has had an Institutional Representative on
the IEEE P1003 (POSIX) committee.  This expanding standards effort
includes greater coverage of the P1003 subcommittees, as well as the
/usr/group Technical Committee and of the ANSII X3J11 C Language committee.

    USENIX Association standards involvement includes:

%  providing information to the membership and the public through ;login:,
comp.std.unix on USENET, BOFs at conferences, and in the trade press;

%  providing forums for technical discussion which may include
workshops or technical sessions at conferences;

%  acting as an ombudsman for those otherwise unrepresented on the
standards committees;

%  encouraging people to become involved in the standards efforts;

%  attempting to enhance the technical quality of the standards by
encouraging concise, written proposals.

This expanded USENIX Association standards effort is being implemented
through two committees.  The first is a working committee of volunteers
from the various standards committees.  The second is a policy committee
initially consisting of Alan G. Nemeth, USENIX Association President,
John S. Quarterman, USENIX Association Director and the Association's
Institutional Representative to the IEEE P1003 committee, Shane McCarron,
IEEE P1003.1 Secretary, and Grover Righter.

Volume-Number: Volume 14, Number 27

From news  Thu Jul 14 17:01:19 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA18513; Thu, 14 Jul 88 17:01:19 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Floating Point Verification
Message-Id: <[e-mail]>
Reply-To: uunet!tahoe.unr.edu!bryson (Derry Bryson)
Organization: University of Nevada Reno
Date: 13 Jul 88 17:54:33 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!tahoe.unr.edu!bryson (Derry Bryson)

I am searching for a standard to check floating point processors and
emulators against.  Basically what I would like to find is a program
that performs several operations and evaluates the accuracy of the answers
based upon some kind of accepted standard.  If anyone has any information
or advice I would greatly appreciate hearing from you.

Thanks in advance,

Derry Bryson

Volume-Number: Volume 14, Number 28

From news  Thu Jul 14 17:07:21 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA19321; Thu, 14 Jul 88 17:07:21 EDT
From: Chris Reynolds <[e-mail]>
Newsgroups: comp.std.unix
Subject: Info about next SUG conference
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: uunet!hubcap.clemson.edu!quirk (Chris Reynolds)
Date: 13 Jul 88 18:08:49 GMT
Apparently-To: std-unix-archive
Status: O

From: [e-mail] (Chris Reynolds)

I saw your message about "Access to Unix User Groups ..." in
comp.unix.questions in which you listed information about various groups
and their upcoming conferences.  I find this information very helpful.
I have more information about the next Sun Users Group conference than
you had in the posting.  It will be held December 5-7, 1988 at the
Fontainebleau Hilton in Miami Beach, Florida.

Chris Reynolds                   uucp: ... !gatech!hubcap!quirk
CS Dept, Clemson University      inet: [e-mail]
phone: (803)656-{2639,3444}

Volume-Number: Volume 14, Number 29

From news  Thu Jul 14 17:14:30 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA20164; Thu, 14 Jul 88 17:14:30 EDT
From: Clyde T. Poole <[e-mail]>
Newsgroups: comp.std.unix
Subject: OSF
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail] (Clyde T. Poole)
Date: 13 Jul 88 16:08:42 GMT
Apparently-To: std-unix-archive
Status: O

From: [e-mail] (Clyde T. Poole)

You might want to correct your "Access to UNIX User Groups and Publications"
posting for OSF to reflect their new telephone number [phone].  It
is now located in Lawrence, Mass.  The person in charge of membership
info is Jo Ann (sp?) Hall.

ctp

Volume-Number: Volume 14, Number 30

From news  Sun Jul 17 23:29:27 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA05357; Sun, 17 Jul 88 23:29:27 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Floating Point Verification
Summary: paranoia, source from netlib
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: uunet!gatech.edu!ut-sally!ut-emx!chpf127 (J. Eaton)
Organization: The University of Texas at Austin, Austin, Texas
Date: 14 Jul 88 21:23:45 GMT
Apparently-To: std-unix-archive
Status: O

From: uunet!gatech.edu!ut-sally!ut-emx!chpf127 (J. Eaton)

In article <[e-mail]>
> From: uunet!tahoe.unr.edu!bryson (Derry Bryson)
>
> I am searching for a standard to check floating point processors and
> emulators against.  Basically what I would like to find is a program
> that performs several operations and evaluates the accuracy of the answers
> based upon some kind of accepted standard.  If anyone has any information
> or advice I would greatly appreciate hearing from you.
...
> Volume-Number: Volume 14, Number 28

  There is a program called PARANOIA available from [e-mail]
  (the online software library maintained at Argonne National Laboratory)
  which does what you want.  There are five versions I know about, one
  each in C, Pascal, and Basic, and two in Fortran (double/single).
  This program tries to test the floating point processor and/or library of
  floating point subroutines.  If the machine you use has one library
  which all languages share it shouldn't matter what version you use
  (but running all of them might prove to be interesting...)

  To get a copy of one of the versions, send a message of the form:

    send <item> from paranoia

  <item> is one of:  paranoia.b, paranoia.c, paranoia.p, spara.f, or dpara.f

  your message can include more than one request, but only one request
  per line.  You might also want to get the general netlib index, by sending
  the message:

    send index


  J. Eaton
  UT Department of Chemical Engineering

  Not really doing anything with chemicals.

Volume-Number: Volume 14, Number 31

From news  Tue Jul 19 21:03:11 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA07283; Tue, 19 Jul 88 21:03:11 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Floating Point Verification
Message-Id: <[e-mail]>
Reply-To: Curt Hern <uunet!cs.utexas.edu!decwrl.dec.com!spar!ascway!hern>
Date: 19 Jul 88 15:42:33 GMT
Apparently-To: std-unix-archive
Status: O

From: Curt Hern <uunet!cs.utexas.edu!decwrl.dec.com!spar!ascway!hern>

"Software Manual for the Elementary Functions" by
William J. Cody, Jr. and William Waite
(Prentice-Hall, 1980) contains Fortran code to check
the accuracy of many elementary functions.  It also
gives the values generated by implementations on
IBM and CDC machines for comparison.

Curt Hern
Schlumberger Well Services
Austin, TX

Volume-Number: Volume 14, Number 32

From news  Sat Jul 23 20:45:40 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA14756; Sat, 23 Jul 88 20:45:40 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Floating Point Verification
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: Dominic Dunlop <uunet!mcvax!sphinx.co.uk!domo>
Organization: Sphinx Ltd., Maidenhead, England
Date: 22 Jul 88 17:53:13 GMT
Apparently-To: std-unix-archive
Status: O

From: Dominic Dunlop <uunet!mcvax!sphinx.co.uk!domo>
Cc: bryson <[e-mail]>

In article <[e-mail]> Derry Bryson writes:
>I am searching for a standard to check floating point processors and
>emulators against.  Basically what I would like to find is a program
>that performs several operations and evaluates the accuracy of the answers
>based upon some kind of accepted standard.
>...
>Volume-Number: Volume 14, Number 28

;login:, Volume 11, Number 2, March/April, 1986, pp 31-56

A Report on the Accuracy of Some Floating Point Math Functions on Selected
Computers

Technical Report GIT-ICS 85/06

Eugene H Spafford
John C Flaspohler

School of Information and Computer Science
Georgia Institute of Technology
Atlanta, Georgia 30332-0280
[phone]

Software Engineering Research center
Georgia Institute of Technology
Atlanta, Georgia 30332-0280
[phone]

Abstract
The UNIX operating system and the C programming language have gained a
large folloing in recent years, especially in research and academic
settings.  C and UNIX-like environments are available on a wide variety of
machines from personal computer to mainframe computers; however, few, if
any, of these implementations provide accurate floating point libraries,
although users tend to believe they do.  This paper presents the results of
running a set of accuracy test on more than a dozen different computer
systems under various versions of UNIX and UNIX-like environments.

Funding for the original printing of this report was obtained from the
School of Information and Computer Science, and from the Software
Engineering Research Center.

Copies of this report may be requested by sending US mail to the authors at
the address given on the title page or from
{akgua,decvax,hplabs,ihnp4,seismo}!gatech!tech-reports

Well, the path's a history lesson,

[ Spafford is now at Purdue, and can be reached as [e-mail];
as Dominic alludes, ihnp4 and seismo are effectively dead, but gatech is
still quite active, and can be reached from most of the known world.  -mod ]

but the paper's well worth getting hold of.  It pulls no punches in
showing some magnificently awful results.  No re-usable test suite is
mentioned -- although I dare say Georgia Institute of Technology may
still have one.  The tests used were carefully coded from ``random
accuracy tests for various standard mathematical functions'' given in
_Software Manual for Elementary Functions_, William J Cody Jr. &
William Waite, Computational Mathematics, Prentice-Hall, 1980.

It came as a surprise to me that the 3B2 had the most accurate math
package at the time.  It was also as slow as hell, but that's been fixed
now.  Wonder how accurate the new math package is...
--
Dominic Dunlop
[e-mail]  [e-mail]

Volume-Number: Volume 14, Number 33

From news  Sat Jul 23 22:43:53 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA27636; Sat, 23 Jul 88 22:43:53 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Access to UNIX-Related Standards
Message-Id: <[e-mail]>
Expires: 22 Aug 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 24 Jul 88 00:45:32 GMT
Apparently-To: std-unix-archive
Status: O

From: [e-mail] (Moderator, John S. Quarterman)

This is the latest in a series of similar comp.std.unix articles.
Corrections and additions to this article are solicited.

There are two companion articles, posted at the same time as this one
and with subjects ``Access to UNIX User Groups and Publications'' and
``Calendar of UNIX-related Events.''

Also note that Shane McCarron now writes a quarterly summary report for
USENIX soon after each IEEE 1003 meeting for posting in comp.std.unix
and in ;login:, the Newsletter of the USENIX Association.

Changes from last posting:  NBS workshops.  USENIX Standards Watchdog.

Access information is given in this article for the following standards:
IEEE 1003.1 (operating system interface), 1003.2 (shell and tools),
    1003.3 (testing and verification), 1003.4 (real time),
    1003.5 (ADA binding), 1003.6 (security), 1003.0 (POSIX guide).
NBS FIPS.
/usr/group Technical Committee Subcommittees on distributed file system,
    network interface, graphics/windows, database, internationalization,
    performance measurements, realtime, security, and super computing.
X3H3.6 (display committee)
X3J11 (C language)
/usr/group 1984 Standard
System V Interface Definition (SVID, or The Purple Book)
X/OPEN PORTABILITY GUIDE (The Green Book)
4.3BSD Manuals


UNIX is a Registered Trademark of AT&T.
IEEE is a trademark of the Institute of Electrical and Electronic Engineers,
    Inc.:  POSIX is no longer a trademark.
X/OPEN is a licensed trademark of the X/OPEN Group Members.


The IEEE P1003 Portable Operating System Interface for Computer
Environments Committee is sometimes known colloquially as the UNIX
Standards Committee.  They published the 1003.1 "POSIX" Trial Use
Standard in April 1986.  According to its Foreword:

    The purpose of this document is to define a standard
    operating system interface and environment based on the
    UNIX Operating System documentation to support application
    portability at the source level.  This is intended for
    systems implementors and applications software developers.

Published copies are available at $19.95, with bulk purchasing discounts
available.  Call the IEEE Computer Society in Los Angeles

        714-821-8380

and ask for Book #967.  Unfortunately, this only works for multiple copies.
But the following mail address works for single copies:

        IEEE Computer Society
        P.O. Box 80452
        Worldway Postal Center
        Los Angeles, Ca. 90080

Include a check for $19.95 + $4 for shipping and handling.  For UPS
shipping, add another $4.  Or contact:

        IEEE Service Center
        445 Hoes Ln.
        Piscataway, NJ 08854

and ask for "IEEE 1003.1 Trial Use Standard" - stock number SH10546.

The Trial Use Standard will be available for comments for a period such
as a year.  The current target for a Full Use Standard is Summer 1988.
Initial balloting is completed, and ballot resolution is in progress:
it's too late to ballot if you haven't already.


IEEE has brought the 1003.1 effort into the International Organization
for Standardization (ISO) arena.  IEEE 1003.1 Draft 12 is also a
``Draft Proposed International Standard (ISO DP)'' under SC22 WG15.
The convenor is Jim Isaak:  see below for his address.  There is a U.S.
Technical Advisory Group (TAG) to ISO SC22 WG15:  the chair is Donn
Terry of HP.

TAG meetings tend to be held wherever 1003.1 is meeting.
The next ISO SC22 WG15 meeting is:

1988 Oct 17-19,20-21    ISO SC22 & WG15    Tokyo, Japan


The National Bureau of Standards is producing a Federal Information
Processing Standard (FIPS) based on IEEE 1003.1.  It will probably
be available before the Full Use Standard, and may reflect Draft 12,
rather than the final 1003.1 standard.  For information, contact:

        Roger Martin
        National Bureau of Standards
        Building 225
        Room B266
        Gaithersburg, MD  20899
        [phone]

NBS is also producing a FIPS based on IEEE 1003.2, probably from
the draft made by 1003.2 at their March meeting.

NBS sponsors a number of standards-related workshops, including:
1988 Sep 22    System Administration and Shell & Tools
1988 Sep 23    X Windows and POSIX FIPS
1988 Oct 5    POSIX Conformance Testing & Laboratory Accreditation
1988 Nov 15    POSIX Applications
1988 Nov 16    POSIX FIPS Revision
1989 Jan 17    Terminal Interface Extensions and Network Services
1989 May 16    POSIX Applications


Machine readable copies of the IEEE 1003.1 Trial Use Standard are not
and will not be available.  The same applies to copies of later drafts.

There is a paper mailing list by which interested parties may get
copies of drafts of the standard.  To get on it, or to submit comments
directly to the committee, mail to:

        James Isaak
        Chairperson, IEEE/CS P1003
        Tel.: [phone]
        Fax.: [phone]
        decvax!isaak
        [e-mail]
        Digital Equipment
        ZK03-3/Y25
        110 Spit Brook Rd.
        Nashua, NH  03062-2698

Sufficiently interested parties may join the working group.

The term POSIX actually applies to all of the P1003 subcommittees:
group    subject                co-chairs
1003.0    POSIX Guide            Al Hankinson (NBS), Kevin Lewis (DEC)
1003.1    Systems Interface        Jim Isaak (DEC), Donn Terry (HP)
1003.2    Shell and Tools Interface    Hal Jespersen (UniSoft), Don Cragun (Sun)
1003.3    Verification and Testing     Roger Martin (NBS), Carol Raye (AT&T)
1003.4    Real Time             Bill Corwin (Intel)
1003.5    Ada Binding for POSIX        Terry Fong (USArmy), Stowe Boyd(Compass)
1003.6    Security            Dennis Steinauer (NBS), Ron Elliot (IBM)

Inquiries regarding any of the subcommittees should go to the same address
as for 1003.1.


The next scheduled meetings of the P1003 working groups are:

1988 October 17-19,20-21 ISO SC22 Advisory Group & WG15 - Tokyo, Japan
1988 Oct 24-28    IEEE 1003    Hawaii
1989 Jan 9-13    IEEE 1003    Embassy Suites, Ft. Lauderdale, FL
1989 Apr 17(29?)    IEEE 1003    Minneapolis-St. Paul, MN
1989 Jul 10-14    IEEE 1003    San Francisco, CA
1989 Oct 16-20    IEEE 1003    Brussels (or Amsterdam)
1990 Jan 29    IEEE 1003    New Orleans, LA
1990 Apr    IEEE 1003    Montreal, Quebec

Here are some details from Hal Jespersen regarding P1003.2:

The IEEE P1003.2 "Shell and Utilities" Working Group is developing a
proposed standard to complement the 1003.1 POSIX standard.  It will
consist of

    a shell command language (currently planned to be based on the
    Bourne Shell),

    groups of utility programs, or commands,

    programmatic interfaces to the shell (system(), popen()) and
    related facilities (regular expressions, file name expansion,
    etc.)

    defined environments (variables, file hierarchies, etc) that
    applications may rely upon

    utilities for installing application programs onto conforming
    systems

which will allow application programs to be developed out of existing
pieces, in the UNIX tradition.  The scope of the standard emphasizes
commands and features that are more typically used by shell scripts or
C language programs than those that are oriented to the terminal user
with windows, mice, visual shells, and so forth.

There has been some controversy in the Working Group about clarifying
the scope of the 1003.2 standard in regard to its relationship with
1003.1.  The Working Group is attempting to produce a standard that
will assume the structure and philosophy of a POSIX system is
available, but it will not require a fully conforming implementation as
a base.  For example, it should be feasible to eventually produce a
1003.2 interface on a V7 system, or on a system very close to POSIX,
but missing a few crucial features (as long as the shell and utilities
didn't need them).  However, the proposed standard will *not* be
unnecessarily watered down simply to allow non-POSIX systems to conform.

The group is currently seeking proposals for groupings of commands that
may be offered by implementors.  As groups are identified, command
descriptions will be solicited.  There is no requirement that the commands
be in System V or BSD today, but they should realistically be commands
that are commonly found in most existing implementations.


There are four Institutional Representatives to P1003:  John Quarterman
from USENIX, Heinz Lycklama from /usr/group, Mike Lambert from X/OPEN,
and Clem Cole from OSF.  The two from USENIX and /usr/group are also
representatives to the U.S. TAG to ISO SC22 WG15.

There is a USENIX Standards Watchdog Committee of volunteers who report
on issues raised in standards committee meetings; composite reports are
published quarterly in comp.std.unix, in ;login: (the USENIX Association
Newsletter), and in the trade press.  Occasionally, these volunteers may
speak for USENIX, if authorized by the USENIX Standards Policy Committee,
which currently consists of Alan G. Nement (USENIX President), John S.
Quarterman, Shane P. McCarron (IEEE 1003 Secretary), and Grover Righter.
Comments, suggestions, etc., may be sent to

        John S. Quarterman
        Texas Internet Consulting
        701 Brazos, Suite 500
        Austin TX 78701-3243
        [phone]
        uunet!usenix!jsq
        [e-mail]
        [e-mail]

For comp.std.unix:
Comments:    uunet!std-unix-request [e-mail]
Submissions:    uunet!std-unix        [e-mail]

CommUNIXations (the /usr/group magazine) contains reports about every
other issue by Heinz Lycklama on the /usr/group Technical Committee meetings.

If you are interested in starting another /usr/group working group, contact
Heinz Lycklama:

        Heinz Lycklama
        Interactive Systems Corp.
        2401 Colorado Ave., 3rd Floor
        Santa Monica, CA 90404
        [phone]
        decvax!cca!ima!heinz


Here is contact information for /usr/group working groups as taken from
the CommUNIXations article mentioned above.

/usr/group Working Group on Distributed File System:
    Art Sabsevitz            Frederick Glover
    AT&T Information Systems    MK02-1/H10
    190 River Road            Digital Equipment Corporation
    Summit, NJ  07933        Continental Boulevard
    201-522-6248            Merrimack, NH  03054-0430
    attunix!bump            603-884-5111
                    decvax!fglover

/usr/group Working Group on Network Interface:
    Steve Albert
    AT&T Information Systems
    190 River Road, Rm. A-114
    Summit, NJ  07901
    [phone]
    attunix!ssa

/usr/group Working Group on Internationalization:
    John Wu                Laurie Goudie
    Charles River Data Systems    Santa Cruz Operation
    983 Concord St.,        400 Encinal
    Framingham, MA 01701        Santa Cruz, CA 95060
    617-626-1000            408-458-1422

/usr/group Working Group on Graphics/Windows:
    Tom Greene
    Apollo Computer, Inc.
    330 Billerica Road
    Chelmsford, MA  01824
    [phone], ext. 7581

/usr/group Working Group on Realtime:
    Bill Corwin
    Intel Corp.
    5200 Elam Young Pkwy
    Hillsboro, OR 97123
    [phone]

/usr/group Working Group on Database:
    Val Skalabrin
    Unify Corp.
    1111 Howe Ave.
    Sacramento, CA 95825
    [phone]


/usr/group Working Group on Performance Measurements:
    Ram Chelluri        David F. Hinnant
    AT&T Computer Systems    Northern Telecom, Inc.
    Room E15B        Dept. 0226
    4513 Western Ave.    P.O. Box 13010
    Lisle, IL 60532        Research Triangle Park, NC  27709-3010
    [phone]        [phone]
                ...{decvax,akgua}!mcnc!rti!ntirtp!dfh

/usr/group Working Group on Security:
    Steve Sutton            Ms. Jeanne Baccash
    Consultant, Addamax        AT&T UNIX Systems Engineering
    1107 S. Orchard            190 River Road
    Urbana, IL  61801        Summit, NJ  07901
    217-344-0996            201-522-6028
                    attunix!jeanne

/usr/group Working Group on Super Computing:
    Karen Sheaffer            Robin O'Neill
    Sandia National Laboratory    Lawrence Livermore Laboratory
    P.O. Box 969            P.O. Box 5509, L560
    Livermore, CA  94550        Livermore, CA  94550
    415-422-3431            415-422-0973
                    oneill#[e-mail]


The X3H3.6 display management committee has recently formed to develop
a model to support current and future window management systems, yet
is not based directly on any existing system.  The chair solicits
help and participation:

        Georges Grinstein
        wanginst!ulowell!grinstein


The Abstract of the 1003.1 Trial Use Standard adds:

    This interface is a complement to the C Programming Language
    in the C Information Bulletin prepared by Technical Committee X3J11
    of the Accredited Standards Committee X3, Information Processing
    Systems, further specifying an environment for portable application
    software.

X3J11 is sometimes known as the C Standards Committee.  Their liaison to
P1003 is

        Don Kretsch
        AT&T
        190 River Road
        Summit, NJ 07901

A contact for information regarding publications and working groups is

        Thomas Plum
        Vice Chair, X3J11 Committee
        Plum Hall Inc.
        1 Spruce Avenue
        Cardiff, New Jersey 08232

The current document may be ordered from

        Global Engineering Documents
        2805 McGaw
        Irvine, CA 92714
        USA
        [phone]
        [phone]

Ask for the X3.159 draft standard.  The price is $65.

The current X3J11 meeting schedule is:

1988 August 15-19    Cupertino, CA
1988 December 12-16    Seattle, WA
1989 April 10-11    Phoenix, AZ


The /usr/group Standard is a principal ancestor of P1003.1, X/OPEN,
and X3J11.  It may be ordered for $15.00 from:

        /usr/group Standards Committee
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        Tel: [phone]
        Fax: [phone]

/usr/group also publishes an eight page document, ``Your Guide to POSIX,''
explaining what IEEE 1003 is, and a nineteen page document, ``POSIX Explored,''
about technical aspects of IEEE 1003.1, and its relations to other standards
and historical implementations.  Contact /usr/group at the above address
for details.


The System V Interface Definition (The Purple Book, or SVID).
This is the AT&T standard and is one of the most frequently-used
references of the IEEE 1003 committee.

        AT&T Customer Information Center
        Attn:  Customer Service Representative
        P.O. Box 19901
        Indianapolis, IN 46219
        U.S.A.

        800-432-6600 (Inside U.S.A.)
        800-255-1242 (Inside Canada)
        317-352-8557 (Outside U.S.A. and Canada)

    System V Interface Definition, Issue 2
    should be ordered by the following select codes:

    Select Code:    Volume:        Topics:
    320-011        Volume I    Base System
                    Kernel Extension
    320-012        Volume II    Basic Utilities Extension
                    Advanced Utilities Extension
                    Software Development Extension
                    Administered System Extension
                    Terminal Volume Interface Extension
    320-013        Volume III    Base System Addendum
                    Terminal Interface Extension
                    Network Services Extension
    307-131        I, II, III    (all three volumes)

The price is about 37 U.S. dollars for each volume or $84 for all three.
Major credit cards are accepted for telephone orders:  mail orders
should include a check or money order, payable to AT&T.


The X/OPEN PORTABILITY GUIDE (The Green Book)
is another reference frequently used by IEEE 1003.

The X/OPEN Group is "Ten of the world's major information system
suppliers" (at time of publication, Bull, DEC, Ericsson, Hewlett-Packard,
ICL, NIXDORF, Olivetti, Philips, Siemens and Unisys and subsequently
augmented by AT&T) who have produced a document intended to promote
the writing of portable applications.  They closely follow both SVID
and POSIX, and cite the /usr/group standard as contributing, but
X/OPEN's books cover a wider area than any of those.

The book is published by

        Elsevier Science Publishers B.V.
        Book Order Department
        P.O. Box 1991
        1000 BZ Amsterdam
        The Netherlands

and distributed in the U.S.A. and Canada by:

        Elsevier Science Publishing Company, Inc.
        52 Vanderbilt Avenue
        New York, NY 10017
        U.S.A.

There are currently five volumes:
    1) System V Specification Commands and Utilities
    2) System V Specification System Calls and Libraries
    3) System V Specification Supplementary Definitions
    4) Programming Languages
    5) Data Management

They take a large number of credit cards and other forms of payment.

Comments, suggestions, error reports, etc., for Issue 2 of the Green Book
may be mailed directly to:

        [e-mail]
        uunet!mcvax!inset!xopen!xpg2

Information about X/OPEN can be requested from:

        Mike Lambert
        Technical Director
        X/OPEN Ltd
        c/o ICL BRA01
        Lovelace Road
        Bracknell
        Berkshire
        England
        [phone]
        [e-mail]
        uunet!mcvax!inset!xopen!mgl


Finally, 4.2BSD and 4.3BSD have influenced POSIX in a number of areas.
The best reference on them is the 4.3BSD manuals, published by USENIX.
An order form may be obtained from:

        Howard Press
        c/o USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710

        415-528-8649
        {ucbvax,decvax}!usenix!office

4.3BSD User's Manual Set (3 volumes)        $25.00
    User's Reference Manual
    User's Supplementary Documents
    Master Index

4.3BSD Programmer's Manual Set (3 volumes)    $25.00
    Programmer's Reference Maual
    Programmer's Supplementary Documents, Volume 1
    Programmer's Supplementary Documents, Volume 2

4.3BSD System Manager's Manual (1 volume)    $10.00

Unfortunately, there are some license restrictions.
Contact the USENIX office for details.

Volume-Number: Volume 14, Number 34

From news  Sat Jul 23 22:49:38 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA27723; Sat, 23 Jul 88 22:49:38 EDT
From: <[e-mail]>
Newsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
Subject: Access to UNIX User Groups and Publications
Message-Id: <[e-mail]>
Expires: 22 Aug 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Date: 24 Jul 88 00:48:28 GMT
Apparently-To: std-unix-archive
Status: O

From: [e-mail]

This is the latest in a series of similar comp.std.unix articles,
intended to give summary information about UNIX User groups
and publications; to be accurate, but not exhaustive.
I'm cross-posting it to comp.org.usenix and comp.unix.questions
because there might be interest there.

There are two related articles, posted at the same time as this one,
and with subjects ``Calendar of UNIX-related Events'' and ``Access to
UNIX-Related Standards.''  The latter is posted only to comp.std.unix.

Corrections and additions to this article are solicited.  I keep track
of the conferences, groups, and publications that I attend, am a member
of, or subscribe to.  All others (the majority of the listings) I derive
either from listings elsewhere, or from contributions by readers.
In particular, the meeting schedules and descriptions of most of the
groups are provided by their members.  If a group doesn't have a
meeting schedule listed, it's because nobody has sent me one.  This is
a low-budget operation:  I publish what I have on hand when the time
comes (approximately monthly).

Recent additions: Sun User Group date and place.  OSF update.


Access information is given in this article for the following:
user groups:    USENIX, /usr/group, EUUG, AUUG, NZUSUGI, JUS, KUUG, AMIX,
        DECUS UNIX SIG, Sun User Group (SUG),
        Apollo DOMAIN Users' Society (ADUS),
        AT&T and Sun V.4 Software Developer Conferences,
        Open Software Foundation (OSF).
newsletters:    ;login:, /usr/digest, EUUGN, AUUGN, NUZ
journal:    Computing Systems
magazines:    CommUNIXations, UNIX REVIEW, UNIX/WORLD,
        Multi-User Computing Magazine, UNIX Systems, UNIX Magazine

Telephone numbers are given in international format, i.e., +n at
the beginning for the country code, e.g., +44 is England, +81 Japan,
+82 Korea, +61 Australia, +64 New Zealand, and +1 is U.S.A. or Canada.

UNIX is a Registered Trademark of AT&T.


USENIX is ``The Professional and Technical UNIX(R) Association.''

        USENIX Association
        P.O. Box 2299
        Berkeley, CA 94710
        U.S.A.
        [phone]
        {uunet,ucbvax,decvax}!usenix!office
        [e-mail]

USENIX sponsors two USENIX Conferences a year, featuring technical papers,
as well as tutorials, and with vendor exhibits at the summer conferences:

    Jan 31-Feb 3 1989 Town & Country Inn, San Diego, CA
    Jun 12-16 1989    Hyatt Regency, Baltimore, MD
    Jan 23-26 1990    Washington, DC
    Jun 11-15 1990    Marriott Hotel, Anaheim, CA
    Jan 22-25 1991    Dallas, TX
    Jun 10-14 1991    Opryland, Nashville, TN

They also sponsor workshops, such as
    Aug 29-30 1988    UNIX Security, Portland, OR
    Sep 26-27 1988    UNIX & Supercomputing, Pittsburgh, PA
    Oct 17-20 1988    C++ Conference, Denver, CO
    Nov 17-18 1988    Large Installation System Administration II, Monterey,CA
    Apr    1989    Software Management, New Orleans, LA

Proceedings for all conferences and workshops are available at
the door and by mail later.

USENIX publishes ``;login:  The USENIX Association Newsletter''
bimonthly.  It is sent free of charge to all their members and
includes technical papers.  There is a USENET newsgroup,
comp.org.usenix, for discussion of USENIX-related matters.

In 1988, USENIX started publishing a new refereed quarterly
technical journal, ``Computing Systems:  The Journal of the USENIX
Association,'' in cooperation with University of California Press.

They also publish an edition of the 4.3BSD manuals and distribute the
2.10BSD software distribution.  They coordinate a software exchange for
appropriately licensed members.  They occasionally sponsor experiments,
such as methods of improving the USENET and UUCP networks (e.g., UUNET),
that are of interest and use to the membership.

There is a USENIX Institutional Representative on the IEEE P1003
Portable Operating System Interface for Computer Environments Committee.
That representative also moderates the USENET newsgroup comp.std.unix,
which is for discussion of UNIX-related standards, especially P1003.
There is also a USENIX Standards Watchdog Committee following several
standards bodies.  For more details, see the posting in comp.std.unix,
``Access to UNIX-Related Standards.''


/usr/group is a non-profit trade association dedicated to the promotion
of products and services based on the UNIX operating system.

        /usr/group
        4655 Old Ironsides Drive, Suite 200
        Santa Clara, California 95054
        U.S.A.
        tel: [phone]
        fax: [phone]

The annual UniForum Conference and Trade Show is sponsored by /usr/group
and features vendor exhibits, as well as tutorials and technical sessions.

    Feb 28-Mar 3 1989 Moscone Center, San Francisco, CA
    Jan 23-26 1990    Washington Hilton, Washington, DC
    Jan 22-25 1991    Infomart, Dallas, TX
    Jan 21-24 1992    Moscone Center, San Francisco CA (tentative)

They also sponsor a regional show, UniForum D.C.:

    Aug 2-4 1988    Washington Hilton Hotel, Washington, D.C.

Proceedings for all conferences are available at the shows and later
by mail.

/usr/group publishes ``CommUNIXations,'' a member magazine that
features articles by industry leaders and observers, technical issues,
standards coverage, and new product announcements.

/usr/group also publishes the ``UNIX Products Directory,'' which lists
products and services developed specifically for the UNIX operating system.
``/usr/digest'' is also published by /usr/group.  This newsletter covers
product announcements and industry projections, and is sent biweekly
to General members of /usr/group and to non-member subscribers.

/usr/group has long been deeply involved in UNIX standardization,
having sponsored the ``/usr/group 1984 Standard,'' providing an Institutional
Representative to the IEEE P1003 Portable Operating System for Computer
Environments Committee, and sponsoring the /usr/group Technical Committee
on areas that P1003 has not yet addressed.  They have recently produced
an executive summary, ``Your Guide to POSIX,'' and a technical overview
``POSIX Explored,'' and funded production of a draft of a ``Rationale and
Notes'' appendix for IEEE 1003.1.


EUUG is the European UNIX systems Users Group, which is currently
celebrating its tenth anniversary.  EUUG is closely coordinated with
national groups in Europe, and with the European UNIX network, EUnet.

        EUUG secretariat
        Owles Hall
        Buntingford
        Herts SG9 9PL
        England
        Telephone [phone]
        Telefax [phone]
        uunet!mcvax!inset!euug
        [e-mail]

They have a newsletter, EUUGN (a previous version of this article
appeared in the latest one), and hold two conferences a year:
    3-7 October 1988, Lisbon, Portugal
    April 1989, Brussels, Belgium


AUUG is the Australian UNIX systems Users Group.

        AUUG
        P.O. Box 366
        Kensington
        N.S.W.    2033
        Australia
        uunet!munnari!auug
        [e-mail]

Phone contact can occasionally be made at [phone]

AUUG holds at least one conference a year, usually in the spring
(August or September).  The next one will be in Melbourne on 13-15
September 1988, will be the first three day meeting, will have a larger
equipment exhibition than any before, and will be professionally
organized for the first time.

They publish a newsletter (AUUGN) at a frequency defined to be every 2 months.


The New Zealand UNIX Systems User Group, Inc. (NZUSUGI) has an annual meeting
and publishes a newsletter, ``NUZ.''

        New Zealand UNIX Systems User Group
        P.O. Box 585
        Hamilton
        New Zealand
        [phone]

If you wish to present a paper, acceptance of which entitles you to a free
conference registration, please contact the local speakers organiser,
Dr Dick Cooper, ADATA, PO Box 2555, Christchurch, New Zealand,
[e-mail]   or ...uunet!vuwcomp!cantuar!dick

If you would just like to attend, please respond to Ray Brownrigg, including
a postal address for the delivery of further information as it becomes
available.  Registration forms are expected to be available in February.

        UUCP: {utai!calgary,uunet}!vuwcomp!dsiramd!ray
        ACSnet:    [e-mail][@munnari]
        Ray Brownrigg
        Applied Maths Div, DSIR
        PO Box 1335
        Wellington
        New Zealand


The Korean UNIX User Group (KUUG) has a software distribution service
and a newsletter.

        Korean UNIX User Group
        ETRI
        P.O. Box 8
        Daedug Science Town
        Chungnam 300-32
        Republic of Korea
        [phone]


The Japan UNIX Society has two meetings a year, and a newsletter.

        Japan UNIX Society (JUS)
        #505 Towa-Hanzomon Corp. Bldg.
        2-12 Hayabusa-cho
        Chiyoda-ku, Tokyo 102
        Japan
        [phone]

1988 Nov 10-11    UNIX Symposium    Osaka, Japan


AMIX - the Israeli UNIX user group, is a S.I.G. of the Israeli Processing
Association (IPA). AMIX has a yearly conference (next one on 4-6 July 1988)
and a yearly workshop (last one was in November).

        AMIX, c/o IPA
        P.O. Box 919
        Ramat-Gan
        Israel, 52109
        Tel: [phone],715772
        [e-mail]
        [e-mail]


There are similar groups in other parts of the world.  If such a group
wishes to be included in later versions of this access list, they
should please send me information.

There is a partial list of national organizations in the November/December
1987 CommUNIXations.



DECUS, the Digital Equipment Computer Users Society,
has a UNIX SIG (Special Interest Group) that participates
in its general meetings, which are held twice a year.

        DECUS U.S. Chapter
        219 Boston Post Road, BP02
        Marlboro, Massachusetts  01752-1850
        U.S.A.
        [phone]

The next DECUS Symposia are:

    Oct 17-21, 1988        Anaheim, California
    May 8-12, 1989        Atlanta, Georgia
    Nov 6-10, 1989        Anaheim, California
    May 7-11, 1990        New Orleans, Louisiana

See also the USENET newsgroup comp.org.decus.


The Sun User Group (SUG) is an international organization that promotes
communication among Sun users, OEMs, third party vendors, and Sun
Microsystems, Inc.  SUG sponsors conferences, collects and distributes
software, produces the README newsletter and T-shirts, sponsors local
user groups, and communicates members' problems to Sun employees and
management.

    Sun Microsystems User Group, Inc.
    2550 Garcia Avenue
    Mountain View, CA  94043
    U.S.A.
    [phone]
    [e-mail]
    sun!users

Their next annual conference is:

1988 Dec 5-7    Fontainebleau Hilton, Miami Beach, Florida


ADUS is the Apollo DOMAIN Users' Society:

    Apollo DOMAIN Users' Society
    c/o Andrea Woloski, ADUS Coordinator
    Apollo Computer Inc.
    330 Billerica Rd.
    Chelmsford, MA 01824
    [phone], x4448



AT&T and Sun Microsystems are holding a series of
Software Developer Conferences on System V Release 4.0,
related to the Sun/AT&T Applications Binary Interface (ABI).

1988 Sep 14-16    New York, NY
1988 Sep 27-29    Los Angeles, CA
1988 Oct 11-13    Tokyo, Japan
1988 Oct 25-27    London, England
1988 Nov  9-11    Boston, MA
1988 Nov 29-Dec 1    Chicago, IL
1988 Dec 13-15    Washington, DC
1988 TBA    Toronto, ON

For more information, call 1-800-387-6100.


The Open Software Foundation (OSF) is a vendor group formed 17 May 1988
by Apollo, Bull, DEC, HP, IBM, Nixdorff, and Siemens, and later joined
by Philips.  Excerpts from a press release of that date:

The Open Software Foundation (OSF) will develop a software environment,
including application interfaces, advanced system extensions, and a new
operating system, using X/Open(tm) and POSIX* specifications as the
starting point. ...  OSF membership is available to computer hardware
and software suppliers, educational institutions, and government
agencies around the world.  ...  The foundation has a management
organization, staff, and a funding comittment in excess of $90 million
to begin immediate operations.  Its initial development will be based
on technologies offered by the members and its own research, to be
carried out worldwide.

A research institute is being created to fund research for the
advancement of applications portability, interoperability standards,
and other advanced technologies for future foundation use.  An
academic advisory panel will provide guidance and input to the
institute.  The Institute's research will be conducted worldwide.

For more information, contact:

    Deborah Siegel
    Cohn & Wolfe
    [phone]

or

    [phone]
    Larry Lytle or Gary McCormack
    Open Software Foundation
    20 Ballard Way
    Lawrence, MA 01843

The main general circulation (more than 10,000 copies per issue) magazines
specifically about the UNIX system are:

    UNIX REVIEW            UNIX/WORLD
    Miller Freeman Publications Co.    Tech Valley Publishing
    500 Howard Street        444 Castro St.
    San Francisco, CA 94105        Mountain View, CA 94041
    U.S.A.                U.S.A.
    monthly                monthly
    [phone]            [phone]

    Multi-User Computing magazine    UNIX Systems
    Storyplace Ltd.            Eaglehead Publishing Ltd.
    42 Colebrook Row        Maybury Road
    London  N1 8AF            Woking, Surrey GU21 5HX
    England                England
    [phone]            [phone]

    UNIX Magazine
    Jouji Ohkubo
    c/o ASCII Corp.
    [e-mail]
    [phone]
    fax: [phone]
    telex: 242-6875 ASCIIJ

Some of the above information about magazines was taken from the
November/December 1987 issue of CommUNIXations, which also lists
some smaller-circulation magazines and newsletters.

In addition, there is the Journal of the USENIX Association and
the /usr/group member magazine:

    Computing Systems        CommUNIXations
    USENIX Association        /usr/group
    P.O. Box 2299            4655 Old Ironsides Drive, Suite 200
    Berkeley, CA 94710        Santa Clara, California 95054
    U.S.A.                U.S.A.
    quarterly            bimonthly
    [phone]            [phone]


Finally, Dominic Dunlop <[e-mail]> has pointed out several
publications that frequently include articles about the UNIX system or
the C language.  I've listed them below; the comments after each entry
are his.  I have excluded listings of magazines about specific hardware.

    AT&T Technical Journal
    AT&T Bell Laboratories
    Circulation Dept.
    Room 1K-424
    101 J F Kennedy Parkway
    Short Hills, NJ 07078
    Bimonthly
    $40/yr (US); $50/yr (overseas)
    [phone]
    While few issues are devoted to UNIX,
    most turn out to mention its applications.

    Byte
    McGraw-Hill Inc.
    Phoenix Mill Lane
    Peterborough, NH 03458
    Monthly
    $22/yr (US); $25/yr(Mex,Can); $37/yr (surface); $69/yr (air,Europe)
    [phone]
    Concentrates mainly on personal computers,
    but covers low end of UNIX market in some depth.

    The C Users Journal
    ``A service of the C Users Group.''
    R&D Publications Inc
    PO Box 97
    McPherson, KS 67460
    Eight issues per year
    $20/yr (US/Mex/Can); $30/yr (overseas)
    [phone]
    Mainly DOS-oriented; some UNIX.

    Unique
    ``The UNIX System Information Source.''
    Infopro Systems
    PO Box 220
    Rescue, CA 95672
    Monthly
    $79/yr (US,overseas); $99/yr (air)
    [phone]
    High-quality industry newsletter.
    Emphasis on marketing implications of technical developments.


The following information about bookstores was taken from the
November/December 1987 issue of CommUNIXations.  In the interests of
space, I have arbitrarily limited the selection listed here to those
bookstores or suppliers specifically dedicated to computer books, and
not part of other organizations.

    Computer Literacy Bookshop    UNIX Book Service
    2590 No. First St.        35 Bermuda Terrace
    San Jose, CA 95131        Cambridge, CB4 3LD
    U.S.A.                England
    [phone]        [phone]

    Cucumber Bookshop        Jim Joyce's UNIX Book Store
    5611 Kraft Ave.            47 Potomac St.
    Rockville, MD 20852        San Francisco, CA 94117
    U.S.A.                U.S.A.
    [phone]            [phone]

Volume-Number: Volume 14, Number 35

From news  Sat Jul 23 22:54:29 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA27876; Sat, 23 Jul 88 22:54:29 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Calendar of UNIX-related Events
Message-Id: <[e-mail]>
Expires: 22 Aug 88 21:45:37 GMT
Sender: [e-mail]
Reply-To: [e-mail] (Moderator, John S. Quarterman)
Date: 24 Jul 88 00:50:26 GMT
Apparently-To: std-unix-archive
Status: O

Here is a combined calendar of planned conferences, workshops, or
standards meetings by various organizations.  I compiled it for
my own use and thought it might be of some public interest.  Most
of this information came from the various conference organizers,
although some was taken from ;login: (USENIX), 13, 1, Jan/Feb
1988 and CommUNIXations (/usr/group), VII, 6, Nov/Dec 1987.

If your favorite meeting is not listed, it's probably because I
don't know about it.  If you send me information on it, I will
probably list it both here and in the companion article, ``Access
to UNIX User Groups and Publications.'' There is also another
companion article, ``Access to UNIX-Related Standards,'' that
appears only in comp.std.unix.

Changes since last posting: Sun User Group date and place.
TCP/IP Interoperability Workshop.  NBS Standards Workshops.
USENIX Software Management Workshop.

[e-mail]    John S. Quarterman       uunet!longway!jsq
[e-mail]              88/07/23             uunet!usenix!jsq


88/07/23 pg. 2   Calendar of UNIX-Related Events    comp.std.unix

year mon days        conference         (sponsor,) (hotel,) location

1988 Aug 2-4         UniForum/DC        Washington Hilton, Washington, DC
1988 Aug 15-19       ANSI X3J11         Cupertino, CA
1988 Aug 29-30       U Security W       USENIX, Portland, OR
1988 Sep 13-15       AUUG               Melbourne, Australia
1988 Sep 14-16       V.4 Soft. Dev.     AT&T and Sun, New York, NY
1988 Sep 22          Syst. Adm. W       and Shell & Tools W, NBS, G, MD
1988 Sep 23          X Windows W        and POSIX FIPS W, NBS, G, MD
1988 Sep 26-27       U&Supercomp. W     USENIX, Pittsburgh, PA
1988 Sep 26-30       TCP/IP Interop     ACE, Santa Clara, CA
1988 Sep 27-29       V.4 Soft. Dev.     AT&T and Sun, Los Angeles, CA
1988 Oct 3-7         EUUG               Lisbon, Portugal
1988 Oct 5           POSIX Conformance  Test. & Lab. Accred. W, NBS, G, MD
1988 Oct 11-13       V.4 Soft. Dev.     AT&T and Sun, Tokyo, Japan
1988 Oct 17-21       DECUS S            Anaheim, California
1988 Oct 17-21       C++ Conference     USENIX, Denver, CO
1988 Oct 17-19,20-21 ISO SC22 & WG15    Tokyo, Japan
1988 Oct 24-28       IEEE 1003          Hawaii
1988 Oct 25-27       V.4 Soft. Dev.     AT&T and Sun, London, England
1988 Oct             UNIX Expo          New York, NY
1988 Nov  9-11       V.4 Soft. Dev.     AT&T and Sun, Boston, MA
1988 Nov 15          POSIX Appl. W      NBS, G, MD
1988 Nov 16          POSIX FIPS Rev. W  NBS, G, MD
1988 Nov 17-18       Large Install.     Syst. Adm. W II, USENIX, Monterey, CA
1988 Nov 10-11       U Symposium        JUS, Osaka, Japan
1988 Nov 29-Dec 1    V.4 Soft. Dev.     AT&T and Sun, Chicago, IL
1988 Dec             UNIX Fair          JUS, Tokyo, Japan
1988 Dec 5-7         Sun User Group     Fontainebleau Hilton, Miami Beach, FL
1988 Dec 12-16       ANSI X3J11         Seattle, WA
1988 Dec 13-15       V.4 Soft. Dev.     AT&T and Sun, Washington, DC
1988 TBA             V.4 Soft. Dev.     AT&T and Sun, Toronto, ON

1989 Jan 9-13        IEEE 1003          Embassy Suites, Ft. Lauderdale, FL
1989 Jan 17          Terminal Int. Ext. and Net. Serv. W, NBS, G, MD
1989 Jan 31-Feb 3    USENIX             Town and Country, San Diego, CA
1989 Feb             U in Gov. C&T      Ottawa, ON
1989 Feb 28-Mar 3    UniForum           Moscone Center, San Francisco, CA
1989 Apr 10-11       ANSI X3J11         Phoenix, AZ
1989 Apr 17(29?)     IEEE 1003          Minneapolis-St. Paul, MN
1989 Apr             EUUG               Brussels, Belgium
1989 Apr             Soft. Management W USENIX, New Orleans, LA
1989 May 8-12        DECUS S            Atlanta, Georgia
1989 May 16          POSIX Appl. W      NBS, G, MD
1989 May             U 8x/etc C&T       /usr/group/cdn, Toronto, ON
1989 Jun             NZSUGI             New Zealand
1989 Jun 12-16       USENIX             Hyatt Regency, Baltimore, MD
1989 Jul 10-14       IEEE 1003          San Francisco, CA
1989 Oct 16-20       IEEE 1003          Brussels (or Amsterdam)
1989 Oct             UNIX Expo          New York, NY
1989 Nov 6-10        DECUS S            Anaheim, California

[e-mail]    John S. Quarterman       uunet!longway!jsq
[e-mail]              88/07/23             uunet!usenix!jsq


88/07/23 pg. 3   Calendar of UNIX-Related Events    comp.std.unix

year mon days  conference    (sponsor,) (hotel,) location

1990 Jan 23-26 USENIX        Washington, DC
1990 Jan 23-26 UniForum      Washington Hilton, Washington, DC
1990 Jan 29    IEEE 1003     New Orleans, LA
1990 Feb       U in Gov. C&T Ottawa, ON
1990 Apr       IEEE 1003     Montreal, Quebec
1990 May 7-11  DECUS S       New Orleans, Louisiana
1990 May       U 8x/etc C&T  /usr/group/cdn, Toronto, ON
1990 Jun 11-15 USENIX        Marriott, Anaheim, CA

1991 Jan 22-25 USENIX        Dallas, TX
1991 Jan 22-25 UniForum      Infomart, Dallas, TX
1990 Feb       U in Gov. C&T Ottawa, ON
1990 May       U 8x/etc C&T  Toronto, ON
1991 Jun 10-14 USENIX        Opryland, Nashville, TN

1992 Jan 21-24 UniForum      Moscone Center, San Francisco CA

Abbreviations: C for Conference, G, MD for Gaithersburg,
Maryland, S for Symposium, T for Tradeshow, U for UNIX, V.4 for
System V Release 4.0, W for Workshop.  USENIX, EUUG, AUUG and
DECUS sponsor conferences of the same names; /usr/group sponsors
UniForum.  UNIX is a Registered Trademark of AT&T.

[e-mail]    John S. Quarterman       uunet!longway!jsq
[e-mail]              88/07/23             uunet!usenix!jsq

Volume-Number: Volume 14, Number 36

From root  Mon Jul 25 21:16:20 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA13026; Mon, 25 Jul 88 21:16:20 EDT
From: John S. Quarterman <[e-mail]>
Newsgroups: comp.std.unix,comp.org.usenix,comp.unix.questions
Subject: Re: Access to UNIX User Groups and Publications
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: longway!jsq (John S. Quarterman)
Organization: TIC
Date: 26 Jul 88 00:14:36 GMT
Apparently-To: std-unix-archive
Status: O

Peter Salus, USENIX Executive Director, reminds me that the dates
I've been posting for winter USENIX Conferences are all off by one,
because the USENIX Board of Directors decided several meetings ago
to make them all five days long, i.e., Monday through Friday, not
Tuesday through Friday.  Also, there are conferences scheduled for
1992, and at least the month and general location is known for
winter 1993.

The correct dates for all scheduled USENIX Conferences (not including
Workshops nor the C++ Conference) are these:

1989 Jan 30-Feb 3 Town & Country Inn, San Diego, CA
1989 Jun 12-16    Hyatt Regency, Baltimore, MD
1990 Jan 22-26    Washington, DC
1990 Jun 11-15    Marriott Hotel, Anaheim, CA
1991 Jan 21-25    Dallas, TX
1991 Jun 10-14    Opryland, Nashville, TN
1992 Jan 20-24    Hilton Square, San Francisco, CA
1992 Jun 8-12    Marriott, San Antonio, TX
1993 Jan    somewhere in northeast of North America

Also, the dates for the Spring 1989 EUUG are:

1989 Apr 10-14    Brussels, Belgium


Volume-Number: Volume 14, Number 37

From root  Thu Jul 28 22:32:08 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA13567; Thu, 28 Jul 88 22:32:08 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: correction info about JUS
Message-Id: <[e-mail]>
Reply-To: uunet!kddlab!jus.junet!nisimura (Tohru Nisimura at NITECH)
Date: 28 Jul 88 02:13:25 GMT
Apparently-To: std-unix-archive
Status: O

Return-Path: <[e-mail]>
From: uunet!kddlab!jus.junet!nisimura (Tohru Nisimura at NITECH)



Hello and how are you ? I found a (may be) serious incorrectness in the most
recent "Access to UNIX User Group and Publications" article.

    +---------------------------------------------------+
    Subject: Access to UNIX User Groups and Publications
    Message-ID: <[e-mail]>
    +---------------------------------------------------+

JUS office TEL phone No. was incorrect...
I made it correct and added information quite a bit.


Tohru NISHIMURA (one of JUS bod)

--

The Japan UNIX Society has two meetings a year, and a newsletter.

        Japan UNIX Society (JUS)
        #505 Towa-Hanzomon Corp. Bldg.
        2-12 Hayabusa-cho
        Chiyoda-ku, Tokyo 102
        Japan
        [e-mail]
        [phone]

1988 Nov 10-11    UNIX Symposium    Osaka, Japan
1988 Dec 17-18  UNIX FAIR '88   Tokyo, Japan


Volume-Number: Volume 14, Number 38

From root  Thu Aug  4 03:17:41 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA11539; Thu, 4 Aug 88 03:17:41 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: headings postings
Message-Id: <[e-mail]>
Reply-To: uunet!unisoft!titipu!hlj (Hal Jespersen)
Date: 28 Jul 88 04:19:01 GMT
Apparently-To: std-unix-archive

From: uunet!unisoft!titipu!hlj (Hal Jespersen)

Hi, John.  Could you pls post this to the stds newsgroup?  Thanks.

[ Hal is the Technical Editor of IEEE 1003.1.  -mod ]


                Hal Jespersen
                [phone], ext 448
                FAX: [phone]
                ...{uunet|amdahl|sun}!unisoft!hlj
                UniSoft Corporation
                6121 Hollis Street
                Emeryville, CA 94608-2092


# This is a shell archive.  Remove anything before this line,
# then unpack it by saving it in a file and typing "sh file".
#
# Wrapped by hlj on Wed Jul 27 21:16:11 PDT 1988
# Contents:  posixheads.mm

echo x - posixheads.mm
sed 's/^@//' > "posixheads.mm" <<'@//E*O*F posixheads.mm//'
@.\"
@.\"  This document contains the -mm header macros from the IEEE Std
@.\"  1003.1-1988 (POSIX).  Only the normative portions of the standard are
@.\"  included; the Appendix headings are omitted.
@.\"
@.\"  The reason this is being disseminated electronically is that the
@.\"  standard requires that each implementation provide a POSIX Conformance
@.\"  Document that describes how it supports various limits and
@.\"  implementation-defined things; see section 2.2.1.2 for a description of
@.\"  this requirement.  The implementation is required to format the
@.\"  document so that the table of contents matches the standard itself.
@.\"  So, these macros will give you a head start.  I have included all the
@.\"  heading levels (except for unnumbered headings), but I doubt that you
@.\"  would be required to include every single one.  For example, if you
@.\"  have nothing to say about a certain function (all of which should be at
@.\"  .H 3 levels), you shouldn't have to carry around the empty .H 4's
@.\"  underneath it, such as:
@.\"
@.\"      .H 4 "Synopsis."
@.\"      .H 4 "Description."
@.\"      .H 4 "Returns."
@.\"      .H 4 "Errors."
@.\"      .H 4 "References."
@.\"
@.\"  But, keep them in if you like them.
@.\"
@.\"  In case this prompts you to ask, the IEEE P1003 Working Group will not
@.\"  be making the full copyrighted standard available in any machine-readable
@.\"  format.  There are two reasons for this:
@.\"
@.\"      1.  We want to prevent unauthorized reprints, particularly
@.\"      those with invisible modifications.
@.\"
@.\"      2.  We want you to buy the book!
@.\"
@.\"  It is planned that Draft 13 of the standard will be sent out from the IEEE
@.\"  in late August; it will be dated August 15, 1988.  A typeset hard cover
@.\"  book version will follow in September/October (I hope).  Except for the
@.\"  inevitable formatting changes that crop up with working with
@.\"  typesetters, though, Draft 13 is the final word.
@.\"
@.\"                    Hal Jespersen
@.\"
@.H 1 "Scope"
@.H 1 "Definitions and General Requirements"
@.H 2 "Terminology."
@.H 2 "Conformance."
@.H 3 "Implementation Conformance."
@.H 4 "Requirements."
@.H 4 "Documentation."
@.H 4 "Conforming Implementation Options."
@.H 3 "Application Conformance."
@.H 4 "Strictly Conforming \s-1POSIX\s0 Application."
@.H 4 "Conforming \s-1POSIX\s0 Application."
@.H 5 "\s-1ISO\s0 Conforming \s-1POSIX\s0 Application."
@.H 5 "<National Body> Conforming \s-1POSIX\s0 Application."
@.H 4 "Conforming \s-1POSIX\s0 Application Using Extensions."
@.H 3 "Language-Dependent Services for the C Programming Language."
@.H 4 "Types of Conformance."
@.H 4 "C Standard Language-Dependent System Support."
@.H 4 "Common Usage C Language-Dependent System Support."
@.H 3 "Other C Language Related Specifications."
@.H 2 "General Terms."
@.H 2 "General Concepts."
@.H 2 "Error Numbers."
@.H 2 "Primitive System Data Types."
@.H 2 "Environment Description."
@.H 2 "C Language Definitions."
@.H 3 "Symbols From The C Standard."
@.H 3 "\s-1POSIX\s0 Symbols."
@.H 4 "C Standard Language-Dependent Support."
@.H 4 "Common Usage-Dependent Support."
@.H 3 "Headers and Function Prototypes."
@.H 2 "Numerical Limits."
@.H 3 "C Language Limits."
@.H 3 "Minimum Values."
@.H 3 "Run-Time Increasable Values."
@.H 3 "Run-Time Invariant Values (Possibly Indeterminate)."
@.H 3 "Pathname Variable Values."
@.H 2 "Symbolic Constants."
@.H 3 "Symbolic Constants for the \f2access\fP\^(\^) Function."
@.H 3 "Symbolic Constant for the \f2lseek\fP\^(\^) Function."
@.H 3 "Compile-Time Symbolic Constants for Portability Specifications."
@.H 3 "Execution-Time Symbolic Constants for Portability Specifications."
@.H 1 "Process Primitives"
@.H 2 "Process Creation and Execution."
@.H 3 "Process Creation."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Execute a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Process Termination."
@.H 3 "Wait for Process Termination."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Terminate a Process."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "References."
@.H 2 "Signals."
@.H 3 "Signal Concepts."
@.H 4 "Signal Names."
@.H 4 "Signal Generation and Delivery."
@.H 4 "Signal Actions."
@.H 4 "Signal Effects on Other Functions."
@.H 3 "Send a Signal to a Process."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Manipulate Signal Sets."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Examine and Change Signal Action."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Examine and Change Blocked Signals."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Examine Pending Signals."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Wait for a Signal."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Timer Operations."
@.H 3 "Schedule Alarm."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Suspend Process Execution."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Delay Process Execution."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 1 "Process Environment"
@.H 2 "Process Identification."
@.H 3 "Get Process and Parent Process \s-1ID\s0s."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "User Identification."
@.H 3 "Get Real User, Effective User, Real Group, and Effective Group \s-1ID\s0s."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Set User and Group \s-1ID\s0s."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Get Supplementary Group \s-1ID\s0s."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Get User Name."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Process Groups."
@.H 3 "Get Process Group \s-1ID\s0."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Create Session and Set Process Group \s-1ID\s0."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Set Process Group \s-1ID\s0 for Job Control."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "System Identification."
@.H 3 "System Name."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 2 "Time."
@.H 3 "Get System Time."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 3 "Process Times."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Environment Variables."
@.H 3 "Environment Access."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Terminal Identification."
@.H 3 "Generate Terminal Pathname."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Determine Terminal Device Name."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 2 "Configurable System Variables."
@.H 3 "Get Configurable System Variables."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 1 "Files and Directories"
@.H 2 "Directories."
@.H 3 "Format of Directory Entries."
@.H 3 "Directory Operations."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Working Directory."
@.H 3 "Change Current Working Directory."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Working Directory Pathname."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "General File Creation."
@.H 3 "Open a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Create a New File or Rewrite an Existing One."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "References."
@.H 3 "Set File Creation Mask."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Link to a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Special File Creation."
@.H 3 "Make a Directory."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Make a \s-1FIFO\s0 Special File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "File Removal."
@.H 3 "Remove Directory Entries."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Remove a Directory."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Rename a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "File Characteristics."
@.H 3 "File Characteristics: Header and Data Structure."
@.H 4 "<sys/stat.h> File Types."
@.H 4 "<sys/stat.h> File Modes."
@.H 4 "<sys/stat.h> Time Entries."
@.H 4 "References."
@.H 3 "Get File Status."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "File Accessibility."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Change File Modes."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Change Owner and Group of a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Set File Access and Modification Times."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Configurable Pathname Variables."
@.H 3 "Get Configurable Pathname Variables."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 1 "Input and Output Primitives"
@.H 2 "Pipes."
@.H 3 "Create an Inter-Process Channel."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "File Descriptor Manipulation."
@.H 3 "Duplicate an Open File Descriptor."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "File Descriptor Deassignment."
@.H 3 "Close a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Input and Output."
@.H 3 "Read from a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Write to a File."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 2 "Control Operations on Files."
@.H 3 "Data Definitions for File Control Operations."
@.H 3 "File Control."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Reposition Read/Write File Offset."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 1 "Device- and Class-Specific Functions"
@.H 2 "General Terminal Interface."
@.H 3 "Interface Characteristics."
@.H 4 "Description."
@.H 4 "Opening a Terminal Device File."
@.H 4 "Process Groups."
@.H 4 "The Controlling Terminal."
@.H 4 "Terminal Access Control."
@.H 4 "Input Processing and Reading Data."
@.H 4 "Canonical Mode Input Processing."
@.H 4 "Non-Canonical Mode Input Processing."
@.H 5 "Case A: \s-1MIN\s0 > 0, \s-1TIME\s0 > 0."
@.H 5 "Case B: \s-1MIN\s0 > 0, \s-1TIME\s0 \&\fC=\fP 0."
@.H 5 "Case C: \s-1MIN\s0 \&\fC=\fP 0, \s-1TIME\s0 > 0."
@.H 5 "Case D: \s-1MIN\s0 \&\fC=\fP 0, \s-1TIME\s0 \&\fC=\fP 0."
@.H 4 "Writing Data and Output Processing."
@.H 4 "Special Characters."
@.H 4 "Modem Disconnect."
@.H 4 "Closing a Terminal Device File."
@.H 3 "Settable Parameters."
@.H 4 "\f2termios\fP Structure."
@.H 4 "Input Modes."
@.H 4 "Output Modes."
@.H 4 "Control Modes."
@.H 4 "Local Modes."
@.H 4 "Special Control Characters."
@.H 4 "Baud Rate Functions."
@.H 5 "Synopsis."
@.H 5 "Description."
@.H 5 "Returns."
@.H 5 "Errors."
@.H 5 "References."
@.H 2 "General Terminal Interface Control Functions."
@.H 3 "Get and Set State."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Line Control Functions."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Get Foreground Process Group \s-1ID\s0."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Set Foreground Process Group \s-1ID\s0."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 1 "Language-Specific Services for the C Programming Language"
@.H 2 "Referenced C Language Routines."
@.H 3 "Extensions to Time Functions."
@.H 3 "Extensions to \f2setlocale\fP\^() Function."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 2 "\s-1FILE\s0-Type C Language Functions."
@.H 3 "Map a Stream Pointer to a File Descriptor."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Open a Stream on a File Descriptor."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Returns."
@.H 4 "Errors."
@.H 4 "References."
@.H 3 "Interactions of Other \s-1FILE\s0-Type C Functions."
@.H 4 "\f2fopen\fP\^()."
@.H 4 "\f2fclose\fP\^()."
@.H 4 "\f2freopen\fP\^()."
@.H 4 "\f2fflush\fP\^()."
@.H 4 "\f2fgetc\fP\^(), \f2fgets\fP\^(), \f2fread\fP\^(), \f2getc\fP\^(), \f2getchar\fP\^(), \f2gets\fP\^(), \f2scanf\fP\^(), \f2fscanf\fP\^()."
@.H 4 "\f2fputc\fP\^(), \f2fputs\fP\^(), \f2fwrite\fP\^(), \f2putc\fP\^(), \f2putchar\fP\^(), \f2puts\fP\^(), \f2printf\fP\^(), \f2vprintf\fP\^(), \f2vfprintf\fP\^()."
@.H 4 "\f2fseek\fP\^(), \f2rewind\fP\^()."
@.H 4 "\f2perror\fP\^()."
@.H 4 "\f2tmpfile\fP\^()."
@.H 4 "\f2ftell\fP\^()."
@.H 4 "Error Reporting."
@.H 4 "\f2exit\fP\^(), \f2abort\fP\^()."
@.H 3 "Operations on Files \(em the \f2remove\fP\^() Function."
@.H 2 "Other C Language Functions."
@.H 3 "Non-Local Jumps."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "References."
@.H 3 "Set Time Zone."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 1 "System Databases"
@.H 2 "System Databases."
@.H 2 "Database Access."
@.H 3 "Group Database Access."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Errors."
@.H 4 "Returns."
@.H 4 "References."
@.H 3 "User Database Access."
@.H 4 "Synopsis."
@.H 4 "Description."
@.H 4 "Errors."
@.H 4 "Returns."
@.H 4 "References."
@.H 1 "Data Interchange Format"
@.H 2 "Archive/Interchange File Format."
@.H 3 "Extended \&\fCtar\fP Format."
@.H 4 "References."
@.H 3 "Extended \&\fCcpio\fP Format."
@.H 4 "Header."
@.H 4 "File Name."
@.H 4 "File Data."
@.H 4 "Special Entries."
@.H 4 "\&\fCcpio\fP Values."
@.H 4 "References."
@.H 3 "Multiple Volumes."
@//E*O*F posixheads.mm//
chmod u=rwx,g=r,o=r posixheads.mm

echo Inspecting for damage in transit...
temp=/tmp/shar$$; dtemp=/tmp/.shar$$
trap "rm -f $temp $dtemp; exit" 0 1 2 3 15
cat > $temp <<\!!!
    558   2373  14684 posixheads.mm
!!!
wc  posixheads.mm | sed 's=[^ ]*/==' | diff -b $temp - >$dtemp
if [ -s $dtemp ]
then echo "Ouch [diff of wc output]:" ; cat $dtemp
else echo "No problems found."
fi
exit 0


Volume-Number: Volume 14, Number 39

From news  Tue Aug  9 20:26:33 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA27993; Tue, 9 Aug 88 20:26:33 EDT
From: <[e-mail]>
Newsgroups: comp.std.unix
Subject: please add to list
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail]
Date: 9 Aug 88 15:22:44 GMT
Apparently-To: std-unix-archive

From: [e-mail]

I am enclosing a file about out upcoming UNIX exposition in Detroit.
Kindly add it to your regular announcements about UNIX events. Thank
you.
                    -- shan
-------------------------------------------------------------------
Subject: Announcement: Expo@Detroit
Keywords: michigan!/usr/group, Conference, Tutorials, Product Exhibition
Location: Detroit, Michigan

    Expo@Detroit Technical Conference, Tutorials & Exhibition

Expo@Detroit is a conference and trade show designed to attract an
impressive array of attendees - users and developers, buyers and
distributors. This highly concentrated forum features:

    Vendor exhibits and product demonstrations
    Market and industry oriented conference sessions
    Intensive all-day technical tutorials on UNIX and related topics

A large number of people from southeastern Michigan and surrounding areas
will be invited to participate in this exposition, and these conferences,
and tutorials looking for the latest in UNIX, hardware and software
technology.

The Expo@Detroit Technical Conference and Exhibition will
be held September 13 - 14, 1988 at the Southfield Civic Center
in Southfield, Michigan. The event is sponsored by michigan!/usr/group,
the local affiliate of the UNIX trade association, /usr/group.
Michigan!/usr/group is a non-profit, vendor independent organization
dedicated to the promotion of UNIX, and its related  products and
services, thru the exchange of information among participants in the
UNIX industry.

The product exhibition will feature products such as mainframe,
mini, and microcomputer systems, applications and system software,
database systems, communications and network systems, peripheral
computer equipment, educational services, and books and periodicals.

Expo@Detroit will also offer a program of intensive UNIX
full-day tutorials, including subjects such as

    Introductory C Programming
    Advanced C Programming
    Shell Programming
    System Administration
    UUCP and Networking

Two days of conference sessions will take place in conjuction with
the exposition. Conferences will be half day sessions with several
presentations regarding specific topics. These presentations will be
delivered by a wide spectrum of users (GM, Ford, etc), vendors (DEC,
Sun, AT&T, Apollo, Pyramid, Prime, etc.) and consultants (Williams
International, etc.). Topics will include:

    UNIX Standards
         System V
         BSD
         POSIX
         X-windows
         Networking
    Databases
    Manufacturing Applications
    Performance & Benchmarking

For registration/applications information, contact
    Expotech Inc.
    1264 Bedford Rd.
    Grosse Pointe Park, MI 48230
    [phone]

or mail at     INTERNET:    [e-mail]
         UUCP:        uunet!umix!um.cc.umich.edu!aimee_moran
        CIS:        72000,400
        GEnie:        Expotech
        AppleLink:    X1156

or you can contact any of the following for further assistance:
Michael Wayne:    [e-mail]
JT Vogt:    [e-mail]
Sharan Kalwani:    [e-mail]


Volume-Number: Volume 14, Number 40

From news  Thu Aug 11 15:25:51 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA21844; Thu, 11 Aug 88 15:25:51 EDT
From: Jerry Carlin <[e-mail]>
Newsgroups: comp.std.unix
Subject: USING
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail] (Jerry Carlin)
Date: 10 Aug 88 15:35:46 GMT
Apparently-To: std-unix-archive

From: [e-mail] (Jerry Carlin)

Please add USING to the list of organizations.

Also, the 2nd USING national meeting is September 19-21 in Denver. Please
add to calendar.

If you would like me to add info or modify what I've sent, I'd be happy to.
----------------------------

USING: The UNIX Systems Information Networking Group is a users group
in which members are invited to share common telecommunications industry
UNIX based-systems solutions and concerns. USING is organized primarily
by individuals within RBOC and Independent Telephone Company Organizations.

Membership costs $10 per year. If you are interested in the organization,
please write USING, Attention: Membership, P. O. Box 1077, Lisle, IL 60532.


Volume-Number: Volume 14, Number 41

From news  Thu Aug 11 15:34:12 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA22524; Thu, 11 Aug 88 15:34:12 EDT
From: John T. Nelson <[e-mail]>
Newsgroups: comp.std.unix
Subject: Railroading standards...
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: John T. Nelson <[e-mail]>
Date: 11 Aug 88 01:00:04 GMT
Apparently-To: std-unix-archive

From: John T. Nelson <[e-mail]>

>Subject: Re: Eh Charlie... what's that big orange furry thing on the tracks?

    From: Fred Blonder <[e-mail]>

        From: John T. Nelson <[e-mail]>

        Watching trains is fun.  The signaling methods are a tad
        baroque but interesting.  . . .

    But usually work. After all, they've had a century to work most of the
    bugs out of the system.

Yes but look at how many standards for signaling were devised!

Of course we in the computer industry are MUCH smarter.  We devise standards
that benefit everyone and are flexible to accomodate changes in technology.

Imagine what the computer industry would be like if it were run like
the bad old days of railroading!  We would have hundreds of different
rail guages and signaling protocols as well as completely incompatible
tools, engine parts and engines with different controls!  How could
I transfer coal loaded on my trains to your tracks?  How could my
engineers operate your locomotives?  How could I maintain your engines
in my railyard?

HA HA HA ha ha ha ha ... thank heaven we are so much smarter than that!



John T. Nelson            UUCP: sun!sundc!potomac!jtn
Advanced Decision Systems    Internet:  [e-mail]
1500 Wilson Blvd #512; Arlington, VA 22209-2401        [phone]

Shar and Enjoy!



Volume-Number: Volume 14, Number 42

From news  Fri Aug 12 08:35:51 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA08392; Fri, 12 Aug 88 08:35:51 EDT
From: Shannon Nelson <[e-mail]>
Newsgroups: comp.std.unix
Subject: Need a UNIX command test suite
Keywords: UNIX commands test
Message-Id: <[e-mail]>
Sender: [e-mail]
Reply-To: Shannon Nelson <[e-mail]>
Date: 3 Aug 88 22:15:26 GMT
Apparently-To: std-unix-archive

From: Shannon Nelson <[e-mail]>

I'm involved in a project that will be creating a UNIX-like
environment on a new architecture.  Naturally, we'd like to keep the
commands as close as possible to "natural UNIX" (whatever that is).

What we're looking for is a suite of tests for UNIX commands, such as
cat, ls, tar, cpio, grep, ln, size, etc.  Perhaps something like SVVS,
but for the UNIX commands instead of the programming interface.  Source
code for such a suite is required so that we can modify it as necessary
for our environment.

If you know of and/or have something that would be useful, please
contact me at the following email address:

    ...tektronix!ogcvax!intelisc!shannon
        or
    [e-mail]

(Chris Torek or Doug Gwyn, can you be of help?)

As always, if there is enough interest, I'll compile and post...

"And thank you for your support."


Volume-Number: Volume 14, Number 43

From news  Sun Aug 14 17:57:14 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA03630; Sun, 14 Aug 88 17:57:14 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Real-time UNIX
Message-Id: <[e-mail]>
Reply-To: uunet!sugar!peter (Peter da Silva)
Organization: Sugar Land Unix - Houston, TX
Date: 13 Aug 88 21:32:20 GMT
Apparently-To: std-unix-archive

From: uunet!sugar!peter (Peter da Silva)


What sorts of approaches have people taken to doing real-time control under
UNIX? How far apart are the different standards?

[ There is no standard yet that I know of.  IEEE 1003.4 is working on one,
and there is also the /usr/group Technical Committee Working Group on Realtime.
There will be some comments on them in Shane's next report, which we should
see shortly.  -mod ]

[I have this fantasy of one day being able to write a program that does
 something like this under UNIX:

 comm=open("/dev/tty3a", 2);
 status=open("/dev/tty3b", 2);

 memory=open("/usr/scada/mempool", 2);

 mempool=map_file(memory, POOLSIZE);

 commbit = 1 << (commflag = async_read(comm, commbuf, 1));
 statbit = 1 << (statflag = async_read(status, statbuf, 1));

 bits = commbit|statbit;
 while(bits) {
  flags = async_wait(bits);
  if(flags&commbit) {
   bits &= ~commbit;
   do something with *commbuf;
   repost read if necessary;
  }
  if(flags&statbit) {
   bits &= ~statbit;
   do something with *statbuf;
   repost read if necessary;
  }
 }
]
--
        Peter da Silva  `-_-'  [e-mail]
         Have you hugged  U  your wolf today?


Volume-Number: Volume 14, Number 44

From news  Fri Aug 19 14:07:13 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA16964; Fri, 19 Aug 88 14:07:13 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: Re: Real-time UNIX
Keywords: RealTime Unix
Message-Id: <[e-mail]>
References: <[e-mail]>
Reply-To: uunet!csuna.csun.edu!sdsu!aeusemrs (Mike Stump)
Organization: California State University, Northridge
Date: 16 Aug 88 21:24:09 GMT
Apparently-To: std-unix-archive

From: uunet!csun.edu!csuna!aeusemrs (mike stump)

In article <[e-mail]> uunet!sugar!peter (Peter da Silva) writes:
>What sorts of approaches have people taken to doing real-time control under
>UNIX? How far apart are the different standards?

Below is from the Moderator, I hope.

[ All comments I put in as the moderator are marked as from the
moderator, with -mod at the end.  The material you're referring to
(below, starting ``I have this fantasy'') was not so marked, and wasn't
from me:  it came with the submission.  Your submission is also littered
with remarks in square brackets.  I assume you put them there, since I didn't.

In general, I would recommend that submittors use parentheses when
they mean parentheses, instead of using brackets.  -mod ]

>[I have this fantasy of one day being able to write a program that does
> something like this under UNIX:
>
> comm=open("/dev/tty3a", 2);
> status=open("/dev/tty3b", 2);
>
> memory=open("/usr/scada/mempool", 2);
>
> mempool=map_file(memory, POOLSIZE);
>
> commbit = 1 << (commflag = async_read(comm, commbuf, 1));
> statbit = 1 << (statflag = async_read(status, statbuf, 1));
>
> bits = commbit|statbit;
> while(bits) {
>  flags = async_wait(bits);
>  if(flags&commbit) {
>   bits &= ~commbit;
>   do something with *commbuf;
>   repost read if necessary;
>  }
>  if(flags&statbit) {
>   bits &= ~statbit;
>   do something with *statbuf;
>   repost read if necessary;
>  }
> }
>]

I don't offen support, or give hardware advice for systems that run Unix;
but, In partial response to the Moderators comments about RealTime Unix, I
feel I must respond.

[ See above about whose remarks you're responding to.  -mod ]

Elxsi makes a very interesting computer when it comes to real time;
some of the features include:
being able to lock down physical memory, [Yes, I know everybody can do this,
                      but without kernel hacking?!]
lock down a register set, [can you say fast contex switch]
high priority processes, [can you say preempt the Operating System?]
Timer support to programs, [again, no kernel hacking].

And just think, System V, and Berkeley 4.2 run under or was that along with
EMBOS, and EMS, at the same time. (their VMS clone, although some bugs they
don't emulate :-))

All on 1-12 CPU machine [yes, it is pretty transparent], with up to two
gigabytes of memory.  And yes, as a matter of fact, I DO have a fully loaded
one in my back bedroom, right next to the 32ton refrigeration unit. :-)

And, now to the point, one is able to write the above program with little
difficulty.


Volume-Number: Volume 14, Number 45

From root  Sat Aug 27 02:01:25 1988
Received: by uunet.UU.NET (5.59/1.14)
    id AA06664; Sat, 27 Aug 88 02:01:25 EDT
From: [e-mail] (Moderator, John S. Quarterman)
Newsgroups: comp.std.unix
Subject: End of Volume 14
Message-Id: <[e-mail]>
Reply-To: [e-mail]
Date: 27 Aug 88 04:38:01 GMT
Apparently-To: std-unix-archive

This is the last article in Volume 14 of comp.std.unix.
Volume 15 will start forthwith, or as soon as I get the
bad entries in the [e-mail] mailing list
weeded out after mailer daemons reply to this message.

Upcoming:
    What is std-unix/comp.std.unix.
    Standards Update #3 from Shane P. McCarron.
    Access to UNIX-Related Standards.
    Access to UNIX User Groups and Publications.
    Calendar of UNIX-Related Events.

There will probably also be diffs for the last three of those.

Three of these messages are about 500 lines long, or 15K each.
I will space them out a bit to save mailboxes, but if you don't
like long messages, now's the time to unsubscribe.

PS:  IEEE 1003.1 was finally approved on 22 August 1988.


Volume-Number: Volume 14, Number 46