AMD's Linux support leap

AMD have really shown their dedication towards open source software the last couple of years. As explained in the Phoronix-article below this post, AMD has fostered not only one, but two open source driver projects with technical specifications, programming guides and register information for their graphics cards. They have even started shipping their cards with Tux printed on the retail boxes and Linux drivers included on the driver-cd's! Finally, a gfx-card manufacturer that has truly started leaning towards open development.

Personally, I've been using ATi/AMD's proprietary drivers for well over 2 years now. Cannot say I've always had positive experiences with them, but they usually worked without involving too much system hacking and modification. Actually, my experience with problems related to their drivers, were caused by internal driver functions rather than conflicts with system settings/libraries and/or software.

http://www.phoronix.com/scan.php?page=article&item=amd_evolution&num=1

Acer Aspire One

I have made my choice. I chose the Acer Aspire One.

Specs:

• CPU: Intel Atom N270 (1.6GHz, 533MHz FSB, 512 KB L2 Cache).
• Memory: 512MB DDR2 533MHz on-board (Upgradable to 1GB or 1.5GB using 512MB or 1GB soDIMM).
• Display: 8.9" WSVGA (1,024 x 600), LED Backlit, 180 cd/m2.
• Storage: 8GB NAND Flash Module (Linux Versions) & 80GB 2.5in HDD (Windows XP Versions), Memory Card Reader (SD, MMC, RS-MMC, MS, MS PRO, xD).
• Audio: Integrated Intel HD Audio, Integrated Microphone & Speakers
• Communication: 802.11b/g Wi-Fi, 10/100 Fast Ethernet, Integrated 3.6MB 3G/HSDPA (Optional), WiMAX (Optional), 0.3 Megapixel WebCam.
• Dimensions: 249 x 170 x 29mm (WxDxH) for NAND Flash and 3-cell battery version; 249 x 195 x 36mm for HDD version with 6-cell battery.
• Weight: 995g for NAND Flash, 3-cell battery versions; 1.26kg for HDD/6-cell versions.
• Battery: 2200mAh 3-cell battery (3 hours life); 2600mAh 6-cell (7 hours life) - figures derived from NAND Flash editions.
• Warranty: 1 Year Carry-in, upgradeable to 2 Years.

Ordered June 20., Confirmed delivery date: 01.07.2008.

Est.delivery change #1: 09.07.2008.

Est.delivery change #2: 25.07.2008.

Est.delivery change #3: 01.08.2008.

Cancelled order @ retailer, re-ordered @ another retailer June 27., Confirmed delivery date: 09.07.2008.

Est.delivery change #1: 02.08.2008.

Est.delivery change #2: 29.07.2008.

01.08.2008 10:30am - IT HAS ARRIVED! ;p w00h00!

Friday quote

"Never increase, beyond what is necessary, the number of entities required to explain anything"--- William of Ockham (1285-1349)

Quotes galore ;P

“Intelligence is the ability to avoid doing work, yet getting the work done.“

-- Linus Torvalds (creator of the Linux kernel)

Upgrading to Slackware-12.1

A linux.com article reviewing the new Slackware release, click the post title to read.

Last nightwatch, monitoring network connections...

Yes, tonight is my last shift at a Network Operations Central (NOC). Tuesday I start working for a local webdesign/websolution company. No more working weekends, no more evenings and nights.

It was bound to happen sooner or later...me joining the masses of "nine-to-five".

At least I'm going to work with people more down to earth, since it isn't a big corporation. It's owned and run by 2 people. One of which lives in the same area I live in. Some would maybe say it could have it's disadvantages, but I see it differently:

• I don't have a driver's license, and the public transport available where I live isn't excactly tip-top, so at least I don't have to worry about getting to work.
• With just 2 people to answer to, I don't have to argue against a large hierarchy to express my opinions about work-related issues.
  

And for once in my life, I'll be working with things I've been playing with in my own time as a hobby. So I have quite broad experience with it. General webdesign with graphics and cascading style sheets are the subjects I enjoyed best @ school when I studied for a bachelor's degree in IT.

Working with Service Level Agreements in accordance with connection tracking, monitoring and faulthandling at an ISP, wasn't quite as I imagined it would be. At least not at a business level, in which I worked from august'07 up until now. It got to beaurocratic for my taste. Not that I don't value the experience I've had at my current job.

I've learned a lot about network topology (something I had trouble understanding when in school), routing theoretics and Internet backbones. And through a lot of websurfing and manual reading, I've also learned a shit load about network security; on the hardware layer, IP layer and on the software layer. And as a result, I've hardened security in both the LANs and WLANs @ my mom's and dad's places, and also my DMZ (publicly available domain, read: my bedroom ;P).

My experience gained working @ a NOC also gave me the idea of tunneling IP connections between two locations under the same WAN (ISP backbone), allowing me to serve my linux-machines located @ my mom's house (the DMZ), to a router I set up on my dad's Internet access that sports a public Internet IP address (with a DNS record) using Linux IP/port forwarding (Linux IP Masquerade, the Linux version of NAT) and OpenSSL/OpenSSH.