Peter Tribble писал 16.12.2015 19:22:
On Fri, Dec 4, 2015 at 3:01 PM, Alexander Pyhalov wrote:
As for my personal plans, I'd like to look at porting Mate now.
Just as a matter of interest, are you thinking of MATE as an additional
desktop
environment, or as a replacement for
On Fri, Dec 4, 2015 at 3:01 PM, Alexander Pyhalov wrote:
>
> As for my personal plans, I'd like to look at porting Mate now.
>
Just as a matter of interest, are you thinking of MATE as an additional
desktop
environment, or as a replacement for JDS/Gnome?
I found it pretty easy to
On Fri, Dec 11, 2015 at 1:26 PM, Rich Teer wrote:
> This conversation reminds me of this old chestnut:
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What's the most annoying thing on
On Sat, 12 Dec 2015, Ian Collins wrote:
> There is only one of you writing, but many reading. That's why decent
> threading and quoting is important on technical lists!
This conversation reminds me of this old chestnut:
A: Because it messes up the order in which people normally read text.
Q:
Stefan Müller-Wilken wrote:
Sorry, Nicola, but is _this_ the kind of problems that should be
> discussed in the OI community? I would have thought there are more
> serious subjects to ponder...
There is only one of you writing, but many reading. That's why decent
threading and quoting is
: dinsdag 8 december 2015 16:25
Aan: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org>
Onderwerp: Re: [OpenIndiana-discuss] OI roadmap (for production)
On Tue, Dec 8, 2015 at 11:14 AM, Jim Klimov <jimkli...@cos.ru> wrote:
>
> >From: Tim Mooney [mailto:tim.moo...@n
Subject: Re: [OpenIndiana-discuss] OI roadmap (for production)
>
>In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production),
>Stefan...:
>
>> first of all, don't get me wrong. It wasn't the difference in
>security
>> fix frequency that I called a good point but th
On Tue, Dec 8, 2015 at 11:14 AM, Jim Klimov wrote:
>
> >From: Tim Mooney [mailto:tim.moo...@ndsu.edu]
>
> >
> >I'm trying to find a way to verify component security that doesn't rely
> >on more work from the few people that are already doing the security
> >work, but it's not
On Tue, 8 Dec 2015, Jim Klimov wrote:
Might it make sense to use some pkg(5) metadata to list the cve's
known covered by a particular release+patch recipe used in the
build? I know i'd quickly stop maintaining such data though, but
there may be even pedantical people than mysekf out there ;)
In message , Bob F
riesenhahn writes:
>I notice that pkgsrc offers a feature whereby known defects against
>the installed versions may be listed. This is querying some sort of
>remote database.
I find FreeBSD's security announcements
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...:
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
You around tomorrow?
Paul
-Original Message-
From: Tim Mooney [mailto:tim.moo...@ndsu.edu]
Sent: 07 December 2015 15:28
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] OI roadmap (for production)
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production
On 12/ 7/15 06:48 AM, Richard L. Hamilton wrote:
I think there needs to be some change that provides for a clear way for
businesses to account for donations to open source organizations and
developers. Right now, from what I've seen mentioned before, typical
accounting departments have
On 12/ 6/15 08:37 PM, Stefan Müller-Wilken wrote:
Hi Nicola,
unfortunately I'm forced to use MS OWA so unless you know of a way to indent
mails on reply or better associate them to previous mails, I can't do too much
about this. Sorry if this annoys you, but that is how it is.
Whatever you
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production),...:
What would help me (and hopefully others) is if there were documentation
on how we can verify whether an OI /dev package includes a particular
patch. Does that documentation exist?
For /hipster to check if particular
-Oorspronkelijk bericht-
Van: Private openbabel [mailto:openba...@gmail.com]
Verzonden: zondag 6 december 2015 22:00
Aan: openindiana-discuss@openindiana.org
Onderwerp: Re: [OpenIndiana-discuss] OI roadmap (for production)
On 05/12/2015 21:16, Bob Friesenhahn wrote:
> On Fri, 4 Dec 2
On Mon, 7 Dec 2015, Tim Mooney wrote:
What would help me (and hopefully others) is if there were documentation
on how we can verify whether an OI /dev package includes a particular
patch. Does that documentation exist?
Part of the issue is that if I run the software update utility or pkg
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Bob...:
Take libpng for example. The latest OI /dev ships is 1.4.12. Everything
before 1.4.17 is vulnerable to CVE-2015-7981 and CVE-2015-8126. Let's
say that I had just installed a8 today and then updated to a9, so I
: [OpenIndiana-discuss] OI roadmap (for production)
On 12/ 6/15 01:15 AM, Stefan Müller-Wilken wrote:
> Hi Alex,
>
Hi, Stefan Müller-Wilken , just a side note:
Please start hitting 'reply' button on messaged on topic/thread, or
changing mail client application that allows it (like Thunderbird,
On 12/ 6/15 12:59 PM, Private openbabel wrote:
Dear Bob,
I would like to see a foundation registered in the UK in early 2016 to receive
donations and sponsorship similar to Libre Office.This will help with some of
the development objectives outlined.
Will it? Are there going to be enough
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)
>
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
>
> 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.
]
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
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
>>> 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.
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
On 12/04/2015 18:18, Dmitry Kozhinov wrote:
Thank you for the detailed response. I understand that there is a lot of
work to do. But the work should have a goal. "we try to ride the car and
tune it simultaneously" - doesn't that mean that OI will never be ready
for production use?
As for what
On 12/ 4/15 04:18 PM, Dmitry Kozhinov wrote:
Thank you for the detailed response. I understand that there is a lot of
work to do. But the work should have a goal. "we try to ride the car and
tune it simultaneously" - doesn't that mean that OI will never be ready
for production use?
As for what
Alexander, and Predrag,
Thank you for the information. Currently I am using OI 151a9 for a
web/ftp/mail server exposed to Internet. I am satisfied with the
stability but concerned that this branch is not supported. I will
consider hipster next time when I need to setup a server (it may be an
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
, 4. Dezember 2015 16:33
An: openindiana-discuss@openindiana.org
Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/ 4/15 04:18 PM, Dmitry Kozhinov wrote:
> Thank you for the detailed response. I understand that there is a lot of
> work to do. But the work should have a goa
Administrator
[predrag.zece...@2e-systems.com]
Gesendet: Freitag, 4. Dezember 2015 16:33
An: openindiana-discuss@openindiana.org
Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/ 4/15 04:18 PM, Dmitry Kozhinov wrote:
Thank you for the detailed response. I understand that there is a lot
Thank you for the detailed response. I understand that there is a lot of
work to do. But the work should have a goal. "we try to ride the car and
tune it simultaneously" - doesn't that mean that OI will never be ready
for production use?
As for what do I want to know... A simpler question:
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, Gary.
Gary Gendel писал 04.12.2015 19:16:
I moved to OmniOS because I was unable to upgrade hipster at one point
as it broke the bge driver (in a very frustrating way as it looked
like all packets were being filtered). I tried several times as new
releases were available without success.
On 12/04/2015 11:06 AM, Dmitry Kozhinov wrote:
Alexander, and Predrag,
Thank you for the information. Currently I am using OI 151a9 for a
web/ftp/mail server exposed to Internet. I am satisfied with the
stability but concerned that this branch is not supported. I will
consider hipster next
"break everything"
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...:
what speaks against using OI in server use?
Security updates.
Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure 701-231-
roadmap (for production)
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...:
> what speaks against using OI in server use?
Security updates.
Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrast
common?
Von: Tim Mooney [tim.moo...@ndsu.edu]
Gesendet: Freitag, 4. Dezember 2015 17:56
An: Discussion list for OpenIndiana
Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production)
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...:
> wh
41 matches
Mail list logo