as an experiment, i created a small logical volume just for my
kernel git checkout and mounted it read-only to verify that any
"make"s that incorporate "O=" didn't try to modify anything within the
tree.
a side effect was to notice that doing any kind of cleaning failed
to enter the non-enterable "lost+found" directory found at the top of
any filesystem.
not fatal, of course, but perhaps lost+found can be added to the
list of directories to avoid during any search.
rday
p.s. perhaps a cleaner solution would be to use, as the argument to
find, not ".", but an explicit list of directories for which it makes
sense to search.
if that were the case, you could avoid doing any processing on any
top-level directories that couldn't possibly need any cleaning, such
as include/. personally, i think that's a better solution, but that's
just me.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
