From: Artem Bityutskiy <dedekind1@gmail.com>
To: john smith <wempwer@gmail.com>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Is ubiattach alone somehow damaging a partition?
Date: Thu, 10 Mar 2016 11:05:04 +0200 [thread overview]
Message-ID: <1457600704.22708.9.camel@gmail.com> (raw)
In-Reply-To: <CAKmQUfZT+S5--mQntpUrZWR4gk4YcoXChN5254hixYtrT5JFYw@mail.gmail.com>
On Wed, 2016-03-09 at 21:52 +0100, john smith wrote:
> On 3/9/16, Richard Weinberger <richard.weinberger@gmail.com> wrote:
> >
> > Are both mtd1 and mtd2 supposed to carry UBI?
> > I'm not rally sure what you are trying to do...
> Hmm... probably not as kernel booting command does not contain
> anything similar to this:
>
> root=ubi:rootfs rootfstype=ubifs ubi.mtd=flash1.rootfs0
>
> However, I just thought that I can use ubiattach to be able to mount
> any given mtd device. I was looking for a way to get access to a
> currently not used mtd device. If ubiattach is suitable for this,
> then what may be?
Yeah, as Richard said, this is a bit vague description.
If you know what LVM is, what you are saying is something like:
"I just thought that I can use vgimport to be able to mount any block
device. I was looking for a way to get access to a currently not used
block devices. If vgimport is suitable for this, then what may be?"
Indeed, try to express what you want to achieve, and them may be it
becomes clearer to us.
Artem.
prev parent reply other threads:[~2016-03-10 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 10:43 Is ubiattach alone somehow damaging a partition? john smith
2016-03-09 18:55 ` Richard Weinberger
2016-03-09 20:52 ` john smith
2016-03-09 21:00 ` Richard Weinberger
2016-03-10 9:05 ` Artem Bityutskiy [this message]
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=1457600704.22708.9.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=wempwer@gmail.com \
/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