In my summary, I wrote:
-> It was also pointed out that:
->
-> 1. I don't need to use the B option when reading from an NFS mounted directory.
-> The B option is really only needed when reading from a pipe. This
-> contradicts the man page which says "This option exists so that bar can work
-> across the Ethernet, since pipes and sockets return partial blocks even when
-> more data is coming."
J. Matt Landrum (mdl@cypress.com) clarified this point for me, and I thought I would
pass it along to you:
This is not to pick nits, just some info which you can take or leave.
Whenever someone refers to NFS, they are usually talking about it
symbolically, not all the little daemons and packets which are required
to have functional NFS. There is no contradiction in the man page if
you think about NFS in the abstract. The filesystem is local (by
definition) as far as most UNIX commands (including bar and tar) are
concerned. You will see this for virtually all NFS references whereas
anything that requires an rsh may be thought of as "across the
Ethernet". Check out the example of using bar or tar to copy
hierarchies for the use of the B option. The tar man page is a good
thing to be familiar with.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:53 CDT