[OpenAFS-devel] Proposal for capabilities support in Unix client
1.4.x
Derrick Brashear
shadow@gmail.com
Fri, 19 Jun 2009 21:49:06 -0400
--0016363108abae4e49046cbdd809
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On Fri, Jun 19, 2009 at 6:44 PM, Jason Edgecombe <jason@rampaginggeek.com>wrote:
> Marc Dionne wrote:
>
>> On Fri, Jun 19, 2009 at 12:43 PM, Ken Hornstein<kenh@cmf.nrl.navy.mil>
>> wrote:
>>
>>
>>> I think that historically, head and 1.5.x have simply scared
>>>> developers into using 1.4 as a base. I recall a period of close to a
>>>> year (maybe more) where head wouldn't even build on Linux when rxtcp
>>>> was in there, and 1.5 was usually not that much better.
>>>>
>>>>
>>> rxtcp was always on a branch; if you selected that branch, you should
>>> have
>>> known what you were getting in to.
>>>
>>> --Ken
>>>
>>>
>>
>> You're right that it wasn't rxtcp, I think it was
>> bringing-rx-into-21st-century-20060504 which was later taken out of
>> head with taking-rx-back-into-the-20th-century-20061228.
>>
>> My point was not the specific breakage (there were surely other things
>> as well), but more the fact that at least on Linux, head was not
>> buildable for quite a long time.
>>
>>
> Do the tinderbox test boxes help to alleviate this?
Yes, somewhat.
Any idea what's wrong with HPUX? Me either. Compiler SEGVing isn't really
something one can sensibly do something with.
--0016363108abae4e49046cbdd809
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Fri, Jun 19, 2009 at 6:44 PM, Jason E=
dgecombe <span dir=3D"ltr"><<a href=3D"mailto:jason@rampaginggeek.com">j=
ason@rampaginggeek.com</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt =
0pt 0.8ex; padding-left: 1ex;">
<div class=3D"im">Marc Dionne wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Jun 19, 2009 at 12:43 PM, Ken Hornstein<<a href=3D"mailto:kenh@c=
mf.nrl.navy.mil" target=3D"_blank">kenh@cmf.nrl.navy.mil</a>> wrote:<br>
=A0<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think that historically, head and 1.5.x have simply scared<br>
developers into using 1.4 as a base. =A0I recall a period of close to a<br>
year (maybe more) where head wouldn't even build on Linux when rxtcp<br=
>
was in there, and 1.5 was usually not that much better.<br>
=A0 =A0 =A0<br>
</blockquote>
rxtcp was always on a branch; if you selected that branch, you should have<=
br>
known what you were getting in to.<br>
<br>
--Ken<br>
=A0 =A0<br>
</blockquote>
<br>
You're right that it wasn't rxtcp, I think it was<br>
bringing-rx-into-21st-century-20060504 which was later taken out of<br>
head with taking-rx-back-into-the-20th-century-20061228.<br>
<br>
My point was not the specific breakage (there were surely other things<br>
as well), but more the fact that at least on Linux, head was not<br>
buildable for quite a long time.<br>
=A0<br>
</blockquote></div>
Do the tinderbox test boxes help to alleviate this?</blockquote><div><br>Ye=
s, somewhat.<br><br>Any idea what's wrong with HPUX? Me either. Compile=
r SEGVing isn't really something one can sensibly do something with. <b=
r>
</div></div><br>
--0016363108abae4e49046cbdd809--