From: Daniel Egger <degger@fhm.edu>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org, NFS@lists.sourceforge.net
Subject: Re: NFS client locking hangs for period
Date: 29 Jan 2003 22:53:33 +0100 [thread overview]
Message-ID: <1043875672.1094.19.camel@sonja> (raw)
In-Reply-To: <200301280801.h0S81Ns10071@Port.imtp.ilyichevsk.odessa.ua>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Am Die, 2003-01-28 um 09.00 schrieb Denis Vlasenko:
> It was not really *that* difficult for me. I used devfs and symlinks.
> /etc, /var, /tmp are different directories per client,
> /home, /usr are shared. The rest stays on root fs readonly.
> ssh to NFS server if you want to modify some files on root fs.
This will only work dandy if the server runs the same OS on the
same architecture and its own system is well enough equipped to
do software installations and bootstraps. Although I'm using Linux on
my server as well as the same architecture as most of the clients
I sometimes experience troubles working in the chrooted client
environment.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-29 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 20:49 NFS client locking hangs for period Christian Reis
2003-01-25 3:54 ` Neil Brown
2003-01-26 16:02 ` Christian Reis
2003-01-26 21:49 ` [NFS] " Trond Myklebust
2003-01-26 22:47 ` Christian Reis
2003-01-26 23:02 ` Trond Myklebust
2003-01-26 23:56 ` Christian Reis
2003-01-27 0:06 ` Trond Myklebust
2003-01-27 2:19 ` Dell Latitude CPi keyboard problems since 2.5.42 Tom Sightler
2003-01-28 8:14 ` [NFS] Re: NFS client locking hangs for period Denis Vlasenko
2003-01-28 16:47 ` Christian Reis
2003-01-28 8:00 ` Denis Vlasenko
2003-01-28 16:44 ` Christian Reis
2003-01-29 21:53 ` Daniel Egger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 4:57 Christian Reis
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=1043875672.1094.19.camel@sonja \
--to=degger@fhm.edu \
--cc=NFS@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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