[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

multistrap rootfs with initramfs



I'm looking at using multistrap to create a rootfs that can be passed to
a linux build for an initramfs.

Is it feasible to create a linux image with an initramfs based on a
multistrap rootfs ??
Is there a size limitation with initramfs images ??  Could it be 32MB or
64MB or even larger ??

Do people do this already ??

Is emsecondstage still relevant with multistrap ??
Is booting into a multistrap rootfs possible.
The multistrap page on wiki says the rootfs just needs to be mounted (or
chrooted) and configured with "dpkg --configure -a"

Looks like multistrap does not create:
    /dev entries.
    /etc/inittab
    /etc/fstab
    /etc/hosts
    /etc/securetty
    /etc/modules
    /etc/hostname
    /etc/network/interfaces

multistrap rootfs could be put into cpio.gz archive and set in linux
config, or linux config could just point to the multistrap rootfs
directory and the linux build will create the cpio.gz.

The disadvantage of doing the cpio.gz manually is that it has to be
complete, where as specifying a directory allows specifying multiple
directories and control files and the build system will aggregate things.
Also, the initramfs control files can be used to build /dev entries, and
create directories and files with the correct permissions, uid and gid.
Not sure which is better -- it may be just a case of "6 of one -- half a
dozen of the other"

One issue is that I do prefer not to build as root, even via sudo. 
Either fakeroot or initramfs control files are required to ensure the
files have the correct permissions, uids and gids.

Any thoughts about using initramfs with a multistrap rootfs ??

If there are size restrictions, then two possibly two rootfs could be
built -- a small one with enough to boot (eg. /bin /lib /etc /root ...)
and a larger one to mount along side (or over the top) with all the
other apps.

Brendan.


Reply to: