Skip to main content

Getting Stomped by Little Gnome Feet

Well, I gave it the old college try and tried to create an up-to-date Mono development environment on top of my aging Fedora 14 installation. I should have know better, considering how many times in the past I've beaten myself bloody with some specific feature of Linux.

It all started innocently enough. I cloned a copy of Mono from their git repository and built it without any issues. I wrote a number of increasingly complex C# applications to test the compiler and runtime. No problems were encountered. But I noticed I couldn't compile or run any GUI applications. Complimenting that was a lack of MonoDevelop 3, the Mono/C# development IDE. When I started to dig into how to build and run that particular tool, I ran into problems.

Fedora 14, released November 2010, is running Gnome 2.32. Fedora 14 is the last Fedora release to run Gnome 2. Fedora moved to Gnome 3 starting with version 15, and that's one important reason why I stayed with Fedora 14 and continue to stay with Fedora 14. The other important reason is that absolutely everything works on the Dell D630. Everything, from wireless networking to graphics to sleep mode when the notebook is closed back to full operation when it's opened again works and works flawlessly. I've thought about backing up all my work and moving to another version of Fedora, or even a different distribution, but the idea of changing out and hassling with what gets broken doesn't appeal to me. As well as hassling with Gnome 3 (although there's Cinnamon which I like.)

But staying with an aging distribution has its problems. With very few notable exceptions such as Google Chrome and Oracle Java, everything pretty much stays locked in place version-wise. That means if you want to run with the latest version of anything important you're pretty much left behind if you stay with a given release. When I wanted to step up to a full Mono 2.11 release with all the GUI bells and whistles, such as the latest MonoDevelop 3, it also requires that you step up to supporting libraries, such as Gtk# 2.0 and all of its dependencies with GObject, Mono Addins, etc, etc, etc. What finally stopped me from chasing down the rabbit hole was GObject's dependency on glib 2.29.7 or later. Gnome 2.32 supplies 2.26.0.

One other complaint I have from all of this is how stale a lot of the Mono site has become. A lot of the pages still point to tarballs that used to be hosted via Novell, and many of the pages that talk about getting source talk about Subversion. Mono migrated to git (and github) back in July 2010, as did most, if not all, of the supporting projects. After two years I would have thought the Mono site would have been brought up to date. I eventually found everything I was looking for on github and cloned all the projects I wanted to work with, but things might have gone a bit faster if all the site pages were current. And that's a shame, as pulling down the sources and then building the project are dead simple to do. Working with source projects, at least Mono, is the most approachable I think I've ever seen it, showing a lot of quality effort at the project level. That level of quality needs to flow back through the complete "official" Mono site.

In any event I think I've mapped a course of action to follow for the Dell. I'm buying a new 320GB 7200 RPM drive to go into the D630, and an external USB 2.0 case to hold the older 120GB drive. The plan is to install the new drive, install a new up-to-date distribution that supports the absolute latest Mono and supporting environment, plug the old drive back in via USB and then copy off all my projects and files I've collected under Fedora 14 over the last year-and-a-half. Worse case I'll just re-install Fedora 14 (I do need extra disk space and 7200 RPM would make things a bit snappier). I run this notebook with full disk encryption, so getting the latest kernel and encryption might also make things a bit snappier as well.

Comments

Popular posts from this blog

cat-in-a-box channels greta garbo

So I'm sitting at my computer, when I start to notice a racket in back. I ignore it for a while until I hear a load "thump!", as if something had been dropped on the floor, followed by a lot of loud rattling. I turn around and see Lucy in the box just having a grand old time, rolling around and rattling that box a good one. I grab the GX1 and snap a few shots before she notices me and the camera, then leaps out and back into her chair (which used to be my chair before she decided it was her chair).

Just like caring for Katie my black Lab taught me about dogs, caring for Lucy is teaching me about cats. She finds me fascinating, as I do her. And she expresses great affection and love toward me without coaxing. I try to return the affection and love, but she is a cat, and she takes a bat at me on occasion, although I think that's just her being playful. She always has her claws in when she does that.

She sits next to me during the evening in her chair while I sit in mi…

first night for the gingersnaps

The first night has passed and the two have managed to survive, in spite of what their tiny hearts might have thought when first arriving. Greebo, the larger of the two, has been in hiding the entire time so far. Ponder has spent the time zipping in and out of hiding spots, checking things out, and learning just how comfortable pillows are for resting your head.

During the night I felt the tiny body of Ponder hitting the bed as he leaped up on the side, and then climbed to the top to run around on top of me. At least once he play-attacked my fingers. He might be small but his claws are still quite sharp.

When I got up in the morning the bowl of cat kitten food was fairly well depleted. It's been refilled and fresh water put in the big dish on the floor. I'm assuming that both Greebo and Ponder are feeding and drinking. I have seen Greebo under the furniture peeking out at me when I went looking for him. I'm leaving him alone while he continues to adjust.

So far the guys h…

vm networking problem fixed

Over the weekend I upgraded to Windows 8.1, then discovered that networking for the virtual machines wouldn't work. Then I tried something incredibly simple and fixed the problem.

Checking the system I noticed that three VMware Windows services weren't running; VMnetDHCP, VMUSBArbService, and VMwareNatService. VMware Player allows you to install, remove, or fix an existing installation. I chose to try fixing the installation, and that fixed the problem. The services were re-installed/restarted, and the virtual machines had networking again.

Once network connectivity was established there was exactly one updated file for Ubuntu 13.10, a data file. This underscores how solid and finished the release was this time. Every other version of every other Linux installation I've ever dealt with has always been succeeded by boatloads of updates after the initial installation. But not this time.

Everything is working properly on my notebook. All's right with the world.