From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] jffs2 multiple partition
Date: Thu, 26 Nov 2009 16:13:13 +0100 [thread overview]
Message-ID: <20091126161313.57866352@surf> (raw)
In-Reply-To: <87y6lt8i9z.fsf@macbook.be.48ers.dk>
Le Thu, 26 Nov 2009 15:36:40 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> The question is how to generalize this and make is simple to
> use/understand. My initial feeling is that for something as
> specialized as this we should just make it easy to do outside BR
> (like we do with the tarball target), instead of add a lot of
> complexity to BR/Kconfig.
Same opinion here. The feature ? put /usr in one filesystem and the rest
in another filesystem ? is very, very specific. Unless we find a way to
make it more generally useful, I don't think this belongs to Buildroot.
We could imagine that the user can give a text file saying which
file/directory should go in which filesystem, so that parts could be
put into a read-only filesystem and other parts into a read/write
filesystem. But I'm not sure how this would work.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-11-26 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:08 [Buildroot] jffs2 multiple partition Jonathan dumaresq
2009-11-25 16:44 ` Michael S. Zick
2009-11-25 16:55 ` Jonathan dumaresq
2009-11-25 21:25 ` Thomas Petazzoni
2009-11-26 14:30 ` Jonathan dumaresq
2009-11-26 14:36 ` Peter Korsgaard
2009-11-26 15:06 ` Jonathan dumaresq
2009-11-26 15:13 ` Thomas Petazzoni [this message]
2009-11-26 16:45 ` Jonathan dumaresq
2009-11-26 17:03 ` Michael S. Zick
2009-11-26 18:38 ` 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=20091126161313.57866352@surf \
--to=thomas.petazzoni@free-electrons.com \
--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