I started a little quest three months ago when I decided to purchase a netbook. I found those small devices extremely useful for me. Also, as a bonus, they are relatively cheap.
I started trying the acer one. It didn't quiet work for me. The performance was what I was looking for but it had a couple of big problems. First, the keyboard: extremely small and almost unusable if you are planning to do some serious typing. Also, the screen is too small, 8 inches is not enough for me.
My next attempt was the HP 1000. This one was the opposite of the acer: excellent keyboard but bad performance. With also another negative bonus: it run extremely hot. The Via C7 is just not what I need for my netbook.
Finally the Samsung NC10 came along. That was my winner. It basically has the best of the acer and the HP 1000. Very nice and usable keyboard, 10 inches screen and a Intel Atom cpu.
I planned to run an open source OS on it, most likely Linux so hardware compatibility was important for me. The NC10 hardware works out of the box with the latest versions of the Linux kernel and the latest Ubuntu/Fedora.
I performed an out of the box installation of fedora 10. Everything worked just fine: Video, suspend, hibernate, sound, wireless, etc... I used the netbook for around with more or less the default software that came with fedora. But gnome is too much for a netbook. Don't get me wrong, it works fine, but come on, we can do better than that. Then dwm came along. I don't recall how I found that amazing window manager but I am extremely happy I found it. It is exactly what I was looking for. First of all it allows me to control the computer mostly with the keyboard. On the other hand it is extremely fast and light. Actually I doubt it gets lighter than that.
Don't get scared by the minimalistic approach of dwm. If you try it, you will never go back to your old window manager. Check out the links I have in my delicious account (drio), under dwm. That's a pretty good start point. Don't forget of course the README.
Once you switch to dwm you lose all the convenient features you get for free in gnome: battery info, brightness control using fn keys, suspend/hibernate, wireless GUI wrapper, etc...
There are easy work arounds to that. Let's go one by one. For the battery info you can use the acpi command. Even better, use it to display info in your status bar. You'll find the details in the links I mentioned above.
For the brightness control use xbacklight. For example, to increase the brightness 10% do:
$ xbacklight -dec 10Of course these little tools work because your kernel has access to the hardware.
For the suspend/hibernate, use the pm-utils. Gnome goes a step forward and hooks the power button to these tools. We could do the same but I am particularly fine just using the pm-utils from the console.
Finally the wireless. The device driver that interacts with the wireless card is the ath5k. There are other options out there but this one works just fine for me. Again, you can probably fire a GUI iwconfig wrapper but I prefer the console. And particularly, for home, I use this script:
#!/bin/bash sudo rmmod ath5k sleep 0.5 sudo modprobe ath5k sleep 0.5 sudo ifconfig wlan0 down sleep 0.5 sudo ifconfig wlan0 up sleep 0.5 sudo iwconfig wlan0 ap XX:XX:XX:XX:XX:XX sleep 0.5 sudo iwconfig wlan0 essid "myessid" sleep 0.5 sudo killall dhclient sleep 1 sudo dhclient -v wlan0
I was in the market for an external storage array. I needed around 10Tb of space to run illumina's offline analysis. Our current LSF cluster is not stable enough and the resources are very limited.
I ordered a Dell MD3000 and a 2 cpus x 4 cores AMD machine with a SASe5 raid controller to hook up the MD3k.
My initial idea was to setup a Raid6 11Tb virtual disk and to format it for xfs. By the way, I was using CentOS since dell supports redhat for that hardware.
After reading some basic documentation I hooked the MD3k to the server (I ended up calling it milhouse). I wasn't sure how the server sends the commands to the md3k to configure the system. I setup a vtrack storage array two months ago and the configuration was done over ethernet. This array also allows that but if your server is physically connected to the md3k, that's the only thing you need.
The software installation wasn't very complicate. The CD comes with some rpms that install device drivers and some tools to control the array. I decide to start using the GUI, a java tool.
When I started it I thought, well, this is pretty typical. But then I had this issue: I couldn't configure volumes bigger than 2Tb. I spent a lot of time searching the documentation. The vtrak allowed me to configure a RAID6 11TB volume without problems.
Tired of searching I decided to pull from Linux once again: particularly from LVM. I created 6 volumes in the array and then I exposed them to linux. Once that was done I setup a lvm volume to join them, and finally I created the actual disk.
drio@milhouse ~/tmp $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
128G 5.3G 116G 5% /
/dev/sda3 99M 28M 66M 30% /boot
tmpfs 16G 0 16G 0% /dev/shm
/dev/mapper/md3000-slx
11T 174G 11T 2% /mnt/slx
After some more research I found here
that the Dell MD3000 is a re-branded LSI/Engenio array. In that same blog entry, you have
a link to the LSI/Engio documentation. Much better than the Dell one.
posted at: 21:07 | path: /hardware | permanent link to this entry