The Mandriva 2007.1 release is coming up. It will be a very good update for 2007.0 release, with a lot of bug fixes, new software. But as awlays there is still be some caveats: The KDE team has decided for you What Good is: a large, and impressionnant "Mandriva" in the kicker :

Yes That's using some space. And the kicker height is "small".

Most people change the size of the kicker to gain place to "large":

• the 4-virtual screen is 2x2, so less large
• the systray use two lines too, so 2x3 icones instead of 6 icons

So let's change the height of kicker:

Amazing! Does the KDE team try other configuration than theirs own? Does they even use KDE ? Perhaps for forcing us to switch to gnome ?

Let's correct this fu**ing configuration:

edit

 /etc/kderc

and change the default directory to /usr which contains a real KDE configuration.

New computer to install, new error with AD. No problem, that's my job.

Failed to set servicePrincipalNames. Please ensure that the DNS domain of this server matches the AD domain, Or rejoin with using Domain Admin credentials.

Like last year, when I tried to deploy windows 2003, I got problems only resolved with an non public patch from Microsoft

One more day spent to use the internal KDC from AD with NFS v4, without success.

It seems that the "net" command from samba 3.0.22 add a SPN in uppercase, I fixed that but it isn't suffisant to be able to use the SPN.

More generally, is seems that adding some SPN in AD isn't successful, even for CIFS:

for i in $(klist -k -e |cut -f5 -d' ') ; do kinit -k $i 2>/dev/null || echo $i BAD; done

for i in $(klist -k -e |cut -f5 -d' ') ; do kinit -k $i 2>/dev/null && echo $i OK; done

gives that only HOST/hostname_nonfqdn@REALM is working...

enctype is my nightmare.