From: Rocky Bernstein <rocky.bernstein@...>
Date: 2009-01-29T22:57:27+09:00
Subject: [ruby-core:21668] Re: [Bug #1068] Ruby Cannot Handle Some UIDs

--0015175770b2df301304619f80b9
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Thu, Jan 29, 2009 at 8:33 AM, James Gray <james@grayproductions.net>wrote:

> On Jan 29, 2009, at 3:43 AM, Urabe Shyouhei wrote:
>
>  Ondrej Bilka wrote:
>>
>>> On Thu, Jan 29, 2009 at 08:53:38AM +0100, Nobuyoshi Nakada wrote:
>>>
>>>> Hi,
>>>>
>>>> At Thu, 29 Jan 2009 01:23:48 +0900,
>>>> Ondrej Bilka wrote in [ruby-core:21642]:
>>>>
>>>>> Any reason why not handle UID and GID as signed?
>>>>>
>>>> Because they are defined as unsigned on that platform.
>>>>
>>> This can be ignored. It would only display incrorectly UIDs > 2000000000
>>>
>>
>> Out of curiousity, on what basis you can believe that display (and ignore
>> your
>> header instead)?  I'd wather ignore that display and believe what header
>> says if I had such OS.
>>
>
> Well, the OS is using negative UID's.


I am not sure one can make that assertion. It could be another OS which uses
a signed uid  is reporting it (e.g. via NFS) to one which uses unsigned
uids.

 That's just a fact.  If we ignore that, then we know we are broken and that
> doesn't seem good.
>
> James Edward Gray II
>
>

--0015175770b2df301304619f80b9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Jan 29, 2009 at 8:33 AM, James G=
ray <span dir=3D"ltr">&lt;<a href=3D"mailto:james@grayproductions.net">jame=
s@grayproductions.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0=
pt 0.8ex; padding-left: 1ex;">
On Jan 29, 2009, at 3:43 AM, Urabe Shyouhei wrote:<br>
<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;">
Ondrej Bilka 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 Thu, Jan 29, 2009 at 08:53:38AM +0100, Nobuyoshi Nakada 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;">
Hi,<br>
<br>
At Thu, 29 Jan 2009 01:23:48 +0900,<br>
Ondrej Bilka wrote in [ruby-core:21642]:<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;">
Any reason why not handle UID and GID as signed?<br>
</blockquote>
Because they are defined as unsigned on that platform.<br>
</blockquote>
This can be ignored. It would only display incrorectly UIDs &gt; 2000000000=
<br>
</blockquote>
<br>
Out of curiousity, on what basis you can believe that display (and ignore y=
our<br>
header instead)? &nbsp;I&#39;d wather ignore that display and believe what =
header says if I had such OS.<br>
</blockquote>
<br>
Well, the OS is using negative UID&#39;s. </blockquote><div><br>I am not su=
re one can make that assertion. It could be another OS which uses a signed =
uid&nbsp; is reporting it (e.g. via NFS) to one which uses unsigned uids. <=
br>
<br></div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
 rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&nbsp;T=
hat&#39;s just a fact. &nbsp;If we ignore that, then we know we are broken =
and that doesn&#39;t seem good.<br>

<br>
James Edward Gray II<br>
<br>
</blockquote></div><br>

--0015175770b2df301304619f80b9--