Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Huge update
Date: Fri, 7 Mar 2008 13:57:00 +1100	[thread overview]
Message-ID: <20080307025700.GA31483@cloud.net.au> (raw)
In-Reply-To: <46a136670803061710ka7f2c40u223e1348b1a04d21@mail.gmail.com>

On Thu, Mar 06, 2008 at 08:10:41PM -0500, John Voltz wrote:
>  > --- trunk/buildroot/scripts/build-ext3-img
>  (rev 0)
> > +++ trunk/buildroot/scripts/build-ext3-img    2008-03-06 17:52:37 UTC (rev
> 21176)
> 
> Why isn't this just a normal target? Or an option to the current ext2
> target?
> 
> I would like to do that once I find a good way to do it. It will create a
> bootable ext3 image with grub that can be run directly with qemu or vmware.

Right, I see that it's building a whole hard disk image rather than just
an ext3 file system image.

> The move to /usr/lib was partly because a few embedded systems have the root
> file system stored in a smallish flash device on the main board, sufficient

OK. I'm a bit concerned that we might have some binaries installed in
/bin or /sbin which need those libraries that moved.

Also we don't any targets (image generators) capable of generating
separate root and /usr images afaik. But they can be developed later.


Thanks for all your patches by the way. I don't mean to be a harsh
critic.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-03-07  2:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  1:10 [Buildroot] Huge update John Voltz
2008-03-07  2:57 ` Hamish Moffatt [this message]
2008-03-07  7:47 ` Ulf Samuelsson
  -- strict thread matches above, loose matches on Subject: below --
2008-03-07  0:04 John Voltz
2008-03-07  0:08 ` Hamish Moffatt
2008-03-06 19:16 John Voltz
2008-03-06 19:14 ` Erik Andersen
2008-03-06 20:52 ` JS
2008-03-06 23:44 ` Ulf Samuelsson
2008-03-07  8:21 ` Hans-Christian Egtvedt

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=20080307025700.GA31483@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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