From: Frank Steiner <fsteiner-mail1-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>
To: nfs@lists.sourceforge.net
Subject: Re: [NFS] locking failure with rpcbind and nfsroot (SLES 11, 2.6.27)
Date: Tue, 28 Jul 2009 12:31:50 +0200 [thread overview]
Message-ID: <4A6ED396.7000705@bio.ifi.lmu.de> (raw)
In-Reply-To: <4A671ADE.5060109-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>
So, is no one but me using root-over-nfs anymore?
Otherwise I wonder how one can handle a /var filesystem with root-over-nfs
and locking. I can't be the only one having this problem?!
cu,
FRank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
prev parent reply other threads:[~2009-07-28 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 13:57 [NFS] locking failure with rpcbind and nfsroot (SLES 11, 2.6.27) Frank Steiner
[not found] ` <4A671ADE.5060109-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>
2009-07-28 10:31 ` Frank Steiner [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=4A6ED396.7000705@bio.ifi.lmu.de \
--to=fsteiner-mail1-g0geqqhi7dhyikxmg8wjig@public.gmane.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox