Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: How do you tell how much disk free is remaining
Message-ID: <12820@dog.ee.lbl.gov>
Date: 4 May 91 23:32:21 GMT
References: <9105041944.AA09678@shaman.com>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 31
X-Local-Date: Sat, 4 May 91 16:32:21 PDT

In article <9105041944.AA09678@shaman.com> jiro@shaman.com
(Jiro Nakamura) writes:
>	This is for a NeXT (BSD4.3) system, BTW.

NeXTs do not run 4.3BSD.

Suns do not run 4.3BSD (not even mine---when it runs my stuff, which
it does not, quite, this is *not* 4.3BSD but rather something between
4.3reno and 4.4).  Suns generally run SunOS (some run Sprite).

Nothing that is not a VAX is capable of running 4.3BSD.

The Tahoe series can run 4.3BSD-tahoe and 4.3BSD-reno.

Some HP 680x0 boxes can run 4.3BSD-reno and/or HP-BSD (which is not
4.3BSD, again).

4.3BSD-tahoe and 4.3BSD-reno are not 4.3BSD (they are close, but not
identical).

Incidentally, the same problem applies to System V, only more so, as
the name appearing on the documentation may claim `System V Release N'
yet the system may be (and often is) significantly different from the
same name `System V Release N' on some other architecture.  At least
4.3BSD-tahoe and 4.3BSD-reno are built from a single source tree, so
that any time programs differ in behaviour on different architectures,
save for deliberate architecture dependencies such as device drivers,
it is a bug, rather than a feature.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov