From: James J. Dines <jdines@jdines.net>
To: buildroot@busybox.net
Subject: [Buildroot] Why is extfs filesystem mandatory?
Date: Tue, 07 Sep 2010 13:42:47 -0400 [thread overview]
Message-ID: <4C867997.1050309@jdines.net> (raw)
In-Reply-To: <1283878421.11196.7.camel@dubciaranr1.verifone.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/07/2010 12:53 PM, Quotient Remainder wrote:
> Ar M?irt, 2010-09-07 ag 12:34 -0400, scr?obh James J. Dines:
>
>> In the menuconfig, under "Target Filesystems" I have an asterisk
>> surrounded by dashes, i.e.:
>>
>> - -*- ext2 root filesystem
>
> Do you have ISO9660 FS enabled by any chance?
>
> From the help for ext2:
> Selected by: BR2_TARGET_ROOTFS_ISO9660 && (BR2_i386 || BR2_x86_64) && BR2_LINUX_KERNEL
>
>
Yes, that was the issue. I have to admit I feel a bit foolish having
not looked more closely at the dependencies by choosong the help option,
but on the other hand I cannot imagine why this dependency exists.
Obviously one can have an iso image without having an ext2 filesystem,
or there would be no such thing as an iso image for Windows.
Or am I missing something?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMhnmWAAoJECSpOhdQESq67zsH/RobUwNThApVjeWikX29G9MK
qyS2Kiggg8c2DV6FKeOmwBPvDgTe1QxGnGdxAPG0SgWj+GPd2mVMiha7ZaGZR+tB
cEhtVBeTeDexelV8K+XLvTq3e6cLAVJ2uEuX7sc/L+P1aHlbgEdXc9MdTlUSnkic
xQ4CPX5MvrXyJXimGPipb7PUjS2u6g7rDCqhsrbFeN7B/nE1vlGDcxYCEeWRoi01
ww8KtcuaGPwKw/c5bKXEED42rkQoPQWeCvZdAZauH1IEJ6K8cIKxMft+xnBDMeDJ
/tdrhQLK1Q9scNqrTGEwZ/lwPrm8pL5VwxPZvPk9DH6g8eu0bvLK56V0Q7xJ6jQ=
=foEH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-09-07 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 13:23 [Buildroot] Why is extfs filesystem mandatory? James J. Dines
2010-09-07 14:55 ` Thomas Petazzoni
2010-09-07 16:34 ` James J. Dines
2010-09-07 16:53 ` Quotient Remainder
2010-09-07 17:42 ` James J. Dines [this message]
2010-09-07 19:03 ` Thomas Petazzoni
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=4C867997.1050309@jdines.net \
--to=jdines@jdines.net \
--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