Hi Evan, I have one more question...
Since you are going to try to provide fixit strings for users, is there a way we can incorporate the ability to fix the error automatically for them in some cases? thank, sarah ***** > Hi Evan, > > A couple of comments/questions... > > -I assume the crux of the problem for BE error handling was the > inability to let users know what went wrong when we made calls to > other programs, such as installgrub? Your solution seems geared toward > that type of issue. > > -Are there issues with error codes for BE functions that need to be > addressed as well? The structure you have defined doesn't appear to > include BE error codes as part of its definition. Is there a need for > this as well, for more general BE errors that do not occur when > calling another program? > > thanks, > sarah > **** >> >> Here is the functional/design spec for the BE error and observability >> project. >> >> It's a first version and does include some design elements for what >> will eventually become the error handling and logging service for the >> Caiman Unified Design project. However this project is not intended >> to provide that error handling and logging but just the beginnings of >> it and the ability to mesh easily with it. >> >> I would like to get any comments by the end of the day on Friday (8/21). >> >> Thanks! >> -evan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
