Date: 05 Aug 2003 11:30:20 +0100 From: Peter Edwards <peter.edwards@openet-telecom.com> To: Simon Barner <barner@in.tum.de> Cc: freebsd-hackers@freebsd.org Subject: Re: getfsent(3) and spaces in fstab Message-ID: <1060079419.57234.35.camel@rocklobster.openet-telecom.lan> In-Reply-To: <20030805100558.GA15128@zi025.glhnet.mhn.de> References: <20030730224505.GD531@zi025.glhnet.mhn.de> <1060076564.57234.11.camel@rocklobster.openet-telecom.lan> <20030805100558.GA15128@zi025.glhnet.mhn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2003-08-05 at 11:05, Simon Barner wrote: > Hi, > > > Check PR 37569: This bugged the hell out of me also, so I created a > > patch to allow enclosing the device name in quotes. The PR was logged > > over a year ago: I can't remember the details, but the source has been > > sitting silently in my tree and working since then. Whatever way the > > problem is resolved, can someone close the PR? > > I can't believe it... I have searched the PR database, Google, etc. for > existing solutions to this problem, but I did not find yours. I also > considered using quotes, but since you need escape-sequences to encode > quotes in your solution, too, the approach using '\ ', '\<TAB>', '\\' is > simpler and cleaner IMHO. > > Simon I find the "quotes" approach produces more readable (and manageable) fstabs, but I don't care about that sufficiently to argue further :-). Anything that addresses the problem and can close the PR will suit me!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1060079419.57234.35.camel>