On Friday 03 March 2006 13:18, Lee Revell wrote: > On Fri, 2006-03-03 at 12:02 +0200, Sampo Savolainen wrote: > > Quoting Lee Revell <rlrevell@xxxxxxxxxxx>: > > > On Fri, 2006-03-03 at 11:33 +0200, Sampo Savolainen wrote: > > > > Quoting Clemens Ladisch <clemens@xxxxxxxxxx>: > > > > > Lee A. Azzarello wrote: > > > > > > ----- Clemens Ladisch <clemens@xxxxxxxxxx> wrote: > > > > > > cannot submit datapipe for urb 4, err = -28 > > > > > > > > > > 28 = ENOSPC (not enough bandwidth) > > > > > > > > Why doesn't jack tell the user this, why did Clemens need to > > > > post on > > > > > > LAU to ask? > > > > > > These are standard, well known error codes, > > > see /usr/include/linux/errno.h > > > > So, instead of interpreting them to users the software should say: > > "learn C headers and read errno.h?". Gah. > > > > Good software tells the users what's really wrong and directs the > > user in how to fix the issue. This leads to happier users and less > > repeated "why doesn't this work" questions on mailing lists, irc, > > personal email, etc. > > We don't KNOW what's wrong beyond "not enough bandwidth". > > Lee Then why not report "not engouh bandwidth" to the user?
