I’m gonna explain you how to do this, in this tutorial I’ll use my windows box as the “master” as it has the best soundcard, keyboard and such of the two computers. Let’s starts:

Keyboard and Mouse

Keyboard and Mouse are probably the easiest part of this – Synergy is a small utility that allow you to share a mouse/keyboard between multiple computers, download the binary for windows and launch it, there set the computer as a server, and click configure. Set two screens, for the name use the hostnames of each computers, then create two links like in the following screenshot:

Don’t forget to create the two links ! Or when you’ll switch one the second computer, you will not be able to go back

Then on our archlinux box, do the following:

That will launch the synergy client and connect to your server and voila, you can use only one keyboard/mouse between the two computers. Don’t forget to setup autostart in synergy on Windows, and add the client command in the Gnome Session Manager. Now it’s time to take care of the sound.

Using the sound over the network

Here is the hard part, setting up the sound over the network is a long task. First, download pulseaudio for windows here. Extract the thing in a folder like C:\pulseaudio then create a config file named default.pa containing the following:

And put it in this folder. The first line tells pulseaudio to listen to all connections on the local network while the second line allow us to output sound. Next step is to double-click on pulseaudio.exe – Don’t paye attention to the warnings and go to C:\Users\<username> on Vista or C:\Document And Settings\<username> on previous windows then copy the .pulse-cookie here ( create by pulseaudio.exe ) to /etc/pulse-cookie on your linux box ( using WinSCP for example ). You can now add pulseaudio.exe to windows start ( there are lots of softs out there allowing it, just use whatever you want ) and we’re done with the windows box.

Now for our archlinux, we need to works on lots of things, let’s start on installing/configuring pulse:

Then add to your rc.conf

Avahi is needed for network communications in pulse. Now change our cookie modes:

And finally setup pulseaudio by editing /etc/pulse/client.conf:

We are now done with pulse itself. Don’t forget to add your users to the pulse-access group.
Let’s configure ALSA to use Pulse by editing /etc/asound.conf ( create it if it doesn’t exists ) and add the following lines:

With all that, you should be ok, try launching mplayer using the -ao=alsa flag and you should hear the sound on your windows box

I took the latest archboot, and within 30 minutes I was booting on my shell, archboot using the 2.6.28 kernel, most of the hardware was working, I plugged to the internet and started installing xorg, gnome and gdm. Most people are saying that GNOME on the EEE is useless because of the screen size, but with a little tweaking, you can get really nice results. Here is what I got after working for several hours:

Once gnome installed, I had somes issues with Fn-Keys preventing me to set the sound or luminosity without overlays bugs and such, to prevent this, install the “acpi-eee” package from aur, add eee to the DAEMONS variable in rc.conf and you’ll be ready to go.

So, now GNOME isn’t really pretty when just installed, so we’re gonna take care of that. First install the xf86-video-intel package from extra, then install compiz-fusion. You’ll need to add the following lines to the “Device” section of your xorg.conf file:

Then add fusion-icon inside the Gnome Session Manager. You can now look on gnome-look.org for themes, I use the GNOME colors backgrounds and icons.

You should also look toward the “splashy” package, it adds a nice splash when booting arch and the themes are easily editable.

Update: Info about the wifi
Using the wifi is not something very hard, first plug your EEE using an ethernet cable, then with yaourt, fetch the aur package named rt2860 and install NetworkManager with the corresponding applet for your WM, and you should be ok.