Re: [OpenIndiana-discuss] OI roadmap (for production)
That would require to have some hipster release that can be positively > upgraded to. > Then let us just finish migrating the consolidations to oi-userland so that we can talk about the next Hipster snapshot being frozen and promoted to /dev. -resurrect GUI update, (python devs welcome) > -maintain GUI installation (python also) > Two project proposals for student in computer sciences at KTH Stockholm were formulated for that, it would be great if they are picked. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/05/2015 00:43, Stefan Müller-Wilken wrote: Good point, indeed. Just curious: But isn't that something all Illumos distributions have in common? Bad point. I watch latest news and try to fix security issues which are known. I suspect that there could be issues in GUI programs (as our GNOME version is dated), perhaps in the ancient sendmail version which we use, but server software in oi-userland is regularly fixed. From what I'm aware now, perhaps, percona and MariaDB could be updated to the latest minor versions, but I don't know if there were critical security issues in these DBMS recently. If you aware about security issues in server packages, let me know (packages, CVE numbers). -- Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] using touch ... whats wrong here
v...@bb-c.de (Volker A. Brandt) writes: > Hi Harry! > > >> find scripts/perl/ -cnewer NewerThan -and ! -cnewer ButNotNewerThan > > Stupid question: Which find are you using? The -cnewer construct gnu find ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] using touch ... whats wrong here
Thanks for the good input... yes I see it is `-newer' I was after... not -cnewer. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
> > Two project proposals for student in computer sciences at KTH Stockholm > were formulated for that, it would be great if they are picked. > Great idea! And this is very good idea to have young people getting involved with OI. IMHO this is the only way to get things like KMS, USB3, etc. A.S. -- Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Hi Alex, first of all, don't get me wrong. It wasn't the difference in security fix frequency that I called a good point but the relevance of it. I sure would not insult those keeping my favorite server OS alive! And great to hear that the security alerts / CVEs are being patched on a regular basis. As so often, this simply might be a matter of missing information. Is there a CVE patch log? The current release notes under http://wiki.openindiana.org/oi/Release+Notes don't seem to list any. Cheers Stefan Von: Alexander Pyhalov [a...@rsu.ru] Gesendet: Samstag, 5. Dezember 2015 13:57 An: Discussion list for OpenIndiana Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production) On 12/05/2015 00:43, Stefan Müller-Wilken wrote: > Good point, indeed. Just curious: But isn't that something all Illumos > distributions have in common? > Bad point. I watch latest news and try to fix security issues which are known. I suspect that there could be issues in GUI programs (as our GNOME version is dated), perhaps in the ancient sendmail version which we use, but server software in oi-userland is regularly fixed. From what I'm aware now, perhaps, percona and MariaDB could be updated to the latest minor versions, but I don't know if there were critical security issues in these DBMS recently. If you aware about security issues in server packages, let me know (packages, CVE numbers). -- Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss - Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | USt-IdNr.: DE208833022 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/ 4/15 04:01 PM, Alexander Pyhalov wrote: On 12/04/2015 17:16, Dmitry Kozhinov wrote: Alexander Pyhalov, Thu Dec 3 12:39:35 UTC 2015: > As for /dev, I think it's not a big secret that it's efficiently dead. Nikola M, Thu Dec 3 18:46:38 UTC 2015: > It is not big secret that hipster is never planned for any kind of production What is the plan then? Hi. What do you want to know? Currently we try to ride the car and tune it simultaneously (like illumos-gate does). I mean, there are changes which will affect urgent needs (e.g, security fixes) and some development (for example, major version updates). As for the current plan, there are several links http://wiki.openindiana.org/oi/Packaging+projects http://wiki.openindiana.org/oi/TODO+list As for my personal plans, I'd like to look at porting Mate now. As for other tasks, I think we have to remove python2.6 from OI, but to make this real, we have either: 1) officially state that /dev is dead and try to merge python2.7 changes to illumos-gate, Just to make sure people understand, that is because not contributing to /dev in the first place. That would require to have some hipster release that can be positively upgraded to. Actually it would be best that hispter releases land in /dev because hipster's way of landing new packages without announcements, plannings and sometime one sentence of description is not what wider audience would expect to see in releases. 2) invent some decision which would work on OI /dev and old python, That could be branded zone with 151a9. I am using hipster on laptop for personal use, lack of alternatives and because there needs to be someone who reports bugs and there are always many bugs, so many that I am not reporting them on tracker but just on IRC, not to make impression everything is full of bugs... (but they get fixed gradually as they could, usually by alp alone) I also think there could be setting what is important and what currently is not and work on important things and not on everything one just wants to. I think it is important to: -resurrect GUI update, (python devs welcome) -maintain GUI installation (python also) -avoid all core dumps from main applications (testers, bug reporting) -have hipster recompiled fully -have OI hipster's own illumos patching process. (maintainers, illumos dev) -gksudo, gksu does not work, -revert removal of GUI administration tools -have pfexec working by default with administrative account (possibly 2 accounts by fresh install, one with pfexec) -fix issue of source availability of hipster's packages, because hipster does not use OI's own infrastructure for storing source changes and it is needed to have sources for every build available on OI servers to fulfill licenses, at least in releases. (maintainers) - standby/resume to make work again (it used to work on hipster till first half of 2014). (illumos or hipster issue?) - last but not least: both Firefox and Thunderbird lost their spellcheck Some of them are essential (GUI update, GUI install, core apps not core dumping, recompliation, source availability, illumos patchig, default pfexec for admin account) and some are not and I am sure everyone can have it's own list but some dort of attitude toward releasing something needs to be established. That could all go before porting Mate and make things with OI /dev to hipster update even more complicated. There are simply more important things then that. There got to be some hipster release (maybe till the end of the year) that people can update from /dev to new /dev made out of hipster. Landing hipster release in /dev can boost up OI brand and inclusion of more people reporting bugs and contributors. I can suggest people follow hipster for testing and everyday use and contribute to changes that lead to stabilization, not adding more buggy packages , therefore, respecting community need for releases instead of never ending rolling updates. Contributors willing to fix listed bugs and make release out of hipster that could be upgradeable and land into /dev are welcome. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
>>> what speaks against using OI in server use? >> Security updates. > Good point, indeed. Just curious: But isn't that something all Illumos > distributions have in common? No. SmartOS and OmniOS get prompt security updates as CVEs and other announcements become available. -- Joshua M. Clulow UNIX Admin/Developer http://blog.sysmgr.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On Fri, 4 Dec 2015, Predrag Zečević - Unix Systems Administrator wrote: Also, number of people involved in OS maintenance made me suggest SmartOS or OmniIT... OmniOS succeeds due to its quite limited scope rather than a large number of maintainers. It leaves the responsibility for providing common server applications (e.g. Apache) to others. SFE is in a fledgling state for OmniOS, but might prove to be a significant future source of applications (in addition to Joyent-supported pkgsrc and third parties who have provided public access to their IPS packages). SmartOS does not likely have a large number of maintainers either, but Joyent has bet its future on it. SmartOS also succeeds by limiting its scope. OpenIndiana has a much larger scope given how many packages it offers by default. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
