From owner-freebsd-arch@FreeBSD.ORG  Sat Oct  6 12:23:23 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 E0C661065672;
	Sat,  6 Oct 2012 12:23:23 +0000 (UTC)
	(envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.freebsd.org (Postfix) with ESMTP id 6D56E8FC08;
	Sat,  6 Oct 2012 12:23:23 +0000 (UTC)
Received: from critter.freebsd.dk (critter-phk.freebsd.dk [192.168.48.2])
	by phk.freebsd.dk (Postfix) with ESMTP id 7236B3B754;
	Sat,  6 Oct 2012 12:23:21 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id q96CNQwe003021;
	Sat, 6 Oct 2012 12:23:26 GMT (envelope-from phk@phk.freebsd.dk)
To: Stefan Farfeleder <stefanf@FreeBSD.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sat, 06 Oct 2012 11:11:55 +0200."
	<20121006091154.GB1434@mole.fafoe.narf.at>
Content-Type: text/plain; charset=ISO-8859-1
Date: Sat, 06 Oct 2012 12:23:26 +0000
Message-ID: <3020.1349526206@critter.freebsd.dk>
Cc: arch@FreeBSD.org
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 <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Oct 2012 12:23:24 -0000

In message <20121006091154.GB1434@mole.fafoe.narf.at>, Stefan Farfeleder writes
:
>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.

Or improve unvis ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.