> Yeh, cutting edge.. I have system lock/freeze every time with bittorent
> (aria2 or rtorrent) when net bandwidth 5 mbit/s or more :)
This is the point I am getting flak again, please don't pollute the env
you're doing it wrong.
> (ffs+softdep on softraid crypto)
Plus a person trying to post
Hi Donovan,
thanks for your help, i committed this.
/Benno
Donovan Watteau(tso...@gmail.com) on 2015.07.30 22:32:41 +0200:
> Hi,
>
> I was playing a bit with httpd(8) new "hsts" setting when some
> trivial tests with Firefox would sometimes give the following error:
>
> The site specified
Hi,
I was playing a bit with httpd(8) new "hsts" setting when some
trivial tests with Firefox would sometimes give the following error:
The site specified an invalid Strict-Transport-Security header.
Some pages would also load and reload a few times before appearing in
the browser.
curl wou
This fixes a bug that allows others to write to remote users pseudo
terminals. Looking at the revision 1.29 commit message and thread[2]
that led to this bug I'm pretty sure that it wasn't intended to be this
way.
[1] https://marc.info/?t=14091389379&r=1&w=2
Index: sshpty.c
===
Karel Gardas wrote:
> Yes, Free also adds softdep journaling. on the other hand Net
> completely abandoned softdep in favour of wapbl, this thing is
> interesting since it's about ~1k lines. Net also as the only one from
> *BSD supports ffs snapshoting, this is about another ~2k lines of
> code. Su
On Thu, Jul 30, 2015 at 3:36 PM, Karel Gardas wrote:
> On Thu, Jul 30, 2015 at 2:01 PM, Christian Weisgerber
> wrote:
>> On 2015-07-30, Karel Gardas wrote:
>>
>>> discussion. So far what I've read is that softdep does have some
>>> unreliability issues on somehow limited platforms: either small
2015-07-30 13:26 GMT+03:00 Theo Buehler :
> This is a follow-up to a recent discussion on misc@:
> https://marc.info/?t=14380009452&r=1&w=2
>
> I suggest two small changes to the example in doas.conf(5):
>
> a. make it explicit that the rule allows the users in group wheel to
> run comma
On Thu, Jul 30, 2015 at 2:01 PM, Christian Weisgerber
wrote:
> On 2015-07-30, Karel Gardas wrote:
>
>> discussion. So far what I've read is that softdep does have some
>> unreliability issues on somehow limited platforms: either small kernel
>> memory or slow disk drive or even buggy disk drive.
On 2015-07-30, Karel Gardas wrote:
> discussion. So far what I've read is that softdep does have some
> unreliability issues on somehow limited platforms: either small kernel
> memory or slow disk drive or even buggy disk drive.
If you push a beefy machine hard enough (e.g. bulk amd64 package
bu
This is a follow-up to a recent discussion on misc@:
https://marc.info/?t=14380009452&r=1&w=2
I suggest two small changes to the example in doas.conf(5):
a. make it explicit that the rule allows the users in group wheel to
run commands as any user (not just root).
b. modify the rule
Hi,
I started a review of ikeca.c about the use of system(3). But as there
is a lot of others place of improvement in the code, I prefer to go
step by step, and proposing patches only for one function at time.
The following patch is a review of ca_export() function.
It adds:
- xsnprintf() funct
Right now, an USB_REQUEST ioctl will fail with an EBADF error if done
on a device opened as read-only. With this patch, the ioctl will fail
only if the USB_REQUEST is a write request.
Index: sys/dev/usb/usb.c
===
RCS file: /cvs/src/sys
On Thu, Jul 30, 2015 at 11:30:36AM +0200, Karel Gardas wrote:
> Spent already some time in netbsd/bitrig wapbl code to see what's
> relevant for Open and how to structure it to small sensible patches to
> push for review. This will take some energy and time indeed, the
> problem is that anytime the
On Thu, Jul 30, 2015 at 11:19 AM, Theo de Raadt wrote:
> Your mail sounds like a beg. Perhaps I am being too sensitive.
Spent already some time in netbsd/bitrig wapbl code to see what's
relevant for Open and how to structure it to small sensible patches to
push for review. This will take some e
> W.r.t. code or fixes, I'm afraid this is not only about developer work
> but probably also about simple work analysis and kind of direction
> discussion. So far what I've read is that softdep does have some
> unreliability issues on somehow limited platforms: either small kernel
> memory or slow
W.r.t. code or fixes, I'm afraid this is not only about developer work
but probably also about simple work analysis and kind of direction
discussion. So far what I've read is that softdep does have some
unreliability issues on somehow limited platforms: either small kernel
memory or slow disk drive
16 matches
Mail list logo
