All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: util-linux@vger.kernel.org
Subject: Re: Supporting human parsable journal_dev specifiers
Date: Tue, 15 Jul 2014 13:52:25 +0200	[thread overview]
Message-ID: <20140715115225.GY30288@x2.net.home> (raw)
In-Reply-To: <20140710142824.GA20753@thunk.org>

On Thu, Jul 10, 2014 at 10:28:24AM -0400, Theodore Ts'o wrote:
> 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?

 I talked about it with Eric Sandeen year ago, and the decision was to
 implement some generic FS independent solution based on variables in
 mount options, something like

     mount -o journal_dev=$(LABEL:<ext_journal_label>)

 (or $LOGUUID for XFS log, etc).

 It's not implemented yet, but I can try it if it's still necessary.
 
> If it is a mount helper, what's the best way to do things?  Simply

 Please, do not use mount helpers (/sbin/mount.<type>), it sucks in
 many ways... it will be better to have a generic solution within
 mount(8).

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      parent reply	other threads:[~2014-07-15 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 14:28 Supporting human parsable journal_dev specifiers Theodore Ts'o
2014-07-10 14:31 ` Christoph Hellwig
2014-07-15 11:52 ` Karel Zak [this message]

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=20140715115225.GY30288@x2.net.home \
    --to=kzak@redhat.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.