Releases and the 4.5 branch

2015-06-17 Thread Ilya Bobyr
Hi everyone, I am new to this list, so I am sorry if I am asking something that was already asked. I am using find on Ubuntu 15.04 and hit a bug. It is related to -fstype - sometimes nfs or cifs is identified as ext4. It appears the bug is already fixed in the current development branch 4.5. I

Re: Filename Expansion: Find Utility Pattern Matching vs Bash Shell Pattern Matching

2015-06-17 Thread Assaf Gordon
Hello Michael, On 06/17/2015 12:43 PM, Michael Convey wrote: <...> I'm trying to understand why the operators work differently under different circumstances. For example, according to the following link, 'find -name' appears to use fnmatch(), whereas bash appears to use glob(): I believe this

Re: Filename Expansion: Find Utility Pattern Matching vs Bash Shell Pattern Matching

2015-06-17 Thread Michael Convey
​Stephane, yes, I read your very thorough answer at stackechange -- thank you. You obviously understand how the various globbing/pattern matching operators (i.e. *, ?, [], /, etc.)​ work in different circumstances (as evidenced by your detailed examples). However, I'm trying to understand why the o

Re: Why xargs still call the command when there is no input?

2015-06-17 Thread Stephane Chazelas
2015-06-02 21:59:22 -0600, Eric Blake: > On 06/02/2015 04:02 PM, Peng Yu wrote: > > The following command will call ls. But since there is no input, > > shouldn't xargs quit without doing anything? Thanks. > > > > xargs -0 ls > Try: > > xargs -r -0 ls > Per POSIX, the behavior of one-or-more

Re: Filename Expansion: Find Utility Pattern Matching vs Bash Shell Pattern Matching

2015-06-17 Thread Stephane Chazelas
2015-06-16 12:02:33 -0700, Michael Convey: > For filename expansion, the 'find' utility's '-name' option seems to > function similarly, but not exactly the same as the bash shell's builtin > pattern matching. > > Here are the relevant sections of the GNU reference manual: > >- Bash shell patt