Language Selection

English French German Italian Portuguese Spanish

SUSE 10.1 Beta 6 Report

Filed under
Reviews
SUSE
-s

SUSE 10.1 beta 6 hit the mirrors yesterday and announcements went up all over the web. Seems everyone is following development of 10.1 with great interest. This release brings lots of improvements and a new surprize or two. Overall, we are starting to see the release the 10.1 will become.

OSNews was full of tidbits concerning the development of 10.1. Some highlights include a new roadmap and development plans. They include the interesting quote, "we will go to a bi-weekly schedule and have one more beta." We can expect one more beta, dubbed 8, on or about March 17 and release candidate 1 around March 31. Significant to close followers and testers was the news that all release candidates will only come in the form of delta isos or in the factory tree. We can expect the final announcement on April 13.

Not ones to take much of a vacation, plans for 10.2 were also announced. Testing will start with Alpha 1 on June 16 and 10.2 final can be expected around year's end.

Our subject today, 10.1 beta6 is much improved and evidence starts with a much slimmer "annoying bug list." The few items remaining are:

  • The CD 1 needs to remain in the cd drive after installing from it. Do not remove it during the reboot and wait for YaST to request CD 2.. Otherwise the installation of packages from CD 2-5 will fail afterwards Bug 153073.
  • The partitioner is broken in some cases Bug 151947. which might result in:
    • mixed up filesystem types - for example one chooses ext2 and the partition is getting formatted with reiserfs
    • creates double or totally obscure entries within the fstab of the system
    • makes inproper proposals for a standard partitioning
  • Download of Release Notes will fail.
  • The online test with download of Updates will fail.

The first thing I noticed upon boot of the installation system was the appearance of a new menu screen. It is a very attractive more tasteful blue and very closely matching the rest of the new theme we've seen recently. They state in red letters that this is a preliminary theme and request no complaints. They would get none from me as I think it looks really great.

        

The next thing that I noticed was that hard drive installs, or probably any of the manual installs for that matter, have now returned to their fully functional status. Woohoo! <snoopy dance> And from there the installer is pretty much as we encountered last time, not forgetting the recent addition of a hostname configuration step and the tidied-up software selection screens we found in the last beta.

        

Towards the end of the install, I did encounter the failed online test and received a chance to view logs, however some Release Notes did present themselves. One warning involved a work around if needed for slow fonts in mozilla due to pango.

Earlier in the install process, I did have some trouble with some packages not being installed properly. The errors stated trouble with db similar to the one we get after install when trying to use the package manager. In fact, installation stopped completely here a time or two. I was left with the busy cursor for extended periods, at which point I had to restart. The package counter and timer were way off the mark this time as well. So, my installation was still a bit challenging here.

Upon boot, kde looked its usual wonderful self, but gnome was broken once again. Gnome would start here and a desktop appeared along with the usual icons. I got an empty panel on top of the screen and nothing at the bottom. Gnome was fairly crippled at this point. Whether this is a result of more package installation bugs is up for speculation, although I'm fairly sure it must be.

After install, the software package system showed more signs of improvement. This beta brings the return of the installation sources catagory and a full listing of individual packages either installed or installable. However, packages still can't install due to that db recovery problem.

        

    

The yast online update has a new look, in fact it's a new method. It is now executed through the firefox browser as opposed to an application very similar in appearance and functionality of the regular software packager. There were no updates available and I doubt they would have installed at this point anyway.

        

Another newcomer to 10.1 is Kerry. Kerry is a kde front-end for Beagle. With initial integration on December 16, it brings a nice looking graphical interface to an established desktop search tool. It differs from the regular Beagle interface slightly, but does integrate into KDE wonderfully giving a more uniform environment. The usual functions are present with a variety of search capabilities and one can view the file in an associated program or in a file manager. It's a nice addition.

        

So, we are beginning to see some vast improvements in the functionality and usability in some of the system tools as well as more integration of some applications with the differing desktops. We are able to get more of a glimpse into what 10.1 might become and how some of the newer tools might appear and function. We also now have a peak into what further improvements will be made to theming of the installer and bootloader. We will not be privy to a beta7 and will have to wait for a beta8 around March 17. Allowing more of a lapse in time of internal testing as well as keeping beta7 internal, we have high hopes for the improvements awaiting us in beta8.

