Date: Sat, 06 Oct 2012 15:39:47 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Stefan Farfeleder <stefanf@FreeBSD.org> Cc: arch@FreeBSD.org, Poul-Henning Kamp <phk@phk.freebsd.dk> Subject: Re: Allowing \xxx in fstab Message-ID: <50708903.6060209@FreeBSD.org> In-Reply-To: <20121006091154.GB1434@mole.fafoe.narf.at> References: <20121006084936.GA1434@mole.fafoe.narf.at> <2132.1349513878@critter.freebsd.dk> <20121006091154.GB1434@mole.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50708903.6060209>