[net.unix] ULTRIX

guy@sun.uucp (Guy Harris) (09/30/85)

> Is the Ultrix tar format identical with the BSD tar format?

One should hope so; if it weren't, Ultrix "tar" would be useless.  Since
Ultrix is a 4.2BSD derivative, the "tar"s are probably the same program
modulo some bug fixes.  However, most UNIXes out there are more-or-less V7
derivatives so *all* their "tar" programs are related and have the same
"tar" format.  (Were that not the case, "tar" would be a lousy way of
exchanging data between machines.)

	Guy Harris

gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>) (10/02/85)

Note that IEEE P1003 is defining "tar" as a portable
data exchange format for UNIX-like systems.
(Includes extensions to accommodate 4.2BSD etc.)

mikel@codas.UUCP (Mikel Manitius) (10/06/85)

> > Is the Ultrix tar format identical with the BSD tar format?
> 
> One should hope so; if it weren't, Ultrix "tar" would be useless.  Since
> Ultrix is a 4.2BSD derivative, the "tar"s are probably the same program
> modulo some bug fixes.  However, most UNIXes out there are more-or-less V7
> derivatives so *all* their "tar" programs are related and have the same
> "tar" format.  (Were that not the case, "tar" would be a lousy way of
> exchanging data between machines.)
> 
> 	Guy Harris

I have found that BSD tar is *not* identical to System V tar format,
this gives me a great problem, since I have many source tapes of BSD
that I would like to read on a System V!
-- 
                                        =======
     Mikel Manitius                   ==----=====    AT&T
     (305) 869-2462 RNX: 755         ==------=====   Information Systems 
     ...{akguc|ihnp4}!codas!mikel    ===----======   SDSS Regional Support
     ...attmail!mmanitius             ===========    Altamonte Springs, FL
     My opinions are my own.            =======

guy@sun.uucp (Guy Harris) (10/08/85)

> I have found that BSD tar is *not* identical to System V tar format,
> this gives me a great problem, since I have many source tapes of BSD
> that I would like to read on a System V!

The BSD "tar" format is a superset of the V7/S3/S5 "tar" format.  It puts
out "funny" entries for directories; other "tar"s don't put out any
information about directories.  Reading a BSD "tar" tape on a non-BSD system
causes some warning messages about the directory entries, but all the files
and containing directories are created as before.  (Of course, if it's a
4.2BSD "tar" tape with symbolic links, it won't work if your system doesn't
support symbolic links.)

If the "tar" tape was written with the default block size on a BSD system
(20*512 bytes), you may have trouble reading it on 3B20s with the loser tape
controller or other such machines which can't support large block sizes on
tape.  Otherwise, just mount up the tar tape and start reading.

	Guy Harris

steiny@scc.UUCP (Don Steiny) (06/17/86)

**

	Not only did DEC change a fundemental data structure
of UNIX in ULTRIX (while claiming to high-heaven that it is
UNIX compatible), they did not bother to document it.  The
manual "man 5 acct" describes the UNIX acct structure,
not the one that ULTRIX uses.

	The fact that the manual does not describe the software
leads me to believe that DEC has not even done the most rudimentry
QA on ULTRIX.    I have found more bugs in 8 hours of using
ULTRIX than I could find in a month of QA on HP's new HP-UX.


-- 
scc!steiny
Don Steiny @ Don Steiny Software 
109 Torrey Pine Terrace
Santa Cruz, Calif. 95060
(408) 425-0382