From: Erwin Rol <mailinglists@erwinrol.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: ubifs
Date: Mon, 03 Dec 2018 14:06:21 +0100 [thread overview]
Message-ID: <1543842381.5085.24.camel@erwinrol.com> (raw)
In-Reply-To: <20181203125811.cm6mzwrjy7glrh5j@pengutronix.de>
On Mon, 2018-12-03 at 13:58 +0100, Sascha Hauer wrote:
> Hi Erwin,
>
> On Mon, Dec 03, 2018 at 01:42:11PM +0100, Erwin Rol wrote:
> > Hallo all,
> >
> > I want to create empty ubifs volumes, like this;
> >
> > 1) ubiformat -y -q /dev/nand0.system
> > 2) ubiattach /dev/nand0.system
> > 3) ubimkvol -t dynamic /dev/nand0.system.ubi system 0
> >
> > 4) .... ????
> >
> > 5) mount -t ubifs -o rw /dev/nand0.system.ubi.system /mnt/system/
> >
> >
> > Is this possible with barebox?
>
> It depends on what you do in step 4. Should be something like
> 'ubiupdatevol' or cp /some/image /dev/nand0.system.ubi.system. But then,
> yes, this works
But I need some sort of image, I can not create an empty ubifs volume
and mount it with just barebox tools ?
- Erwin
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-12-03 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:42 ubifs Erwin Rol
2018-12-03 12:58 ` ubifs Sascha Hauer
2018-12-03 13:06 ` Erwin Rol [this message]
2018-12-03 13:26 ` ubifs Sascha Hauer
2018-12-03 13:35 ` ubifs Erwin Rol
-- strict thread matches above, loose matches on Subject: below --
2013-06-18 15:47 ubifs Aidan Totterdell
2011-09-28 15:27 ubifs Renaud Barbier
2011-09-29 10:18 ` ubifs Sascha Hauer
2008-12-10 13:50 Ubifs Жека
2008-12-10 11:44 Ubifs Жека
2008-12-10 11:55 ` Ubifs Artem Bityutskiy
2008-12-10 12:51 ` Ubifs Artem Bityutskiy
2008-12-10 9:02 Ubifs Жека
2008-12-10 11:04 ` Ubifs Artem Bityutskiy
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=1543842381.5085.24.camel@erwinrol.com \
--to=mailinglists@erwinrol.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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.