Good news to all of you out there that watch the project I’m involved with called Unity Linux. What is Unity you ask? Allow me to give you some background:
Unity Linux is a small Linux core based on Mandriva Linux. We whittle down Mandriva to a small base desktop to provide users with ‘just enough graphics’ to be able to login and create their own distribution of Linux with the liveCD project which lies at the heart of Unity Linux. We’ve replaced some of the common things like uprmi with the Smart Package Manager and we’ve moved on past RPM version 4 to RPM version 5. Version 5 gives us some really cool features as well as speed enhancements across the board.
If you’re in the mood for Mandriva goodness (control center) without the extra stuff…give Unity Linux a try as a cholesterol free Mandriva.
In February of this year, Unity Linux turned 2 years old. With this milestone on the horizon, we were approaching the time when our hosting service was coming due for another large chunk of change. I began to seek out different hosting plans and price them and our developers started talking fund raising. In January, I approached a hosting company named Host Color about the possibility of sponsoring Unity Linux via providing a hosting plan for them…to my delight, they were more than happy to provide for us!
I approached Host Color because they have been a sponsor of Yet Another Linux Blog for well over a year now helping the authors here bring excellent how-to’s and editorials about Linux. Now Host Color has offered hosting for Unity Linux and given us a fine place to hang our hosting hat. So, please join me in thanking Host Color for providing us with our new home!
I had been fighting for a very long time with pulseaudio on Unity Linux 2010…it just didn’t seem to work for me. There were problems with having to mute and unmute the external amplifier channel in alsamixer in order to get sound to work. On some boots there was no sound and on others, sound was fine. When I finally installed TinyMe 2010 RC last week, I disabled pulseaudio all together to get the sound working with ALSA only.
Then the worst thing that could possibly happen on my Gateway M250 happened…ALSA stopped working and there was no sound. I started pulseaudio back up to no avail…no matter what I did, nothing worked to get sound up and running.
It was about the time I wanted to carve the sound pieces out of my laptop and throw them across the room that I decided to give everything I tried in the past one more try.
I fixed it…and I was pretty amazed that the solution was as easy as it was having spent weeks upon weeks fighting the pulseaudio issue. I can only surmise that I made a typo in the module that I needed to blacklist. After this arduous journey, it came down to blacklisting the modem sound card to make things work.
To do this on Mandriva and Unity Linux you’ll need to blacklist the following module: snd_intel8x0m. Notice the ‘m’ on the end of the standard module snd_intel8x0 for the ICH6 sound card.
You can do this by editing the following file as root in your favorite text editor: /etc/modprobe.d/blacklist-compat
Add the following line anywhere in this file:
After that, you can reboot to make sure the module is blacklisted. I know there are more elegant ways to load and unload kernel modules but this is the easiest way to get the job done for new users. Subsequent reboots resulted in still having sounds. Thankfully, I didn’t have to rip my laptop apart in a quest to throw the sound portions. I sure hope this helps others out!
I was running Unity Linux 2010.2 with KDE 4.5 for around the last month. I really like what has been done there but it seemed a bit heavy for my Gateway M250…the CPU fan was always on which told me it was always in high use.
I checked out Gnome 2.30 on Unity and found it to be delightful on my resources; however, Gnome doesn’t make me feel warm and tingly when I use it. I find myself frustrated with its lack of configuration options…specifically, right click menu. So I rolled my own using the base install of Unity. That worked quite nicely but lacked much of the polish I became accustomed to when using KDE. What I wanted and needed was a happy medium. I found that happy place with TinyMe Linux.
TinyMe is based on Unity Linux 2010 and was previously based on PCLinuxOS. It uses LXPanel, PCManFM and the Openbox Window Manager to handle the heavy desktop lifting. The ISO I used was a release candidate and lacked much of the polish of the TinyMe stable release of the past. Even though it’s a release candidate, I still found it quite stable and usable…especially since I know my way around the openbox window manager.
After a few adjustments of adding my favorite programs I was in business.
Even without some of the programs that made TinyMe famous (like the TinyCC) this distro is both stable and robust which is a testament to the underlying Unity Linux core. If this release candidate is any indication, look for GREAT things to come from TinyMe 2010’s full release…something I will be looking forward to!
I just took a look at how Unity Linux 2010.1 shapes up and found that the flashplayer plugin doesn’t work with the default browser which is Midori. Here’s a quick fix for getting flash to work with Midori on Unity 2010. First, install the flash-player-plugin (as root in terminal or use the gui):
smart install flash-player-plugin
Next, we need to create a directory under your profile to house the flashplayer plugin and then copy it there. I’m sure we might be able to get by with a symbolic link but I didn’t try that out…
I was quite surprised this morning whilst reading my RSS feeds to discover that Ubuntu has named their most recent ‘lite desktop‘ Unity. Surprised because we have our project, Unity Linux. Strange that both our ‘lightweight distribution and desktop’ and Ubuntu’s ‘lite desktop’ should share a name together.
While I’m not really sure why no one threw up a stop to this in the Canonical brainstorming session that produced ‘Ubuntu Unity’ one can only have a laugh about this and hope we don’t get our pants sued off even though we named our distro first.
If things do get hairy, I’m sure we can change our name to ‘Unity Ubuntu’ or something similar to properly confuse everyone.
So, on behalf of all the Unity Linux developers, I’d like to thank the Academy and give a special shout out to Ubuntu for making our name known! Thanks Mark! Oh and good luck with that Unity thing! 😛
The guys over at Unity Linux have created and developed a ‘build server’ that will allow the automation of package building in both 64bit and 32bit flavors. All the building is done in a chroot and then the package is automatically moved into the ‘Testing’ repository.
Very interesting stuff…much like what rMake does for Conary and Foresight Linux…but applied to RPM’s instead of conary changesets. Just the same, it’s interesting that such a small team of developers are showing their prowess in development and making strides toward building a robust developer community.