Don’t let me get me

Don’t let me get me

Never win first place
I don’t support the team
I can’t take direction
And my socks are never clean

Teachers dated me
My parents hated me
I was always in a fight
cause I can’t do nothin’ right

Everyday I fight a war against the mirror
I can’t take the person staring back at me

I’m a hazard to myself
Don’t let me get me
I’m my own worst enemy
It’s bad when you annoy yourself,
So irritating
Don’t wanna be my friend no more
I wanna be somebody else

I wanna be somebody else

L.A. told me
You’ll be a pop star
All you have to change
Is everything you are

Tired of being compared
To damn Britney Spears
She’s so pretty
That just ain’t me

So doctor, doctor—won’t you please prescribe me something?
A day in the life of someone else

Cause I’m a hazard to myself
Don’t let me get me (No)
I’m my own worst enemy
It’s bad when you annoy yourself,
so irritating
(Don’t want) Don’t want to be my friend no more
I wanna be somebody else

Don’t let me get me (Don’t let me)
I’m my own worst enemy (No)
Its bad when you annoy yourself
So irritating
Don’t wanna be my friend no more
I wanna be somebody else

So doctor, doctor—won’t you please prescribe me something?
A day in the life of someone else
Don’t let me get me

Ohhh, I’m a hazard to myself, yeah
Don’t let me get me
I’m my own worst enemy
Its bad when you annoy yourself
So irritating
(So irritating)
Don’t wanna be my friend no more
Don’t Don’t
Wanna be somebody else

Don’t let me get me (Don’t let) (Don’t let)
I’m my own worst enemy (Don’t let me get me)
Its bad when you annoy yourself (Its bad its so bad)
So irritating
Don’t wanna be my friend no more (How)
I wanna be somebody else
(Don’t let me get me) (Don’t let me get me).

LessWatts at Debconf8

I’m in Mar del Plata, Argentina, for the 8th Debconf, and just finished my talk.

First of all, I’ve heard about the special dedication the organization team put together before I got here, and I have to say it is really “putting a smile on your face“. There are small thoughtful details adding to the content: the bot in the saying who just arrived, what is the next talk, when the dinner is served; a souvenir and local guide in English – Super Cow Powers include – with some cultural and historical facts, places to go around, what to eat, some phrases in Spanish to help, and such. The streaming seems perfect, several volunteers and the people attending it demonstrate their appreciation to the organization and also help to keep the silence in the quite hacklab – right next to the video-audio station.

I talked about LessWatts, a project around many efforts and initiatives around power consumption in Linux. A year ago, when the project was launched, PowerTop was the tool and some documentation. It is impressive how much the project grew in just one year, how many other tools where added: BLTK(Battery Life Tookit), PPM(Power Policy Management) and others, and many many guides, documentation, tricks for development. Like:

  • Polling Avoid frequent, unnecessary polling
  • Race to Idle Save power by running at the highest speed
    Processors tend to be so good at saving power during idle, that often it’s better to go as fast as possible so that you can then be idle longer.
  • Turn devices off Open devices can prevent the system from entering power saving state
  • Group Timers Many programs use times, so group them to reduce idle wakeups.
  • Use large buffers Media playback requires a large buffer, large enough for a minute of audio or 20 minutes of video.
  • Optimize Sleep Duty Cycle It matters how frequently you go in and out of idle. Stay in idle for long periods of time. Avoid interrupting idle as much as possible.
  • Beware of high level languages High level languages are convenient tools to achieve results quickly and often have features to do complex things with minimal effort. However, be aware that some of these contructs are hard to implement and sometimes the runtime environment that implements the high level language does so using polling at a high frequency. When using high level languages such as Java*, Visual C#*, Python*, and Ruby, check the end result and try to avoid some of the more complex threading primitives. In addition, where you have a choice of runtime environment provider, evaluate different alternatives and versions.

There were some questions, which I was glad because I spoke too fast and were expecting more questions as I finished before I should. I was glad to see some developers asking for people to adopt PowerTop and BLTK as packages for Debian, everybody downloading, testing and some funny comments: “Now I will harm the environment again by opening my Firefox”. Of course, many “I would love my battery last longer”. Some nice ideas about areas to be researched and focus: swapping, booting, memory. The video for the talk will be available soon. And the always happy moment of giving t-shirts ) Funny coincidence, this was a special batch from the t-shirts we are doing at Intel for giving to people in conferences, and for my surprise this new ts provider uses the same logo as Debian.

I’m really glad I’ve came, and I think my difficult relationship with Debian may improving. Now I can just relax and enjoy my friends. I will post some pictures later.

Upgrade para WordPress 2.6

Da série “Só Jesus salva, o resto tem que fazer backup”:

Um dos problemas da impulsividade é a crença de que “não vai acontecer comigo”. Então por mais que digam que sempre é bom ler os changelogs antes de migrar mais de duas versões, esta destemida autora que vos escreve decidiu migrar do WordPress neo paleolítico 2.0 para o 2.6 sem muita enrolação. Pelo menos fiz backup….

Na versão 2.3, o WordPress inseriu o suporte a tags, o que eu achava que era o mesmo que categorias. Ainda não tive tempo de ver no que elas são diferentes, porque e qual melhor pra mim, só sei que no upgrade, o WordPress migrou minhas categorias, só que sumiu com os nomes e as descrições delas. Pelo menos manteve os relacionamentos entre os posts e as categorias…

Busca daqui, busca dali, e a solução “mais amigável” que eu encontrei foi editar as tabelas no PhpMyAdmin. Como não uso o PhpMyAdmin, o jeito foi relembrar como se fala com o Mysql e corrigir na unha mesmo. Pelo menos eu havia feito backup antes, então podia consultar que categoria era qual.

Passo a passo:

1)Faça backup – mysqldump -p nome_blog_db >

2)Atualize – Leia as instruções, rápidas (para usuários mais experientes ou que gostam de viver a vida perigosamente) ou detalhadas

3)Recupere as tabelas: antes do 2.3, a tabela que cuidava das categorias era wp_categor*. Agora é wp_term*: wp_terms, wp_term_taxonomy e wp_term_relationships – leia aqui para mais detalhes. Então, comparando as entradas do backup – tabela wp_categories:
| cat_ID | cat_name | category_nicename | category_description | category_parent | category_count |

| 1 | Momentos Musicais | mms | | 0 | 47 |

com a nova tabela wp_terms
| term_id | name | slug | term_group |
| 1 | | | 1 |

corrigimos a entrada:

mysql -u user -p
mysql> use nome_meu_blog
mysql> update wp_terms set name='Momentos musicais',slug='mms' where term_id=1;

4) Vá a página de gerenciar categorias – e se quiser atualize também a descrição.

4) Recupere seu usuário no site do WordPress e preencha um bug report )

Claro que vale lembrar que se você não entende de SQL, e não entendeu como eu consegui o prompt do Mysql, melhor optar pelo PhpMyAdmin, ou se decidir que é até divertido fazer umas destas de vez em quando e ler o manual de referência do Mysql.

Apesar disto tudo, devo dizer que o 2.6 está excelente, com muito mais recursos e melhor organizado: opção para fazer backup – no servidor, no seu computador ou enviar por mail; busca e instalação de pluguins melhorada; opções novas para publicar mídia; importar/exportar, e mais, e isto que não faz um dia que estou mexendo. Uma aplicação totalmente “web 2.0”…