From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: (FOLLOWUP) Re: wierd NFS problem with UP1.1.9
Date: Thu, 31 Dec 1998 02:20:35 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91510127931157@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91498590723709@msgid-missing>
What is the NFS server running?
Anyways, my current hunch is that when I merge our tree to 2.2.0-prex
this may vanish... and this I'm doing soon as the 2.2.x is now on.
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1998-12-31 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-29 20:56 (FOLLOWUP) Re: wierd NFS problem with UP1.1.9 Matthew Jacob
1998-12-31 2:20 ` David S. Miller [this message]
1998-12-31 3:47 ` Matthew Jacob
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=marc-linux-ultrasparc-91510127931157@msgid-missing \
--to=davem@dm.cobaltmicro.com \
--cc=ultralinux@vger.kernel.org \
/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.