I bought my picturebook off of ebay and it came with winblows 2000 pre-intalled. There's a number of documented ways to install GNU/Linux on the picturebook, but luckily I had a friend with the official VAIO CD-ROM so I could boot from that ( after setting the boot priority in the BIOS ).
Taking a hint from this website, when I booted the gentoo Live-CD I passed the kernel options ide2=0x180,0x386 which ensured it saw the CD-ROM ok.
I did a stage 3 install from the gentoo universal 2004.0 ISO and added the pre-built packages.

processor	: 0
vendor_id	: GenuineTMx86
cpu family	: 6
model		: 4
model name	: Transmeta(tm) Crusoe(tm) Processor TM5600
stepping	: 3
cpu MHz		: 661.671
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr cx8 sep cmov mmx longrun lrti
bogomips	: 1317.27

Here's a few of the config files i'm currently using:-
gentoo-sources-2.6.14
x.org config
modules.conf

I've currently got a problem with my X.org config which only seems to allow me to run it in 8bpp :( Using the standard X.org driver gives me 80FPS according to glxgears, and the X.org ATi driver gives 140FPS. However, neither seem to give opengl support. Tried the official ati-drivers and got errors about it not finding a card?!

Just installed the longrun program and re-compiled the kernel with cpuid enabled, so I can now change the CPU's performance on the fly!

atomant root # longrun -l
# %   Mhz  Volts  usage
  0   300  1.300  0.297
 27   400  1.350  0.427
 63   533  1.400  0.612
 81   600  1.500  0.791
100   667  1.600  1.000

atomant root # longrun -p
LongRun: enabled
LongRun: Thermal Extensions (LTX): inactive
Current performance window: 0 to 100
Current performance level: 100
LongRun flags: performance

I got wifi running firstly using a LinkSys WPC54g card I already had. Due to Linksys ( or Broadcom ) not providing open source drivers, I used ndiswrapper which is quite a cool driver that uses the existing winblows drivers! Worked really well
However, maybe it's the card/chipset or maybe it's the driver, but there didn't seem to be a way to put the card into monitor mode ( much like an ethernet cards promiscuous mode ). This meant app's like kismet and airsnort wouldn't work.
So, I bought a NetGear WG511 and after a bit of playing around, and a few kernel rebuilds, I managed to get it working with the prism52 drivers in the 2.6 kernel.
I now have kismet running using source=prism52g,eth0,prism52

Although I normally use wifi in infrastructure mode ( ie with a basestation ), I recently had the vaio running in ad-hoc mode to a winblows PC to get to the 'net:-

atomant ~ # iwconfig
lo        no wireless extensions.

eth0      IEEE 802.11b/g  ESSID:"60br"  Nickname:"60br"
          Mode:Ad-Hoc  Frequency:2.437 GHz  Cell: C6:20:D8:91:15:7A
          Bit Rate:54 Mb/s   Tx-Power=31 dBm   Sensitivity=20/200
          Retry min limit:8   RTS thr:2347 B   Fragment thr:2346 B
          Encryption key:off
          Link Quality=214/0  Signal level=-42 dBm  Noise level=-111 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Played about with using the built-in camera as a CCTV...

atomant # cat /etc/modules.d/motioneye
alias char-major-10-250 sonypi
options sonypi minor=250 fnkeyinit=1 camera=1
alias char-major-81 videodev
alias char-major-81-0 meye
options meye gbuffers=32
atomant # modprobe meye
atomant # dmesg | tail -10
Sony Vaio Jogdial input method installed.
Sony Vaio Keys input method installed.
sonypi: Sony Programmable I/O Controller Driverv1.26.
sonypi: detected type1 model, verbose = 0, fnkeyinit = on, camera = on, compat = off, mask = 0xffffffff, useinput = on, acpi = on
sonypi: enabled at irq=11, port1=0x10c0, port2=0x10c4
meye: using 32 buffers with 600k (19200k total)for capture
PCI: Enabling device 0000:00:0b.0 (0010 -> 0012)
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
meye: Motion Eye Camera Driver v1.13.
meye: mchip KL5A72002 rev. 3, base fc104800, irq 9
atomant # lsmod
Module                  Size  Used by
meye                   31768  0 
sonypi                 24992  1 meye
prism54                57352  0 
firmware_class         10400  1 prism54
pcmcia                 29588  2 
yenta_socket           23496  2 
rsrc_nonstatic         13728  1 yenta_socket
pcmcia_core            54948  3 pcmcia,yenta_socket,rsrc_nonstatic
snd_ymfpci             60448  0 
snd_ac97_codec         83992  1 snd_ymfpci
snd_opl3_lib           11840  1 snd_ymfpci
snd_hwdep               9920  1 snd_opl3_lib
snd_mpu401_uart         8544  1 snd_ymfpci
snd_rawmidi            27264  1 snd_mpu401_uart
usbcore               137372  1 

Working on bluetooth support at the moment ...
As I'm using a wifi pc card, I'm not using the bluetooth pc card the VFK comes with. So, instead I'm using a Mavin Bluetooth USB dongle:

After boot I can run

/etc/init.d/hotplug start
/etc/init.d/bluetooth start

Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd 
Bus 001 Device 003: ID 054c:0056 Sony Corp. 
Bus 001 Device 002: ID 04cc:1122 Philips Semiconductors Hub
Bus 001 Device 001: ID 0000:0000  

root# hciconfig
hci0:	Type: USB 
	BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:0 acl:0 sco:0 commands:0 errors:0
root# hciconfig hci0 up
root# hciconfig
hci0:	Type: USB 
	BD Address: 00:09:DD:10:0C:AE ACL MTU: 192:8  SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:77 acl:0 sco:0 events:8 errors:0
	TX bytes:31 acl:0 sco:0 commands:8 errors:0

More to come...

Links