From owner-freebsd-hackers@FreeBSD.ORG Wed May 7 15:21:58 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0E2137B401 for ; Wed, 7 May 2003 15:21:58 -0700 (PDT) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3BC143FA3 for ; Wed, 7 May 2003 15:21:56 -0700 (PDT) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 65691 invoked from network); 7 May 2003 22:40:55 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 7 May 2003 22:40:55 -0000 Received: (nullmailer pid 670 invoked by uid 136); Wed, 07 May 2003 22:25:12 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20030506222607.A5620@znfgre.qbhto.arg> To: Doug Barton Date: Thu, 8 May 2003 02:25:12 +0400 (MSD) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1052346312.414067.669.nullmailer@cicuta.babolo.ru> cc: hackers@freebsd.org Subject: Re: Bridge config in /etc/rc (patch) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2003 22:21:59 -0000 > On Wed, 7 May 2003 .@babolo.ru wrote: > > There no sed or grep in /bin or /sbin > > This was another reason for my suggestion to keep the code simple, even if > I forgot to say it. :) Anything involving networking has to be dead > simple, because of some of the circular dependencies that you mentioned. > > > Just as example - mount /usr from > > nfs server, which is possible after > > net setup, which is possible after > > sed use, but sed will be useable latter... > > > > It's time to invent new command as > > set bridge_* :-) > > Yeah, that's more or less the direction I started heading mentally when I > was trying to unravel a way to do the devfs stuff without completely > losing my mind. I ultimately went a different direction for that > particular problem, but the idea of a "variable finder" function in > /etc/rc.subr is percolating back there somewhere. It sounds simple, > until you take a look at how many variables are actually set by rc, > infinitely variable user environments, etc.... Interesting... IF new builtin command will be written, has it chance to be accepted? such as "list prefix" lists all sh variables with names prefix* ? Or better expand ${prefix@} to list of variables ? Or may be ${prefix*} or even ${*foo?bar} ?