On Wed, 15 Aug 2012 12:09:24 -0400 (EDT), Mark Post wrote: > On 8/14/2012 at 10:22 PM, Stephen Powell <zlinux...@wowway.com> wrote: >> But getting to the root of the problem, whenever you delete >> a DASD device you need to re-build your initial RAM file system, >> then run zipl. Running zipl, by itself, is not enough. The >> list of DASD devices to be brought online is included in the >> initial RAM file system, and bringing the devices online, >> obviously, must occur before the permanent root file system >> is mounted. Of course, the same holds true for adding a DASD >> device. If you have multiple kernels installed, the initial >> RAM file system must be built separately for each kernel > > Assuming that the DASD device was added/removed correctly, > this is only true if the DASD device is part of your root > file system. That is, for SLES10 the > /etc/sysconfig/hardware/hwcfg-dasd* file was added/removed, > and for SLES11, the /etc/udev/rules.d/51-dasd* file. Only > the devices that make up your root file system are initialized > in the initrd. Everything else is done after init starts.
Perhaps the way this is handled is distribution-dependent. In the versions of Debian that I'm familiar with, all DASD devices are brought online (not mounted, but brought online) while the initial RAM file system is still mounted as the root file system. -- .''`. Stephen Powell : :' : `. `'` `- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
