public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Karel Zak <kzak@redhat.com>
Cc: Matthias Schniedermeyer <ms@citd.de>, util-linux@vger.kernel.org
Subject: Re: Filesystem specific mount options mixed with auto fs type
Date: Fri, 11 Oct 2013 09:45:15 -0400	[thread overview]
Message-ID: <525800EB.9060208@ubuntu.com> (raw)
In-Reply-To: <20131011083742.GA14457@x2.net.home>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/11/2013 4:37 AM, Karel Zak wrote:
> * well designed filesystems allows to save the filesystem specific
>  options to the FS superblock by some tune util (e.g. tune2fs)

Unfortunately, fat isn't well designed.

> * for removable media users usually use udisks based solutions

That works as long as udisks picks the defaults they want, but then if
they want a non default mount option ( or location ), they have to
specify it in fstab.

> * mount by FS identifier
> 
> LABEL=FOO       /mnt/floppy     vfat    utf8 LABEL=BAR
> /mnt/floppy     ext2    default

That ties it to the specific volume.

> Maybe we can improve mount(8) to test all entries from /etc/fstab 
> with the same mountpoint (if you want to mount-by-mountpoint) until
> the filesystem will be mounted successfully. But I have doubts that
> we really need to resolve this very old disadvantage.

Maybe something like:

/dev/fd0 /mnt/floppy auto,vfat utf8
/dev/fd0 /mnt/floppy auto generic-options

The auto would trigger blkid to identify the filesystem, and then only
if it matches one of the additional listed filesystems would that line
be applied.

I suppose that would also require changing other utilities like udisks
to understand it?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSWADrAAoJEJrBOlT6nu75bRYIAKF5CFzLr8hChG6+VoFvWSMY
1O5W8unfYSL4JH86OVuj14w9LaWWxbYaIwzhbAXp5X9Y96ZLXPNxcHaytyoBSmYg
xfDNpgj/Nm6Y8Zg2LM+qwFi+oO4qOb8RetD0uxz3uVBzxVC/PoV4W3AwoCsK3bQ9
xGjxDpMSi9lq3jA/pa8TtJnkUC8cL8vX8AWrGcSd/bBtxVZjM/mpxn4UhoBLSfOE
ICGijygUP+NUbZ7yvBb5LE2B0nqaXlpg8qqrGENhJuUGchhyd45MASzOP+I1030H
AgpMKgfg85qVneRiKl+/PmKKhrefqBkBbrWhXzjCpMNJH7H/BdupOIS+0DfQ/MI=
=QAmw
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-10-11 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 14:21 Filesystem specific mount options mixed with auto fs type Phillip Susi
2013-10-10 17:03 ` Matthias Schniedermeyer
2013-10-10 17:29   ` Phillip Susi
2013-10-11  8:37     ` Karel Zak
2013-10-11 13:45       ` Phillip Susi [this message]
2013-10-11 14:09         ` Karel Zak
2013-10-11 14:40           ` Phillip Susi
2013-10-11 17:17         ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=525800EB.9060208@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=kzak@redhat.com \
    --cc=ms@citd.de \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox