Matt Zimmerman <[EMAIL PROTECTED]> writes: > There is no explicit rule in policy about the interactivity of init scripts > (you can check this yourself), but I would consider it to be in very poor > taste unless the stability of the system is at stake (e.g., manual fsck).
There is the potential of data loss which is why this particular package is so sensitive about what to do when it starts up. I've discussed with upstream, and I think I've found a reasonable solution to make it be non-interactive by default. I'll be uploading a new package shortly, and then commenting in the README.Debian file the reasons behind my change. One question I have however, is should it be a policy violation if a script hangs waiting for user input? Perhaps the policy document should be updated to explicitly deal with this case? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
