From: Richard Weinberger <richard@nod.at>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Artem Bityutskiy <dedekind1@gmail.com>
Cc: Benson Young <benson6877@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Gstir <david@sigma-star.at>, Willy Tarreau <w@1wt.eu>
Subject: Re: ubiblock RW
Date: Fri, 25 Mar 2016 22:25:17 +0100 [thread overview]
Message-ID: <56F5ACBD.8070201@nod.at> (raw)
In-Reply-To: <20160325205011.GA1106@laptop.cereza>
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
next prev parent reply other threads:[~2016-03-25 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABJ+KKu2RJuHXE3LpmzSYtE0i57sHDUHWOxPxufCP94RTa=eBA@mail.gmail.com>
2016-03-24 14:23 ` ubiblock RW Ezequiel Garcia
2016-03-24 20:38 ` Richard Weinberger
2016-03-24 21:26 ` Ezequiel Garcia
2016-03-24 21:39 ` Willy Tarreau
2016-03-25 20:28 ` Richard Weinberger
2016-03-25 11:51 ` Artem Bityutskiy
2016-03-25 20:50 ` Ezequiel Garcia
2016-03-25 20:51 ` Ezequiel Garcia
2016-03-25 21:25 ` Richard Weinberger [this message]
2016-03-26 6:01 ` Willy Tarreau
2016-03-27 22:01 ` Richard Weinberger
2016-03-28 6:56 ` Artem Bityutskiy
2016-03-28 8:17 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F5ACBD.8070201@nod.at \
--to=richard@nod.at \
--cc=benson6877@gmail.com \
--cc=david@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox