From owner-freebsd-current@FreeBSD.ORG Fri Sep 12 22:16:32 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B63BECE; Fri, 12 Sep 2014 22:16:32 +0000 (UTC) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2975164; Fri, 12 Sep 2014 22:16:31 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.9/8.14.9/NETPLEX) with ESMTP id s8CM5WA6021315; Fri, 12 Sep 2014 18:05:32 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Fri, 12 Sep 2014 18:05:33 -0400 (EDT) Date: Fri, 12 Sep 2014 18:05:32 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net Reply-To: Daniel Eischen To: "Rang, Anton" Subject: RE: shells/bash port, add a knob which symlinks to /bin/bash ? In-Reply-To: Message-ID: References: <20140912214004.GT6096@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Craig Rodrigues , Baptiste Daroussin , freebsd-current Current , Emanuel Haupt , ports X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 22:16:32 -0000 On Fri, 12 Sep 2014, Rang, Anton wrote: >> If you want interoperability just use /usr/bin/env bash as a shebang. > > That doesn't work for this use case -- the user shell coming from LDAP > -- but I agree that the port shouldn't be modifying /usr/bin. > > It's easy enough to add the symlink manually after installing the port > if you're in this situation, or there may be a way to configure the > LDAP module to map /bin/bash to /usr/local/bin/bash (I haven't looked > to see what is supported here). We have used LDAP on Solaris for years, and have mixed environments of Solaris, Linux, and FreeBSD. We use /usr/local/bin/bash in LDAP for shells, then either link that to the system /bin/bash or install more up-to-date bash in /usr/local/bin. This way you can always install a more up-to-date shell in /usr/local/bin without changing the base OS - you don't want base OS shell scripts to break by updating to a newer shell. -- DE