Am Dienstag, 26. Februar 2013 schrieb Tsutomu Itoh: > >> Therefore I want you to revert > >> commit:2a2d8e1962e8b6cda7b0a7584f6d2fb95d442cb6. > >> > >> btrfs-progs: require mkfs -f force option to overwrite filesystem > >>or partition table > >> > >> How do you think about it? > > > > What if you submit a patch to look at an environment variable, > > BTRFS_CLOBBERS_ALL=1 which causes it to not require -f to overwrite? > > Then you can just set it once at the top of your test environment, > > and not change every instance? > > Yes. But, > >> (Most of my test scripts fails without -f. So I'll always type > "mkfs.btrfs -f") is one example. > > Almost everyone types "mkfs.btrfs -f" (or BTRFS_CLOBBERS_ALL=1 :) > unconditionally, I think. > So, I think -f option is almost meaningless. No. I don´t. And I teach not to in my trainings as well. Everyone who uses rm -rf by default even just for deleting a single file does it as long as he or she deleted his / her home directory or something. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
