On 2015-11-11, Joerg Jung wrote:
>> Am 11.11.2015 um 05:44 schrieb Daniel Ouellet :
>>
>> Does anyone use this port yet Rspamd.
>>
>> I saw Stuart + a few helpers making a port of Rspamd. Only on current
>> now, so I install current on a server and try to run it.
>>
>> But anyone have any clue
On 11/11/15 5:30 AM, Stuart Henderson wrote:
> On 2015-11-11, Joerg Jung wrote:
>>> Am 11.11.2015 um 05:44 schrieb Daniel Ouellet :
>>>
>>> Does anyone use this port yet Rspamd.
>>>
>>> I saw Stuart + a few helpers making a port of Rspamd. Only on current
>>> now, so I install current on a server
Hi folks,
below you can find the trace and ps for the frozen system,
as well as the output of dmesg.
Hope this helps. Please mail if I can help to track down this
problem.
Many thanx
Harri
-
OpenBSD/amd64 (redgate.red.aixigo.de) (t
Previously, resuming my old amd64/current MacBook2,1 (dmesg below)
resulted in a garbled screen. I just want to report that this problem
has disappeared; apparently, the recent inteldrm thing got improved.
Resume from X now works: I get my screen back and everything just works,
including the resum
Hi,
Tp-Link TL-WN881ND PCI-E ( Atheros / AR9287 / athn0 )
This adapter works fantastic when it is plugged in to my motherboard, can even
set it up with
hostap for an access point - great!!
..Until I try to reboot the machine, then it goes crazy and ifconfig says the
device doesn't exist
etc..
I've done some further testing and I think I've narrowed it down to the
"Unlocking em(4) a bit further"-patch [0]. With the patch reverted, I
haven't seen any watchdog timeouts yet. I'm currently running the router
with the patch reverted to make sure the timeouts don't happen again.
[0]: https://
Em 11-11-2015 00:06, Nick Holland escreveu:
> The point is...if you put in a DNS name, odds are you are going to end
> up thinking you are blocking/passing/redirecting a DNS name..when in
> reality, you are whatevering JUST the IP address that it resolves to at
> the time the firewall rules were lo
On Wed, Nov 11, 2015 at 08:58:37AM -0500, szs wrote:
> $dmesg | grep Atheros
> athn0 at pci1 dev 0 function 0 "Atheros AR9287" rev 0x01: apic 6 int 4
> vendor "Atheros", unknown product 0xff1c (class network subclass ethernet,
> rev 0
> x01) at pci1 dev 0 function 0 not configured
>
> -=-=-=-=-=-
Hello!
My computer is a MacBook Pro 8,2.
There is a GPT on the HD (big surprise!) with four partitions,
the last one being of type OpenBSD.
I managed to put a recent OpenBSD 5.8 snapshot there
by booting and installing from an USB stick via EFI created like that
(in OSX):
dd if=~/install58.f
Is good idea to create a user-friendly and easy-to-use variant of OpenBSD
second the hardcore OpenBSD user community?
If no, because?
GUI is for wimps second the currently opinion of hardcore OpenBSD user
community?
If yes because?
--
View this message in context:
http://openbsd-archive.7691
français wrote:
> Is good idea to create a user-friendly and easy-to-use variant of
> OpenBSD second the hardcore OpenBSD user community?
>
> If no, because?
My opinion: this would be useful to a lot of people, but don't expect
help from upstream.
Things like the lack of Linux capabilities would
From: jtub...@gmail.com [mailto:jtub...@gmail.com] On Behalf Of Jason Tubnor
Sent: Tuesday, November 03, 2015 1:44 AM
To: igyht
Cc: OPENBSD forum
Subject: Re: iked & nat-t problem (no keep alive)
On 19 October 2015 at 21:49, igyht wrote:
I am testing iked on OpenBSD phobos 5.7 GENERIC#738 i386
As cron got a quite interested recently, isn't
right time to move its log to /var/log?
Or does having /var/cron/log have any specific reason?
j.
On 2015-11-10 14:10, Tinker wrote:
...
A "safe" approach to file access would be to read data using mmap()
but write data using fwrite() only. Mmap does have a read-only mode.
This does NOT work in OpenBSD currently though because of the absence
of unified caching.
I find this conversation puzz
Is there any implementation of the OpenMP API
contained in one of the GNU compiler packages?
> I find this conversation puzzling, since even back in BSD 4.3, read() was
> actually implemented by memory mapping the underlying file.
That is an wildly incorrect description of the 4.3 BSD buffer cache,
furthermore 4.3 lacked a working mmap() to hit the coherency issue.
On 2015-11-12 01:30, Theo de Raadt wrote:
I find this conversation puzzling, since even back in BSD 4.3, read()
was
actually implemented by memory mapping the underlying file.
That is an wildly incorrect description of the 4.3 BSD buffer cache,
furthermore 4.3 lacked a working mmap() to hit th
...
LMDB's write performance is pretty mediocre, by design - we emphasized
durability/reliability over performance here. But in practice, it is
always faster than e.g. BerkeleyDB, which supports multiple concurrent
writers. With multiple writer concurrency, we found that BDB spends
much of its ti
> On 2015-11-12 01:30, Theo de Raadt wrote:
> >> I find this conversation puzzling, since even back in BSD 4.3, read()
> >> was
> >> actually implemented by memory mapping the underlying file.
> >
> > That is an wildly incorrect description of the 4.3 BSD buffer cache,
> > furthermore 4.3 lacked
On Wed, Nov 11, 2015 at 05:11:52PM +0100, Jens A. Griepentrog wrote:
> Is there any implementation of the OpenMP API
> contained in one of the GNU compiler packages?
>
A working patch was discussed here:
https://marc.info/?t=14332549291&r=1&w=2
but as far as I know nothing has been committed,
On Wed, 11 Nov 2015 12:29:30 -0500, Jiri B wrote:
> As cron got a quite interested recently, isn't
> right time to move its log to /var/log?
> Or does having /var/cron/log have any specific reason?
Since it is just another syslog file /var/log makes sense.
I worry a bit about people's log watchin
On Wed, Nov 11, 2015 at 10:47:00AM -0700, Todd C. Miller wrote:
> On Wed, 11 Nov 2015 12:29:30 -0500, Jiri B wrote:
>
> > As cron got a quite interested recently, isn't
> > right time to move its log to /var/log?
> > Or does having /var/cron/log have any specific reason?
>
> Since it is just anot
On 2015-11-12 01:42, Theo de Raadt wrote:
On 2015-11-12 01:30, Theo de Raadt wrote:
>> I find this conversation puzzling, since even back in BSD 4.3, read()
>> was
>> actually implemented by memory mapping the underlying file.
>
> That is an wildly incorrect description of the 4.3 BSD buffer cach
On Wed, 11 Nov 2015 12:52:51 -0500, Jiri B wrote:
> Other thing, when I was playing with most filesystems r/o I also
> found having '.sock' in /var/cron/tabs little annoying,
> as we usually use /var/run and I was already having /var/run
> as mfs. Since like piece of cake to move it to /var/run.
> Is good idea to create a [...] variant of OpenBSD
No. If anything can be improved, submit patches.
Hi misc@
cron started to be recently reported in my insecurity output after
upgrading to snapshot from Nov 6:
Checking special files and directories.
Output format is:
filename:
criteria (shouldbe, reallyis)
var/cron/atjobs:
permissions (01770, 0770)
var/cron/tabs
Hi Alexis,
On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE wrote:
> [...]
> Even with heavy network load ?
> [...]
So far, yes. I've saturated the device for about 45 Minutes with
something like this (the other end is my laptop):
## on the router
$ dd if=/dev/zero bs=8k
Hello,
I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in one
of my systems and tried to boot the November 11th amd64 miniroot58.fs
image to test UEFI booting. I get to the bootloader, but it appears to
fail while loading the kernel and goes into a reboot loop. Here's
everything
Hi Gregor,
Even with heavy network load ?
Regards,
Alexis.
De : owner-t...@openbsd.org de la part de Gregor Best
Envoyé : mercredi 11 novembre 2015 15:20
À : Mark Kettenis
Cc : t...@openbsd.org; misc@openbsd.org
Objet : Re: em(4) watchdog timeouts
I've
On Wed, 11 Nov 2015 20:31:03 +0100, Adam Wolk wrote:
> cron started to be recently reported in my insecurity output after
> upgrading to snapshot from Nov 6:
>
> Checking special files and directories.
> Output format is:
> filename:
> criteria (shouldbe, reallyis)
> var/cron/
30 matches
Mail list logo
