<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 12, 2013, at 9:05 AM, Magnus <<a href="mailto:magnus@yonderway.com">magnus@yonderway.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 12, 2013, at 12:02 PM, Jim Klimov wrote:</div><blockquote type="cite"><div><font class="Apple-style-span"><br></font></div><div><font class="Apple-style-span"><br></font>I believe, 32-bit should be retained. While it is of little utility<br>for ZFS and other huge-RAM jobs, it may be required for some netbooks,<br>older hardware repurposed for tests and SOHO servers, as well as for<br>resource-constrained testing VMs. So I'd vouch for this fork/patch<br>approach if this upstream is still followed.</div></blockquote><br></div><div>Not to mention intriguing projects like <a href="http://wiki.illumos.org/display/illumos/Raspberry+Pi+Bring-Up">http://wiki.illumos.org/display/illumos/Raspberry+Pi+Bring-Up</a></div><br></div></blockquote><div><br></div>ARM11 is only 32-bit, and has nothing to do with the discussion of whether we would retain *x86* 32-bit mode support.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Garrett</div><div><br><blockquote type="cite">_______________________________________________<br>oi-dev mailing list<br><a href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>http://openindiana.org/mailman/listinfo/oi-dev</blockquote></div><br></body></html>