All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Brett Petrusek <brettp@aspsys.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS IA32 server / IA64 client problems
Date: Tue, 23 Aug 2005 19:40:07 -0400	[thread overview]
Message-ID: <1124840407.10110.5.camel@lade.trondhjem.org> (raw)
In-Reply-To: <430BA6DB.7080907@aspsys.com>

ty den 23.08.2005 Klokka 16:44 (-0600) skreiv Brett Petrusek:
 
> Networking has been completely ruled out as an issue.

How?

Cheers,
  Trond



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2005-08-23 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 22:44 NFS IA32 server / IA64 client problems Brett Petrusek
2005-08-23 23:40 ` Trond Myklebust [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=1124840407.10110.5.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=brettp@aspsys.com \
    --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 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.