Hi, On Wed, Mar 30 2011, Andrei Warkentin wrote: > The argument against turning it on by default is that someone might > figure that mke2fs-ing the boot partitions is a good way to reclaim > 4MB on their rooted device, > and if they didn't realize the data was necessary for boot-up, they > will brick the device. Ah. Ugh, that sucks; I can totally see that happening. Now I'm wondering if we should just be hardcoding boot devices as always read-only and just refusing to write to them. What do others think? Is there an acceptable tradeoff somewhere? It's not clear to me that Kconfig entries are sufficient to obtain consent to present r/w mounts of the boot partitions; the user writing the "dd" line usually isn't the person who made the Kconfig selection, and the person who made the Kconfig selection is often a distro maintainer who just turns on new Kconfig symbols without reading closely. > That and people might freak out when they see > more mmcblk entries than they expected :-). I'm not worried about this one, as long as they have the postfixes. Thanks, - Chris. -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
