I configured it with 4 partitions:

1. /boot (about 500 MB)
2. Swap (about 5 GB)
3. / (FS root, about 35 GB)
4. /home (the remaining ~210 GB)

As far as the hardware goes, everything appears to work out of the (quite literal) box. The processor’s throttling is automatically handled by cpuspeed and ACPI. The LCD was automatically detected at the appropriate resolution (WSXGA+, 1680×1050) and DPI (129), and graphics (integrated Intel GMA X4500HD) work very well – 3D, Compiz, and everything. Virtualization extensions (so-called “VT”) were disabled in the BIOS by default for whatever reason, but enabling them took only a few seconds and KVM works wonderfully (running an Ubuntu 9.04 virtual machine for a Linux class).

The TrackPoint(tm) and TouchPad both work splendidly, although the TrackPoint does take a lot of practice to get comfortable with. I’m tempted to disable the touchpad in the BIOS, since I don’t actually use it for pointing (and I often erroneously swipe it with my palm while using the so-called “nipple mouse” of the TrackPoint); but I do use it for the scrolling, so I’ve not yet found a happy medium. Suggestions appreciated.

The hard disk (Western Digital WDC WD2500BEVS-0) and DVD burner drive (HL-DT-ST DVDRAM GSA-U20N) are surprisingly speedy. I’ve already burned two copies of the Fedora 11 LiveCD and several data discs (backups) with no problems. The Bluetooth works well, and I can easily send and receive files to and from my phone through the included Bluetooth stack. The wifi  (Intel WiFi Link 5300 [AGN]) works beautifully with the included iwlagn driver, enabled by default. Also, NetworkManager makes connectivity trivial. (Thanks, devs!)

The firewire and PC Card slot also seem to work – they are autodetected and drivers loaded. However, as I have no firewire- or PC Card-based devices, I cannot verify their functionality.

I have come to quickly love the GNOME Power Manager stack. According to it, the battery on a full charge should last me about 5 hours. It keeps track of how much charge the battery has, how quickly I’m consuming or charging it depending on if I am plugged into AC power, etc. It even shows me a graph of my recent power history! Wonderful little tool. With the help of Intel’s fantastic PowerTOP utility, I’ve increased that computed estimate to nearly 6 hours. (!)

With regards to multimedia, things worked beautifully without me even trying. The built-in webcam works perfectly with Cheese, and the built-in sound works for both playback (surprisingly loud at maximum volume!) and recording (not fantastic quality, but it’s very good at eliminating surrounding static and other noises). I can’t wait to try video-calling someone with the recent Empathy enhancements!

All of the hotkeys – brightness-switching, volume control, playback/navigation, etc.) work as expected, and ACPI (with GNOME Power Manager) even automatically suspends when I close the lid – wonderful!

I’ve also noticed that the machine stays colder in Fedora than it ever did while running the preinstalled Windows. Maybe this is only subjective though, as I never checked the actual temperatures in Windows. Or perhaps Linux/Fedora is better at staying in deeper C-states for longer intervals. In either case, I can work with it directly on my lap quite comfortably.

One of the main reasons I decided upon the T-series instead of a similar R-series laptop was weight. Even with the battery installed, it is only about 5.5 pounds. (That’s about 2.5 kilograms for the rest of the world who use a less-insane system of measurements.) This is quite comfortable to carry with me around school and work without tiring my shoulder.

The only thing which I’ve been unable to test, aside from the firewire and PC card slots, is the dual-screen capability. According to the included manual, it should be capable of using the DisplayPort interface to attach a secondary screen (such as a projector) and automatically resize appropriately, with [Fn]+[Spacebar]. I suppose that if this does not yet already Just Work(tm), it will be fixed by the time I need to worry about actually using it though.

Overall, I love this laptop, and am extremely happy with my purchase decision. In fact, the only qualm I have with this wonderful computer is that it’s not yet decorated! Oh great lazyweb, doe anyone know where I can get stickers for GNOME, Fedora, Linux/Tux, et al., to adorn it with?

Also: A huge THANK YOU to all of the developers who helped make my first Linux-on-a-laptop experience an absolutely wonderful one. I love it when things work so simply and effectively!

