[BusyBox] [PATCH] kill error message

[Rob Landley]

On Wednesday 17 August 2005 03:14, Vladimir N. Oleynik wrote:
> Rob,
>
> >>But uclibc support register_printf_function().
> >>If add to busybox autoconfigure for check "%m" or not,
> >>we can use this code (tested):
> >
> > I seldom manage to understand what you're actually saying, but I are you
> > suggesting busybox start using autoconf?
>
> Require long time ago. ;-)

Yeah, but we didn't do it and I'd rather not add this for 1.1 because we've 
got a full plate as it is.  For right now, let's make a decision one way or 
another: either we require %m support or we never use it.  (I suspect the 
first.)  And then document it.  (You'll notice that for 1.01 I rewrote the 
README, and it now has a portability section.  That's big enough that it 
should probably be broken out, and possibly grow a few notes about "look, we 
don't cause kernel panics -- if you've got one it's a kernel problem.  That's 
why it says kernel panic" and so on.  Techie FAQ.

> >>Do you really like show the double "kill" word?
> >
> > Not really, no.
>
> My local ash version outdated.
> Only hands patch for bash-like errors message:
> ash: kill: (pid) - Operation not permitted
>
> Please change exvwarning() to new:

Ok, what's the difference between exvwarning() and the bb_perror stuff?  (Why 
the duplication?)

Could you submit that as a patch against current SVN?

Rob