Linux NFS development
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: nfs@lists.sourceforge.net
Cc: Neil Brown <neilb@suse.de>
Subject: Re: /etc/exports continue line
Date: Thu, 12 Apr 2007 20:49:21 -0400	[thread overview]
Message-ID: <200704122049.22452.vapier@gentoo.org> (raw)
In-Reply-To: <461EAE48.9020703@cogweb.net>


[-- Attachment #1.1: Type: text/plain, Size: 427 bytes --]

On Thursday 12 April 2007, David Liontooth wrote:
> Once you know about this quirk, it's obviously less of an issue.

like everything else in the *nix world ;)

> Could exportfs just filter out TAB characters, 
> or would you consider that unwanted code clutter?

err, i dont think that's not a good idea ... the expots is whitespace 
delimited, not space delimited ... that'd break configurations i'd imagine
-mike

[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-04-13  0:48 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 [this message]
2007-05-02  2:38 ` Ian Kent

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=200704122049.22452.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=neilb@suse.de \
    --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