I’m rebuilding my old desktop PC to a Linux file server. Lots of time has been sunk so far, probably should have used a more modern distro than Debian Etch, but I’ve made my bed.
Mistakes/Lessons so far:
- I wasted a few hours trying to solve why my self booting CD I’d downloaded and burnt wasn’t working….. So I re-burnt it (which requires a blank disk, so I’m not so sure what I did the first time), and it worked.
- I downloaded the i368 CD, yet the Linux Windows Installer was using the amd64. So wasted lots of time reading about that build target, as my AMD Sempron is the non-64 version, but decided to keep with the i386 target. So not to waste yet more bandwidth (on my limited plan)
- I installed Gnome UI then, decided to redo it, with no desktop installed. So I’ve had to hero out some issues that there are now UI tools to solve.
- Spent ages trying to work out why ping’s worked, yet apt-get to ftp.nz.debian.org would resolve as 18.104.22.168. This turns out to be the result of an DNS query with an IPv6 AAAA record present, causing the DNS server to fail. reviewing every /etc/ file I finally found resolve.conf and corrected the DNS servers being used. My simple ADSL route was the problem, and resolve.conf was point to this, as at install time, DCHP worked, so I didn’t get the chance to static setup as I want. Especially as this is a server. So had set the correct DNS servers in the /etc/network/interfaces, but didn’t solve it.
- Throughout all this having working internet, and the MacBook to read lots of how-to’s was so good!
- Once I got the Ethernet working, I started on the “how to get the wifi working” game.
- I mastered apt-get, and git, pulled down the latest Linux Wireless testing branch, and rebuilt with the correct drivers so my wifi NIC should work. Much fluffing around with Debian package build I got my new kernel installed. Hours and hours of wifi configuration fluffing around I found I should be configuring wpa-supplicant, and even more fluffing discovered the my wpa key was being interrupted as a hex number because it was, but it was being used as text. Found the wpa to generate the hex key based on test and SSID. A ifdown/ifup later and it worked!
- Problem I currently have is that after reboot, the wifi is not working until I ifdown ifup the interface. grrr
- As I couldn’t get the wifi working, I started on getting the SlimServer working. It all works, except the music won’t play as the SqueezeBox shows the servers other interface as the server address. Grrr, I’ve re-addressed it onto a different LAN network. So here’s hoping it’s solved….
There’s been so much more, but I’m exhausted from typing, so I’ll get to my point.
I love my MacBook, either it works or it doesn’t. If it works it’s a great user experience.
Windows, it won’t work, but you can download something that will make it work if you can get past the trust problems from software.com or where ever. It might cost.
Linux, it won’t work, and you’ll need to know why to fix it, but there is code, and there are options, and you can make it do anything once you know how to configure it. It’s free, but it costs time.
I still like the extremes of the two (ie not windows), but it’s taking more effort than I had expected.
Back to it then….