Attached to Project: CRUX-ARM
Opened by Victor Martinez - 2012-11-03
Last edited by Jose V Beneyto - 2013-11-02
Opened by Victor Martinez - 2012-11-03
Last edited by Jose V Beneyto - 2013-11-02
FS#42 - initrd miss ext3 and ext4 support.
Busybox lacks ext3 and ext4 support. Do we need to build util-linux and e2fsprogs statically and add them to initrd?
Another options?
well, it is a bit more complex but now it is possible to have ext3, ext4, and other filesystem format support
I tried that and worked just fine:
- put uImage, uInitrd, boot.scr, rootfs.tar.xz, modules.tar.xz and crux.media in a first partition of an SD card
- boot the efikamx (ramdisk option)
- after shell appeared and CRUX media is properly mounted:
# mount -o remount,rw /media
# mkdir /media/rootfs
# tar -C /media/rootfs -xpvf /media/crux-arm-rootfs-3.0-RC3-efikamx.tar.xz
# rmdir /mnt
# ln -s /media/rootfs /mnt
# setup-chroot
- once you're inside the new root you can use fdisk, cfdisk, mkfs* (ext2,ext3,ext4,reiserfs,xfs,jfs,etc. if you've the enough support in booted kernel)
implemented
initrd: https://crux-arm.nu/gitweb?p=initrd.git;a=commitdiff;h=908a5d6e0089b76fdb40a20bf7781035a2c92839
initramfs: https://crux-arm.nu/gitweb?p=initramfs.git;a=commitdiff;h=30f598126121c02261c74a3f8c7f4b74807cacbe