Language Selection

English French German Italian Portuguese Spanish

OpenOffice.org site goes offline, Oracle declines to comment

Filed under
OOo

Two URLs including the OpenOffice.org domain owned by software giant Oracle are currently displaying error messages, but the Larry Ellison-run company is declining to explain why the sites are down.

The openjdk.java.net is also currently failing to load.

Both sites carry the same "Error 503 – service unavailable" message, and the URLs are owned by Oracle.

The OpenOffice.org domain is expected to expire on 12 June 2012 and its IP location in California still carries the Sun Microsystem stamp.

rest here




It's dead

It's dead Jim. Oracle killed it with their latest bullshit.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more