:linux> cp multipatch-1.diff test1
:fbsd> cat test1
:cat: test1: RPC struct is bad
:fbsd> cp test1 /tmp
:fbsd> cat test1
:<SNIP>
:+ (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) {
:
:^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
:^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
:^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
:^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
:^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
:^@^@^@^@^@^@^@^@requested range. Note: we are assuming that
:<SNIP>
:
:Doesn't happen between two linux boxen. (Both 2.2.11-NFSv3)
:
:-Rob
Yah, but that doesn't mean much. What we have here is some sort of
protocol confusion. Try an NFSv2 mount and see if that works.
If the problem is protocol confusion there's a good 70% chance that the
confusion is on the side of the linux server, since linux's NFSv3
implementation is *very* recent. It would take someone with a protocol
analyzer to track it down.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
