From: Artem Bityutskiy <dedekind1@gmail.com>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] do_mounts: Allow mtd names for non-flash block filesystems
Date: Tue, 12 Oct 2010 17:27:07 +0300 [thread overview]
Message-ID: <1286893627.2164.65.camel@localhost> (raw)
In-Reply-To: <AANLkTi=A6djk8hOgLOg045f5XiiwkOYS2QtzOUwiT+Bo@mail.gmail.com>
On Tue, 2010-10-12 at 15:16 +0200, Karl Beldan wrote:
> On Mon, Oct 11, 2010 at 9:24 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Wed, 2010-10-06 at 23:02 +0200, Karl Beldan wrote:
> >> Hi,
> >>
> >> I have been using this tweak for some time now, and I am getting tired of
> >> having to resort to it so often.
> >> It allows to pass such cmdline root as:
> >> "root=mtdb:ubivolx rootfstype=squashfs"
> >> I am pretty sure many people use squashfs/cramfs filesystems on top of nand,
> >> for example, and I thought that this might initiate discussion.
> >>
> >> --
> >> Karl
> >>
> >> Signed-off-by: Karl Beldan <karl.beldan@gmail.com>
> >> ---
> >> init/do_mounts.c | 15 +++++++++++++--
> >> 1 files changed, 13 insertions(+), 2 deletions(-)
> >
> > Dunno...
> >
> > First of all, if you have to do this, let it be mtdblock, not mtdb - no
> > need to breed aliases.
> >
> > But how about teaching squashfs to understand mtdX and mtd:name syntax
> > instead?
> >
>
> Hi Artem,
>
> I would not do that, squashfs and co just ask for a block device, putting mtdx
> syntax awareness in each of them just does not seem a good fit to me.
Right. But the same arguments applies to do_mounts.c which you hack:
mtdblock is just a block device, putting awareness of specific types of
block devices is not a good thing to do.
May be this is why I'm not too happy about your patch?
> BTW 'for-2.6.37' got https://patchwork.kernel.org/patch/145681/.
Yeah, it is better to have a generic approach which can be applied to
all block devices. Make UUID of your mtdblock to be equivalent to the
name of the underlying mtd device and you are done: use
PARTUUID=<mtd_device_name>. Right?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-10-12 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 21:02 [RFC] do_mounts: Allow mtd names for non-flash block filesystems Karl Beldan
2010-10-06 21:22 ` Karl Beldan
2010-10-11 19:24 ` Artem Bityutskiy
2010-10-12 13:16 ` Karl Beldan
2010-10-12 14:27 ` Artem Bityutskiy [this message]
2010-10-12 15:11 ` Karl Beldan
2010-10-12 15:27 ` Artem Bityutskiy
2010-10-12 15:51 ` Karl Beldan
2010-10-13 10:35 ` Peter Korsgaard
2010-10-13 11:16 ` Karl Beldan
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=1286893627.2164.65.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=karl.beldan@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.