From: Hans-Peter Jansen Subject: Re: Adding subroot information to /proc/mounts, or obtaining that through other means Date: Thu, 21 Jun 2007 21:14:24 +0200 Message-ID: <200706212114.25705.hpj@urpla.net> References: <467994BD.6000403@zytor.com> <20070620224135.GC6258@gallifrey> <4679AE5E.4050001@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "H. Peter Anvin" , "Dr. David Alan Gilbert" , Karel Zak , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: In-Reply-To: <4679AE5E.4050001-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> Content-Disposition: inline Sender: util-linux-ng-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org Am Donnerstag, 21. Juni 2007 00:46 schrieb H. Peter Anvin: > Dr. David Alan Gilbert wrote: > > What happens with the (sick) case of spaces in directory names? > > Also is it really nicely defined that there is no way to put a spac= e > > in an option in any of the filesystems? I suppose someone > > particularly sick could have a device node in a directory with a sp= ace > > in it. It would be nice if new formats for this are being defined > > to make it cover everything. > > That's already handled just fine: > > bash-3.1$ mkdir /tmp/'Jag =E4r: \ > en liten mask' > bash-3.1$ sudo mount -t tmpfs none '/tmp/Jag =E4r: \ > en liten mask'/ > bash-3.1$ tail -1 /proc/mounts > none /tmp/Jag\040=E4r:\040\134\012en\040liten\040mask tmpfs rw 0 0 > bash-3.1$ Hmm, and what about the even sicker case: /tmp/\040, parse as /tmp/\\04= 0? Do userspace cope with this? Happy parsingly y'rs, Pete