Re: relayd uses more socket splicing

2012-11-02 Thread Ian McWilliam
fushed -> flushed Though if we were speaking with an extremely broad Australian accent - "I fushed the dunny.", maybe what you would hear. So ends today's lesson on spelling. ;-) Ian McWilliam On 3/11/2012 5:03 AM, Alexander Bluhm wrote: Hi, I have changed relayd so that it uses socket spl

relayd uses more socket splicing

2012-11-02 Thread Alexander Bluhm
Hi, I have changed relayd so that it uses socket splicing also for persistent http connections. Before it spliced the incomming and outgoing tcp streams only if the data should go unmodified through the kernel until the end of stream. With this diff, relayd can give the kernel a maximum splice l

Re: [PATCH] cwm: function menu

2012-11-02 Thread Thomas Pfaff
On Tue, 30 Oct 2012 17:44:25 -0500 "Kent R. Spillner" wrote: This segfaults. See comments below. > Here is an initial attempt at adding a menu for searching/executing internal > functions. It's useful for those times you want to an unbound function, and > even when the function is bound to som

Re: 512 hardcoded into scan_ffs(8)

2012-11-02 Thread Theo de Raadt
> Looking at the source of scan_ffs, 512 is hardcoded all over the place. > Would it be an improvement to have that configurable, for the newer disks > with bigger size? No. ffs information is layed out on the disk in 512 byte chunks.

Re: Replacing "err(1, (char *)NULL);" with "err(1, NULL);" in style(9) manpage

2012-11-02 Thread Jason McIntyre
On Thu, Nov 01, 2012 at 12:41:17AM -0200, Rafael wrote: > Hi tech@, > > The diff below replaces "err(1, (char *)NULL);" with "err(1, NULL);" on > usage example of error functions in style(9) manpage. The casting seems to > be a leftover from the changes from revision 1.38 to 1.39. > fixed, thank

512 hardcoded into scan_ffs(8)

2012-11-02 Thread Jan Stary
Looking at the source of scan_ffs, 512 is hardcoded all over the place. Would it be an improvement to have that configurable, for the newer disks with bigger size?

5.2 SSD won't boot

2012-11-02 Thread Devin Ceartas
hp laptop with Intel SSD won't boot under 5.2 - the problem reported on screen appears to be the one described here: http://old.nabble.com/Re%3A-Fwd%3A--mSATA-failure-on-6501-w--OpenBSD-5.0-td32881415.html#a32884546 > ahci0: stopping the port, softreset slot 31 was still active. > ahci0: failed

SSD won't be recognized

2012-11-02 Thread Devin Ceartas
hp laptop with Intel SSD won't boot under 5.2 - the problem reported on screen appears to be the one described here: http://old.nabble.com/Re%3A-Fwd%3A--mSATA-failure-on-6501-w--OpenBSD-5.0-td32 881415.html#a32884546 > ahci0: stopping the port, softreset slot 31 was still active. > ahci0: failed t