Andrew Benton wrote: > Then redirect the error messages to /dev/null > > find / -name somefile 2> /dev/null
I disagree. In this way you can miss a really important error message so it's better to ignore the warning in question. Concerning something's being misconfigured, the comment in find's source code says "This is likely to be a bug in the filesystem driver (e.g. Linux's /proc filesystem) or may just be a fact that the OS doesn't really handle hard links with Unix semantics" so the failure while finding in /proc is a known (at least, to find's authors :) ) issue and, consequently, you can safely ignore it. -- Nothing but perfection pv -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
