Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts

Tuesday, 3 May 2011

Ubuntu releases

Ps. This is not directly regarding the latest 11.04 Natty release with the infamous Unity UI. (As of 03.05.2011) I am on 10.04 Lucid on my desktop and 10.10 Maverick on my servers (I know, it should be the other way round...), so I have not even tried Unity yet.

Current release schedule

Ubuntu releases a new version every 6 months, in April and October. They are supported for 18 months. I do not really have an issue with this frequency.

Every 2 years one of these releases is a LTS, Long Term Support, version that they will support for 3 to 5 years. This is the release to use for more production systems.

In practice

In practice this 6 month release schedule means a lot of bleeding edge software and versions go into every version. This is good. It means the distribution is up to date, and the software is pushed and cannot rest on its laurels and falter.

Most software versions are stable enough, but however new divergences are often not polished enough and lack enough extensions, documentation, etc. E.g. Unity, Gnome 3, GDM2, Plymouth etc. For the initiated that will research solutions and like dabbling with new software this is not a big issue. For the vast majority of users that just wants something that works, this is risky and often backfires on their impression of Linux and Ubuntu.

Also a 6 months release schedule does mean quite a frequent upgrade requirement. Especially for the uninitiated non heavy Linux fanboys (if such a name exists). But you have to set the line somewhere, and a more frequent upgrade does mean a smaller delta difference and less chance of broken upgrades. On production servers however, 6 months upgrade schedule is a non starter. The LTS schedule is thus more suitable.

LTS

Unfortunately the LTS version is not always the version Ubuntu "promote". After a newer minor version has been released it takes a back burner. Too much emphasis I feel on promoting, discussing and supporting the newer versions and not backporting enough to the "stable" LTS version.

Also when an LTS version is released it is "promoted" as LTS immediately. Being a "major" release a lot of people upgrade to it soon after the release date, but there are still many teething errors before it is more "solid", usually then they release a X.x.1 version.



Small modification

They should promote LTS to everyone, and let fanboys use the latest non LTS versions. This way the keen users will still be up to date, and will ensure fixes and velocity of the features. But they will keep a very stable version for the majority users.

They should not apply the LTS "brand" to the version until the X.x.1 version a few months after the general X.x release. That way teething errors are never found in an LTS version, and more trust can be applied to the version branding.

They should include more backports to the LTS versions. After about a year my LTSes are a nuisance as their packages are too out of date.

Large modification

LTS current biennial release schedule is a large gap. What about a LTS every year or 18 months?

Have a "major", "minor", "tiny" or better "solid", "stable", "unstable" release versioning? Or an unstable release every 4 months(fanboys), stable every 8 (desktops) and solid(servers)(LTS) every 16 months? Too much admin or release confusion perhaps?


While debian's stable/testing/unstable naming is a close match, Ubuntu has always been relible. But lately I have been reluctant to upgrade, waiting months before all initial problems are out of the way before I dabble. And now I usually skip a release or two every time.

Summary

Basically change the promotion of LTS. Let the LTS be the default version. And do not call it LTS until the Ubuntu x.x.1 teething problem bugfix version is released.

And optionally change the schedule to more frequent LTS, or even 3 levels of stability/support releases.

Monday, 10 May 2010

IntelliJ IDEA on Ubuntu (with Maven , Jetty and JRebel)

I have written an howto on Ubuntu+IntelliJ+Maven+Jetty+JRebel, basically a quick quide to get IntelliJ IDEA working on Ubuntu, with Maven, the Jetty plugin for Maven and with JRebel (JavaRebel).

It assumes a clean basic Ubuntu install, and is quite terse for now. I may extend it with more example work flows etc in the future.

Comments are welcome.

Friday, 22 January 2010

Ubuntufying Jira

This will eventually be published here: flurdy.com/docs/jira/.

But meanwhile Ill edit a draft here:



Ok. Ive "finished" the document. Please read it on my website.


Ignore below


Below is my initial draft howto, but a much more up to date version is on my site.



Why


I want to install and run Atlassian's Jira, as it is just great. Especially as I many moons ago had paid for the $10 starter pack for Jira and Confluence

I want to install and run it on an Ubuntu server.

Downloading the standalone version of Jira works very well. Atlassian has very thorough documentation of every step and issue possible.

But I want to be different... No I just like the idea of Ubuntu/debian's package system and obeying the FHS recommendation of file locations etc. So I decided to modify the download from Atlassian:

Steps



Install Jira as recommended


Launch Ubuntu (Follow flurdy ec2 docs for tips on using Ubuntu & ec2)

Install java:
sudo aptitude install sun-java6-jdk;
sudo update-alternatives --config java;
sudo echo JAVA_HOME=/usr/lib/jvm/java-6-sun > /etc/profile.d/java.sh;
sudo echo EXPORT JAVA_HOME >> /etc/profile.d/java.sh;
sudo chmod +x /etc/profile.d/java.sh

Download jira standalone

