From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8806] Buildroot 2016.2 for Raspberry Pi requires that ext4 rootfs is selected. Otherwise the error is reported
Date: Wed, 16 Mar 2016 21:13:04 +0000 [thread overview]
Message-ID: <bug-8806-163-D2GhrIvULN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8806-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8806
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
What do you suggest we do? If you change the defconfig (E.G. to use initramfs
instead of ext4) then it is also your responsibility to ensure it makes sense.
The raspberrypi post-image script creates as sdcard image with the ext4
filesystem the defconfig enables, so if you don't want that - Then just remove
the post-image script from the .config.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-03-16 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:23 [Buildroot] [Bug 8806] New: Buildroot 2016.2 for Raspberry Pi requires that ext4 rootfs is selected. Otherwise the error is reported bugzilla at busybox.net
2016-03-16 21:13 ` bugzilla at busybox.net [this message]
2016-03-16 21:25 ` [Buildroot] [Bug 8806] " bugzilla at busybox.net
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=bug-8806-163-D2GhrIvULN@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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