Re: cwm(1) avoid keygrab on rebinding (r)cycle

2010-01-30 Thread Okan Demirmen
On Sat 2010.01.30 at 20:23 -0500, Okan Demirmen wrote: > On Fri 2010.01.29 at 11:05 +0100, Christian Neukirchen wrote: > > Hi, > > > > Currently cwm(1) grabs the keyboard for M-Tab/MS-Tab cycling, which > > works well until you try to rebind these keys to, say, 4-Tab. I > > propose clearing the k

Re: cwm(1) avoid keygrab on rebinding (r)cycle

2010-01-30 Thread Okan Demirmen
On Fri 2010.01.29 at 11:05 +0100, Christian Neukirchen wrote: > Hi, > > Currently cwm(1) grabs the keyboard for M-Tab/MS-Tab cycling, which > works well until you try to rebind these keys to, say, 4-Tab. I > propose clearing the keygrab if any modifier is released (this kind of > "breaks" the cur

Re: UBC?

2010-01-30 Thread David Gwynne
On Sun, Jan 31, 2010 at 09:41:14AM +1000, David Gwynne wrote: > pmap_enter in this situation should fail, not panic. the error would be > handled properly as the stack unwinds up to ami_allocmem. > > i can change ami_allocmem to take a NOWAIT etc as an argument rather than > just assume it, so c

Re: UBC?

2010-01-30 Thread David Gwynne
pmap_enter in this situation should fail, not panic. the error would be handled properly as the stack unwinds up to ami_allocmem. i can change ami_allocmem to take a NOWAIT etc as an argument rather than just assume it, so callers with process context (like the sensor refresh shown below) can slee

Re: UBC?

2010-01-30 Thread Damien Miller
On Sat, 30 Jan 2010, Bob Beck wrote: > >> > http://professionalsuperhero.com/ > >> > >> That link isn't in iCal format; I can't open it in my scheduler. > > > > You need a pluggable scheduler system, like what has been proposed > > for Linux. > > > > Now you're just taunting me to try to make me

LIFE GOOD NEWSLETTER no 60

2010-01-30 Thread Akis Angelakis
Acapgt]r v_ker jai v_koi, Sto sumgll]mo aqwe_o ejvq\fy tgm eucmylos}mg lou cia to emdiav]qom, tg sulletow^ jai ta jak\ sar k|cia. Sar ]wy emdiav]qomta bimte\jia pou ha sar d~soum d}malg, ]lpmeusg jai paqaj_mgsg. E}wolai ma apoka}sete tir tqeir istoq_er jai ta b_mteo. Le vikijo}r waiqetislo}r,

Re: UBC?

2010-01-30 Thread Bob Beck
Ooooh. nice one. Obviously ami couldn't get memory mappings and freaked out. While not completely necessary, I'd love for you to file that whole thing into sendbug() in a pr so we don't forget it. but that one I need to pester krw, art, dlg, and maybe marco about what ami is doing. note that the

/etc/weekly

2010-01-30 Thread Lars Nooden
Below is some pseudo code to illustrate some options for the weekly script. It's not meant as a solution but as a starting point for discussion to Ted Unangst's request regarding laptops and desktops and Nick Holland's request that ill-considered babble be accompanied by code. Using at to schedul

Re: UBC?

2010-01-30 Thread Jeff Ross
Bob Beck wrote: My question was motivated by noticing that repeated accesses to a fairly large file (~ .75 Gb) during a debugging session were slow. It seemed like the system was re-reading the file from the disk when it felt like it ought to be sitting in the buffer cache. A little experimenting

[PATCH] Wrong SIGCHLD handling in ripd.

2010-01-30 Thread Christiano F. Haesbaert
Hi there, I've spotted the following in ripd.c signal_set(&ev_sigchld, SIGINT, main_sig_handler, NULL); should be SIGCHLD correct ? main_sig_handler handles it with check_child(); That line is there since rev 1.1, so looks like SIGCHLD was never handled. Index: ripd.c =

Re: UBC?

2010-01-30 Thread Bob Beck
>> > http://professionalsuperhero.com/ >> >> That link isn't in iCal format; I can't open it in my scheduler. > > You need a pluggable scheduler system, like what has been proposed > for Linux. > Now you're just taunting me to try to make me explode. Probably because I henninged your wall.. Did t

Re: Why ripd explicitly adds a route to the rip's multicast address ?

2010-01-30 Thread Claudio Jeker
On Tue, Jan 26, 2010 at 01:53:40PM +, Stuart Henderson wrote: > On 2010/01/26 10:32, Christiano F. Haesbaert wrote: > > On Mon, Jan 25, 2010 at 10:27:42PM -0800, Philip Guenther wrote: > > > So, have you read the commit message that added that code? If you're > > > not sure what version that c