I could live with this solution of additional port outside of the main
bash port, which creates the symlink and updates /etc/shells.
One other thing I am seeing is that many, many shell scripts are written
Forcing all upstream script writers to switch to "#!/usr/bin/env bash", or
to convert their scripts to "#!/bin/sh" and remove all bash-specific
behaviors, is getting harder and harder,
since many people are exposed to MacOS X and Linux on desktops.
On Fri, Sep 12, 2014 at 3:02 PM, Alfred Perlstein <bri...@mu.org> wrote:
> The correct thing is to make a port/pkg that installs the symlink and
> /etc/shells this for the user.
> There is no need for changes to 'base' nor do we need a change to the
> system port.
> On 9/12/14 2:40 PM, Baptiste Daroussin wrote:
>> On Fri, Sep 12, 2014 at 02:12:45PM -0700, Craig Rodrigues wrote:
>>> In the last 3 jobs that I have worked at, there have been
>>> a mix of Linux machines and FreeBSD machines.
>>> When using an NIS or LDAP environment where
>>> there is a single login across multiple machines, it is useful to
>>> have a single shell setting.
>>> Since Linux and MacOS X have "/bin/bash" as the shell,
>>> in order to get the FreeBSD boxes to play in this environment,
>>> I have seen admins do the following on FreeBSD setups:
>>> ln -s /usr/local/bin/bash /bin/bash
>>> ln /usr/local/bin/bash /bin/bash
>>> and then make sure that /etc/shells as:
>>> Can we add an optional knob (turned off by default) which creates this
>>> and updates /etc/shells?
>>> This would help with interoperability of FreeBSD hosts in environments
>>> with Linux and MacOS X.
>>> Please no, no and no!
>> We are fighting for a very long time to prevent the ports to pollute base.
>> We have added the shebangfix USES to be able to catch with up with
>> cleanup this
>> properly as well as a qa test to discover it automatically.
>> no interpreters at all have a symlink in base but perl and this one is
>> going to
>> be removed.
>> If you want interoperability just use /usr/bin/env bash as a shebang. Btw
>> cannot get interoprability with OS-X in there because the bash they do
>> is the last GPL-2 recent bash have many incompatiblities with this old
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"