getfsent(3) and spaces in fstab
peter.edwards at openet-telecom.com
Tue Aug 5 02:48:01 PDT 2003
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?
On Wed, 2003-07-30 at 23:45, Simon Barner wrote:
> Hi -hackers,
> discussing some modifications for the sysutils/linneighborhood port,
> Heiner Eichmann and me came across the following problem:
> getfsent(3) will fail, if the name of the file system or the mount point
> contains whitespaces, be them escaped or not (file system names with
> spaces occur quite of with smbfs mounts).
> I searched the mail archives and the PR data base, but apart from this
> email here
> this problem seems to be either unknown or rather well-known but
> I know there is workaround which is to create symbolic links for the
> paths that contain spaces, but to my mind this is not a real solution.
> Before taking any further action:
> Do file system names and mount points with whitespaces violate the
> specification of fstab? If so, the least thing I'd suggest is the document
> this restriction.
> Or should one extend 'getfsent' such that is able to cope with those
> whitespaces? I am not sure whether this would have any further
> implications so I am asking here.
More information about the freebsd-hackers