Language Selection

English French German Italian Portuguese Spanish

OpenSuSE 10.0 RC1 is here too!

Filed under
Linux
Reviews
-s

What an exciting passed couple of days we've had. Mandriva 2006 RC1 and OpenSuSE 10.0 RC1 hitting the mirrors right about the same time. They are running neck and neck. Who will get their final to the market first? Mandrake has a history of missing release dates to fix last minute bugs and OpenSuSE seems to be hitting theirs - ready or not here it comes. In fact, OpenSuSE 10.0 RC1 actually hit the mirrors a little ahead of schedule this time. Their roadmap stated to expect RC1 on Sept 9, while the isos are dated Sept 7. Their dedicated work is showing in the mass of bug fixes, patches and updated versions. There is no new eyecandy or features this release. So how is it progressing?

As stated I didn't see any new eyecandy or features. However the big news is that gnome seems to be fixed for the most part. At version 2.12, they are ahead of Mandriva on that account. According to the cooker list, Mandriva will be shipping with 2.10. However sources say there really isn't much difference. Don't shoot the messenger, I don't use gnome enough to see any difference myself.

In opening and closing the gnome applications and playing with the settings, I only experienced one or two ooppsies. On the first click of the desktop icon "Computer," nautilus "quit unexpectedly". The error box gave three choices: Restart Application, Close, and Inform Developers. I supposed I should have clicked Inform Developers, but I admit I chose Restart Application. After this action nautilus seemed to operate normally and opened a file manager window. Clicking My Home opened a file manager window in my home directory displaying the available files without issue.

    

Then after that little issue, I clicked on the "Audio CD" icon and received a "Couldn't display "cdda:///dev/hdc" error. I clicked OK, but nothing else happened. No music player opened or anything.

Other than those two little issues, I didn't encounter any problems. I clicked around in all the window managers quite extensively changing settings, setting up accounts and whatnot and can report it seems OpenSuSE developers are doing a wonderful job and are making amazing progress in what is now the home stretch.

With the little annoying beagle bug fixed last development release, I thought I'd test drive it in gnome. It opened immediately and items are available for searching. Searching for the term 'desktop' pulled up 3 or 4 files matching that criteria. The interface is nice and clean, but I think I prefer the separate paned view of KAT in Mandriva. However, a little birdie told me Mandriva is considering not shipping with KAT installed by default afterall. There's not much doubt OpenSuSE will be including beagle.

Since I clocked and posted some of the important performance times for Mandriva 2006 RC1, I thought it might be interesting to compare the OpenSuSE 10.0 RC1 times. These are the times I clocked on the same AMD 2800+ machine:

  • Boot up: 26 seconds

  • KDE: 22 seconds
  • OpenOffice: 7 seconds
  • Firefox: 3 seconds (not counting loading the default Novell webpage)
  • Shutdown: 20 seconds

These times are not as speedy as Mandriva's, yet they are still impressive in their own right. I can still recall the days of 2 and 3 minutes boot ups for both distributions.

From here on out I suspect there won't be any obvious changes to the naked eye, and we will probably only be seeing bug fixes. Some package highlights this release include:

  • kernel-default-2.6.13-8

  • kdebase3-3.4.2-24
  • gnome-desktop-2.12.0-3
  • qt3-3.3.4-28
  • glibc-2.3.5-39
  • gcc-4.0.2_20050901-3
  • xorg-x11-6.8.2-96
  • OpenOffice_org-1.9.125-5
  • mozilla-1.7.11-9
  • MozillaFirefox-1.0.6-13
  • Full Rpm list as tested.

Some changelog highlights include:

++++ beagle-index:

- wait for index build to complete
(hack since there seems to be no way to keep it reliably
running in foreground ..)

++++ wireless-tools:

- ipw2200: added broadcast fix

++++ ktorrent:

- update 1.1rc1

++++ metacity:

- Update to version 2.12.0 (GNOME 2.12)

++++ OpenOffice_org:

- updated ooo-build to version 1.9.125.1.2:
* disabled some unreviewed patches [#114992]
* check buttons rendering problem [#80447]

++++ amarok:

- update to version 1.3.1

++++ dhcpcd:

- fix parsing of resolv.conf file when no 'search' line is present

++++ evolution:

- Update to version 2.4.0 (GNOME 2.12)
- Remove upstreamed patch

++++ kdebase3:

- apply fixes for kcheckpass

++++ nautilus:

- Add submount patch (90584)
- Fix spec to apply both desktop search patches
- Update to version 2.12.0 (GNOME 2.12)

++++ MozillaFirefox:

- fixed gconf-backend patch to be able to use
system prefs

++++Full Changelog since Beta 4.

New screenshots HERE.

Previous Coverage:

Beta 4
Beta 3
Beta 2
Beta 1

More in Tux Machines

10 tips for easier collaboration between office suites

Yes, you are likely using the Microsoft formats for your documents. However, they don't always follow OpenDocument Format (ODF) standards. Instead of opting for the proprietary Microsoft formats, switch over to one that's welcomed by nearly all office suites: ODF. You'll find a much more seamless collaboration process and fewer gotchas when moving between office suites. The only platform that can have a bit of trouble with this format is Android. The one Android office suite that works well with ODF is OfficeSuite 7 Pro. Read more

Outsourcing your webapp maintenance to Debian

It turns out that I'm not the only one who thought about this approach, which has been named "debops". The same day that my talk was announced on the DebConf website, someone emailed me saying that he had instituted the exact same rules at his company, which operates a large Django-based web application in the US and Russia. It was pretty impressive to read about a real business coming to the same conclusions and using the same approach (i.e. system libraries, deployment packages) as Libravatar. Regardless of this though, I think there is a class of applications that are particularly well-suited for the approach we've just described. If a web application is not your full-time job and you want to minimize the amount of work required to keep it running, then it's a good investment to restrict your options and leverage the work of the Debian community to simplify your maintenance burden. The second criterion I would look at is framework maturity. Given the 2-3 year release cycle of stable distributions, this approach is more likely to work with a mature framework like Django. After all, you probably wouldn't compile Apache from source, but until recently building Node.js from source was the preferred option as it was changing so quickly. While it goes against conventional wisdom, relying on system libraries is a sustainable approach you should at least consider in your next project. After all, there is a real cost in bundling and keeping up with external dependencies. Read more

How Intel HD Graphics On Linux Compare To Open-Source AMD/NVIDIA Drivers With Steam On Linux

As earlier this week I did a 20-way AMD Radeon open-source comparison, looked at the most energy efficient Radeon GPUs for Linux gaming, and then yesterday provided a look at the fastest NVIDIA GPUs for open-source gaming with Nouveau, in this article is a culmination of all the open-source graphics tests this week while seeing how Intel Haswell HD Graphics fall into the mix against the open-source Radeon R600/RadeonSI and Nouveau NV50/NVC0 graphics drivers. Read more

Leftovers: Gaming