Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] EXT2-fs error
Date: Wed, 15 Sep 2010 19:07:25 +0200	[thread overview]
Message-ID: <20100915190725.459aaca8@surf> (raw)
In-Reply-To: <SNT119-W19D1DBCD197B0F139037EA82790@phx.gbl>

Hello Johny,

On Wed, 15 Sep 2010 12:39:37 +0000
Johnny Beardsmore <jny0@hotmail.com> wrote:

> What does creating this file allow me to do (other than apply the
> previously mentioned e2fsck to it)?  I assume I'll still be
> transfering all the same stuff to the target, but do I also include
> this file, and if so, where should it be located? 

This file is the image of an ext2 filesystem, so you can just copy it
raw to a USB key or the partition of a USB key, and then just mount the
USB key. See 

I don't want to be/seem rude, but it seems you lack some really basic
embedded Linux knowledge. May I suggest to order and read a book such
as Building Embedded Linux Systems [1] ?

That would really help you understanding what is going on.

Also you are not explaining what you are trying to achieve *in the
end*. It might be that generating an ext2 filesystem image is totally
useless for what you're trying to do.

Regards,

Thomas

[1] http://oreilly.com/catalog/9780596529680
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-09-15 17:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01  9:35 [Buildroot] EXT2-fs error JNY
2010-09-01  9:53 ` Peter Korsgaard
2010-09-02 11:17   ` JNY
2010-09-03  5:56 ` Mitch Davis
2010-09-03  5:57   ` Mitch Davis
2010-09-07 16:58 ` JNY
2010-09-07 23:57   ` Mitch Davis
2010-09-08  8:31 ` JNY
2010-09-09 12:35   ` Johnny Beardsmore
2010-09-10 15:41     ` Johnny Beardsmore
2010-09-10 16:12       ` Johnny Beardsmore
2010-09-10 16:16       ` Yann E. MORIN
2010-09-13  7:51     ` Johnny Beardsmore
2010-09-13  8:20       ` Thomas Petazzoni
2010-09-13  8:45         ` Johnny Beardsmore
2010-09-13  9:22           ` Peter Korsgaard
2010-09-15 11:07             ` Johnny Beardsmore
2010-09-15 11:31               ` Thomas Petazzoni
2010-09-15 12:39                 ` Johnny Beardsmore
2010-09-15 13:28                   ` Malte Starostik
2010-09-15 17:07                   ` Thomas Petazzoni [this message]
2010-09-16  6:50                     ` Johnny Beardsmore
2010-09-16  7:01                       ` [Buildroot] FW: " Johnny Beardsmore
2010-09-16  8:51                       ` [Buildroot] " Ormund Williams
2010-09-16  9:21                         ` Johnny Beardsmore
     [not found]                           ` <AANLkTinbDS1nrt4b6TgctMwHArtwrX7_JSrzbeqxWCn=@mail.gmail.com>
2010-09-16 10:11                             ` Johnny Beardsmore
2010-09-16 10:14                               ` Mitch Davis
     [not found]                           ` <233D327176C4471A9A40B36BC1B4EB35@AP366>
2010-09-16 11:14                             ` Johnny Beardsmore
2010-09-16 11:57                               ` Mitch Davis

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=20100915190725.459aaca8@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