On Wed, Dec 26, 2012 at 9:09 AM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Wed, 26 Dec 2012 07:58:34 -0800, Mark Knecht wrote:
> >> 2) Contained executables, as I understand them, either need to be >> built with the static flag or you have to include all the libraries. >> Static seems simpler so (in my case) should I rebuild mdadm & >> e2fsprogs with +static? (I don't currently use lvm or any crypt stuff) > > Yes. > <SNIP> I've done that, played a bit with ldd to see the changes, etc., and it seems to make sense. On the mdadm list one comment came up which was to make sure my mdadm.conf file was up to date and then include it in the initramfs image so that if for some reason the machine doesn't boot I have all the info required to start the RAIDs by hand. I thought that was a good comment. > > Most of it is debug stuff that I haven't used since I first started using > it. OK, it's a good example of a more complete init script so that's helpful. Thanks! One other question came up. So I build the kernel, and the kernel build creates the initramfs image and embeds it in the kernel. Is there a tool that would allow me to query the embedded image prior to booting so that I can check that everything is in there that I think should be in there? Scanning around online I found discussion about lsinitramfs but I haven't found it in portage yet. dracut has lsinitrd. genkernel doesn't have anything like it. And even if I found it I think it only works for stand alone initramfs files. Thanks, Mark
