Package: initramfs-tools Version: 0.97 "softdep" modules are not included in the initial RAM file system when MODULES=dep is specified. Here's an example from the s390 architecture:
/etc/modprobe.d/dasd.conf: options dasd_mod dasd=0.0.0200(diag),0.0.0201,0.0.0202-0.0.0203(diag) softdep dasd_eckd_mod pre: dasd_diag_mod softdep dasd_fba_mod pre: dasd_diag_mod (/etc/modprobe.conf does *not* exist) /etc/initramfs-tools/conf.d/driver-policy: MODULES=dep /etc/initramfs-tools/modules: (dasd_diag_mod is *not* listed) dasd_eckd_mod is included in the initial RAM file system. I assume that that is due to matching on the alias "ccw:t3990m*dt3390dm*". dasd_mod is also included in the initial RAM file system. I presume that that is due to the fact that dasd_mod is a hard dependency of dasd_eckd_mod. But dasd_diag_mod is *not* included in the initial RAM file system, even though it is listed as a soft dependency of dasd_eckd_mod, which has already been selected for inclusion. On the system above, this prevents the system from booting, as the devices marked for use with the diag driver, including the root file system in this case, cannot be brought online. Therefore, the permanent root file system cannot be mounted. I am able to circumvent the problem by explicitly listing dasd_diag_mod in /etc/initramfs-tools/modules, but this should not be necessary. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/922649436.38679.1278600800110.javamail.r...@md01.wow.synacor.com