• Intel Core 2 Duo Processor P8400 (2.26GHz 1066MHz 3MBL2) 25W
• Genuine Windows Vista Home Basic (Will be used only to verify hardware functionality. Fedora will replace it thereafter.)
• 15.4″ WSXGA+ TFT, w/ CCFL Backlight (137 DPI…sweet.)
• Intel Graphics Media Accelerator x4500HD with vPro
• 4 GB PC3-8500 DDR3 SDRAM 1067MHz SODIMM Memory (2 DIMM)
• UltraNav (TrackPoint and TouchPad)
• 250 GB Hard Disk Drive, 5400rpm
• DVD Recordable 8x Max Dual Layer, Ultrabay Slim (Serial ATA)
• Integrated Bluetooth PAN
• Intel WiFi Link 5300 (AGN) with My WiFi Technology
• 9 cell Li-Ion Battery
• 4 Year On Site Upgrade with 4 Year ThinkPad Protection

Thankfully, I found an excellent discount through the CPP (Contractor Purchase Program) which cut the cost from nearly $2,200 to just $1,400 (including shipping and taxes, state fees, et al.) – a savings of 40%! The 4-year protection plan was about 30% of the final cost. Well worth it, though.

As it is, this will be a life-safer, as I’ve been having a lot of intermittent hardware issues on my desktop: I get seemingly-random WiFi disconnects; DVD-burning often fails for no discernible reason, and my hard drive is on its last legs, so to speak. (In fact, just today I saw another 12 sectors go bad and need to be reallocated…its count is now at 177. The manufacturer maximum is 188!) – I’m all anxious and impatient now!

So, in the span of one month, I’ve spent almost $4,000 (tuition/registration fees, books/supplies, and ThinkPad). I think that’s quite enough for a while.

While its parameter handling can be a bit quirky, I find that it is extremely useful for two reasons: The first more or less negates its quirky parameter handling: Clear and thorough documentation, with lots of example program calls  The second is that it saves me a lot of time in copying the files. Similar to the DeltaRPM feature I raved about with Fedora 11, it copies over only the changed content instead of the entire directory tree. With my home directory at nearly 20 GB, incrementally updating my backup like this prevents a good 90+% of the data from needed to be copied again.

In this way, I know that I have at least two copies of my data at any given time. A major plus to copying the directory tree as-is is that, once the drive does die and I replace it, I merely need to copy it over, without changing anything or unpacking huge tarballs and applying diffs, et al.

The disadvantage to this is that I only have one consistent backup copy of my data at a given time, and that backup is on a hard drive in the same computer. So, should there be a massive system failure of some sort (knock on wood!), then I would lose my data for certain. I also intend to purchase CD-RWs for this purpose – that is, as an additional backup medium – in the near future. But for right now, the second on-disk copy suffices. I also want to setup a RAID system in my next computer build…but that’ll have to wait.

So this simple rsync method, as with any storage decision, has its benefits and downfalls:
Pros:

• Easy to configure;
• Can be automatically run (e.g., in a cron job);
• Updates occur via content deltas, not full copies;
• Backup data is “as-is”, and can be used immediately after copying.

Cons:

• Only one backup copy;
• Physical proximity to original data;
• Requires space for an entire duplicate of the directory tree.

For me, though, this method works out well. Do others have a similar system? Would you suggest any improvements/simplifications? I’d like to hear your thoughts on the matter! Thanks.

With over 50 new features in this release (more than any previous release, I’ve been told!), it would seem logical that this staggering amount of new improvements would leave us with many majors bugs and issues yet to resolved – the more features we add, the less manpower/resources we can expend on each individually, right?

Wrong. With so many test days and an amazing Quality Assurance team, we’ve hammered, smashed, pounded, banged, and kicked this release into a uniquely rich and stable Fedora experience.

One of my favorite features of this release is Presto. Though not enabled by default, Presto allows users to use so-called DeltaRPMs to update the packages installed on their system. That is, instead of downloading the whole new updated packages, only the changes between the installed version and the update need be downloaded. Especially for large packages (such as some game data and OpenOffice.org) or those who are on a slower or pay-per-usage internet connection, this can be a very hefty savings both in time and cost. I used it immediately after installed Leonidas, and it saved me quite a bit on the initial updating:

Size of all updates downloaded from Presto-enabled repositories: 14M
Size of updates that would have been downloaded if Presto wasn't enabled: 128M
This is a savings of 89 percent

