getfsent(3) and spaces in fstab

From: Simon Barner (barner_at_in.tum.de)
Date: 07/31/03

  • Next message: Murray Taylor: "Re: getfsent(3) and spaces in fstab"
    Date: Thu, 31 Jul 2003 00:45:05 +0200
    To: freebsd-hackers@freebsd.org
    
    
    

    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

    http://freebsd.rambler.ru/bsdmail/freebsd-questions_2003/msg05947.html

    this problem seems to be either unknown or rather well-known but
    accepted.

    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.

    Cheers,
     Simon

    
    



  • Next message: Murray Taylor: "Re: getfsent(3) and spaces in fstab"

    Relevant Pages

    • Re: getfsent(3) and spaces in fstab
      ... if the name of the file system or the mount point ... > I searched the mail archives and the PR data base, ... > Do file system names and mount points with whitespaces violate the ...
      (freebsd-hackers)
    • Re: mount() function problem !
      ... mount() attaches the filesystem specified by source (which is often a device name, ... point within a file system. ... details of the options available for each filesystem type. ... Specifies the journalling mode for file data. ...
      (comp.lang.c)
    • Re: bin, sbin, etc as seperate LVM volumes
      ... RD>>that's where mount lives, and you almost certainly need to mount ... driver modules needed to get to the root file system. ... to start with -- these all must be all on the same file system. ...
      (comp.os.linux.misc)
    • RE: Machine not Booting - Continued
      ... If you see /etc/rc.sysinit you can see some sections for managing raid partitions. ... Otherwise specify the same mkraid and mount command in /etc/rc.local. ... it has no proper file system to mount. ... For address and company registration details of certain entities ...
      (RedHat)
    • Re: Salvaging data from USB flash disk
      ... mount: wrong fs type, bad option, bad superblock on /dev/loop0, ... Disk /dev/sda doesn't contain a valid partition table ... Your flash disk most likely has a vfat file system. ... only the partition containing the file system with data. ...
      (comp.os.linux.hardware)