Aug 31 2009

How to change your hostname and domain name in Linux

To change your hostname and/or domain name in Linux you need to modify two files.

/etc/sysconfig/network should read:
NETWORKING=yes
HOSTNAME=

– and –

/etc/hosts
127.0.0.1 localhost locahost.localdomain

Replace the terms in brackets (<>) with your own hostname and domainname, and then reboot.

Post to Twitter


Aug 17 2009

Ultra ATA data cables

Wow, I spent 2 days trying to figure out why after upgrading a server to Fedora 11, the system wouldn’t boot. It would either throw a system boot failure error or hang at the ‘Verifying DMI Pool Data’ line. This was only when I plugged in a third drive — it didn’t matter which one. And in the BIOS boot order the only thing listed would be ‘Bootable Add-In Cards’, and not my drives. Turns out it really matters the order in which you plug in drives with the ATA cable! I’m still not totally clear on in, but once I saw this image I switched the cable around and it worked!

Post to Twitter


Aug 17 2009

CSS: Where the hell are all these div gaps coming from???

Sometimes I like to write seemingly stupid little posts, but it’s usually because they are solutions to problems that drive me up the wall and take me way longer than they should to figure out.
Anyway, today’s lesson is that if there’re gaps showing up between your div tags and you’ve set the appropriate containers to have a margin and padding of 0, well, don’t forget about setting white-space: nowrap. Ack! This removes all the whitespace that may just be hanging out within your file that contains the html code.

Post to Twitter


Aug 4 2009

Solving “Verifying DMI Pool Data” hang in Fedora

I have a Linux server with Fedora that I use mainly to host storage drives. It has one boot drive, and 4 storage drives, the fourth of which is connected through a Promise Sata 200 Tx2 Plus controller.
All was great for a year or more, til I started getting a hang on boot at “Verifying DMI Pool Data”. This only happened when I plugged in a drive through the Sata Controller. I saw lots of threads with various (complex) possible solutions, but my fix luckily turned out to be simple enough, just took a lot of time to figure out.
In BIOS settings, under ‘Advanced BIOS Features’, ‘Hard Disk Boot Priority’, ‘Bootable Add-in Cards’ had made it’s way to the top, so it was trying to boot off that 4th non-bootable data drive. As soon as I moved that down below my bootable drive, everything was peachy.
Yay, finally!

Post to Twitter