On Jan 14, 2012, at 12:27 AM, Bryan Kadzban wrote: > That text-format description is *much* easier for me to debug when I'm > seeing issues with it, than even a shell script that builds a directory > tree and runs cpio against it. (And certainly easier to debug than a > binary that builds a directory tree.) Of course the mkinitramfs shell > script that I have basically just echos this format through the program > from the kernel, so there's some shell involved. But it does feel > easier to edit.
I prefer to have it build a directory tree so I can throw things in there
willy-nilly, but the particular method LFS documents doesn't seem important to
me.
So long as the basic boot scripts can be copied between the main-boot and
initramfs-boot sequences there's not much "extra" to be done in terms of
maintaining an initramfs -- if you write a script to build a tree or a text
file that is used a spec to build a cpio archive or whatever, it's still
totally scriptable and doesn't change from build-to-build. In other words, the
maintenance load, both for LFS authors and LFS users is not very high.
Zach
smime.p7s
Description: S/MIME cryptographic signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
