Here is the workaround I came up with. Rather than try preseed, we can simply answer the questions at the time they are asked using debconf.
The EDITOR frontend essentially dumps the debconf array into a file, reads it back and uses the results to modify the debconf array.
So rather than even bother with the output it created for us, I just pass in the values I know/want to set - the rest will use defaults.
/root/test.sh would obviously be replaced by something a little more robust but it's good to illustrate the point.
Saves me writing a new Frontend, can re use an existing one.
Here is the workaround I came up with. Rather than try preseed, we can simply answer the questions at the time they are asked using debconf.
The EDITOR frontend essentially dumps the debconf array into a file, reads it back and uses the results to modify the debconf array.
So rather than even bother with the output it created for us, I just pass in the values I know/want to set - the rest will use defaults.
/root/test.sh would obviously be replaced by something a little more robust but it's good to illustrate the point.
Saves me writing a new Frontend, can re use an existing one.
root@gaz4:~# grep ldap /etc/pam. d/common- auth runtime/ profiles= "Unix authentication, LDAP Authentication" /root/test. sh DEBIAN_ FRONTEND= editor pam-auth-update d/common- auth
root@gaz4:~# cat test.sh
#!/bin/sh
cat > $1 <<EOF
libpam-
EOF
root@gaz4:~# EDITOR=
root@gaz4:~# grep ldap /etc/pam.
auth [success=1 default=ignore] pam_ldap.so use_first_pass
root@gaz4:~#