Some new version number highlights this release are:

  • kernel-default-2.6.16_rc5_git2-2

  • MozillaFirefox-1.5.0.1-11
  • gaim-1.5.0-34
  • xorg-x11-6.9.0-20
  • kdebase3-3.5.1-32
  • gnome-desktop-2.12.2-9
  • samba-3.0.21c-4
  • python-2.4.2-7
  • perl-5.8.8-6
  • kerry-0.07-6
  • OpenOffice_org-kde-2.0.2-4
  • beagle-0.2.1-28
  • Full List as tested.

Some changelog highlights include:

  • kernel-default

    - update patches.drivers/e100-ethtool-sefltest.patch
    fix ethtool -t support
    - add patches.arch/ppc-iseries-double-phys_to_abs.patch
    Fix double phys_to_abs bug in htab_bolt_mapping
    - update to 2.6.16-rc5-git2, netfilter, xfs, x86_64 fixes
    disable FUA in libata
    -Fix partition table reading for DASDs
    - Stop using bash's =~ operator

  • banshee:

    - Fix missing columns in banshee

  • evolution:

    - Update to version 2.5.92
    -lots and lots of bug fixes

  • gnome-system-monitor:

    - added system info tab

  • kerry:

    - call beagle-shutdown on KDE logout

  • amarok:

    - Ensure exclusive access to CollectionDB instances

  • gdm:

    - Add patch to fix tab keynav.

  • xorg-x11:

    - disabled DRI when switching to radeon driver (Bug #152473)
    - disabled DEBUG info for ACPI code

  • Full Changelog since beta 5.

Related Links:

  • 10.1 Beta 5.
  • 10.1 Beta 4.
  • 10.1 Beta 3.
  • 10.1 Beta 1.
  • Few New Screenshots.
  • Anybody, Yoper 3 Beta?

    After everybody thought it was dead, Yoper released a new pre-release, 3.0-beta! (It's KDE 3.5.0.)

    I guess this aussie distro was quite a competitor for SuSE, esp. in Germany (the KDE-land Smile).

    Anybody trying it yet?!

    Comment viewing options

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

    More in Tux Machines

    ROSA Fresh R9

    ROSA is a desktop distribution that was originally forked from Mandriva Linux, but now is independently developed. While the company which produces ROSA is based in Russia, the distribution includes complete translations for multiple languages. The ROSA desktop distribution is designed to be easy to use and includes a range of popular applications and multimedia support. ROSA R9 is available in two editions, one featuring the KDE 4 desktop and the second featuring the KDE Plasma 5 desktop. These editions are scheduled to receive four years of support and security updates. I decided to download the Plasma edition of ROSA R9 and found the installation media to be approximately 2GB in size. Booting from the ROSA disc brings up a menu asking if we would like to load the distribution's live desktop environment or begin the installation process. Taking the live option brings up a graphical wizard that asks us a few questions. We are asked to select our preferred language from a list and accept the project's warranty and license. We are then asked to select our time zone and keyboard layout from lists. With these steps completed, the wizard disappears and the Plasma 5.9 desktop loads. Read more

    More of today's howtos

    Software: Linfo, EasyTag, Simple Scan, Albert, VLC, Remote Desktop, Frogr, Brisk Menu, and OpenShot

    • Linfo – Shows Linux Server Health Status in Real-Time
      Linfo is a free and open source, cross-platform server statistics UI/library which displays a great deal of system information. It is extensible, easy-to-use (via composer) PHP5 library to get extensive system statistics programmatically from your PHP application. It’s a Ncurses CLI view of Web UI, which works in Linux, Windows, *BSD, Darwin/Mac OSX, Solaris, and Minix.
    • 2 tag management tools for organizing your music library
      These days, EasyTag seems to be my go-to tag editor. While I can't claim to have tried them all, I have mostly stopped looking now that I have this one. Generally speaking, I like its three-panel layout: file system directory on the left; selected tracks in the middle, showing file name and tags; and specific tags and cover image on the right.
    • New Simple Scan Designs Emerge; Seeking Devs to Implement Them
      Simple Scan is one of my personal favourite and perhaps even one of the "essential" apps on the Linux desktop for me. It does what it says on the tin: it's simple and it scans, with a nice preview system and enough options to be decently functional. Some new designs for the app have emerged and they are looking quite nice indeed. GNOME UX designer and Red Hat Desktop Team Member, Allan Day, showed the new mockup designs off in his blog post. Simple Scan has a pretty sparse and simplistic interface already, and I mean that in a positive way, but Allan believes that "just because it's great, doesn't mean it can't be improved" and that most of the improvements are simply "refinements", rather than major overhauls, in order to make some of the app's functions a bit easier to discover and navigate.
    • Albert – A Fast, Lightweight and Flexible Application Launcher for Linux
      A while ago, we have written about Ulauncher which is used to launch application quickly. Today we came up with similar kind of utility called Albert which is doing the same job and have some additional unique features which is not there in ulauncher.
    • 5 Tricks To Get More Out Of VLC Player In Linux
      In fact, for the desktop, VLC is much more than just a tool to play videos stored on your hard drive! So, stay with me for a tour of the lesser known features of that great software.
    • 5 of the Best Linux Remote Desktop Apps to Remotely Access a Computer
      Remote desktop apps are a very useful group of apps because they allow access to a computer anywhere in the world. While the simplest way to do this is via a terminal, if you don’t want to have to type commands but rather want a more advanced way to access a remote computer, here are five of the best remote desktop apps for Linux.
    • Frogr 1.3 released
    • Brisk Menu 0.4.0 Is Out with Super Key Support, Adapts to Vertical Panel Layouts
      Solus Project founder and lead developer Ikey Doherty is today announcing the release and immediate availability of the Brisk Menu 0.4.0 application menu for Solus and other supported GNU/Linux distributions.
    • OpenShot 2.3.3 Open-Source Video Editor Released with Stability Improvements
      OpenShot developer Jonathan Thomas is announcing the release and immediate availability of the third maintenance update to the OpenShot 2.3 stable series of the open-source and cross-platform non-linear video editor.

    CloudReady - Chromebook re-experienced

    I haven't done any extensive testing, but then, how much testing is really needed to run a bunch of Web apps. The whole idea is to have this cloud-based operating system, with easy, flexible access to your data anywhere you go. So if you judge this from the perspective of a typical desktop, you miss the point. But that is the point. When I install something on a desktop-like form factor, I expect its behavior to match. CloudReady takes you away from that experience, and the transition is not comfortable. You feel very limited. This makes a lot of sense for schools, for instance, where you do want to lock down the devices, and make them simple for reuse. In a home setup, why would you go for just cloud, when you can have that plus any which desktop application on a typical system? After all, nothing prevents you from launching a browser and using Google applications, side by side with your desktop stuff. It's the same thing. The notion of reviving old hardware is a bit of a wishful thinking. My eeePC test shows that it gets completely crippled when you run HD content in either Firefox or Chrome. An operating system based on Chromium OS will not drastically change that. It cannot do that. Maybe you will have better performance than having Windows there, the same way I opted for a Linux setup on the Asus netbook, but there are physical limits to what old hardware can accomplish. And then, there's the whole question of cloud ... Most people might be comfy with this, after having used smartphones for a while, but I don't think this is anything novel or mindblowing. CloudReady works as advertised, it's a very cool concept, but ultimately, it gives you a browser on steroids. Google and Neverware have their own agenda for doing this, but for home users, there really isn't any added value in transforming their keyboard-and-mouse box into a browsing portal. So if you ask me, am I ready for the cloud, the answer is, only when it becomes sophisticated enough to match my productivity and freedom of creativity. And for you, do you want a simple, locked down, secure and entirely Google machine that isn't a mobile phone or a dedicated piece of hardware? The answer is 42. Read more