Hi! Till Maas writes: > attached is a patch that makes cryptsetup write "Command successful" to > stdout instead of stderr. Normally only error or debug messages go to > stderr imho, therefore it fits better to stdout. I disagree: all status messages should go to stderr, because stdout should be reserved for carrying application output. This way, you can use programs in a unix pipe to pass application output to the next application while still a) being able to read all messages, b) avoiding contamination of the stdout stream with messages. Now, cryptsetup does not seem to write application data (yet), but it can read the key files from stdin. Imagine the chaos if the source application contaminated that stream with messages. There should be a clear distinction between application data (stdout) and user messages (stderr). **Henrik --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
