Re: Generic errno which can be mapped to custom user error

["Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>]

Hi

On Fri, Mar 7, 2008 at 4:35 PM, Manish Katiyar <mkatiyar@xxxxxxxxx> wrote:
> Hi,
>
>  As more applications are getting developed on linux shouldn't we have
>  a generic user errno ( similar to SIGUSR{1,2} ) which the user can use
>  to map his own custom error.

The problem is, purely my opinion, how many more we should add? This
doesn't mean I am trying to offend your idea, Manish. In fact, if we
have "plenty of room" for errno and user space can adapt such a fast
change, maybe that won't be a problem.

This kind of problem is similar to question: should it become syscall
or not? Should we change existing syscall parameters composition or
not? This might or might not introduce new problem.

My take on this situation: fix user space application so it can
"interpret" the real reason why a trouble happened. OK, it might cause
more headache....but this way we don't need to push libc and/or kernel
to adapt...which is...as you know....hard to dictate the way we
wanted.

Over all, this is just my opinion, so you may agree or disagree with it.

regards,

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