On Fri, Sep 12, 2014 at 02:12:45PM -0700, Craig Rodrigues wrote: > Hi, > > 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 > > or > > ln /usr/local/bin/bash /bin/bash > > and then make sure that /etc/shells as: > /usr/local/bin/bash > /bin/bash > > Can we add an optional knob (turned off by default) which creates this > symlink > and updates /etc/shells? > > This would help with interoperability of FreeBSD hosts in environments mixed > 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 you cannot get interoprability with OS-X in there because the bash they do provide is the last GPL-2 recent bash have many incompatiblities with this old version. regards, Bapt
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:52 UTC