From: "Bryan J. Smith" <b.j.smith@ieee.org>
To: Tom McNeal <trmcneal@attbi.com>
Cc: "Bryan J. Smith" <b.j.smith@ieee.org>,
Daniel Forrest <forrest@lmcg.wisc.edu>,
Alan Witz <awitz@magstarinc.com>,
nfs@lists.sourceforge.net
Subject: Re: Corrupt Data when using NFS on Linux -- This should be in the HOWTO
Date: Tue, 29 Oct 2002 13:23:43 -0500 (EST) [thread overview]
Message-ID: <1035915823.3dbed22fa9dc0@webmail.smithconcepts.com> (raw)
In-Reply-To: <3DBECE74.506@attbi.com>
Quoting Tom McNeal <trmcneal@attbi.com>:
> Its easier with the FAQ, but the HOWTO might be the better place.
> We'll take a look at it...
Maybe just a "Top 10 Differences Between NFS And Local"
- Mounts in exported filesystems are not automatically exported
- Locking issues and accomodation in scripts/programs
- Etc...
I think it would go a long way to helping many.
--
Bryan J. Smith, E.I. Contact Info: http://thebs.org
A+/i-Net+/Linux+/Network+/Server+ CCNA CIWA CNA SCSA/SCWSE/SCNA
---------------------------------------------------------------
limit guilt = { psychopath,
remorse->0 innocent }
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-10-29 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 20:48 Corrupt Data when using NFS on Linux Lever, Charles
2002-10-28 23:05 ` Alan Witz
2002-10-29 1:34 ` Eff Norwood
2002-10-29 17:03 ` Daniel Forrest
2002-10-29 17:20 ` Corrupt Data when using NFS on Linux -- This should be in the HOWTO Bryan J. Smith
2002-10-29 18:07 ` Tom McNeal
2002-10-29 18:23 ` Bryan J. Smith [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=1035915823.3dbed22fa9dc0@webmail.smithconcepts.com \
--to=b.j.smith@ieee.org \
--cc=awitz@magstarinc.com \
--cc=forrest@lmcg.wisc.edu \
--cc=nfs@lists.sourceforge.net \
--cc=trmcneal@attbi.com \
/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.