From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] How to handle targets that need more than one file system to boot?
Date: Thu, 3 Jan 2013 19:08:07 +0100 [thread overview]
Message-ID: <201301031908.07247.yann.morin.1998@free.fr> (raw)
In-Reply-To: <CAEYzJUFB5qbQBguXNoux=kqMHhqpj0pKDFhBi6j0FHAF7QU8Mw@mail.gmail.com>
Bj?rn, All,
On Thursday 03 January 2013 Bj?rn Forsman wrote:
> On 3 January 2013 18:33, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > As for ext4, it is probably not possible, as it is really different from
> > an ext2/3 filesystem.
>
> You can also convert ext3 to ext4:
>
> https://ext4.wiki.kernel.org/index.php/Ext4_Howto#Converting_an_ext3_filesystem_to_ext4
Ah, good to know! Thank you! :-)
So, we now know how to generate filesystems for all the ext familly. Yeah!
Regarfds,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-01-03 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 0:00 [Buildroot] [RFC] How to handle targets that need more than one file system to boot? Yann E. MORIN
2012-12-25 3:52 ` Steve Calfee
2013-01-02 6:57 ` Arnout Vandecappelle
2013-01-02 23:56 ` Yann E. MORIN
2013-01-03 0:32 ` Steve Calfee
2013-01-03 8:31 ` Willy Lambert
2013-01-03 17:33 ` Yann E. MORIN
2013-01-03 17:54 ` Bjørn Forsman
2013-01-03 18:08 ` Yann E. MORIN [this message]
2013-01-03 8:40 ` Yann E. MORIN
2013-01-03 8:52 ` Jeremy Rosen
2013-01-03 8:53 ` Arnout Vandecappelle
2013-01-03 8:57 ` Thomas Petazzoni
2013-01-03 9:13 ` Yann E. MORIN
2013-01-03 10:30 ` Peter Korsgaard
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=201301031908.07247.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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