From owner-freebsd-current  Mon Jan 29  8:31:51 2001
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 6F0BB37B402
	for <current@FreeBSD.ORG>; Mon, 29 Jan 2001 08:31:34 -0800 (PST)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA34977;
	Mon, 29 Jan 2001 11:31:32 -0500 (EST)
	(envelope-from wollman)
Date: Mon, 29 Jan 2001 11:31:32 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200101291631.LAA34977@khavrinen.lcs.mit.edu>
To: "Jacques A. Vidrine" <n@nectar.com>
Cc: "Steve O'Hara-Smith" <steveo@eircom.net>, current@FreeBSD.ORG
Subject: Re: /etc/shells #include syntax support patch
In-Reply-To: <20010128190227.B25222@spawn.nectar.com>
References: <20010128101349.2c94539f.steveo@eircom.net>
	<20010128190227.B25222@spawn.nectar.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Sun, 28 Jan 2001 19:02:27 -0600, "Jacques A. Vidrine" <n@nectar.com> said:

> I would rather that a separate configuration file be read, for example,
> with a list of shells(5) format files to consult.

I would rather have a single file, located in a directory intended for
configuration files.  Perhaps we could call it ``/etc/shells'' which
seems to be popular.

There is no inherent virtue in having (some subset of) configuration
files on every partition.

-GAWollman




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message