> We are going to follow the path which was chosen by Oracle in
> userland-gate.
> Basic macroses are not touched. Compilers still produce 32-bit binaries by
> default. 64-bit binaries are produced when necessary and delivered in
> /usr/bin
> if 32-bit binaries are not present. We'd like to avoid d
Aurélien Larcher писал 23.01.2016 21:20:
We are going to follow the path which was chosen by Oracle in
userland-gate.
Basic macroses are not touched. Compilers still produce 32-bit
binaries by
default. 64-bit binaries are produced when necessary and delivered in
/usr/bin
if 32-bit binaries are
Hello,
> Why not deliver amd64 bits in /usr/bin ? If we deliver them in
> /usr/bin/amd64, they are not in default PATH,
> and we have to use isaexec. I don't see good reason for this. We can
> deliver them in /usr/bin/amd64 and hardlinks
> in /usr/bin, but I don't see benefits from doing this.
>
Hoping a few here may have experience with this hardware and can speak
from experience about installing OI and using as a home NAS.
My skill level is weak but I have done something very similar on one
previous occasion. (With plenty of help from this list)
Am I likely to be walking into known hea
First of all, I have several 32-bit computers in production, and I
would like to be able to install and run OpenIndiana on them, but I
cannot demand that anyone donate his time to accommodate my wishes.
I mention this only if the volunteers are curious to know whether
anyone would use 32-bit OpenI
