Blog de Alejo

http://www.baselinemag.com/article2/0,1540,2082922,00.asp

In November, MySpace, for the first time, surpassed even Yahoo in the number of Web pages visited by U.S. Internet users, according to comScore Media Metrix, which recorded 38.7 billion page views for MySpace as opposed to 38.05 billion for Yahoo.

The bad news is that MySpace reached this point so fast, just three years after its official launch in November 2003, that it has been forced to address problems of extreme scalability that only a few other organizations have had to tackle.

The result has been periodic overloads on MySpace’s Web servers and database, with MySpace users frequently seeing a Web page headlined “Unexpected Error” and other pages that apologize for various functions of the Web site being offline for maintenance.

http://www.artima.com/intv/dry.html

All programming is maintenance programming, because you are rarely writing original code. If you look at the actual time you spend programming, you write a bit here and then you go back and make a change. Or you go back and fix a bug. Or you rip it out altogether and replace it with something else. But you are very quickly maintaining code even if it’s a brand new project with a fresh source file. You spend most of your time in maintenance mode. So you may as well just bite the bullet and say, “I’m maintaining from day one.” The disciplines that apply to maintenance should apply globally.

http://www.apple.com/hotnews/thoughtsonmusic/

With the stunning global success of Apple’s iPod music player and iTunes online music store, some have called for Apple to “open” the digital rights management (DRM) system that Apple uses to protect its music against theft, so that music purchased from iTunes can be played on digital devices purchased from other companies, and protected music purchased from other online music stores can play on iPods.

http://www.37signals.com/svn/posts/272-control-vs-communication

Every once in a while we get an email from a customer asking about how permissions work with our products. They’re almost always asking how to prevent someone from doing something. “How do we prevent someone from posting a message or adding a to-do or downloading a file? How can we make our project site read only except for a select few?”

When we set out to build Basecamp we decided that it was going to be about communication, not control. It is our belief that when you collaborate with trusted parties it’s important for people to be able to communicate any way they see fit. Preventing someone from saying or doing something often breaks these free flowing communication channels and introduces miscommunication or silence—two cancers of collaboration.

No hay que ser agricultor para saber que una buena cosecha requiere de buena semilla, buen abono y riego constante. También es obvio que quien cultiva la tierra no se impacienta frente a la semilla sembrada, halándola con el riesgo de echarla a perder, gritándole con todas sus fuerzas: ¡Crece, por favor!

Hay algo muy curioso que sucede con el bambú japonés y que lo transforma en no apto para impacientes: siembras la semilla, la abonas, y te ocupas de regarla constantemente.

Durante los primeros meses no sucede nada apreciable. En realidad,
no pasa nada con la semilla durante los primeros siete años, a tal punto que, un cultivador inexperto estaría convencido de haber comprado semillas infértiles.

Sin embargo, durante el séptimo año, en un período de sólo seis semanas la planta de bambú crece ¡mas de 30 metros! ¿Tardó sólo seis semanas crecer? No, la verdad es que se tomó siete años y seis semanas en desarrollarse.

Durante los primeros siete años de aparente inactividad,
este bambú estaba generando un complejo sistema de raíces
que le permitirían sostener el crecimiento, que iba a tener después de siete años.

Sin embargo, en la vida cotidiana,
muchas veces queremos encontrar soluciones rápidas y triunfos apresurados, sin entender que el éxito es simplemente resultado del crecimiento interno y que éste requiere tiempo.

De igual manera, es necesario entender que en muchas ocasiones
estaremos frente a situaciones en las que creemos que nada está sucediendo.

Y esto puede ser extremadamente frustrante.

En esos momentos (que todos tenemos), recordar el ciclo de maduración del bambú japonés y aceptar que “en tanto no bajemos los brazos” ni abandonemos por no “ver” el resultado que esperamos, sí está sucediendo algo, dentro nuestro…

Estamos creciendo, madurando.

Quienes no se dan por vencidos, van gradual e imperceptiblemente
creando los hábitos y el temple que les permitirá sostener el éxito
cuando éste al fin se materialice.

Si no consigues lo que anhelas, no desesperes…
quizá sólo estés echando raíces…

Autor desconocido

Hola!

