"You know how the Debian packages, unlike Redhat packages, are allowed to interact with the console during installation. Argh. What a horrible idea. It's just like fsck asking if you want to reset inode 118182. Well? Do I?"
Mod quote up. As to the response that you can force Debian to answer Y, I request feedback that such is really true. 5 years ago, on whatever stable was back then (sid-1?), I spent literally many hours attempting such, figuring out which aspects of my install kernel cmdline I had to sacrifice due to character limits, in order to place the things there that alleged to achieve this 'force Y' mode. What I discovered, is that with 2 major avenues taken to try this, there were _still_ half a dozen packages that managed to thwart my attempt at a fully automated install. Eventually I managed to preseed, _explicitly_ the problem questions that affected my single case installset. But I never did find a solution to achieve this mythical 'force Y(thus allowing fully automated install)' mode. Now, I presume the half dozen I ran across were just packaging bugs, doing off-policy things. I hope to hear that in the last 5 years things are better. But it did strike me that I never had that problem with fedora/rh and kickstart, because of what I presumed to be a key differentiation between the rpm/dpkg world. Though note, I had run across some corporate annoying rpm which would use post-scripts to go unavoidably interactive. But I never ran into that with any typical routine stock fedora/rh installset (or in fact any installset I ever tried, which is a fair number).