Чук Норрис © co-worker Arnaud

Чертыре черненьких чумазеньких чертенка чертили черными чернилами changelog. (C) мы с ykaliuta

убивайfs (orig).

andy_shev on elderly women:
No pussy, no face, no shape.

My babe wakes up.

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.99.5 (XXX) #92: Tue Feb 10 11:25:35 EET 2009
        ash@dew:/home/ash/work/nbobj-arm/sys/arch/evbarm/compile/XXX
total memory = 128 MB
avail memory = 122 MB
mainbus0 (root)
cpu0 at mainbus0: ARM1176J-S r0p4 (ARM11J core)
cpu0: DC enabled IC enabled WB disabled EABT
cpu0: 32KB/32B 4-way Instruction cache
cpu0: 32KB/32B 4-way write-back-locking-C Data cache
Initializing kernel page counter /dev/kp0
437 paged used by kernel
boot device: 
root device: _

My tightly-coupled memories are hereafter uncached.

Following numerous requests from co-workers (andy_shev), here goes a quote of yesterday, actually, but entertaining nonetheless:

No internet -- yes lunch! © andy_shev

Verbosed version of a log
© andy_shev

P.S. Инкризнем нашу вербозность, да.

[color]
        ui = auto

when put to ~/.gitconfig brings a new meaning to life.

Actually, it's the best one I've had filed against me.

Summary: 'Satanic' is a not so good word in version string

© andy_shev

Absolutely, unmistakably.

For the record, future generations and sighup. If you ever have to debug ld.so (or whatever it is that the runtime loader is called in your system) and its debug_printf() fails, repeat after me:

#define __q(x) x, strlen(x)
write(2, __q("debugging disabled by Perkele\n"));

and you shall be saved.

via captain_hell

Terms and references, used in this post:

• scrum -- an irrititerative incremental process of software development


• for those who care about... -- a post in debian-devel-announce immediately following a plea from ubuntu people, which I don't seem to be able to find in 5 seconds

Стоил ли переезд в Финляндию того, чтобы услышать от начальника "с сегодняшнего дня дверь в проектную комнату должна быть постоянно закрыта, потому что из-под моего носа куда-то исчез лаптоп" в терминах "хуйня" и "выебу" (нет, я работаю не на лесопилке)? Ни одного даже отдаленно похожего случая с предыдущих работ не вспоминается. Это я не риторики ради, а по причине недостатка жизненного опыта.

What I came to like about netbsd is that there's still so many things to be done there. Another thing is that is absolutely never fails to amaze me with what miracles might lie under the surface.

In reference to this.
If a build tool is required to access configuration variables for any reason, it must be an API-conforming tool since non-API conforming tools cannot access configuration variables.
© TET Programming Guide

bad_opcode, y0.

static void
BadOp (void)
{
  /* Throw away prefixes and 1st. opcode byte.  */
  codep = insn_codep + 1;
  oappend ("(bad)");
}

from the GNU debugger

we have a dust problem!

Just found out that one of our (slind) recent night builds failed to the point of destroying the repository on the main server (that is, rsyncing up an empty repository). Which in itself is not much of a problem, but still sets it several days back and not to mention the bandwidth. This, however is not why we're here.

Investigation of the problem that caused said failure was much shorter than I dreaded and the problem itself turned out to be pretty simple. Each time the build starts, one of the scripts involved downloads a database file, which is most important for the build infrastructure. It used to do so by issuing 'curl $URL'. Pretty simple, but not safe against network and/or server failures. Then, one of our engineers decided to make it safer by patching it like this (these snippets are simplified, see below for original code):

- curl $URL
+ curl $URL || die "Failed to download a very important file!"

...which is a nice try, except that curl will always exit with 0 code regardless of HTTP response code, unless given -f/--fail option. IOW, we still have incorrect code, but this one gives us false sense of security.
And of course, if -f was there the night before, the repository wouldn't have been destroyed at all.

P.S. And the commit in question is here.