Pull in upstream before 9.1 code freeze?
Eduardo Morras
nec556 at retena.com
Tue Jul 17 09:22:15 UTC 2012
At 19:15 05/07/2012, Mike Meyer wrote:
>On Thu, 5 Jul 2012 13:09:44 -0400
>Jason Hellenthal <jhellenthal at dataix.net> wrote:
> > On Thu, Jul 05, 2012 at 06:19:31PM +0200, Damien Fleuriot wrote:
> > > As long as it can be toggled off system-wide, persistently (sysctl?), I
> > > can't see the harm in bringing that in.
> > Haha sysctl... thats going quite a bit too far into the system for this.
>
>Yup. A sysctl (or rc.conf variable) intended specifically to control
>the behavior of shells is an even worse idea than turning this nanny
>behavior on for everyone.
Add sysctl for apps is a no-no, sysctl is for
system control, not userland control. The rc.conf
is not for that neither, it has system wide
configuration, not app specific config.
The best solution (for me) is leave sh untouched
without this functionality. Fork it and make a
sh++ port with this (and more) functionality ,
install it and use it. Is it really too much work
to change your default (non-root) shell? I use zsh f.ex.
Take care, if you start the system in rescue mode
or singleuser mode, will the new "hook" feature
search the unmounted partitions for ports info?
will it connect to internet for that? will fail miserably?
> <mike
L
----------------------------------------------
Si la vida te da la espalda, ¡tocale el culo!
More information about the freebsd-hackers
mailing list