From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCHv4] MMC: MMC boot partitions support. Date: Fri, 1 Apr 2011 11:23:14 +0200 Message-ID: <201104011123.14675.arnd@arndb.de> References: <1300533491-2378-2-git-send-email-andreiw@motorola.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.126.186]:63977 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755192Ab1DAJXS (ORCPT ); Fri, 1 Apr 2011 05:23:18 -0400 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Andrei Warkentin Cc: Chris Ball , linux-mmc@vger.kernel.org On Thursday 31 March 2011, Andrei Warkentin wrote: > > Another strawman, after brainstorming a bit on IRC -- how about > > the block device itself comes up read-only, until you use a module > > parameter/sysfs entry to make it read-write. As a strawman: > > > > echo 1 > /sys/module/mmc_block/boot_partitions_are_writeable > > > > (That way people who write to it regularly can throw the module parameter > > in their boot environment, and the rooting enthusiasts who didn't compile > > the kernel are safe until they learn enough to be really dangerous..) > > Sure, I like this, I'll do it. I don't think it's even needed, but it sounds much more useful than a Kconfig option, so no objections from me. Arnd