From owner-freebsd-arch@FreeBSD.ORG Sat Oct 6 09:12:04 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 0280C1065670 for ; Sat, 6 Oct 2012 09:12:04 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from fep13.mx.upcmail.net (fep13.mx.upcmail.net [62.179.121.33]) by mx1.freebsd.org (Postfix) with ESMTP id 440E68FC08 for ; Sat, 6 Oct 2012 09:12:03 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep13-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20121006091155.HPKZ3518.viefep13-int.chello.at@edge01.upcmail.net>; Sat, 6 Oct 2012 11:11:55 +0200 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge01.upcmail.net with edge id 7lBv1k00b2xdvHc01lBvUg; Sat, 06 Oct 2012 11:11:55 +0200 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id 361E16D430; Sat, 6 Oct 2012 11:11:55 +0200 (CEST) Date: Sat, 6 Oct 2012 11:11:55 +0200 From: Stefan Farfeleder To: Poul-Henning Kamp Message-ID: <20121006091154.GB1434@mole.fafoe.narf.at> References: <20121006084936.GA1434@mole.fafoe.narf.at> <2132.1349513878@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2132.1349513878@critter.freebsd.dk> User-Agent: Mutt/1.5.21 (2010-09-15) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Oct 2012 09:12:04 -0000 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. Stefan