From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Wright <chrisw@osdl.org>
Cc: Matt Bernstein <mb/lkml@dcs.qmul.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6: can't lockf() over NFS
Date: 25 Nov 2003 20:35:17 -0500 [thread overview]
Message-ID: <shsznejzzca.fsf@charged.uio.no> (raw)
In-Reply-To: <20031125165501.A20302@build.pdx.osdl.net>
>>>>> " " == Chris Wright <chrisw@osdl.org> writes:
> Yes, can you either change your config to:
> CONFIG_SECURITY=n
> or:
> CONFIG_SECURITY=y CONFIG_SECURITY_CAPABILITIES=y
> or:
> CONFIG_SECURITY=y CONFIG_SECURITY_CAPABILITIES=m and modprobe
> capability
Sorry, yes. That one slipped my mind...
Cheers,
Trond
next prev parent reply other threads:[~2003-11-26 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 16:17 2.6: can't lockf() over NFS Matt Bernstein
2003-11-26 0:39 ` Trond Myklebust
2003-11-26 0:55 ` Chris Wright
2003-11-26 1:35 ` Trond Myklebust [this message]
2003-11-26 11:21 ` Matt Bernstein
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=shsznejzzca.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb/lkml@dcs.qmul.ac.uk \
/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.