From: Roger Leigh <rleigh@codelibre.net>
To: util-linux@vger.kernel.org
Subject: Preservation of non-kernel mount options
Date: Tue, 8 Jan 2013 10:44:43 +0000 [thread overview]
Message-ID: <20130108104443.GF3739@codelibre.net> (raw)
Hi,
Apologies if this is already implemented in git and I didn't notice.
Options like _netdev, comment= etc. are currently just ignored by
mount AFAICS. It would however be quite useful if they could be
preserved in e.g. utab if possible so that you can use this to
label mounts so that you can query for the information later using
e.g. mount or findmnt. Is this something which might be possible
to add if it's not already possible?
It turned out (at least in Debian) that some users were using the
"bind" option to track which filesystems were to be e.g. backed up,
space usage checked etc. (or not). With the switch to /proc/mounts
this information has been lost. While using the bind option to do
this is debatable, I was looking for a better and more robust
solution to their problem, and being able to attach comments to
the mounts seemed like it would fit in with the existing tools
if they could be stored.
Thanks,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
next reply other threads:[~2013-01-08 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 10:44 Roger Leigh [this message]
2013-01-10 10:07 ` Preservation of non-kernel mount options Karel Zak
2013-01-21 13:16 ` Roger Leigh
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=20130108104443.GF3739@codelibre.net \
--to=rleigh@codelibre.net \
--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