[illumos-Developer] Establishing requirements and test cases for tail replacement
Joerg Schilling
Joerg.Schilling at fokus.fraunhofer.de
Mon Sep 6 16:20:55 PDT 2010
"Garrett D'Amore" <garrett at damore.org> wrote:
> On Mon, 2010-09-06 at 13:59 +0200, Joerg Schilling wrote:
>
> >
> > > The Solaris tail(1) manpage specifies LANG, LC_ALL, LC_CTYPE as affecting its behavior. I see no evidence that the FreeBSD code deals with this issue and I'm going to plead some level of ignorance here as a US developer who has never dealt with anything other than the default POSIX locale.
> >
> > If you cannot do full tests (including non-US locales), I would vote against an
> > integration. Tail rewinds by a known byte offset and then e.g. needs to be able to
> > synchronize again on multi byte characters.
> >
> > This is an essential feature that needs to be tested.
> >
> > BTW: Doing this correctly even on stateful locales could forbid to use lseek(2)
> > at all.
>
>
> A quick note: We have an urgent need to replace some closed code. Its
> likely that there will be some regressions in functionality. If you
> want to help prevent these, then please get involved *constructively*.
This is why I wrote the previous mails, I am trying to help. If you are
interested in constructive help, you are welcome.
Jörg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
More information about the Developer
mailing list