Util-Linux package development
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: fstab format
Date: Tue, 14 Jun 2016 13:22:24 -0500	[thread overview]
Message-ID: <57604B60.3060206@gmail.com> (raw)
In-Reply-To: <20160614083051.2rm5bdksffs6hiei@ws.net.home>

Karel Zak wrote:
> On Mon, Jun 13, 2016 at 06:18:36PM -0500, Bruce Dubbs wrote:
>> Does the fstab file support line continuation with a backslash-newline?
>
> No.
>
>> There is no indication in the fstab man page one way or another.  In the
>> case of some entries that use long device IDs like PARTUUID or several
>> options, it would be nice to be able to control the format for easier
>> reading.
>
> Yes, but fstab is de-facto standard file parsed on many many places.
> We cannot change/extend the file format.

I understand.  Thanks.  There are certain other projects that wouldn't 
care about de-facto standards, but I appreciate your position.

   -- Bruce

      reply	other threads:[~2016-06-14 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 23:18 fstab format Bruce Dubbs
2016-06-14  8:30 ` Karel Zak
2016-06-14 18:22   ` Bruce Dubbs [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=57604B60.3060206@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=kzak@redhat.com \
    --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