Extract and move Jira
tar xzf atlassian-jira-enterprise-4.0.1-standalone.tar.gz;
sudo mkdir /opt/atlassian;
sudo mv atlassian-jira*-standalone /opt/atlassian/jira-4.0.1

Add Jira user
sudo /usr/sbin/useradd --create-home --home-dir /usr/local/jira --shell /bin/bash jira;
sudo chown -R jira:jira /opt/atlassian/jira-4.0.1


If you are not interested in seperating the file locations etc, then you could now run Jira by launching
sudo /opt/atlassian/jira-4.0.1/bin/startup.sh
But I prefer not to...


Makign the install more FHSish



Create folder for changeable data
sudo mkdir /etc/opt/atlassian /etc/opt/atlassian/jira;
sudo mkdir /var/opt/atlassian /var/opt/atlassian/jira;
sudo chown jira:jira /etc/opt/atlassian/jira /var/opt/atlassian/jira


Move logs
sudo mv /opt/atlassian/jira-4.0.1/logs /var/log/jira;
sudo touch /var/log/jira/atlassian-jira.log;
sudo chown jira:jira /var/log/jira/atlassian-jira.log;
sudo ln -s /var/log/jira/atlassian-jira.log /opt/atlassian/jira-4.0.1/atlassian-jira.log;


Link configurations
sudo ln -s /opt/atlassian/jira-4.0.1/atlassian-jira/WEB-INF/classes/jira-application.properties\
/etc/opt/atlassian/jira/;

sudo ln -s /opt/atlassian/jira-4.0.1/atlassian-jira/WEB-INF/classes/log4j.properties\
/etc/opt/atlassian/jira/;

sudo mv /opt/atlassian/jira-4.0.1/conf\
/etc/opt/atlassian/jira/tomcat;

sudo ln -s /etc/opt/atlasiian/jira/tomcat\
/opt/atlassian/jira-4.0.1/conf



Edit configuration and enter Jira home
sudo vi /etc/opt/atlassian/jira/jira-application.properties;
jira.home=/var/opt/atlassian/jira


Move the database
sudo mkdir /var/lib/hsqldb;
sudo mkdir /var/lib/hsqldb/jira;
sudo chown jira:jira /var/lib/hsqldb/jira;
sudo ln -s /var/lib/hsqldb/jira\
/opt/atlassian/jira-4.0.1/database



Move non static tomcat files
sudo mkdir /var/opt/atlassian/jira-tomcat;
sudo mv /opt/atlassian/jira-4.0.1/work\
/var/opt/atlassian/jira-tomcat/;

sudo mv /opt/atlassian/jira-4.0.1/temp\
/var/opt/atlassian/jira-tomcat/;

sudo ln -s /var/opt/atlassian/jira-tomcat/work\
/opt/atlassian/jira-4.0.1/;

sudo ln -s /var/opt/atlassian/jira-tomcat/temp\
/opt/atlassian/jira-4.0.1/





Init script



Copy Atlassian's init.d script


Jira port


Follo Atlassian's port page.



Apache proxy



Using elements from my own tomcat+apache howto and Atlassian's Apache page




Saturday, 3 January 2009

Civilization IV Beyond the Sword in Ubuntu with CrossOver Games

I recently tried to install and run Civilization IV Beyond the Sword in Ubuntu. And it worked flawlessly!

* Civilization IV by Firaxis and its range of games has always in been a favorite of mine.
* Beyond the Sword is a recent extention to this game.
* Ubuntu is a linux distrobution that I use.
* For this to work I used CodeWeaver's CrossOver Games. CrossOver is based on Wine, with some not-yet-in-Wine code and some proprietary code.
* And I installed this on Dell D820 laptop PC.

There was nothing complicated in installing it either. And from CDs.

* I simple installed Ubuntu 8.10 Intrepid Ibex.
* then installed CrossOver Games 7.1.0
* then inside CrossOver installed Civilization IV.
* then installed Beyond the sword. It automatically updated my Civ4 and installed DirectX which I presume CrossOver intercepted.
* then I downloaded the most recent patch of BTS. 3.17. Installed it inside CrossOver.
* Then ran the game.
* Sound did not work 1st time, but specifying ALSA as sound in CrossOver fixed it.

Video introduction, etc everything seems to work. In fullscreen and as a windowed version.

The only think I noticied was that city production bar did not change colour, but changing that to a number in the options solved that. There may be other missing graphics, but I have not seen any. May need to run in side by side of a windows version to notice these things. Certainly nothing game playwise is missing. However I did notice one MOD did not work.

Civilization IV is only marked with a Bronse on CodeWeavers site, however I would say Gold, as 99.5% work.

If you do have problems, many of the forums recommend in Civ's ini files to disable intro videos etc. I have not needed to touch those files.

* Ubuntu thread on Civ4 BTS
* Ubuntu howto on Civ4 BTS
* CodeWeavers page on Civ IV compatability
* WineHQ page on Civ IV