home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
std_unix
/
v20
/
followdir
/
1003.1.a
next >
Wrap
Internet Message Format
|
1990-08-02
|
3KB
From jsq@tic.com Sat Jun 30 01:21:24 1990
Received: from cs.utexas.edu by uunet.uu.net (5.61/1.14) with SMTP
id AA08840; Sat, 30 Jun 90 01:21:24 -0400
Posted-Date: 29 Jun 90 21:33:13 GMT
Received: by cs.utexas.edu (5.64/1.65)
id AA05298; Sat, 30 Jun 90 00:21:19 -0500
Received: by longway.tic.com (4.22/tic.1.2)
id AA12387; Sat, 30 Jun 90 00:20:56 cdt
From: Doug Gwyn <gwyn@smoke.brl.mil>
Newsgroups: comp.std.unix
Subject: Re: Standards Update, IEEE 1003.1: System services interface
Message-Id: <754@longway.TIC.COM>
References: <385@usenix.ORG>
Sender: std-unix@tic.com
Reply-To: std-unix@uunet.uu.net
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Date: 29 Jun 90 21:33:13 GMT
Apparently-To: std-unix-archive@uunet.uu.net
From: Doug Gwyn <gwyn@smoke.brl.mil>
>There was a discussion about whether it is possible (and preferable)
>to improve the low-level directory interfaces instead of adding new,
>high-level interfaces. Do the high-level interfaces really add new
>functionality for portable applications? Do they belong with the
>low-level operating system interfaces specified in 1003.1?
No, definitely not. However, they would be appropriate at the 1003.2
level. Note that 1003.2 implementations are not constrained to use
only 1003.1 facilities, so the fact that it's hard to implement tree
walkers right using the existing 1003.1 directory access functions is
no argument against defining tree walkers as part of a higher level.
>The ISO POSIX group (JTC1/SC22/WG15) pointed out that both of these
>[tar, cpio] formats are incompatible with accepted international and U.S.
>standards. After some arm twisting, the 1003.1 working group agreed
>to devise a new data interchange format based on IS 1001: 1986, which
>is more or less equivalent to ANS X3.27-1987, the familiar ANSI
>labeled tape format.
The ANSI magtape format is simply inappropriate. UNIX archives were
designed to be single files, making it simple to transport them by
means other than magnetic tape. In this modern networked world, for
the most part magnetic tape is an anachronism. Any archive format
standard for UNIX should not depend on the archive supporting
multiple files, tape marks, or any other non-UNIX concept.
It is to the credit of UNIX's original designers that they did NOT
blindly adopt existing standards when they were technically inferior.
Let's not make the POSIX standards impose conventional-think upon
UNIX environments..
Volume-Number: Volume 20, Number 69