Date: Thu, 8 May 2003 02:25:12 +0400 (MSD) From: "."@babolo.ru To: Doug Barton <DougB@FreeBSD.org> Cc: hackers@freebsd.org Subject: Re: Bridge config in /etc/rc (patch) Message-ID: <1052346312.414067.669.nullmailer@cicuta.babolo.ru> In-Reply-To: <20030506222607.A5620@znfgre.qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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} ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1052346312.414067.669.nullmailer>