On Mon, 10 Jul 2017, Stefan Sperling wrote:
> From: Stefan Sperling
> To: SOUL_OF_ROOT 55
> Cc: misc@openbsd.org
> Date: Mon, 10 Jul 2017 22:16:36
> Subject: Re: Doubts about the successors of OpenBSD leadership and development
>
> On Mon, Jul 10, 2017 at 06:04:53PM -0300, SOUL_OF_ROOT 55 wrote:
On Tue, Jul 11, 2017 at 06:54:32AM +0200, Michele Curti wrote:
> On Mon, Jul 10, 2017 at 11:16:36PM +0200, Stefan Sperling wrote:
> > On Mon, Jul 10, 2017 at 06:04:53PM -0300, SOUL_OF_ROOT 55 wrote:
> > > Who will succeed Theo de Raadt in the leadership and development of
> > > OpenBSD?
> >
> >
On Mon, Jul 10, 2017 at 11:16:36PM +0200, Stefan Sperling wrote:
> On Mon, Jul 10, 2017 at 06:04:53PM -0300, SOUL_OF_ROOT 55 wrote:
> > Who will succeed Theo de Raadt in the leadership and development of OpenBSD?
>
> Obviously, Theo de Raadt will succeed Theo de Raadt in the leadership and
> deve
Hi Theo,
On 07/10/2017 09:24 PM, Theo Buehler wrote:
On Mon, Jul 10, 2017 at 07:44:19PM -0700, jungle boogie wrote:
Hi All,
I just updated from the 6th of July snapshot to the 10th of July.
When I logged in and check the mail, I didn't see a message advising a new
kernel link. Between the 6th a
On Mon, Jul 10, 2017 at 07:44:19PM -0700, jungle boogie wrote:
> Hi All,
>
> I just updated from the 6th of July snapshot to the 10th of July.
> When I logged in and check the mail, I didn't see a message advising a new
> kernel link. Between the 6th and 10th I rebooted my machine many times and
>
Hi All,
I just updated from the 6th of July snapshot to the 10th of July.
When I logged in and check the mail, I didn't see a message advising a
new kernel link. Between the 6th and 10th I rebooted my machine many
times and didn't see the mail.
Are the mails no longer expected? How do I verif
Hi Jan,
Jan Stary wrote on Mon, Jul 10, 2017 at 05:57:08PM +0200:
> This is how ports.7 is rendered on my 6.1-current:
>
> For more information about using ports, see The OpenBSD Ports System (
> https://www.openbsd.org/faq/faq15.html#Ports
> ).For information about cr
On 7/10/2017 5:53 PM, Raul Miller wrote:
On Mon, Jul 10, 2017 at 5:04 PM, SOUL_OF_ROOT 55 wrote:
Theo de Raadt no responds to me private message since I told him that I do
not understand English.
If you told him that in english, I can imagine why.
Perhaps his English is mode 0266.
> From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
> Stefan Sperling
> Sent: July 10, 2017 16:17
> Subject: Re: Doubts about the successors of OpenBSD leadership and development
>
> Obviously, Theo de Raadt will succeed Theo de Raadt in the leadership
> and development of
On Mon, Jul 10, 2017 at 5:04 PM, SOUL_OF_ROOT 55 wrote:
> Theo de Raadt no responds to me private message since I told him that I do
> not understand English.
If you told him that in english, I can imagine why.
(You effectively said that you do not know what you are saying - which
makes any resp
On Mon, Jul 10, 2017 at 06:04:53PM -0300, SOUL_OF_ROOT 55 wrote:
> Who will succeed Theo de Raadt in the leadership and development of OpenBSD?
Obviously, Theo de Raadt will succeed Theo de Raadt in the leadership and
development of OpenBSD: http://marc.info/?l=openbsd-misc&m=137609553004700&w=2
Who will succeed Theo de Raadt in the leadership and development of OpenBSD?
Can I succeed Theo de Raadt in the leadership and development of OpenBSD?
Theo de Raadt no responds to me private message since I told him that I do
not understand English.
On Mon, Jul 10, 2017 at 10:22:06PM +0200, Stefan Fritsch wrote:
> On Saturday, 8 July 2017 14:58:59 CEST Stefan Fritsch wrote:
> > A difference between i386 and amd64 is that on amd64, openbsd uses MSI-X for
> > virtio. Maybe legacy interrupts are broken with vhost-net. This needs some
> > more deb
On Saturday, 8 July 2017 14:58:59 CEST Stefan Fritsch wrote:
> A difference between i386 and amd64 is that on amd64, openbsd uses MSI-X for
> virtio. Maybe legacy interrupts are broken with vhost-net. This needs some
> more debugging. But its either a bug in qemu or in the linux kernel, not in
> op
On 2017-07-07, Kaya Saman wrote:
>>> ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting
>
> The exact problem is that the service doesn't start... I have disabled
> the ntpd from base in rc.conf then execute the rc.d script and no
> service?? - just the error above.
>
> The servi
This is how ports.7 is rendered on my 6.1-current:
For more information about using ports, see The OpenBSD Ports System (
https://www.openbsd.org/faq/faq15.html#Ports
). For information about creating new ports, see the OpenBSD Porter's
Handbook (
https://www.
On 2017-07-10, Florian Viehweger wrote:
>> I don't think it's really documented anywhere prominent, an errata
>> would be the usual place for something like this but they aren't
>> usually done without a code patch that can be applied..
>
> I've also stumbled across it. If an errata is not in real
> I don't think it's really documented anywhere prominent, an errata
> would be the usual place for something like this but they aren't
> usually done without a code patch that can be applied..
I've also stumbled across it. If an errata is not in real prospect,
maybe a little notice in the upcomin
On 2017-07-07, Thomas Smith wrote:
>> There was an installer bug in 6.1 resulting in the wrong path getting
>> written to installurl if you entered the mirror URL manually (this has
>> since been fixed). What you did (i.e. editing the file to remove 6.1)
>> is the the correct workaround.
>
> Under
On 2017-07-10, Paul B. Henson wrote:
> mdb has been disabled in the openldap port since it looks like
> 2015/02/16, I was wondering if anyone has tried it since then to see if
> maybe the issues with it have been resolved? The other backends are
> deprecated upstream, it would be nice to get mdb w
The other answers you've had are good, just a couple of extras:
On 2017-07-07, J Doe wrote:
> Ok, thank you for clarifying that for me. I will proceed with
> development in C. As an aside - do OpenBSD developers track with the
> latest standard (C11), or is another standard preferred ?
Compilers
21 matches
Mail list logo