From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 17 09:22:15 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 637F81065670 for ; Tue, 17 Jul 2012 09:22:15 +0000 (UTC) (envelope-from nec556@retena.com) Received: from resmaa13.ono.com (smtp13.ono.com [62.42.230.16]) by mx1.freebsd.org (Postfix) with ESMTP id E737F8FC0A for ; Tue, 17 Jul 2012 09:22:14 +0000 (UTC) Received: from GogPortatil.retena.com (85.219.45.167) by resmaa13.ono.com (8.5.113) (authenticated as nec556@retena.com) id 4FA882720124B385 for freebsd-hackers@freebsd.org; Tue, 17 Jul 2012 11:22:08 +0200 Message-ID: <4FA882720124B385@> (added by postmaster@resmaa13.ono.com) X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 17 Jul 2012 11:25:02 +0200 To: freebsd-hackers@freebsd.org From: Eduardo Morras In-Reply-To: <20120705131518.06898223@bhuda.mired.org> References: <4FF4BEED.10103@FreeBSD.org> <62039A45-92E4-4588-988D-6DF39D7B01E5@bsdimp.com> <201207050922.25815.j.mckeown@ru.ac.za> <20120705082857.GB37083@server.rulingia.com> <4FF55864.8040807@FreeBSD.org> <4FF5BE93.4010509@my.gd> <20120705170944.GA43725@DataIX.net> <20120705131518.06898223@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Antivirus: AVG for E-mail 2012.0.2197 [2437/5135] Subject: Re: Pull in upstream before 9.1 code freeze? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 09:22:15 -0000 At 19:15 05/07/2012, Mike Meyer wrote: >On Thu, 5 Jul 2012 13:09:44 -0400 >Jason Hellenthal 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=20 system control, not userland control. The rc.conf=20 is not for that neither, it has system wide=20 configuration, not app specific config. The best solution (for me) is leave sh untouched=20 without this functionality. Fork it and make a=20 sh++ port with this (and more) functionality ,=20 install it and use it. Is it really too much work=20 to change your default (non-root) shell? I use zsh f.ex. Take care, if you start the system in rescue mode=20 or singleuser mode, will the new "hook" feature=20 search the unmounted partitions for ports info?=20 will it connect to internet for that? will fail miserably? >