From: Ian Kent <raven@themaw.net>
To: David Liontooth <liontooth@cogweb.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: /etc/exports continue line
Date: Wed, 02 May 2007 10:38:58 +0800 [thread overview]
Message-ID: <1178073538.3393.3.camel@raven.themaw.net> (raw)
In-Reply-To: <461EA1CC.2050102@cogweb.net>
On Thu, 2007-04-12 at 14:17 -0700, David Liontooth wrote:
> I've been using \ to continue a line in /etc/exports, and ran into an
> odd problem -- if you accidentally hit the TAB key after the continue
> line and save, the entry becomes invalid. Since the TAB key is
> invisible, it can be difficult to figure out what's going on.
>
> I reported it as Debian bug 418491 to nfs-kernel-server, and the
> maintainer responded by saying \ isn't a valid continue character.
Well, he's right.
As far as I remember the line continuation has always been "\<NL>",
otherwise you get a solitary <NL> which would end the entry.
> Comments? I routinely do this sort of thing:
>
> /spare \
> 165.97.21.130(rw,no_root_squash,no_subtree_check,async) \
> 165.97.21.132(rw,no_subtree_check,async) \
> 165.97.21.133(rw,no_subtree_check,async) \
> 165.97.21.134(rw,no_subtree_check,async) \
> 165.97.21.135(rw,no_root_squash,no_subtree_check,async) \
> 165.97.21.136(rw,no_subtree_check,async) \
> 165.97.85.112(rw,no_subtree_check,async) \
> 165.97.85.117(rw,no_subtree_check,async)
>
> A lot easier to maintain that a single line. Is there an alternative way
> to continue the line?
>
> Cheers,
> Dave
>
>
> -------- Original Message --------
> Subject: Re: Bug#418491: nfs-kernel-server: Lots of misleading error
> messages if there's a TAB in /etc/exports
> Date: Thu, 12 Apr 2007 16:06:27 +0200
> From: Steinar H. Gunderson <sgunderson@bigfoot.com>
> To: David Liontooth <liontooth@cogweb.net>, 418491-done@bugs.debian.org
> References:
> <20070410023140.32254.14380.reportbug@localhost.localdomain>
> <20070411002242.GD8811@uio.no>
>
>
>
> On Wed, Apr 11, 2007 at 02:22:42AM +0200, Steinar H. Gunderson wrote:
> >> Try this: edit /etc/exports and add a TAB after a \ (continue line). For instance, mine uses
> > \ isn't supported as continue line, TTBOMK.
>
> Thus, closing this one; forgot to do so last time.
>
> /* Steinar */
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-05-02 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 21:17 /etc/exports continue line David Liontooth
2007-04-12 21:37 ` Mike Frysinger
2007-04-12 21:38 ` Neil Brown
2007-04-12 22:10 ` David Liontooth
2007-04-13 0:49 ` Mike Frysinger
2007-05-02 2:38 ` Ian Kent [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=1178073538.3393.3.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=liontooth@cogweb.net \
--cc=nfs@lists.sourceforge.net \
/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