public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: util-linux@vger.kernel.org
Subject: Supporting human parsable journal_dev specifiers
Date: Thu, 10 Jul 2014 10:28:24 -0400	[thread overview]
Message-ID: <20140710142824.GA20753@thunk.org> (raw)

I have a user request that mount be able to interpret the device
specifier for the journal_dev mount option, so that instead of having
to type something like

   mount -o journal_dev=0x0803 ....

they could unstead use: "journal_dev=/dev/sda3" or even
"journal_dev=LABEL=ext_journal".  I assume the right way to do this is
a mount helper?  Or is this something that you would be willing to
accept as a patch into util-linux?

If it is a mount helper, what's the best way to do things?  Simply
parse through the mount options until finding the journal_dev one, and
then calling blkid or stat as necessary to interpret the argument, and
then re-exec mount with the modified mount option?  Or is there some
gotchas involved with doing this?

Thanks,

						- Ted

             reply	other threads:[~2014-07-10 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 14:28 Theodore Ts'o [this message]
2014-07-10 14:31 ` Supporting human parsable journal_dev specifiers Christoph Hellwig
2014-07-15 11:52 ` 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=20140710142824.GA20753@thunk.org \
    --to=tytso@mit.edu \
    --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