Bug#616036: /bin/mount: /bin/mount: Fstab options causing failed mounts

[Cameron Berkenpas <cam@neo-zeon.de>]

Is coming up with a new patch for freebsd's mount command each time it's 
updated less than ideal? mount probably isn't updated very often, however.

 Would the better approach be to to insure that the installer generates an 
fstab with rw in the options for each mount?

On Wednesday, March 02, 2011 02:38:10 AM Mats Erik Andersson wrote:
> This is due to the following code in upstream source
> 
>     /* src/sbin/mount/mount.c */
> 
>     #define	BADTYPE(type)  \
>         (strcmp(type, FSTAB_RO) && \
>              strcmp(type, FSTAB_RW) && strcmp(type, FSTAB_RQ))
> 
>     /* A later test */
> 
>     if (BADTYPE(fs->fs_type))
>         errx(1, "%s has unknown file system type", *argv);
> 
> In consequence, exactly one of "rw", "ro", or "rq" __must__
> be present as file option, as soon as 'mount' is used with its
> fstab-based invokation form. Here "rq" is read-write with quota.
> 
> It is not the wrapper which is casing the problem here, it is the
> original executable pushed to /libexec/freebsd/mount that carries
> an implicit assumption, different from the custom for GNU/Linux.