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

Miklos Szeredi <[EMAIL PROTECTED]> writes: > From what I understand, the solution for the find > problem will actually make fts more optimal in some cases even for > POSIX filesystems, and will cause no regressions whatsoever. If so, then that's good for fts. The problem will continue to remain

[bug #15587] static linking to glibc 2.3.6 fails

Follow-up Comment #2, bug #15587 (project findutils): this is actually a bug in gnulib which has been fixed already so upgrade your findutils ___ Reply to this item at: ___

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

> Yes, for systems with O_NOFOLLOW, that is a perfect (efficient, race > free) solution. For systems without O_NOFOLLOW, just moving the > lstat() and the open() close to each other Actually moving the lstat() _after_ the open() totally removes the race for inode-less filesystems. The following

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

> > > There must already be such problems with hard links anyway, so this > > > extra problem isn't that much worse. > > > > Yes it is. Neither sftp, nor smbfs, nor fat support hard links. All > > of them support rename. > > Not entiirely accurate. SSHFS supports whatever the underlying > remo

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

On 10/7/06, Miklos Szeredi <[EMAIL PROTECTED]> wrote: [ JY: I assume that "> >" quotes statements by Paul Eggert, but the attribution has been lost ] > There must already be such problems with hard links anyway, so this > extra problem isn't that much worse. Yes it is. Neither sftp, nor smbfs

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

> > If you were thinking of a soltuion, where the filesystem itself > > supplies two different inode numbers based on the variant of the > > userspace interface, then I'm sorry to inform you, that this sort of > > interface is not likely to happen in the Linux kernel. > > I don't see why not. Bec

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

Miklos Szeredi <[EMAIL PROTECTED]> writes: > If you were thinking of a soltuion, where the filesystem itself > supplies two different inode numbers based on the variant of the > userspace interface, then I'm sorry to inform you, that this sort of > interface is not likely to happen in the Linux ke

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

> > The legacy app will break regardless of how many files there are on > > the filesystem, or even wheter it needs to use the inode number or > > not. It will break because the stat() family of syscalls will return > > with an error. > > I don't see why. The kernel should be able to tell whethe