From: John Dallaway <john@dallaway.org.uk>
To: "Carruth, Rusty" <RCarruth@Adtron.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: RedBoot 2.0.0 cannot find files on ext2 partitions formatted with mke2fs 1.41.3 from Ubuntu
Date: Wed, 29 Jul 2009 15:55:00 -0000 [thread overview]
Message-ID: <4A7070D3.1090507@dallaway.org.uk> (raw)
In-Reply-To: <9EFFCEC257D2B649BCD6495F5C704AA9085E15EF@sr-fre-exch01.smartm.internal>
Hi Rusty
Carruth, Rusty wrote:
> I have a problem with RedBoot - apparently Red Boot 2.0.0 can read ext2
> formatted filesystems if you use mke2fs 1.36, but not with mke2fs 1.41.3
> (from Ubuntu 8.10). (I get 'file not found', or something along those
> lines, when I try to boot with 1.41.3-formatted ext2 partition, but it
> works fine with 1.36-formatted ext2 partition. And I'm using a script
> which does simple 'mke2fs /dev/sda1' commands identically when building
> either 1.36-formatted or 1.41.3-formatted CF images).
Firstly, where did your RedBoot sources come from? The "2.0.0" version
string suggests that your RedBoot build is not from the official eCos
2.0 distribution.
> I looked all over the place for a 'revision history' for RedBoot (and
> eCos), but no joy.
Each eCos package has its own ChangeLog. The ChangeLog for RedBoot is
located within the eCos repository at:
packages/redboot/<version>/ChangeLog
You might also consider looking at the mke2fs ChangeLog to see what has
changed between 1.36 and 1.41.3.
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2009-07-29 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 15:18 [ECOS] " Carruth, Rusty
2009-07-29 15:55 ` John Dallaway [this message]
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=4A7070D3.1090507@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=RCarruth@Adtron.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).