Follow-up Comment #19, bug #12162 (project findutils):
I like Nigel's suggestion of -filesize.
i suggest adding "c" as a synonym for "b."
I further suggest that all the units be made case-insensitive.
I like Nigel's further suggestion about -size and -blocksize. Also, print a
warning to s
Follow-up Comment #2, bug #26217 (project findutils):
Damn, I knew I must be doing something dumb, sorry.
Now that I know what it means, the error message is clear, but the eye just
skipped past the : ; combo.
Might I suggest a special-case error message when an unnecessary trailing ;
is encoun
Follow-up Comment #16, bug #12162 (project findutils):
I don't believe the behavior is correct, but here's the line of reasoning.
THe original find implementation counts disk blocks. A block is either used
(partially or fully), or not.
Blocks are (typically? always?) 512 bytes long.
You ar
Follow-up Comment #11, bug #12162 (project findutils):
While I was at it I checked Solaris 10.
Their find command does not have any units other than blocks & characters.
The -size N behaves like gnu find, ie, 513-byte files are not shown if you
ask for -size -2
-size -1024c, however, works l
Follow-up Comment #10, bug #12162 (project findutils):
FreeBSD 7 find also works the way i'd want it to, and the man page snippet
is identical to the one from MacOS I quote below.
thanks for taking the time to think about this.
___
Reply
Follow-up Comment #9, bug #12162 (project findutils):
MacOS find behaves in the way i'd expect, at least in the obvious case of
-size -1G;
It has this in the man page:
-size n[ckMGTP]
True if the file's size, rounded up, in 512-byte blocks is n.
If
n is followed
Follow-up Comment #7, bug #12162 (project findutils):
Due to the nature of filesystem disk allocation and use of blocks,
I guess i can imagine why someone who's searching on blocks would
be sad if his block search showed him files that were using that
Follow-up Comment #6, bug #12162 (project findutils):
I ran into this bug today. The degenerate case was that "find -size -1G"
only matches files zero bytes in size. I am really having a hard time
imagining who in their right mind would want this.
I find this behavior to be horribly broken. M
