Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

> > Follow-up Comment #8, bug #17877 (project findutils): > > > > Thanks for the patch. I've tested it and it doesn't seem to make any > > difference. > > Are you using the fts version of find 4.3.x? Yes, find/find from 4.3.1+patch. With find/oldfind the bug doesn't show up. Miklos

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

> > Follow-up Comment #1, bug #17877 (project findutils): > > > > > There are several Linux filesystems (including smbfs, fat, and > > > some FUSE based ones) which cannot provide stable inode numbers > > > for unreferenced files or directories. > > OP, can you provide a test case which demonstrat

[bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

Follow-up Comment #10, bug #17877 (project findutils): > if some Linux-based file systems can't provide stable inode > numbers, they should be fixed so that they do. It shouldn't > be that hard. It's not hard, it's impossible. Take for example path based network filesystems (smbfs, sshfs). Fo

[bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

Follow-up Comment #9, bug #17877 (project findutils): Miklos Szeredi <[EMAIL PROTECTED]> writes: > What the patch does is to release the inode as > soon as there are no more references to it. Sorry, but that's going to break lots of code. It's not just gnulib; it's lots of other uses as well.

Re: Fwd: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

"James Youngman" <[EMAIL PROTECTED]> wrote: > On 10/4/06, Jim Meyering <[EMAIL PROTECTED]> wrote: > >> The resulting down side is that the old version of find is >> susceptible to a nasty type of attack when traversing a directory >> that is writable by another user. > > I think even oldfind (i.e.

Re: Fwd: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

On 10/4/06, Jim Meyering <[EMAIL PROTECTED]> wrote: The resulting down side is that the old version of find is susceptible to a nasty type of attack when traversing a directory that is writable by another user. I think even oldfind (i.e. version 4.2.x and the alternate binary in 4.3.x) has suf

Fwd: findutils 4.2.28 compilation fails on Solaris 9

FYI. -- Forwarded message -- From: Frank Baird <[EMAIL PROTECTED]> Date: Sep 18, 2006 10:40 PM Subject: Re: findutils 4.2.28 compilation fails on Solaris 9 To: James Youngman <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] James, I have found a way to get findutils-4.2.28 to compile

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

On 10/4/06, Miklos Szeredi <[EMAIL PROTECTED]> wrote: Follow-up Comment #8, bug #17877 (project findutils): Thanks for the patch. I've tested it and it doesn't seem to make any difference. Are you using the fts version of find 4.3.x? ___ Bug-find

[bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

Follow-up Comment #8, bug #17877 (project findutils): Thanks for the patch. I've tested it and it doesn't seem to make any difference. ___ Reply to this item at: