Commentary

Serdar Yegulalp
 

My Linux Broke -- Is It My Fault?

One of the adages about Linux that gets passed around a lot goes something like, "It's a great system, but you really have to know what you're doing." The other day, I got a firsthand example of that -- I got bitten by a bug in a package that's readily available in Ubuntu's software repository.

One of the adages about Linux that gets passed around a lot goes something like, "It's a great system, but you really have to know what you're doing." The other day, I got a firsthand example of that -- I got bitten by a bug in a package that's readily available in Ubuntu's software repository.First, a word of praise: I do like the way most of the Linux distributions handle software via a package manager -- it's often far easier to figure out what's installed and what's not installed than it is in Windows. (Windows does have standardized mechanisms for adding and removing things, but it's too easy for a programmer to not use them.)


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Within Ubuntu's software repository, you'll often find multiple packages for the same basic function, so you can try out a few different ones and stick with the one closest to what you need. For instance, after working a bit with Google Desktop Search for Linux, I decided to remove it and try something else. One of the other options for indexed search is a package called, simply, Search, based on the Beagle search engine project.

I didn't know that Beagle was a tad buggy, although I guess the revision number -- 0.2.16.3 -- should have been a hint. I installed Search, and soon noticed that whenever I attempted to search Ubuntu's help system, I got results that didn't match at all with my search terms. After some digging, I found that this is a known problem with Beagle -- or, rather, it's a problem with the way Beagle and the help system in Ubuntu talk to each other. It's also apparently a known issue (see here and here), so at least I wasn't alone in having been bitten by it. Removing Search and reinstalling the help system (which took all of five minutes) fixed the problem, so at least it was not that hard to back out.

Out of curiosity, I checked to see if there was an updated version of Beagle available directly from the project's Web site. There was, but there were no current binaries available for Ubuntu Feisty -- and if I have to compile a given item from source, that's a major strike against its usability.

What I'm worried about here is how a relative newcomer could install the Beagle Search package (something provided by Ubuntu's own software repository, which is why this is a little upsetting), not have much of a way to know about this issue, and then wonder what they did that broke the search function in help. That's a function they're likely to use a great deal; the more experienced users don't touch it as much and therefore might not see it as being a show-stopper.

Yes, I'm willing to accept blame for not doing as much homework as I might have -- but at the same time, I don't think it's asking too much for at least some warning that installing a package from Ubuntu's own software repository could cause something of that scope to break. Is it?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links