As a slight distraction from the topic, is this actually possible in
general? I'm thinking in particular of ports that install kernel
modules. Since LOCALBASE may be (and very often is) a different file
system from /, such modules cannot be accessible to loader and so can't
be loaded in early boot. This is potentially a problem for wireless
driver firmware modules, for example.
On 09/12/14 14:38, Bryan Drewery wrote:
"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
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=/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:
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 mixed
with Linux and MacOS X.
freebsd-po...@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"