On Thursday 31 March 2011, Andrei Warkentin wrote:
> Well, there are less esoteric ways of turning something into a
> paperweight =). No, the whole point of adding the device partition
> support is so you don't have to go through hoops to read and write
> them.
Agreed.
> The scenario where it matters (embedded Linux devices booting through
> boot partitions) are such, that if you went through sufficient hoops
> to get root access, and can build and boot a kernel to enable these
> options for that device, then you must know what you're doing, and a
> warning message in the Kconfig help is sufficient. The generic case of
> people sticking cards into a PCI SDHCI controller under Ubuntu is such
> that you can do no real damage.
One possible way of dealing with this would be to make the boot partition
a character device instead of a block device. That would still allow
you to overwrite it, but make it very obvious that you cannot mount or
partition it.
On the other hand, it would be a rather esoteric interface, since the
hardware is still fundamentally block based, we just use it in a different
way.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
