[osol-discuss] Re: Real work needs to be done Was: Re:

2006-09-07 Thread James C. Cotillier
The core problem appears to be that Joerg did not get a response at all. With regard to this comment in an earlier post: >Maybe, it was the same reason, why I did not get an answer on the >question why something simple like fnmatch.c from libc is still not >available as source. a boilerplate res

[osol-discuss] Re: Real work needs to be done Was: Re:

2006-09-07 Thread James C. Cotillier
[b]As an aside:[/b] > > I think that's flawed. There is no way to determine > what licenses may > or may not apply to a given bit of source code by > looking at the > object file produced. > This may be true for Sun for Solaris, and true for other UNIX vendors generally, but it is not universa

Re: [osol-discuss] Re: Real work needs to be done Was: Re:

2006-09-07 Thread Casper . Dik
>a boilerplate response could have been made, of the form > >" [is |are] entwined with encumbered code, and certain >agreements are in place that would be repudiated if Sun were to discuss any instant details in a public forum" We're not allowed to name and shame. So that's all we can say "we

Re: [osol-discuss] Re: Real work needs to be done Was: Re:

2006-09-07 Thread James Carlson
James C. Cotillier writes: > This may be true for Sun for Solaris, and true for other UNIX > vendors generally, but it is not universally so. > > Another large vendor, in a very large OS, has since 1964 had > the standard of placing such information in human-readable > characters at the start of e

Re: [osol-discuss] Re: Real work needs to be done Was: Re:

2006-09-07 Thread Rich Teer
On Thu, 7 Sep 2006, James Carlson wrote: > In other words, if you want the answer as to what the specific > restriction might be, I'm afraid we can't divulge that, and even if we > could, it likely would do you no amount of good. "Can't" is all we > can say. One wonders at the stupidity of compa

i18n libc bits [was Re: [osol-discuss] Re: Real work needs to be done Was: Re:]

2006-09-07 Thread James Carlson
Rich Teer writes: > If the original writer of the code doesn't want their code released, > that's their right and that's OK, but it would sure be nice if they > would allow their identity and reasons to be known. After all, what > have they got to lose? Their code is still kept secret. Welcome t

Re: i18n libc bits [was Re: [osol-discuss] Re: Real work needs to be done Was: Re:]

2006-09-07 Thread Rich Teer
On Thu, 7 Sep 2006, James Carlson wrote: > Welcome to the world of contracts. > > I'm not saying I'm thrilled with the answer, but just that there isn't > another one. No matter how urgently or nicely you ask. :-/ Indeed. :-( > A productive place to take this conversation would be a proposal

Re: i18n libc bits [was Re: [osol-discuss] Re: Real work needs to be done Was: Re:]

2006-09-07 Thread James C. McPherson
Rich Teer wrote: On Thu, 7 Sep 2006, James Carlson wrote: Welcome to the world of contracts. I'm not saying I'm thrilled with the answer, but just that there isn't another one. No matter how urgently or nicely you ask. :-/ Indeed. :-( A productive place to take this conversation would be a

Re: i18n libc bits [was Re: [osol-discuss] Re: Real work needs to be done Was: Re:]

2006-09-07 Thread Dave Miner
Rich Teer wrote: On Thu, 7 Sep 2006, James Carlson wrote: ... not encumbered. I can't ... but perhaps there's someone interested who can. Why can't you make such a proposal?* You (and all other Sun engineers) are just as much of our community as anyone else, so in principle there should be