From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why is extfs filesystem mandatory?
Date: Tue, 7 Sep 2010 21:03:11 +0200 [thread overview]
Message-ID: <20100907210311.0bad86cd@surf> (raw)
In-Reply-To: <4C867997.1050309@jdines.net>
Hello,
On Tue, 07 Sep 2010 13:42:47 -0400
"James J. Dines" <jdines@jdines.net> wrote:
> 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.
Well, the ISO image is in fact a little bit more than just an ISO image
of the filesystem: it's a bootable ISO image, and the build process for
this image considers that the root filesystem is an ext2 initrd for the
ISO image.
From fs/iso9660/iso9660.mk :
cp $(GRUB_DIR)/stage2/stage2_eltorito
$(ISO9660_TARGET_DIR)/boot/grub/ cp $(ISO9660_BOOT_MENU)
$(ISO9660_TARGET_DIR)/boot/grub/menu.lst cp
$(LINUX26_IMAGE_PATH) $(ISO9660_TARGET_DIR)/kernel cp
$(BINARIES_DIR)/rootfs.ext2 $(ISO9660_TARGET_DIR)/initrd
I must admit that I'm not an user of this feature, so when I did the
cleanup/rewrite of filesystem support, I left it as it was. Maybe it
needs to work differently.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-09-07 19:03 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
2010-09-07 19:03 ` Thomas Petazzoni [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=20100907210311.0bad86cd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.