On 05/31/17 10:30 AM, Richard L. Hamilton wrote:
On May 31, 2017, at 13:01, Alan Coopersmith wrote:
On 05/31/17 09:43 AM, Richard L. Hamilton wrote:
The alternative would be a large times analog of large file support; why that
wasn't done when 64-bit began, I
> On May 31, 2017, at 13:01, Alan Coopersmith
> wrote:
>
> On 05/31/17 09:43 AM, Richard L. Hamilton wrote:
>> The alternative would be a large times analog of large file support; why
>> that wasn't done when 64-bit began, I don't understand. :-)
>
> It was
On 05/31/17 09:43 AM, Richard L. Hamilton wrote:
The alternative would be a large times analog of large file support; why that
wasn't done when 64-bit began, I don't understand. :-)
It was considered at Sun in the late 90's but discarded as going full LP64
already provided a solution without
> On May 31, 2017, at 12:32, Alan Coopersmith
> wrote:
>
> On 05/31/17 09:19 AM, Richard L. Hamilton wrote:
>> Aside from executables that reference timestamps (given that a signed
>> twos-complement will overflow after Tue Jan 19 03:14:07 2038 GMT), and for
>>
On 05/31/17 09:19 AM, Richard L. Hamilton wrote:
Aside from executables that reference timestamps (given that a signed
twos-complement will overflow after Tue Jan 19 03:14:07 2038 GMT), and for
programs that will never need to manipulate files larger than 2GiB-1 (unless
they use large file
> On May 26, 2017, at 12:01, Alan Coopersmith
> wrote:
>
> On 05/26/17 04:26 AM, Harry Putnam wrote:
>> Jonathan Adams writes:
>>
>>> Much better than the Linux "file 'which file'" (with back ticks) ...
>>>
>>
>> sudo file `which file`
Alan Coopersmith writes:
> On 05/26/17 11:34 AM, Harry Putnam wrote:
>> Alan Coopersmith writes:
>>
>>> For the one I work on (not OI, but "Big Red"), we've been making
>>> this conversion across 5+ years now, and are >90% done in our
On 05/26/17 11:34 AM, Harry Putnam wrote:
Alan Coopersmith writes:
For the one I work on (not OI, but "Big Red"), we've been making
this conversion across 5+ years now, and are >90% done in our
development trunk, though much less done in what's been released so
Alan Coopersmith writes:
> For the one I work on (not OI, but "Big Red"), we've been making
> this conversion across 5+ years now, and are >90% done in our
> development trunk, though much less done in what's been released so
> far. I've written far more about the
>
>
> Jonathan Adams writes:
>
> > Much better than the Linux "file 'which file'" (with back ticks) ...
> >
>
>
> sudo file `which file`
> /usr/bin/file: ELF 32-bit LSB executable 80386 Version 1, dynamically
> linked, not stripped, no debugging information available
>
>
On 05/26/17 04:26 AM, Harry Putnam wrote:
Jonathan Adams writes:
Much better than the Linux "file 'which file'" (with back ticks) ...
sudo file `which file`
/usr/bin/file: ELF 32-bit LSB executable 80386 Version 1, dynamically
linked, not stripped, no debugging
On 05/25/17 23:10, Harry Putnam wrote:
How can quickly tell what bit my Hipster 2017.04 is?
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
I remember this from
On 05/25/17 11:18 PM, Alan Coopersmith wrote:
> On 05/25/17 02:13 PM, Will Brokenbourgh wrote:
>> On 05/25/17 14:10, Harry Putnam wrote:
>>> How can quickly tell what bit my Hipster 2017.04 is?
>>
>> Have you tried:
>>
>> uname -a
>
> The Solaris/openSolaris/illumos kernel doesn't change any of
Alan Coopersmith writes:
> On 05/25/17 02:10 PM, Harry Putnam wrote:
>> How can quickly tell what bit my Hipster 2017.04 is?
>
> "isainfo -kv" will tell you which kernel is running.
>
And so it does... thanks:
sudo isainfo -kv
64-bit amd64 kernel modules
---
Much better than the Linux "file 'which file'" (with back ticks) ...
On 25 May 2017 22:21, "jason matthews" wrote:
>
>
> On 5/25/17 2:17 PM, Alan Coopersmith wrote:
>
>> "isainfo -kv" will tell you which kernel is running.
>>
>
> winner winner chicken dinner.
>
> isainfo is
On 5/25/17 2:17 PM, Alan Coopersmith wrote:
"isainfo -kv" will tell you which kernel is running.
winner winner chicken dinner.
isainfo is the most elegant way i know of.
j.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
On 05/25/17 02:13 PM, Will Brokenbourgh wrote:
On 05/25/17 14:10, Harry Putnam wrote:
How can quickly tell what bit my Hipster 2017.04 is?
Have you tried:
uname -a
The Solaris/openSolaris/illumos kernel doesn't change any of the values
in uname between 32 & 64-bit kernels, much to the
On 05/25/17 02:10 PM, Harry Putnam wrote:
How can quickly tell what bit my Hipster 2017.04 is?
"isainfo -kv" will tell you which kernel is running.
-alan-
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
On 05/25/17 14:10, Harry Putnam wrote:
How can quickly tell what bit my Hipster 2017.04 is?
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Have you tried:
uname
19 matches
Mail list logo