G'day Jim, On Fri, 6 Feb 2004, Jim Sibley wrote:
> Is it that the boot record has to be > updated by zipl to get to the new initrd module? Yes. As I understand it, it goes like this... When you ran mkinitrd, what's happened on the disk is that a new file to contain your initrd has been allocated from free space on the disk, and the space used by the old file with the old initrd is returned to free space *with the data still in place*. So, without re-running zipl, you are actually still pointing at the old initrd. If you had one of those filesystems that scrub deleted files from the disk, or you wrote something else to your disk that happened to drop into the space your old initrd was, you would have had an un-IPLable system at that point. Re-running zipl updates the pointers in the IPL block that point to where the new initrd is located on the disk. Hoo-roo, Vic Cross
