devnet, Author at Yet Another Linux Blog

Unity Linux Theme Refreshes

I’ve been pretty busy lately with theme design for the Unity Linux project. The following pages were updated:

Unity-Linux.org
Planet.Unity-Linux.org
A new forum theme called SMFPress @ forum.unity-linux.org

Uniformity was the key ingredient to the stylings. I’m trying to match everything to the front page theme at the main site page. Using the color pallete from that site, I worked on creating a theme for our forum and then gave planet unity a facelift as well. We’ll test out the planet capability a bit longer (see how updates go) before we ultimately conclude to use it. However, the forum and main site are finished products.

Let me know if you find any bugs or have any problems with the theme. If all goes well I’ll start on a wiki theme for our documentation site 🙂

Convert PNG to GIF via Command Line

I installed a bare bones Arch Linux system today and took a screenshot. With no graphics utilities installed, I needed a way to convert a PNG to a GIF for a Simple Machines forum template thumbnail. I figured I’d use a command line utility to help me and ImageMagick is installed by default on most distributions. A quick read through the ImageMagick manpage and I found the convert command and thought I’d share it with everyone. Use convert in the following fashion: convert [input-options] input-file [output-options] output-file

convert SMFPress.png -channel Alpha -threshold 80% -resize 120x120 thumbnail.gif

This did a quick, same-size conversion with little loss for me to display the thumbnail online. For more information on the options I used and other options that I didn’t use, take a peek at the ImageMagick Online Help Page for convert.

Foresight, rPath, LiveCD, and Unity Linux

Most, if not all, top distributions of Linux ship a live CD that allows an end user to preview the operating system without installing it.

Foresight Linux is the exception.

Now, this isn’t because they don’t WANT to have a Live CD…they do. The problem is that rPath, the creators of rBuilder Online, have discontinued the Live CD image creation type.

There was no announcement…no news posting…no clue dart thrown toward Foresight for this discontinuation. There was only a comment on a single bug in the rPath issue tracker just this past May…Formally discontinued…which in my opinion, is a HUGE mistake as far as community goes. Why? Because a community is a solid base on which to stand for any distribution or toolset for open source. rPath has essentially dismissed a feature that the community would find valuable and in the process alienated anyone who finds this feature valuable or desirable. But I’m not here to talk about whether or not people want to develop their own distributions on rBuilder Online using rPath tools nor the incentive to do so…I’m talking about Foresight.

So, what incentive does rPath have to help Foresight by fixing it? Not much…I’m sure there will be those that argue: “rPath has customers and their first allegiance needs to be to them” and those people would be right. But can’t the Foresight community pick up the torch for Live CD building on rBO and develop it as a community effort? Can’t a license be found that it can be released under that would prevent forking? Can’t it be modularized as a ‘plug-in’? I don’t pretend to know the answer to those questions…I just think that Foresight will continue to suffer as they have been for many, many months now with respect to not having a Live CD.

I’m sure that there will also be those out there saying “but Foresight has a bunch of Virtualized Images to choose from!! No one really cares about a Live CD!!” and I’d say you’re halfway correct. Developers don’t really care about a Live CD…but those that Foresight attempted to attract…the end user…they DO care about having something they can ‘try before they buy’. It is my belief that Foresight would be a crap-ton more popular if they had a Live CD.

So What Solutions Are There?

I don’t think rPath will suddenly fix the broken Live CD creation in rBO. I don’t think they’ll release the code anytime soon (though this is more likely than a fix). So in the meantime, what if Foresight helped out with LiveCD project that recently was taken over by Unity Linux? Both Unity and Foresight are Red Hat like distributions and use similar file structures and OS organization. I think that if Foresight were able to integrate LiveCD onto the distribution, a huge niche would be filled.

Where to Start?

Being involved both with Foresight Linux and Unity Linux gives me a unique perspective on what areas of collaboration could be developed. One thing is for sure…having both distro development teams onboard would be a huge boon to LiveCD development…and Foresight could suck in SRPMs quite easily from Unity to hit the ground running right away.

I am by no means offering to be the head of this project because I can’t even begin to know where it would start or finish. I’m just offering a workaround to a problem I’ve seen Foresight have for longer than it should have. I know the Unity Linux guys would welcome anyone wanting to get involved with helping LiveCD development. Would Foresight be open to this? I can’t answer. I hope so…Foresight needs a Live CD if it hopes to attract more people to it…and that’s something I’m keen on seeing. Is this something you’d like to see as well?

[poll id=”2″]

YALB – ITLPD

In honor of today, which is International Talk like a Pirate Day, my blog now comes in pirate flavor thanks to a very interesting plugin.

