From: Christian Reis <kiko@async.com.br>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, NFS@lists.sourceforge.net
Subject: Re: [NFS] Re: NFS client locking hangs for period
Date: Tue, 28 Jan 2003 14:47:59 -0200 [thread overview]
Message-ID: <20030128144759.D11078@blackjesus.async.com.br> (raw)
In-Reply-To: <200301280815.h0S8FLs10146@Port.imtp.ilyichevsk.odessa.ua>; from vda@port.imtp.ilyichevsk.odessa.ua on Tue, Jan 28, 2003 at 10:14:09AM +0200
On Tue, Jan 28, 2003 at 10:14:09AM +0200, Denis Vlasenko wrote:
> > None of the users have root access so writing to the partition only
> > is done as the result of servers running. I used a lot of reboots and
> > ls -lt to find out what needs to be separate, and there are few
> > issues that need fixing (/etc/ioctl.save being the latest).
>
> Entire /etc. How can you have different per-client configs for
> e.g. /etc/resolv.conf? I know you don't usually need that.
> Sometimes we need to do unusual things ;)
Well, the per-client configurations are an exception at our office, and
the only things we customize are XFree86 (we use the
Xfree86Config.hostname capability), gpm and the kernel, which is
dealt out by DHCPD. We also have a special startup script that is run
for the named box if it exists (/etc/init.d/host-specific/`hostname`).
I'm sure this won't work for everybody, but it does work for us, a
smallish development team.
> Same here. Devfs is cool ;)
> For one, it forces people to think before they got strange ideas of
> putting something foreign in /dev. Like abm syslogd.
Only after using devfs in this context have I come to appreciate how
nice it is. And I had it in place after 10 minutes of reading and two of
recompiled kernels. Amazing.
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
next prev parent reply other threads:[~2003-01-28 16:39 UTC|newest]
Thread overview: 14+ 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 [this message]
2003-01-28 8:00 ` Denis Vlasenko
2003-01-28 16:44 ` Christian Reis
2003-01-29 21:53 ` Daniel Egger
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=20030128144759.D11078@blackjesus.async.com.br \
--to=kiko@async.com.br \
--cc=NFS@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=trond.myklebust@fys.uio.no \
--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