On Tue, 2023-05-16 at 06:33 -0600, Theo de Raadt wrote:
> Rudolf Leitgeb wrote:
>
> > Lots of people (including myself) come from linux background and use
> > OpenBSD for specific security sensitive tasks. Since OpenBSD, like
> > every other desktop OS these days, h
On Tue, 2023-05-16 at 09:16 +0100, Stuart Henderson wrote:
> The strategy is that the sysadmin should configure datasize limits so
> that processes hit memory allocation failures if they try to
> overreach.
> Defaults are setup with typical use-cases and machines in mind but
> you
> might know
Lots of people (including myself) come from linux background and use
OpenBSD for specific security sensitive tasks. Since OpenBSD, like
every other desktop OS these days, has some strategy to deal
with OOM conditions, the term "OOM killer" is perfectly clear
regardless of what the actual
I am anything but an OpenBSD expert, but from other operating systems
knowledge I would suggest, that you see file system cache in action.
Your system comes with much more RAM than needed, at least initially,
and that RAM is used to cache slow hard disk operations. If you copy
100MB, these 100MB
This potentially erroneous call to put_entries() happens only, if
a malloc at a very early stage fails. In my opinion, the call to
put_entries in pfnote() should be wrapped:
--- tree.c.ORIG 2019-11-04 09:01:30.320610560 +0100
+++ tree.c 2019-11-04 09:02:09.024609588 +0100
@@ -57,7 +57,8 @@
traffic in this thread (or lack thereof from other devs),
I tend to believe, that (2) is the case, and therefore stand by my
suggestion to revert USB3 to USB2 on octeon.
On Sat, 2019-09-28 at 09:32 -0600, Theo de Raadt wrote:
> Rudolf Leitgeb wrote:
>
> > If one of your vast pool o
> Someone who doesn't develop in the kernel makes proposal for
> a platform they deride as sucking, so why not just do the worst
> possible job because who cares
That platform is perfect for what I need, that's why I installed
OpenBSD on it and started configuring it for the task in question.
We
> > AFAICT octeon is a hideously slow platform with no need for
> > anything
> > faster than USB2.
> That is a ridiculous statement.
Now that sounds impressive and convincing
wrote:
> Oh yes, that's a great idea, we should simply install workarounds all
> the time, rather than keeping the problems visible, so that someone
> will fix it properly.
>
>
> Rudolf Leitgeb wrote:
>
> > Since octeons are not exactly high power CPUs, wouldn't it
> &g
Since octeons are not exactly high power CPUs, wouldn't it
suffice to treat its USB3 port as USB2 port for now, at least
as an option? From playing with the system I have the strong
impression, that a performance difference would not be noticed.
Cheers,
Rudi
On Tue, 2019-09-24 at 07:04 -0600,
>Synopsis: octeon: Unable to write large amounts of data to USB
disk
>Category: octeon USB disks
>Environment:
System : OpenBSD 6.5
Details : OpenBSD 6.5 (GENERIC.MP) #0: Mon Apr 15 07:34:41
UTC 2019
Am I correct in assuming, that your OpenBSD image lives
on a different medium than the original linux image?
Is there a chance that the flash medium holding the
OpenBSD image is defective?
On Sun, 2019-03-10 at 17:02 +0300, Sergey Bronnikov wrote:
> > Synopsis: ddb trap 4 happens on edgerouter
12 matches
Mail list logo
