On Jan 04 23:27:48, h...@stare.cz wrote:
Here's some more cleanage for cwm:
the hmaximize and vmaximize functions are, obviously, completely dual,
except that hmaximize uses Conf.bwidth when adjusting for a boundary,
while vmaximize uses cc-bwidth (correctly IMHO).
Also, it seems that
On Jan 05 14:50:21, h...@stare.cz wrote:
On Jan 04 23:27:48, h...@stare.cz wrote:
Here's some more cleanage for cwm:
the hmaximize and vmaximize functions are, obviously, completely dual,
except that hmaximize uses Conf.bwidth when adjusting for a boundary,
while vmaximize uses cc-bwidth
Hi,
Here is my kernel diff to expand socket splicing to UDP. The
advantage for relaying applications is that they can forward the
data without copying it to user space. Currently relayd uses socket
splicing for TCP connections only.
The idea of my implementation is to merge the code relevant
Hi
Here is a diff for all but one of the unknown devices for the VIA VX900
chipset. A few questions:
1. Some devices were already listed as for the VX800, should these be
changed to identify as say VX800/VX900? And same for some support chips
that have been integrated into the VX900 - the
On x86:
$ /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 5 blocks x 16384 bytes
fs block shift 2; part offset 63; inode block 112, offset 3496
master boot record (MBR) at sector 0
partition 3: type 0xA6 offset 63
Below is a diff that enables cwm to maximize a window
in a given direction (left / right / up / down) only.
Only left/right is implemented actually; I want to make sure
this isn't completely wrong before writing up the other half
(which will be dual of course).
The motivating situation for me is
Future events year should be 2013.
--
James Turner | 0x560B0C49
--- events.html.origSat Jan 5 14:53:23 2013
+++ events.html Sat Jan 5 14:52:15 2013
@@ -38,7 +38,7 @@ like-minded people.
h2Future events:/h2
-h32012/h3
+h32013/h3
ul
listronga name=bsddayeu2013/a
On Sat 2013.01.05 at 14:50 +0100, Jan Stary wrote:
On Jan 04 23:27:48, h...@stare.cz wrote:
Here's some more cleanage for cwm:
the hmaximize and vmaximize functions are, obviously, completely dual,
except that hmaximize uses Conf.bwidth when adjusting for a boundary,
while vmaximize uses
