Bug 37569 - [patch] Extend fstab(5) format to allow for spaces in filenames
Summary: [patch] Extend fstab(5) format to allow for spaces in filenames
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Stefan Farfeleder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-29 16:40 UTC by Peter Edwards
Modified: 2015-01-07 05:06 UTC (History)
1 user (show)

See Also:


Attachments
fstab-quotes.tar.Z (2.20 KB, text/plain)
2002-04-29 16:40 UTC, Peter Edwards
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Edwards 2002-04-29 16:40:01 UTC
I use "smbfs", and, on machines beyond my control, some of the shares
have spaces in their names. Unfortunately, fstab(5) can't do spaces in
the device name. This adds the ability.

The only incompatibility should be with people already using the "
character in their device / mount point names, which I assume will be
less than the number who find this useful.

How-To-Repeat: Try to put a space in an entry in /etc/fstab, then use mount
Comment 1 Matteo Riondato 2005-03-29 21:59:13 UTC
I modified the patch and applied it.
It worked.
It adds support for spaces in the first 2 fields of /etc/fstab .
The new patches can be found at
http://www.riondabsd.net/fstab-quotes.tar.gz
I think they should be committed (after having been reviewed) because
they add a feature which can be really useful.
Anyway, this is absolutely not a conf PR, but I don't know which
category fits it best.

-- 
Rionda aka Matteo Riondato
Disinformato per default
G.U.F.I. Staff Member (http://www.gufi.org)
FreeSBIE Developer (http://www.freesbie.org)
Comment 2 Matteo Riondato freebsd_committer freebsd_triage 2006-03-04 10:55:20 UTC
Responsible Changed
From-To: freebsd-bugs->matteo

I'll handle this
Comment 3 Gavin Atkinson freebsd_committer freebsd_triage 2008-06-21 20:17:14 UTC
See also PRs 55539 and 117687 for other solutions to this problem.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2010-06-19 05:39:12 UTC
Responsible Changed
From-To: matteo->freebsd-bugs

Reset PR assigned to inactive committer. 

Hat:	gnats-admin
Comment 5 Stefan Farfeleder freebsd_committer freebsd_triage 2012-10-11 12:49:23 UTC
State Changed
From-To: open->patched

Grab and mark patched. 


Comment 6 Stefan Farfeleder freebsd_committer freebsd_triage 2012-10-11 12:49:23 UTC
Responsible Changed
From-To: freebsd-bugs->stefanf

Grab and mark patched.
Comment 7 Eitan Adler freebsd_committer freebsd_triage 2013-03-15 23:41:38 UTC
State Changed
From-To: patched->closed

MFCed/fixed by now or it will never be MFCed
Comment 8 jwdevel 2015-01-07 05:06:59 UTC
This bug says it is FIXED, but I certainly do not see this patch applied on my 9.1-RELEASE box.

The duplicate issues, bug 117687 and bug 55539, are still in the Open state.

What's the deal, here?