So have a look around! Some posts are pretty silly sounding and others are downright hilarious. And have a great day or you’ll probably have to walk the plank somewhere 🙂

Clarification on Foresight and Fedora

I previously wrote about a possible “rebasing” of Foresight Linux on the Fedora platform. This conjecture was a bit premature it seems as I am completely wrong on this being a possibility 🙂 The best part about me being absolutely wrong on this is that there is still going to be benefits for Foresight and Fedora even without the rebase.

Foresight is toying with the idea of having a sub-project (completely separate from Foresight Linux base) that it has tentatively called ‘boots, a Fedora remix‘ (a play on Dora in Fedora for those of you with kids).

What would happen is that mirrorball, a tool from rPath that ‘sucks in’ repositories, would pull in a Fedora repository into a separate Foresight repository. From there, it is fully consumable by any product/project that is hosted on rBuilder Online from rPath. Conary really is one of the most innovative package managers on the planet and I’ve mentioned it once or twice before (never got around to part II on one of those though). The ability to fully suck in a RPM repository is already being done with CentOS and Scientific Linux on rBuilder Online…even Ubuntu is currently being done as well…so we have proof that it is totally possible. Once imported, Conary takes over the management of said packages.

So what does this give Foresight? A few things:

Testing of packages in 2 communities
Developer eyes/chatter in 2 communities
The ability of Foresight to cherry pick packages from a large base
Compare and contrast for packages from 2 different sources to track down bugs

So, as I said, I was wrong initially and I hope this clears up what Foresight plans to do. A sub-project will be started that imports the Fedora repository changing them from (rpm to Conary) allowing Foresight to both test and cherry pick packages from a larger base hopefully freeing up a bit more time for Foresight architects. Phew! What a mouthful, run-on-sentence that was!

Why Conary? How does this help Fedora?

I know some of you may be asking Why Conary? What does it have over RPM that Foresight should suck in a repositoroy and change it to Conary packages? The reason this is an absolute necessity is because the tools on which Foresight are built (rBuilder Online) works with Conary only…that means ISO generation and repository hosting are all mandated to be Conary based.

The other interesting part about this is that Conary blends version control with package management. It deals with changesets as packages. Imagine SVN…you have a local changeset that you’re working on and the version inside the SVN repository differs from that. You can then diff the state of your local copy to see how it differs from the remote copy. This allows you to see the changes you’ve made and allows you to see what code may be broken. Also, commits are numbered automagically so that you don’t have to worry about breaking things much because you can rollback to a previous known good state.

The same is true with Conary…you can rollback to previous known good states. You can also diff each changeset locally with the remote repository. Now imagine this with Fedora packages…if something is broken, chances are Foresight will find a fix for it much more quickly than someone in Fedora…a single command can diff the previously known good version with the broken version and find out the shortcoming. Or perhaps a known good verion in Foresight that isn’t Fedora based might be used to diff the Fedora RPM version and find out the differences in them. In all, it’s going to help developers track down problems faster. This helps Fedora…they now have a small number of Foresight developers who will be working with hundreds of popular Fedora RPMs looking to see if they work or are broken.

Most of the benefit will be measurable in Foresight because they’ll be able to use just about any package Fedora creates…but the Foresight community is FULL of very capable developers…guys that really know what they’re doing. If they can make this a collaborative effort Fedora will gain exceptionally smart developers as well…even if testing packages on a different platform, they’ll have eyeballs on these packages and if a fix is found or made for them they will definitely go upstream to Fedora.

Hopefully, this puts things right from my initial wrong. I don’t claim to be an insider for Foresight…I just know a lot of the people involved and ask questions a lot….I also pay attention to the developer mailing list. If you have any questions, please leave a comment and I’ll attempt to track down answers for them 😀

Adding Color to Bash List Command Part II

I previously blogged about how to add color to the ‘ls’ command utilizing an config file and alias. I then stumbled across a nugget of wisdom from a Foresight Linux user on the developers mailing list who gave a handy command that remedies some problems with missing color in a terminal.

On some distributions, the system-wide /etc/DIR_COLORS* files are removed or not present. This results in no colors being given inside of a terminal when looking for color directories and filenames. If you find yourself in this boat, try the following command to re-populate this setting:

devnet-> cd ~/
devnet-> dircolors -p >.dircolors

This should create a default profile for colors for your session if it hasn’t been done or was accidentally removed. For more information on the dircolors command try ‘man dircolors’. Please also note that dircolors command uses the environmental variable LS_COLORS to set your session.

For more information on LS_COLORS and how it pertains to the terminal/shell/cli/prompt, there are a few blog posts that do an excellent job explaining here, here and here.