[OpenWrt-Devel] Firmware without SquashFS (initramfs + overlay)
sgparry at mainscreen.com
Sat Aug 23 16:30:20 EDT 2014
The thing that makes my blood boil is this - there are plenty of use
cases where initramfs is a must:
- ELF boot from external media
- KEXEC to external media
- TFTP boot
None of these currently work in BB whereas they used to. And you cannot
easily add the scripts to support them because all the 'hookability' is
outside of process id 1. This means when you try switch_root it blows up
in your face. If you try pivot_root it fails cause you can't pivot_root
ramfs. I have raised a bug - but no response yet. I have also submitted
a small patch which was bounced?
P.S. Sorry for first post without subject - noob error.
On 22/08/14 08:21, openwrt-devel-request at lists.openwrt.org wrote:
> Message: 3 Date: Thu, 21 Aug 2014 21:33:15 +0200 From: Rafa? Mi?ecki
> <zajec5 at gmail.com> To: Hauke Mehrtens <hauke at hauke-m.de> Cc: OpenWrt
> Development List <openwrt-devel at lists.openwrt.org> Subject: Re:
> [OpenWrt-Devel] Firmware without SquashFS (initramfs + overlay)
> <CACna6rxub8Qm3-u3p-kB4gdX-sn-Hb6dnKHa3WFkHJrg1eaOiA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8 On 20 August 2014 23:22, Hauke
> Mehrtens <hauke at hauke-m.de> wrote:
>> > You want to use initramfs because the SquashFS image is booting very
>> > unreliable or are there any other reasons?
> Because firmware with SquashFS boot in unreliable :|
>> > This boot problems seams to be in the boot loader. The boot loader
>> > should not see a difference between an initramfs and a SquashFS image,
>> > could it be that the boot loader does not like small images or not
>> > aligned images?
> Could be some timing issue in OpenWrt as well. No idea how to debug that.
> -- Rafa?
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel