From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from a.ns.miles-group.at ([95.130.255.143] helo=radon.swed.at) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ajZEk-0006R2-NP for linux-mtd@lists.infradead.org; Fri, 25 Mar 2016 21:25:43 +0000 Subject: Re: ubiblock RW To: Ezequiel Garcia , Artem Bityutskiy References: <56F4502D.3030902@nod.at> <1458906697.615.20.camel@gmail.com> <20160325205011.GA1106@laptop.cereza> Cc: Benson Young , "linux-mtd@lists.infradead.org" , David Gstir , Willy Tarreau From: Richard Weinberger Message-ID: <56F5ACBD.8070201@nod.at> Date: Fri, 25 Mar 2016 22:25:17 +0100 MIME-Version: 1.0 In-Reply-To: <20160325205011.GA1106@laptop.cereza> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am 25.03.2016 um 21:50 schrieb Ezequiel Garcia: > I guess we could have some UBI parameter to enable this support, > and print a very noisy message to warn users about potential > device wear out -- naively assuming users read messages... As I wrote in my previous mail, I think a new parameter for the ubiblock tool would do the job. I'd default ubiblock to RO and via the ubiblock tool you can enable RW mode. ...which would also trigger a warning. What I'd like to avoid is a kernel command line or a Kconfig option to make RW default. If someone *really* wants RW she has to run ubiblock --enable-rw.... in userspace. This should even work for block filesystems on top of UBI as root fs as you can remount them later RW. Sounds like a plan? Thanks, //richard