* Cyril Brulebois [Thu Sep 25, 2014 at 12:32:22PM +0200]: > Michael Prokop <mika@debian.org> (2014-09-25): > > * Karsten Merker [Thu Sep 25, 2014 at 08:15:48AM +0200]: > > > Inside the /target chroot created by d-i, update-initramfs is by default > > > configured to run with "MODULES=dep" and gives only the following > > > modules on my armhf/sunxi test system: > > Hmpf, I so much am not a fan of this default "MODULES=dep" behaviour > > of d-i... > Can you please clarify? I see this in base-installer: > | if db_get base-installer/initramfs-tools/driver-policy && \ > | [ -z "$RET" ]; then > | # Get default for architecture > | db_get base-installer/kernel/linux/initramfs-tools/driver-policy > | db_set base-installer/initramfs-tools/driver-policy "$RET" > | fi > | db_settitle debian-installer/bootstrap-base/title > | db_input medium base-installer/initramfs-tools/driver-policy || true > | if ! db_go; then > | db_progress stop > | exit 10 > | fi > | > | db_get base-installer/initramfs-tools/driver-policy > | if [ "$RET" != most ]; then > | cat > $IT_CONFDIR/driver-policy <<EOF > | # Driver inclusion policy selected during installation > | # Note: this setting overrides the value set in the file > | # /etc/initramfs-tools/initramfs.conf > | MODULES=$RET > | EOF > | fi > Granted, no coffee yet. But I seem to recall that people having issues > with MODULES="dep" are those who actually selected it manually (e.g. > through expert install). I'm just not a friend of "MODULES=dep" as a default behaviour, good to know that d-i uses a sane default here. :) Thanks for verifying! > My local test confirms that a basic installation (netboot-gtk image on > amd64 using udebs from sid) leads to MODULES="most" in /target. I didn't > go further than the popcon prompt though. Excellent, then from my PoV there's nothing further to be done in i-t, since the default configuration works fine. regards, -mika-
Attachment:
signature.asc
Description: Digital signature