>>> On 2/18/2009 at 3:03 PM, Ivan Warren <[email protected]> wrote:
> Why doesn't mkinitrd *ONLY* take care of the IPL > volume (or volumes in you're LVM).. - as the initrd was designed - then > - depending on what config is on the root fs, enable this or that volume > - once control has been passed to the root fs hosted init (and the > pivotroot() has been done) ? That's is all that's necessary. And, again, if you make sure that when DASD volumes are added, that the proper configuration files are there, it should work just fine. However, consider the case where / is on an LV, and you just added another volume to the VG. That's big time trouble. So, to try to be on the safe side, the SUSE folks have apparently decided to err on the side of caution. Any active DASD volumes at the time mkinitrd is run get added to the initrd. If you add DASD via YaST, that all gets done for you, and you don't have to worry about it. If you do it manually, you better know what you're doing, either in the setup, or the recovery effort. :) Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
