Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Find And Locate Your Files" video.

  1. 8:07 Just checked the man page, and “+” means “greater than”, not “at least”. Similarly “-” means “less than”, not “at most”. Also k is kibibytes, not kilobytes, and M is mebibytes, not megabytes. And the sizes are rounded to the specified unit. Thus, “-10M” will only match files up to 9 × 1048576 = 9437184 bytes in size, not 10 × 1048576 - 1 = 10485759 bytes as you might have been expecting.
    3
  2. The find executable on my 64-bit system is just about 300K in size. What do you not consider “bloated”?
    2
  3.    So what features would you remove from find, and where else can you find them?
    2
  4.    So what about options to find files by size, timestamps and permissions, for example--how would you implement those? What about ranges for size and timestamps? Really, you don’t know what find does, and yet you feel qualified to describe it as “bloat”?
    1
  5. 2:09 And you can do a case-insensitive search with -iname instead of -name. Useful if you have files transferred from other systems that end up with uppercase names (e.g. .TXT instead of .txt).
    1
  6. 6:57 Ah, OK.
    1
  7. One common idiom is feeding a list of files from find to some other command using xargs: find «criteria» -print | xargs «cmd» When feeding file names to another shell command, beware of shell-specials, for example spaces in filenames. Don’t forget you can also have newlines in filenames. The GNU versions of find and xargs have the option to use nulls as pathname separators, which avoids this problem: find «criteria» -print0 | xargs -0 «cmd»
    1
  8. ldo@theon:~> man find | wc -l 1277 But it’s handy for looking up things as I need them.
    1
  9. What does “C:, D:, E” mean?
    1
  10. I sincerely hope you are not a fan of GNU info ...
    1