On 05-02-2025 16:02, Rolf M. Dietze wrote:

[..]
- sparc port of OI (why was sparc removed anyway?)

Because we do not have enough developers, we have no equipment to test with, old SPARC systems are way too slow (20-30 minutes of illumos gate build versus 4-5 or more hours). In short, we should be looking into the future (get ARM64 going) and not into the past. ARM64 systems are very affordable now, SPARC? why one should get rack server in their flat? It is great if there are some people willing to play around with SPARC bits (I myself do like SPARC very much), but …

so OI is focused only on desktop?

No, OI is the server part PLUS desktop. We use single image OI for
both our desktops and servers for various purposes.

Actually solaris based systems are
as far as I know, the only systems that support generic windows acl
from the zfs base via nfsv4 to the windows box. I do like to have an OI
zfs fileserver for windows desktops that supports real acls.

OI supports real ACLs because it builds on stock illumos.

And for the sparc systems, there is nothing that stable as sparc
hardware. and obp on it is far more comfortable as this BIOS stuff.
one doen't realy have a text console on off the shelf BIOS boxes
Used sparc T2 boxes are damm cheap to get if one isn't just giving
them out nothing


We dumped our sparcs 25 years ago because already then they were a
factor of 6 too slow compared to the then recent DEC hardware (ES40),
which was superseeded by even faster Sun x86 machines (Blade 8000).
Cannot comprehend why anyone would stick to SPARC today except for
computer museum show cases ...

--
Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMKASF-SAT
https://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology          https://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to