Date: Tue, 08 Nov 2005 10:46:59 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: freebsd-bluetooth@freebsd.org, Brooks Davis <brooks@one-eyed-alien.net>, freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem Message-ID: <4370F2A3.8060808@savvis.net> In-Reply-To: <20051108183203.GA40364@comp.chem.msu.su> References: <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051105113503.GA13863@comp.chem.msu.su> <436F9C8B.1000300@savvis.net> <20051108183203.GA40364@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
Yar, >>if expr "$_line" : "[a-zA-Z0-9_]*=" > /dev/null 2>&1 ; then >>... >>fi >> >>i do not really have any objection to this. since i already pass the >>value through eval i might as well pass the entire line. > > And so the users will be able to use basic sh(1) tricks in the lines. depending on one's position it may or may not be a good thing :) >>>And AFAIK stdin to a while loop can be redirected w/o enclosing >>>the loop in braces. >> >>sure, but it looked more clear (to me anyway) this way :) > > Hmmm, I'm unsure if it worked at all ;-) In sh(1) you need to > place a ';' before '}' if there is no '\n' after the last command > in braces. That is, the sh(1) syntax dictates that you can write it works. i tried these patches on my system. also there is a similar code in /etc/rc.subr (please see devfs_rulesets_from_file() function). but if it make sh(1) purists uncomfortable i certainly can change it :) thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4370F2A3.8060808>