Date: Fri, 12 Sep 2014 16:38:25 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Craig Rodrigues <rodrigc@freebsd.org>, ports <freebsd-ports@freebsd.org>, Emanuel Haupt <ehaupt@freebsd.org> Cc: freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: shells/bash port, add a knob which symlinks to /bin/bash ? Message-ID: <541367D1.8090002@FreeBSD.org> In-Reply-To: <CAG=rPVf5z4c6aheCngKy1g-iH8HexAWGQfHoSbtU9D1UC0Pbpg@mail.gmail.com> References: <CAG=rPVf5z4c6aheCngKy1g-iH8HexAWGQfHoSbtU9D1UC0Pbpg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --F7FUAdP0V4vcjdqnOdPIBbe1OrETM8Sfo Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable "No" (as portmgr). Ports should not be touching the base system like this. Let's NOT go backwards and add a /bin/bash. In fact the /usr/bin/perl one will be removed soon as well. If we can actually eliminate ports touching /usr and / (not including /usr/local and /var) then we gain a very large memory optimization for package building by being able to ro null-mount these to the build jails.= There's no reason for bash (and perl) to be exceptions to the 24000 other ports that install to /usr/local/bin. I can think of dozens of other ports that will fall into the same arguments being made here, but it does not mean it is the right thing for FreeBSD. If you want to install the symlink on your system feel free to do it. I install a static bash to /bin/bash on mine and only because I prefer bash shell and want it in / for single-user mode. That's my personal choice though. The proper fix is to fix scripts to be portable and use #! /usr/bin/env bash rather than /bin/bash. We install all packages to PREFIX=3D/usr/local by default. Why should a bin symlink be an exception? There's no suggestion for symlinking includes or libraries which also hit users often. On 9/12/2014 4:12 PM, Craig Rodrigues wrote: > Hi, >=20 > 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. >=20 > 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 >=20 > or >=20 > ln /usr/local/bin/bash /bin/bash >=20 > and then make sure that /etc/shells as: > /usr/local/bin/bash > /bin/bash >=20 > Can we add an optional knob (turned off by default) which creates this > symlink > and updates /etc/shells? >=20 > This would help with interoperability of FreeBSD hosts in environments = mixed > with Linux and MacOS X. >=20 > -- > Craig > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org= " >=20 --=20 Regards, Bryan Drewery --F7FUAdP0V4vcjdqnOdPIBbe1OrETM8Sfo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJUE2fRAAoJEDXXcbtuRpfPxocH/2jJqFz0Ba3dJprTIAs7+qRR uUuD51jqElpSSL62kQZkrqPEIsReq2Y2cM7mAng3uArtbtP8s9GOYMT2fxVqxJOR 76OUz2F2EmXpIruOcu2/hSHS2FBQZGhb23CprLB6oncziByxiTJYvKIzthBlve7M xJ+oWZxHwOsIDFS+UhkVr2wutMf2oDfaRBbFNLIFpu5OmsCwXzH3YTgwuttFE5J6 OUcDYozWQcDY2a6hUMut+BQqPinKSvCtRrDoQ/HMY14aY2a0SeDz3DEHIufvuX/+ aqRr8KvB8JoVXQrqZwR+vmII2K5iEo+qL96XSwN5Js61vZCLvpBAYAjT6MipKvk= =1u+b -----END PGP SIGNATURE----- --F7FUAdP0V4vcjdqnOdPIBbe1OrETM8Sfo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?541367D1.8090002>