From owner-freebsd-doc@FreeBSD.ORG Wed Oct 26 20:46:43 2005 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD6B616A41F for ; Wed, 26 Oct 2005 20:46:43 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id C59FD43D45 for ; Wed, 26 Oct 2005 20:46:41 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j9QKkeZ6027929; Wed, 26 Oct 2005 23:46:40 +0300 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j9QKkYIg042823; Wed, 26 Oct 2005 23:46:34 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j9QKkYJl042822; Wed, 26 Oct 2005 23:46:34 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 26 Oct 2005 23:46:34 +0300 From: Giorgos Keramidas To: "Eli K. Breen" Message-ID: <20051026204634.GA42792@flame.pc> References: <200510262020.j9QKKv4Q073769@freefall.freebsd.org> <435FE939.6070203@unixforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <435FE939.6070203@unixforge.net> Cc: freebsd-doc@freebsd.org Subject: Re: docs/87351: Jail building instructions don't work as described with default CSH shell X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2005 20:46:43 -0000 On 2005-10-26 13:38, "Eli K. Breen" wrote: > Call me madcap, but wouldn't it make more sense to have the base case > example match the default shell, with exceptions for other shells as the > side-comments? > Given how little of this script/instructions need to change to suit csh, > something like... > > [...] > #For csh > set D=/here/is/the/jail > #For bourne shells (sh,bash,...) > D=/here/is/the/jail > cd /usr/src > mkdir -p $D > [...] > > or > > [...] > #For csh > set D=/here/is/the/jail > #For bourne shells (sh,bash,...) > # D=/here/is/the/jail > cd /usr/src > mkdir -p $D > [...] Nope. csh(1) is terrible for scripting and only mildly annoying for interactive use. I'd accept something that lists *two* sets of commands that can be copied to a file and minimally changed to alter the $D path, but intermixing scripts that run in sh(1), csh(1), zsh(1) or anything else is not very nice imho :/