From owner-freebsd-arch@FreeBSD.ORG Sat Oct 6 19:39:48 2012 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 708F010656D1; Sat, 6 Oct 2012 19:39:48 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 449A98FC20; Sat, 6 Oct 2012 19:39:48 +0000 (UTC) Received: from John-Baldwins-MacBook-Air.local (c-68-39-198-164.hsd1.de.comcast.net [68.39.198.164]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 910B3B91E; Sat, 6 Oct 2012 15:39:47 -0400 (EDT) Message-ID: <50708903.6060209@FreeBSD.org> Date: Sat, 06 Oct 2012 15:39:47 -0400 From: John Baldwin User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Stefan Farfeleder References: <20121006084936.GA1434@mole.fafoe.narf.at> <2132.1349513878@critter.freebsd.dk> <20121006091154.GB1434@mole.fafoe.narf.at> In-Reply-To: <20121006091154.GB1434@mole.fafoe.narf.at> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Sat, 06 Oct 2012 15:39:47 -0400 (EDT) Cc: arch@FreeBSD.org, Poul-Henning Kamp Subject: Re: Allowing \xxx in fstab X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Oct 2012 19:39:48 -0000 On 10/6/12 5:11 AM, Stefan Farfeleder wrote: > On Sat, Oct 06, 2012 at 08:57:58AM +0000, Poul-Henning Kamp wrote: >> In message <20121006084936.GA1434@mole.fafoe.narf.at>, Stefan Farfeleder writes >> : >> >>> +static void >>> +unescapeoctal(char *s) >> >> >> Use unvis(3) ? > > The unvis functions unfortunately cannot be told be decode only octal > escapes. But if everyone agrees that strings like "\^C" or "\$" will > never occur in device names, I'm happy to use them. I think you are probably fine to just use strunvis(). It would also be nice to allow simple escaping of spaces (\ ). -- John Baldwin