Win! The DRI2/KMS support has also been updated heavily and now works out of the proverbial box, at least for a large portion of Intel and AMD/ATi hardware. (This allows a proper composited desktop with 3-D and all. By default. VERY awesome.)

Another excellent feature is that the installation now defaults to using the Ext4 filesystem where applicable. I must admit, I was a bit afraid of actively using this when I was first reading about it, due to all of the reports of data corruption people have experienced; but it seems those issues are long-since fixed, as I’d been using Ext4 for my root partition since Fedora 10. With Leonidas, I took the plunge and upgraded my /home partition (via Anaconda) from Ext3 to Ext4, and have yet to notice a problem. (For those wishing to do similar – and even for those not – I would still highly recommend keeping proper backups Just In Case^TM)

Finally, while I could pinpoint each and every feature and how I feel it’s improved Fedora, suffice it to say that I don’t have adequate time to type out such a long rave. However, as much as these individual features improve Fedora on their own, it is their conglomeration which impacts us the most – the way things are so well-integrated and work properly “out of the box” (so to speak), the way that we as a community of many actively support all of this so well, the way we as a community so diverse handle bugs and packaging, the beautiful artwork and the amazing work of the Release Engineering team to distribute this blend of creativity so readily.

I’d like to rehash those last few points: It’s the wonderful combination of the efforts of you countless contributors and users which makes Fedora so great. Thank you all. Keep up the impressive work. I can’t wait for what’s to come in Fedora 12+!

I really should have posted some sort of away message or “Offline for a while” email; but completely neglected to do so. Mea culpa. As I’m now officially on summer vacation (at least, until I can find a good job/internship), that will definitely change.

I was also quite pleased in that, as the limelights dimmed for the movie to begin, at least two other people in the theater joined me in shouting Qapla’! (Klingonese: “success”). There were no Klingons in this film, but that made it no less fun!

On the other hand, I do apologize that schoolwork has taken up most of my free time recently, and will continue do so until the end of the semester (two more weeks), and because of this I’ve not been very active on the Fedora front. However, I hope to change that once classes let out for the summer.

With Spring Break giving me some much-needed time off from classes, I had some time to install and test the recently-released Fedora 11 Beta. While I do think there are many minor issues (such as Urban Terror having no sound and not being able to quit), there are many awesome improvements over Fedora 10 already. Among these are such niceties as DRI2 & Kernel Mode-Setting support for Intel video (enabled by default!), DeviceKit, and the obvious benefits of GNOME 2.26.

However, one thing that I noticed over the past weekend (looking through the awesome new Palimpsest disk utility) is that my secondary hard drive (a Western Digital WD740 Raptor) has begun to show its age after nearly 4 years of trusty service. The automatic block-reallocation and CRC error counts were already listing as “Failing” and just about everything else in the SMART self-test results are listed as “Pre-Fail.” Thankfully, it persisted long enough to backup my entire home directory to the primary disk (a 40GB Maxtor something-or-other). However, this backup has made that primary disk – which I have partitioned with everything else) almost full, with only about a gigabyte free. (That was close!) So, until I can get that replaced, I’m going to be getting my work done on my parents’ computers and those in the school labs – which means I’m not going to be able do anything Fedora-related other than simple bug-triaging for a while. With schoolwork and other duties now, it’ll probably take me about a week or so to order the new drive from NewEgg, have it shipped, and properly install it in my PC.

I do apologize for any inconvenience this may cause; but as I’ve said on prior occasions, hardware and I seem to have a very love/hate relationship.  :-/

“If debugging is the process of removing bugs, then programming must be the process of putting them in.” (Edsger W. Dijkstra)

After fixing the notification-daemon bubbles (thanks, Martin!), I spent some time perusing through some of the other GConf settings and found another rather interesting gem: /desktop/gnome/interface/show_input_method_menu which is set to off (False) by default. Now, for the longest time I’ve had trouble in Xchat-GNOME (my IRC client of choice) with getting Japanese input to work properly. There was no preedit text or conversion from Romaji to Kana/Kanji. SCIM/Anthy just wasn’t being used at all! But changing this one item, it’s easy now to get SCIM working as it should, but selecting the “SCIM Bridge Input Method” from the context menu.

Granted, it’s definitely not a correct or long-term fix by any means; but at least now I’m not given the inconvenience of opening up gedit or some other application to switch back and forth when I want to IRC in Japanese. Yay!

I should probably go package up that new Midori release now.