On Mon, Nov 17, 2008 at 02:47:14AM +0100, Henrik Theiling wrote: > 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). I agree. The piping possibility should not be compromised. However a -q switch that prevents all output to stderr unless an error has happened would be quite useful. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier --------------------------------------------------------------------- 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
