• Installeer wpa-supplicant

$ sudo aptitude install wpasupplicant

• Controleer dat je draadloze netwerkkaart goed ondersteund wordt. Door onderstaande commando's uit te voeren, zou je netwerkkaart moeten herkend zijn. Bij errors => verder zoeken om draadloze netwerkkaart te configureren

$ iwconfig && iwlist scan

• Ga naar /etc/network/interfaces en pas de code voor jouw draadloze netwerkinterface aan:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <YOUR_SSID_HERE>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <YOUR_KEY_HERE>

auto eth1

• Jouw netwerkkaart (kan ook wlan0, rausb0, ra0, ... zijn)

iface eth1 inet dhcp

• Een IP-adres wordt geleverd door de DHCP-server

wpa-driver

• Dit is de WPA-driver voor jouw kaart. wext is een generische driver die toepasbaar is als je met ndiswrapper werkt. Laat dit standaard staan. Je kan ook andere drivers selecteren

* hostap = Host AP driver (Intersil Prism2/2.5/3)
* atmel = ATMEL AT76C5XXx (USB, PCMCIA)
* wext = Linux wireless extensions (generic)
* madwifi = Atheros
* wired = wpa_supplicant wired Ethernet driver

wpa-ssid

• Jouw network SSID (zonder quotes!)

wpa-ap-scan

* 1 = Broadcast van ESSID
* 2 = Verborgen broadcast van ESSID

wpa-proto

* WPA = WPA
* RSN = WPA2

wpa-pairwise & wpa-group

* TKIP = TKIP encryptiealgoritme als onderdeel van de WPA standaard
* CCMP = AES encryptiealgoritme als onderdeel van de WPA2 standaard

wpa-key-mgmt

* WPA-PSK = Authenticatie van voorafgesproken sleutel (zie verder!!!)
* WPA-EAP = Authenticatie via een 'enterprise authentication server'

• Nu moeten we nog onze WPA key omzetten naar een hash waarde zodat deze niet letterlijk blijft staan in onze config file

$ wpa_passphrase <your_essid> <your_ascii_key>

• Dit levert zoiets als

network={
   ssid="test"
   #psk="12345678"
   psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab15bbc6c52e7522f709a
}

• De hex_key waarde die je naast psk vindt, moet je onder wpa-psk zetten van het /etc/network/interfaces bestand
• Herstart je netwerk

$ sudo /etc/init.d/networking restart

Choosing a Grub background image

• You can pick an image yourself, or you can use one of the default Grub images:
  

  $ sudo aptitude install grub2-splashimages

• Once installed, the images are located in the /usr/share/images/grub folder

Installing splash Images

• Check your version of Grub (this blogpost was tested with Grub 1.99):
  

  $ grub-install -v

• Open /etc/default/grub with a text editor an add the following line:
  

  GRUB_BACKGROUND=/path/to/your/image 

• Update GRUB to incorporate the image into the menu:

$ sudo update-grub

Changing text colors

• To add menu_color_normal and/or menu_color_highlight values when using a splash image
• Open /etc/grub.d/05_debian_theme as root
• Find the following lines:

if [ -z "${2}" ] && [ -z "${3}" ]; then
    echo "  true"
fi

• Change the entry to the following, replacing 'color1' and 'color2' to the desired colors. Leave /black as is!

if [ -z "${2}" ] && [ -z "${3}" ]; then
    # echo "  true"
    echo "    set color_highlight=color1/color2"
    echo "    set color_normal=color1/black"
fi

• Save the file and run update-grub

Installatie Samba

• Installatie pakket

$ sudo aptitude install samba

• Ga naar /etc/samba/smb.conf en pas volgende wijzingen toe:
• Toegang tot werkgroep:

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MSHOME

• Netwerknaam computer:

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

• Sharen van de home folder:

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username
[homes]
   comment = Home Directories
   browseable = yes
 
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.  Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S
 
# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
   writable = yes

• Toevoegen gebruiker aan SMB PASSW DB:

$ sudo smbpasswd -a jochus
New SMB password:
Retype new SMB password:

• Herstart Samba

$ sudo /etc/init.d/samba restart

Installatie SMBFS