Hace menos de dos semanas contraté el servicio de cablemodem flash internet 600k. En mi casa tengo una lan con varias pcs (yo, mi viejo, mi hermana) por lo que puse una vieja pentium como router con linux (dado que el modem que me dieron no rutea), y un MRTG con el snmpd para medir el uso de la conexion. Al cabo de unos dias veo que en el MRTG la interfaz de red en la que esta conectado el modem tiene un promedio de 30 Kilobytes/s de bajada, pero la interfaz de red que esta conectada al switch tiene un promedio de menos de 1 kbyte por segundo de salida. En el router no tengo ningun servicio o programa funcionando excepto lo minimo indispensable para hacer funcionar NAT. No hay un apache, ni ningun otro servicio que pueda estar usando la conexion.

Al cabo de un par mas de dias cuando logre encontrarme algo mas de tiempo y ganas para usar el tcpdump, encontre algo muy extraño: hay un flood de paquetes ARP entrando por la placa de red:

12:24:14.378360 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: arp who-has 201.212.81.63 tell 201.212.81.1
12:24:14.378829 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 201.212.81.191 tell 201.212.81.1
12:24:14.380383 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.127.189.160 tell 200.127.189.1
12:24:14.384210 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.122.80.235 tell 200.122.80.1
12:24:14.384539 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 201.212.201.247 tell 201.212.201.1
12:24:14.384821 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.127.30.212 tell 200.127.30.1
12:24:14.386023 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.127.62.101 tell 200.127.62.1
12:24:14.391857 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 201.212.205.214 tell 201.212.205.1
12:24:14.395486 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.127.127.225 tell 200.127.127.129
12:24:14.399138 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.127.50.239 tell 200.127.50.1
12:24:14.400025 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 201.212.145.211 tell 201.212.145.1
12:24:14.400646 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 201.213.7.80 tell 201.213.7.1
12:24:14.400976 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 201.212.45.44 tell 201.212.45.1
12:24:14.401996 00:01:5c:23:63:82 > ff:ff:ff:ff:ff:ff, ethertype ARP (0×0806), length 60: arp who-has 200.122.80.158 tell 200.122.80.1

Y no solo eso, estas son las estadisticas:


# tcpdump -vvvne host ! 192.168.2.9 > arp-flood.txt

# cat arp-flood.txt | grep arp | grep 12:24:18 | wc -l
306
# cat arp-flood.txt | grep arp | grep 12:24:19 | wc -l
307
# cat arp-flood.txt | grep arp | grep 12:24:20 | wc -l
309
# cat arp-flood.txt | grep arp | grep 12:24:21 | wc -l
316
# cat arp-flood.txt | grep arp | grep 12:24:22 | wc -l
340
# cat arp-flood.txt | grep arp | grep 12:24:23 | wc -l
312
# cat arp-flood.txt | grep arp | grep 12:24:24 | wc -l
321
# cat arp-flood.txt | grep arp | wc -l
3884
# cat arp-flood.txt | wc -l
3906

Como se pueden imaginar, 192.168.2.9 es la direccion de mi pc en la lan y al router me conecto por ssh.

Buscando en internet encontre esto:

http://lists.debian.org/debian-user/2001/06/msg01689.html

En fin, alguien me puede decir que esta pasando o que puedo hacer ?

Hi!

Today, in a friendly 3-hour long meeting, the location of the Debian annual conference for 2008 was chosen, and it will be the city of Mar del Plata, Argentina [1].

The estimated dates are the second and third weeks of August, 2008. Which means that this will be the first DebConf to take place in winter.

The other group that participated in the election was the team from Venezuela, who presented a very good proposal as well. Choosing between both options was quite difficult. We do hope to have DebConf hosted in Venezuela in the future.

A webpage about the future conference is currently in preparation. In the meantime, to find more information about the chosen venue, you can visit the proposal’s webpage [2].

DebConf is the Debian Project’s developer conference. In addition to a full schedule of technical, social and policy talks, DebConf provides an opportunity for developers, contributors and other interested people to meet in person and work together more closely. It has taken place annually since 2000 in locations as varied as Canada, Finland and Mexico.

DebConf is preceded by DebCamp, which is a smaller, less formal event that gives an opportunity for group work on Debian projects. Between both events, DebianDay takes place. DebianDay is a short conference aimed at Debian users, and others interested in learning more about free software.

[1]: http://en.wikipedia.org/wiki/Mar_del_Plata
[2]: http://wiki.debconf.org/wiki/Argentina/Mar_del_Plata

–
Love,
Margarita Manterola