On Mon, Jul 11, 2011 at 03:13:41PM +0100, David Howells wrote:
Christoph Hellwig h...@infradead.org wrote:
would do the same.
But is much less obvious. The LOOKUP_FOLLOW flag is the primary reason for
this statement. The rest are subordinate and would be wholly irrelevant
On Thu, Apr 07, 2011 at 04:24:29PM -0400, Chuck Lever wrote:
See http://oss.oracle.com/projects/fedfs-utils for more information and
source code downloads. Two mailman mailing lists are also available:
fedfs-utils-annou...@oss.oracle.com
fedfs-utils-de...@oss.oracle.com
Is it really a
On Thu, Aug 07, 2008 at 07:40:23PM +0800, Ian Kent wrote:
Patch to add documentation for the miscellaneous device module of
autofs4.
Any documentation should preferably stay withthe patch introducing
the interface. But hopefully most of this won't be needed anyway
with the proper solution.
On Thu, Aug 07, 2008 at 07:40:31PM +0800, Ian Kent wrote:
The actual problem with autofs is that it can't reconnect to existing
mounts. Immediately one things of just adding the ability to remount
autofs file systems would solve it, but alas, that can't work. This is
because autofs direct
On Thu, Aug 07, 2008 at 07:40:06PM +0800, Ian Kent wrote:
Usage of the AUTOFS_TYPE_* defines is a little confusing and
appears inconsistent.
Not enough of an explanation for this patch.
It does:
- move AUTOFS_TYPE_INDIRECT/AUTOFS_TYPE_DIRECT/AUTOFS_TYPE_OFFSET
to include/linux/auto_fs4.h.
On Sat, Aug 09, 2008 at 11:29:09PM +0800, Ian Kent wrote:
On Sat, 2008-08-09 at 08:59 -0400, Christoph Hellwig wrote:
On Thu, Aug 07, 2008 at 07:40:31PM +0800, Ian Kent wrote:
The actual problem with autofs is that it can't reconnect to existing
mounts. Immediately one things of just
On Mon, Feb 20, 2006 at 09:05:59AM +0800, Ian Kent wrote:
autofs_wqt_t wait_queue_token;
Hiding types in user visible structures behind typedefs is bad.
What type is behind this? If this is not an __u32 you have
a padding issue.
This has been an occassion problem for a long time.
On Fri, Dec 09, 2005 at 08:33:45AM -0500, John T. Kohl wrote:
Christoph path_walk and firends resolve a full path. As such they are
Christoph definitly not suitable for stackable filesystem, they are
Christoph intendeded only for implementating syscalls (and syscall-like
Christoph interfaces,
On Wed, Dec 07, 2005 at 12:46:39PM -0500, Will Taber wrote:
problem at hand. Anyway, with this information, is it appropriate for
us to replace our calls to lookup_one_len with calls to path_walk or is
that also forbidden?
path_walk and firends resolve a full path. As such they are
On Wed, Dec 07, 2005 at 10:22:23AM -0500, Brian Long wrote:
I believe the filesystem is IBM Rational's mvfs (multi-version
filesystem) used in ClearCase. My team is the internal support
organization at Cisco for Red Hat Enterprise Linux issues and we opened
the support case with Red Hat about
On Tue, Dec 06, 2005 at 04:20:29PM -0500, Jeff Moyer wrote:
hch No, for current TOT that can't happen. It could happen for older
hch kernels but nothing is doing it in the tree anymore and if anything
hch outside is doing it it's fundamentally broken.
This is a bit unclear to me. What do
11 matches
Mail list logo
