<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt">Hello,<br><br>Just so we can tack up a goal for the visionaries who like roadmaps and such...<br><br>Proposed list of 'core' updates for oi_151a(8-9):<br><br>* Bump illumos to 19e11862653b <br> Implement accept4()<br> stack overflow due to zfs lz4 compression<br> Fast reboot support in ixgbe<br> Chelsio 10GbE driver support<br> Support LSI SAS2008 (Falcon) Skinny FW for mr_sas(7D)<br> Allow ixgbe to use unsupported SFP modules<br> detect socket type of newer AMD CPUs<br>* New JDS package updates
(2013-04-09)<br> from: http://pkg.opensolaris.cz/osol/en/index.shtml<br>* Wifi Stack improvement patches (enrico)<br><br>Hope that helped,<br>Ken Mays<br><div><span><br></span></div><div><br></div> <div style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Andrzej Szeszo <aszeszo@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> OpenIndiana Developer mailing list <oi-dev@openindiana.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, May 12, 2013 7:11 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [oi-dev] OI project reboot required<br> </font> </div> <div class="y_msg_container"><br><div
id="yiv6103471111"><div dir="ltr">Hi Piotr<div><br></div><div style="">I made some choices without consulting anyone but it allowed me to get something set up in a short period of time.</div><div style=""><br></div><div style=""><span style="font-family:arial, sans-serif;font-size:13px;">oi_151a8 is based on </span><span style="font-family:arial, sans-serif;font-size:13px;">sfw-gate, that's correct. Milan built JDS against </span><span style="font-family:arial, sans-serif;font-size:13px;">oi_151a8. Because </span><span style="font-family:arial, sans-serif;font-size:13px;">oi_151a8 and JDS bits were already available I thought it would be a shame to not to include them in the repo I was preparing.</span><br>
</div><div style=""><span style="font-family:arial, sans-serif;font-size:13px;"><br></span></div><div style=""><span style="font-family:arial, sans-serif;font-size:13px;">/experimental, </span><span style="font-family:arial, sans-serif;font-size:13px;">oi-build, illumos-userland didn't really took off. I know they exist but it would take time to figure out in what shape the binary package repos are. I thought it would be a better idea to start fresh in terms of binary packages. Build recipes however we should reuse. The github repo currently does not produce anything else other than few meta-packages. Build recipes from oi-build or </span><span style="font-family:arial, sans-serif;font-size:13px;">illumos-userland can be added to the tree and should just work. </span><span style="font-family:arial, sans-serif;font-size:13px;">There is an option of enabling disabled Oracle provided packages as well.</span></div>
<div style=""><span style="font-family:arial, sans-serif;font-size:13px;"><br></span></div><div style=""><font face="arial, sans-serif">This time I wanted to keep things really simple. There is single publisher now - '<a rel="nofollow" target="_blank" href="http://openindiana.org/">openindiana.org</a>' - but pointing at different repo. And single source repo - <a rel="nofollow" target="_blank" href="https://github.com/OpenIndiana/oi-userland">https://github.com/OpenIndiana/oi-userland</a>. Any fixes or additions should be made in the github repo.</font></div>
<div style=""><span style="font-family:arial, sans-serif;"><br></span></div><div style=""><span style="font-family:arial, sans-serif;">In terms of fixes to the packages that came from SFW , I recommend using equivalent package from one of the userland-style repos. </span><span style="font-family:arial, sans-serif;">The idea is to not to have to compile SFW or run distro-importer ever again :)</span></div>
<div style=""><span style="font-family:arial, sans-serif;"><br></span></div><div style=""><span style="font-family:arial, sans-serif;">Correct me if I am wrong, but illumos-userland is dead. I don't see a point using it directly. Build recipes should be borrowed from it though :)</span></div>
<div style=""><span style="font-family:arial, sans-serif;"><br></span></div><div style=""><font face="arial, sans-serif">I have heard about libffi. Not sure what the problem is. It doesn't look like it would be difficult to provide userland build recipe for it in case we need an updated version.</font></div>
<div style=""><div><font face="arial, sans-serif"><br></font></div><div><span style="font-family:arial, sans-serif;">Andrzej</span><br></div><div><br></div></div><div style=""><font face="arial, sans-serif"><br></font></div></div>
<div class="yiv6103471111gmail_extra"><br><br><div class="yiv6103471111gmail_quote">On 12 May 2013 12:09, Piotr Jasiukajtis <span dir="ltr"><<a rel="nofollow" ymailto="mailto:estibi@me.com" target="_blank" href="mailto:estibi@me.com">estibi@me.com</a>></span> wrote:<br><blockquote class="yiv6103471111gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Andrzej,<br>
<br>
oi_151a8 is still based on sfw-gate, wouldn't be better to resurrect /experimental which was based on illumos-userland?<br>
<br>
To me it was hard to manage different IPS versions along with the build environments/zones because some were based on /experimental while my main host was /dev.<br>
Another source of confusion are 3 different source repositories: sfw, oi-build and illumos-userland. Which one to use if I need a new package on my production systems? and no, I don't want to touch SFW anymore :)<br>
<br>
Maybe create another version based on illumos-userland in the /dev let say oi_152a1 or something?<br>
<br>
<br>
Btw, someone mentioned about some libffi issues on oi_151a8.<br>
I barely checked that and it seems pkg and python do work but I don't know what the issue was. Is that fixed?<br>
<br>
Thanks for doing that :)<br>
<br>
--<br>
Piotr Jasiukajtis<br>
<div class="yiv6103471111HOEnZb"><div class="yiv6103471111h5"><br>
On May 12, 2013, at 10:30 AM, Andrzej Szeszo <<a rel="nofollow" ymailto="mailto:aszeszo@gmail.com" target="_blank" href="mailto:aszeszo@gmail.com">aszeszo@gmail.com</a>> wrote:<br>
<br>
> Hi All<br>
><br>
> Apologies for a delay. Some things are set up now.<br>
><br>
> New IPS repository is up: <a rel="nofollow" target="_blank" href="http://pkg.openindiana.org/hipster/">http://pkg.openindiana.org/hipster/</a>. It is a clone of the /dev repo + oi_151a8 bits from Jon Tibble and JDS bits from Milan Jurik merged in. Run commands below to update your system. You can ask Jon Tibble where the name of the repo came from :)<br>
><br>
> pkg set-publisher -O <a rel="nofollow" target="_blank" href="http://pkg.openindiana.org/hipster/">http://pkg.openindiana.org/hipster/</a> <a rel="nofollow" target="_blank" href="http://openindiana.org/">openindiana.org</a><br>
> pk install -v pkg://package/pkg<br>
> pkg update -v<br>
><br>
> Latest Oracle userland hg repo was converted to git and uploaded to <a rel="nofollow" target="_blank" href="https://github.com/OpenIndiana/oi-userland/">https://github.com/OpenIndiana/oi-userland/</a>. Most of the components were masked and don't build by default. I have only unmasked few meta packages to test if things build/publish correctly.<br>
><br>
> Quick Jenkins instance that automatically builds packages and publishes them directly to <a rel="nofollow" target="_blank" href="http://pkg.openindiana.org/hipster/">http://pkg.openindiana.org/hipster/</a>.<br>
><br>
> To start hacking, fork a repo on github, make your changes (unmask packages, add new ones) and submit pull request. If you are an existing contributor, give me a shout and I will give you direct access to the repo.<br>
><br>
> Please let me know if you have any questions.<br>
><br>
> Let's see if the process works out.<br>
><br>
> Kind regards,<br>
><br>
> Andrzej<br>
><br>
><br>
><br>
> On 11 May 2013 18:28, Andrzej Szeszo <<a rel="nofollow" ymailto="mailto:aszeszo@gmail.com" target="_blank" href="mailto:aszeszo@gmail.com">aszeszo@gmail.com</a>> wrote:<br>
> Hi Alasdair<br>
><br>
> I would like to try setting up a repo on github, give trusted people direct access and support pull requests from independent developers. And then have jenkins publish packages incrementally to publicly accessible repository. In theory, it should only take few minutes from a push to a published package in a repo.<br>
><br>
> It is a variation on the process which was tried earlier. I think it might work this time.<br>
><br>
> I did some prep work last night. Will try to have something usable by others later tonight.<br>
><br>
> Cheers,<br>
><br>
> Andrzej<br>
><br>
><br>
><br>
><br>
> On 10 May 2013 14:04, Alasdair Lumsden <<a rel="nofollow" ymailto="mailto:alasdairrr@gmail.com" target="_blank" href="mailto:alasdairrr@gmail.com">alasdairrr@gmail.com</a>> wrote:<br>
> Andrzej,<br>
><br>
> Your vision is pretty much the same one I had. The challenge is this:<br>
><br>
> "Existing releng process and contribution process prevent anything from happening though. I would like to help to change that."<br>
><br>
> How?<br>
><br>
><br>
> On Fri, May 10, 2013 at 12:54 PM, Jim Klimov <<a rel="nofollow" ymailto="mailto:jimklimov@cos.ru" target="_blank" href="mailto:jimklimov@cos.ru">jimklimov@cos.ru</a>> wrote:<br>
> On 2013-05-10 02:19, Garrett D'Amore wrote:<br>
> There is little "commercial future" in the desktop for Linux distributions as well yet almost all of them have a graphical desktop.<br>
><br>
> I would be entirely *unsurprised* if distro vendors like RedHat and Oracle simply *ditched* their desktop support at some point in the future -- its clear to me at least that folks aren't running those distros on the desktop.<br>
><br>
> Well, Oracle does provide and promote SunRays, and while admittedly most of their market targeting is about VDI and access to virtual<br>
> Windows desktops, there are many requests on the SRSS mailing list<br>
> about adding support for server-side Ubuntu as the SRSS terminal<br>
> server, because certain apps only exist for Linux and tunneling<br>
> of connections makes their graphics lag, and RHEL/OEL/Solaris<br>
> desktops are argued to be not so user-friendly (I have no opinion<br>
> on this, to me X11 is a means to display more characters on screen<br>
> than possible in a text mode).<br>
><br>
> Not that Oracle seems to care to address that demand, at least<br>
> publicly - just recently they began supporting versions 6 of RHEL<br>
> and OEL as server-side Linuxes. But there is certain demand for<br>
> non-MS/Apple desktops, and one linked to commercial interest as<br>
> well. I am not sure if OI/illumos can ride that tide, though.<br>
> Maybe with some other terminal client technologies (ThinLinc,<br>
> Wyse, etc)?..<br>
><br>
> //Jim<br>
><br>
><br>
><br>
> _______________________________________________<br>
> oi-dev mailing list<br>
> <a rel="nofollow" ymailto="mailto:oi-dev@openindiana.org" target="_blank" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>
> <a rel="nofollow" target="_blank" href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a><br>
><br>
><br>
><br>
> --<br>
> Alasdair Lumsden<br>
><br>
> <a rel="nofollow" target="_blank" href="http://www.everycity.co.uk/">http://www.everycity.co.uk</a><br>
><br>
> EveryCity Managed Hosting<br>
> Studio 18 Bluelion Place<br>
> 237 Long Lane, London, SE1 4PU<br>
><br>
> general: 020 <a href="" rel="nofollow">7183 2800</a><br>
> support: 020 <a href="" rel="nofollow">7183 2801</a><br>
> email: <a rel="nofollow" ymailto="mailto:al@everycity.co.uk" target="_blank" href="mailto:al@everycity.co.uk">al@everycity.co.uk</a><br>
><br>
> Every City Limited<br>
> Registered in England and Wales, No. <a href="" rel="nofollow">5689474</a> Registered Office: Roper<br>
> Yard, Roper Road, Canterbury, CT2 7EX<br>
><br>
> _______________________________________________<br>
> oi-dev mailing list<br>
> <a rel="nofollow" ymailto="mailto:oi-dev@openindiana.org" target="_blank" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>
> <a rel="nofollow" target="_blank" href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> oi-dev mailing list<br>
> <a rel="nofollow" ymailto="mailto:oi-dev@openindiana.org" target="_blank" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>
> <a rel="nofollow" target="_blank" href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a><br>
<br>
<br>
_______________________________________________<br>
oi-dev mailing list<br>
<a rel="nofollow" ymailto="mailto:oi-dev@openindiana.org" target="_blank" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>
<a rel="nofollow" target="_blank" href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a><br>
</div></div></blockquote></div><br></div></div><br>_______________________________________________<br>oi-dev mailing list<br><a ymailto="mailto:oi-dev@openindiana.org" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br><a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank">http://openindiana.org/mailman/listinfo/oi-dev</a><br><br></div> </div> </div> </div></body></html>