• Verder wil ik ook mijn windows-server data schijf kunnen mounten. Er zijn hiervoor 2 mogelijkheden. Ofwel gebruik je een commandline tooltje als ''smbclient'', ofwel ga je data schijf mounten alsof het echte harde schijven zijn
• Installeer smbfs

$ sudo aptitude install smbfs

• Om andere gebruikers de map te kunnen mounten, moeten we deze ook rechten geven

$ sudo chmod u+s /usr/bin/smbmnt /usr/bin/smbumount

• Maak een mount point aan

$ sudo mkdir /mnt/data

• Om aan de schijf te kunnen geraken moeten we inloggen met Windows credentials

$ sudo nano /etc/samba/user

• Vul in

USERNAME
PASSWORD

• Voor de veiligheid

$ sudo chmod 0600 /etc/samba/user

• Voeg aan /etc/fstab het volgende toe:

//server/share   /mnt/data   smbfs   credentials=/etc/samba/user,rw,uid=bob   0   0

• Mounten gaat nu via:

$ mount /mnt/data

I just tested the "new" (already in Facebook since June 2011) Graph API of Facebook. Using the RestFB Java client (http://www.restfb.com/), I was able to get a list of my friends, update my status, ... etc, etc. For testing, I retrieved an access token using the Graph Explorer tool (https://developers.facebook.com/tools/explorer).

Java project setup (pom.xml)

<project>
	<modelVersion>4.0.0</modelVersion>
	<groupId>be.jochenhebbrecht</groupId>
	<artifactId>facebook-test</artifactId>
	<version>1.0.0-SNAPSHOT</version>
 
	<dependencies>
		<dependency>
			<groupId>com.restfb</groupId>
			<artifactId>restfb</artifactId>
			<version>1.6.11</version>
		</dependency>
	</dependencies>
</project>

Getting a list of friends

import com.restfb.Connection;
import com.restfb.DefaultFacebookClient;
import com.restfb.FacebookClient;
import com.restfb.types.User;
 
public class FacebookTest {
 
	private static final String MY_ACCESS_TOKEN = "##REPLACE_ME##";
 
	public static void main(String[] args) {
		FacebookClient facebookClient = new DefaultFacebookClient(MY_ACCESS_TOKEN);
		Connection<User> myFriends = facebookClient.fetchConnection("me/friends", User.class);
 
		for (User u : myFriends.getData()) {
			System.out.println(u.getName());
		}
        }
}

Updating my status

import com.restfb.DefaultFacebookClient;
import com.restfb.FacebookClient;
import com.restfb.Parameter;
import com.restfb.types.FacebookType;
 
public class FacebookTest {
 
	private static final String MY_ACCESS_TOKEN = "##REPLACE_ME##";
 
	public static void main(String[] args) {
		FacebookClient facebookClient = new DefaultFacebookClient(MY_ACCESS_TOKEN);
		FacebookType publishMessageResponse = facebookClient.publish("me/feed", FacebookType.class, Parameter.with("message", "Test from Graph API"));
		System.out.println("Published message ID: " + publishMessageResponse.getId());
        }
}

Problem

The following error appeared in the error.log of my Kerio Mail server:

Cannot access message 0000000x in folder ~<a href="mailto:someone@somedomain.com">someone@somedomain.com</a>/INBOX

Solution

In most of the cases, Kerio Mail Server is smart enough to repair the errors by itself. But in some cases, it just doesn't work. Manual repair is required.

• Make sure all your clients are disconnected from the server - so you won't have any active sessions left
• Go to the folder: /store/mail/domain/user/folder_name/
• Rename the file index.fld to index.fld.bad
• Now connect again with your user. Kerio Mail Server will see the index file is missing and it will automatically rebuild it. This step can take a while for very large mail folders!

Problem

When you're having multiple users on your windows installation, the system will always ask you which user should be used to login. But in some cases, you always want to login automatically with the same user (because the 2nd, 3rd, ... user are almost not used). How to achieve the automatic login?

Solution

Go to:

• Start > Run
• Type: control userpasswords2
• Unhceck: Users must enter a user name and password to use this computer
• Press OK
• The system will ask you now for the default username and password (2x). This user will be used to automatically log in