Date: Wed, 9 Nov 2005 09:38:47 +0300 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, Panagiotis Astithas <past@ebs.gr> Subject: Re: [RFC] rc.d integration for the bluetooth subsystem Message-ID: <20051109063847.GB4605@comp.chem.msu.su> In-Reply-To: <43713B7D.7090405@savvis.net> References: <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> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> <20051108201620.GD27091@odin.ac.hmc.edu> <43713B7D.7090405@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 08, 2005 at 03:57:49PM -0800, Maksim Yevmenkin wrote:
>
> i also removed offending { } in while loop stdin redirection. if this is
Thanks! The handling of {} seems to be one of gray corners in sh(1)
syntax if it works as in the initial version of your script. Another
one I've noticed is the case operator. Your line was like this:
case $line in
and it still worked for $line containing IFS chars. sh(1) seems
to put double quotes aroung the word passed to case implicitly.
While such things may seem to make sh(1) coding a tad easier, I'm
afraid they shouldn't be relied upon.
--
Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051109063847.GB4605>