Beim FreeBSD German Documentation Project hat sich in
letzter Zeit einiges getan. Leider sind aber viele Leute
inaktiv geworden und so ist es mal wieder an der Zeit, nach
frischem Blut zu suchen. Ich weiss, dass viele helfen wollen
aber nicht wissen wie. Es ist relativ einfach. Du
sprichst/schreibst englisch gut bis sehr gut? Dann bist du
herzlich willkommen. Wer Interesse an einer Mitarbeit hat,
ist eingeladen, bei freenode im channel #freebsd-doc.de
vorbeizuschauen oder sich bei mir direkt zu melden (wo man
mich findet, sollte allgemein bekannt sein). Man muss also
kein Hacker sein, um dem Projekt etwas beizusteuern. Es waere
sehr schade, wenn es weiter einschlaeft, Johann (jkois)
ist im Moment leider wieder so gut wie alleine mit allem.
Unsere aktuelle Site findest du hier .

So long..

A friend of mine Dennis Herrmann wrote a small howto
how you can use send-pr(1) with msmtp support,
Unfortunately in German, so I translate it here:

Who looked at the source of send-pr(1) will notice
that the most important functions are packed into
variables. Even the functionality for the mail agent

Of course we assume a working ~/.msmtprc. The rest is
easy, you just add

export GNATS_ADDR=FreeBSD-gnats-submit@freebsd.org
export MAIL_AGENT="${MAIL_AGENT:-/usr/local/bin/msmtp -f ${USER}/.msmtprc ${GNATS_ADDR}}"

to your ~/.zshrc or ~/.bashrc depending on your shell.
You also have to regard that not every shell is using
export to assign something to a variable. The first
variable is neccessary so the MAIL_AGENT knows where
to send the mail. Allowing this way would result in an
error by send-pr(1) and you have to rewrite everything
again. Would the variable be local in send-pr(1) we
wouldn’t have that problem!

The parameter -f of smtp in the second variable is
neccessary to ensure that your settings are really
used. But please remember that you also need your
~/.msmtprc if you want to send a pr as root!

Have fun

Lately I posted a lot about QT4/KDE4 now it’s time to post some private stuff.

I received a lot of mails in the last 3-4 weeks about what happened to me.
The answer is easy: First of all we had ports freeze from Oct 8 to Oct 22.
I also got bad news from my mother 3.5 months ago. My mom’s cancer is back.
It began 4 years ago with breast cancer, but she won the fight. Last year we
got the cancer diagnose and were really hard shocked. She had an operation and
got chemotherapy but never really recovered. 3.5 months ago in the next medical
checkup cancer was diagnosted in liver and kidneys. 3 weeks ago I got a call
from my dad that my mother is now in hospital because she can’t eat or drink
without vomiting. She got a feeding tube and the first 3-4 days it looked good a
we had a little hope that she will live. But two days ago I got another call
from my dad that my mother passed away on 20:32 (CEST). I knew it was only a
question of time and I am very sad about all this though realistically seen it
is better because she had a lot of pains. Now I hope that she looks from heaven
to my family from time to time. The funeral will be next Monday. So I need a bit
of distraction. I will spend time with my family over the weekend and a bit on
FreeBSD so I can divert myself a bit.

So long..

The KDE team released KDE-4.1.2 two days later than planned.
We are in a ports slush and can’t update KDE until it’s
ended. If you can’t wait to get KDE 4.1.2, you can now
download it from our area51 repo. The full KDE changelog
can be seen here. We removed FAM support completely.
This gives a bit more speed and the program starts faster.
Thanks to Kris Moore (PC-BSD) who tested this patchset,
we also removed the KDE debug modues.

And a tweak reported by from Hannes Hauswedell.
He experience high CPU-Usage by kded4 and slowdowns
with Konqueror as Filebrowser, he recommends you
try radically lowering the DirWatch-rate of kded4
by adding the following to your
$HOME/.kde4/share/config/kdedrc:

[DirWatch]
PollInterval=60000

This is explained here.

So, if you want to get the port, please read following
instructions:
https://kf.athame.co.uk/access.php

Note: you also need to first update Qt4 to
4.4.2