While reading portmap's postinst, I noticed that it calculates a value for portmap_changed, then if the portmap configuration was changed, uses rpcinfo to check for services using the portmapper. Seems to me this is unnecessary for new installs; portmap will not be running before the postinst gets to this point, so obviously no services are using portmap on a new install. So this problem could be avoided by changing line 104 of the postinst to: if [ -n "$2" ] && [ "$portmap_changed" -eq 1 ] ; then That's probably not the whole story for this issue in d-i. To address the underlying issue in d-i, it seems we should bring up the loopback interface, probably in netcfg. -- see shy jo
Attachment:
signature.asc
Description: Digital signature