Skip to main content

stupid bug

while playing with some python binding for the silc toolkit that I am working on, I wasted a good half an hour on the most stupid assumption...bah..

not much else to report really

IPV6 Rfcs

for i in "1752 1809 1828 1881 1886 1887 1888 1924 1981 2450 2030 2080 2185 2283 2292 2365 2373 2374 2375 2401 2402 2406 2428 2450 2452 2454 2460 2461 2462 2463 2464 2465 2466 2467 2470 2471 2472 2473 2474 2491 2492 2497 2507 2508 2509 2526 2529 2545 2590 2675 2710 2711 2732 2740 2765 2766 2767 2851 2874 2893 2894 2921 2928 3019 3041 3053 3056 3068 3089 3111 3122 3142 3146 3162 3175 3177 3178 3226 3266 3306 3307 3314 3316 3363 3364 3484 3493 3513 3531"; do echo $i; wget http://www.ietf.org/rfc/rfc$i.txt; done

<p>

hazey

Built the new 2.4.23 kernel with ipsec and NAT-T support. Took me too damn long anyhow..like anything else?

Alsa

mmh..add works quite ok..but only on the specific ALSA apps (alsaplayer for example)..it surely gives a crappy sound with xine or xmms. Need to dig a little deeper..

toying around

Installed a 2.6-test11 kernel on the powerbook:

rsync -avz --delete source.mvista.com::linuxppc-2.5-benh .

Had to use Ben's tree, since the old Radeon FB in the stock kernels breaks for me, whereas the new one which is only in the linuxppc tree breaks. Here is the config file I used.

So far everything seems to be working smoothly. It does appear to be a bit more responsive.

On another side note, I've packaged silky 0.4.1 (only the sparc build is missing ATM)

_ ..I'm so afraid I did a mistake 40 minutes ago.._

No Content Found

"""

As a programmer, I know you shouldn't trust _any software. Software is at best a faithful but bumbling zombie servant that ineptly performs your bidding. At worst, it's an evil zombie that wants to kill you and eat your brain. Neither kind of zombie should be trusted implicitly with your car keys or your cat._

"""