From owner-freebsd-current  Tue Sep 24 23:03:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA29078
          for current-outgoing; Tue, 24 Sep 1996 23:03:12 -0700 (PDT)
Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA29042
          for <current@freebsd.org>; Tue, 24 Sep 1996 23:03:06 -0700 (PDT)
Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM)
	id AA06925; Tue, 24 Sep 1996 23:02:42 -0700
Date: Tue, 24 Sep 1996 23:02:42 -0700 (PDT)
From: "Brian N. Handy" <handy@sag.space.lockheed.com>
To: Nate Williams <nate@mt.sri.com>
Cc: Chuck Robey <chuckr@glue.umd.edu>, Richard Wackerbarth <rkw@dataplex.net>,
        Warner Losh <imp@village.org>, current@freebsd.org
Subject: Re: install on {Net,Open}BSD vs install on FreeBSD
In-Reply-To: <199609250410.WAA10368@rocky.mt.sri.com>
Message-Id: <Pine.OSF.3.94.960924230203.5271C-100000@sag.space.lockheed.com>
X-Files: The truth is out there
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 24 Sep 1996, Nate Williams wrote:

>> of the case is based on compatibility.  I've disagreed with Richard in the
>> past when he was using the compatibility to move us towards SYSV without a
>> strong reason, but since we ARE bsd, and the -d option IS bsd, the
>
>The -d option *ISN'T* BSD.  It was added by J.T. in NetBSD, and when
>OpenBSD took the entire NetBSD source tree over it was there as well.
>I'll bet BSDi doesn't have it, and neither does Ultrix, which are also
>BSD based systems.

FYI, -d doesn't exist in Ultrix.  

Brian