Language Selection

English French German Italian Portuguese Spanish

SUSE Linux 10.0 Beta 2 Report

Filed under
Reviews
SUSE
-s

The "Lizard Blizzard" continues as OpenSUSE released Beta 2 of the upcoming SUSE Linux a coupla days ago. So what's new in this release since the August 9th release of Beta 1?


Most of the changes appear to have taken place beneath the hood, updating software versions, squashing bugs, kernel patches and the like. But to the nekked eye, upon boot one notices the koffice icon on the desktop has been replaced by an OpenOffice.org icon. The late developemental version 1.9.123 of OOo is presently included with OpenSUSE. I've been running a pre-2.0 version of OOo for months on my gentoo install due to some bugs (or updated dependencies), and have found it to be very stable and much nicer looking. Novell lays claim to a "Novell Edition" on OpenSUSE. I didn't note anything special about it other than a nice start splash. If anyone knows, please feel free to respond.

Another addition to the desktop is a systray icon for Beagle. Clicking on that opens the Beagle search tool. I supposed that could be a handy feature. Speaking of the Beagle search utility, it now also has a systray icon in gnome as well. So, now Beagle opens each login not only in KDE but gnome as well. I'm sure this has got to be a bug, I hope so.

Also included is KAT. It's not installed by default, but I did note references to updating to version 0.6.2. I first became aware of this wonderful utility with the release of Mandriva's 2006 Beta 2. In subsequent communication with the author I found it to be much more comprehensive than Beagle and I hope OpenSUSE will consider using it as default as opposed to Beagle, especially if that feature of opening each and every login continues.

Oh man, speaking of logins, if one logs in, one must inevitably log back out. Another bug that reared it ugly head in Beta 2 is the total lock up of the system when logging out KDE, gnome, or icewm. This happens if you choose log out or reboot. How annoying. I had to hit reset 3 times in researching SUSE Linux for this article. Fortunately I chose the reiser filesystem and haven't lost data or my install yet.

Also new are many more modules in yast. Many deal with more options for networking and more hardware configurations. I thought I'd test out installing and configuring Zen. It made it through the extensive install, however, all of yast crashed and burnt when it was time to do the configuring and finish the install.

So, all in all, I found that Beta 2 introduced several new bugs and a few new features. An old friend at Mandrake once told me that sometimes the more bugs you squash, the more you make. ...Meaning that sometimes you fix one bug and it introduces two more. He said that's why sometimes you have to choose to release even though you know there are some bugs as they might be preferrable to the ones you make when you fix the first ones.

Some highlights in the 6 mb ChangeLog include:

  • ifolder3:

    • changed prefix to /usr/lib/ifolder3 [#104474]
  • installation-images:
    • fixed /etc permissions (#104715)
  • nmap:
    • Don't strip binaries
  • yast2
    • Lots of typo fixes, and bug fixes
  • OpenOffice_org:
    • fixed some potentially dangerous warnings

    • fixed to build portaudio with RPM_OPT_FLAGS
    • updated branding for 10.0 [#102355]
  • hotplug:
    • removed also desktop templates

    • removed all files except hotplug.functions and desktop templates
      package will be dropped completely in next beta
  • hwinfo:
    • added hdtv cards (#102933)

    • find input device udi (#102575)
    • fixed usb device udi matching (#102575)
    • read modules.alias, not modules.pcimap
    • updated X11 data
  • initial:
    • minor string format changes to ease the translators' work

    • updated po/{de,fr}.po
    • added po/{cs,hu,nb,pa,pt}.po
  • installation-images:
    • added sfdisk
  • kernel-source:
    • update to 2.6.13-rc6-git7

    • config.conf: Enable Xen build.
    • series.conf: Re-activated ntfs-subfs
  • Lots and lots of application version updates
  • Way too much to list here

I've carved down the changelog to only include since the last beta release and posted it here.

I've posted the License.txt here, as some expressed interest in it. Glancing over it, I'm not sure it's exactly the same one as in the installer, but this is the readable version on the install isos.

I've posted a complete list of rpms included as tested here if you wanted to check on the progress of your favorite app.

I've posted some screenshots of some of the new features here.

For a more complete report of the goodies in SUSE Linux by OpenSUSE, consult my previous report.

re: better experience

Oh wonderful! Good news. Thanks for your input. Smile

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

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

More in Tux Machines

today's howtos

GameMode 1.5

  • Feral's GameMode 1.5 Now Supports Changing The CPU Governor Differently For iGPUs

    With Feral's GameMode 1.5 the big change facing users is for those running integrated graphics. In a change led by an Intel open-source graphics driver developer, GameMode now supports setting an alternative CPU frequency scaling governor for integrated graphics use-cases. Up to now GameMode has defaulted to always using the "performance" CPU frequency scaling governor for normally delivering the best performance, but for integrated graphics that in some situations can lead to lower performance. Due to the integrated graphics and CPU cores sharing the same power envelope, ramping up the CPU performance can throw the graphics performance out of balance and at least for some games lead to lower performance. So with GameMode 1.5, the user can now opt for "powersave" or an alternative governor instead when using an iGPU.

  • Feral Interactive's open source 'GameMode' system performance booster has a new release

    Feral Interactive don't just port a lot of games to Linux, they also work on some open source bits here and there. One of their projects is GameMode, which just got a new release. GameMode is a "daemon/lib combo for Linux that allows games to request a set of optimisations be temporarily applied to the host OS and/or a game process". In simple terms, it can help ensure your Linux PC is giving the game all it can to run smoothly. Looks like someone new is handling the project too, with Alex Smith having left Feral Interactive.

Mozilla on Privacy Badger, Rust and Digital ID Systems

  • Firefox Extension Spotlight: Privacy Badger

    People can't be expected to understand all of the technically complex ways their online behavior is tracked by hidden entities. As you casually surf the web, there are countless techniques different third party actors use to secretly track your online movement. So how are we supposed to protect our privacy online if we don't even understand how the game works? To help answer this, the good folks at the Electronic Frontier Foundation (a non-profit devoted to defending digital privacy) built Privacy Badger--a browser extension designed to give you highly advanced tracking protection, while requiring you to do nothing more than install it on Firefox. No configuration, no advanced settings, no fuss. Once you have Privacy Badger installed, it automatically scours every website you visit in its relentless hunt for hidden trackers. And when it finds them, blocks them.

  • This Week In Rust: This Week in Rust 322
  • What could an “Open” ID system look like?: Recommendations and Guardrails for National Biometric ID Projects

    Digital ID systems are increasingly the battlefield where the fight for privacy, security, competition, and social inclusion is playing out. In our ever more connected world, some form of identity is almost always mediating our interactions online and offline. From the corporate giants that dominate our online lives using services like Apple ID and Facebook and Google’s login systems to government IDs which are increasingly required to vote, get access to welfare benefits, loans, pay taxes, get on transportation or access medical care. Part of the push to adopt digital ID comes from the international development community who argue that this is necessary in order to expand access to legal ID. The UN Sustainable Development Goals (SDGs) call for “providing legal identity for all, including birth registration” by 2030. Possessing legal identity is increasingly a precondition to accessing basic services and entitlements from both state and private services. For the most marginalised communities, using digital ID systems to access essential services and entitlements from both state and private services are often one of their first interactions with digital technologies. Without these commonly recognized forms of official identification, individuals are at risk of exclusion and denial of services. However, the conflation of digital identity as the same as (or an extension of) “legal identity”, especially by the international development community, has led to an often uncritical embrace of digital ID projects. In this white paper, we survey the landscape around government digital ID projects and biometric systems in particular. We recommend several policy prescriptions and guardrails for these systems, drawing heavily from our experiences in India and Kenya, among other countries. In designing, implementing, and operating digital ID systems, governments must make a series of technical and policy choices. It is these choices that largely determine if an ID system will be empowering or exploitative and exclusionary. While several organizations have published principles around digital identity, too often they don’t act as a meaningful constraint on the relentless push to expand digital identity around the world. In this paper, we propose that openness provides a useful framework to guide and critique these choices and to ensure that identity systems put people first. Specifically, we examine and make recommendations around five elements of openness: multiplicity of choices, decentralization, accountability, inclusion, and participation.

Red Hat/IBM: Red Hat Enterprise Linux, OpenShift 4.3 and OpenSCAP

  • Red Hat Enterprise Linux 8 for SAP Solutions on IBM POWER9: An open foundation to power intelligent business decisions

    At Red Hat Summit 2019, we unveiled Red Hat Enterprise Linux 8, the next generation of the world’s leading enterprise Linux platform, which provides the scale, flexibility and innovation to drive enterprise workloads across the hybrid cloud. Even with the advancements across the platform, we recognize that there’s no singular panacea to overcome every unique IT challenge. To meet these needs, Red Hat delivers specialized offerings built around Red Hat Enterprise Linux to address specific hardware, applications and environment requirements, and Red Hat Enterprise Linux 8 continues this strategy with the availability of Red Hat Enterprise Linux 8 for SAP Solutions on IBM Power Systems (POWER9).

  • OpenShift 4.3: Quay Container Security Integration

    In the Red Hat OpenShift 4.2 Web UI Console, we introduced a new Cluster Overview Dashboard as the landing page when users first log in. The dashboard is there to help users resolve issues more efficiently and maintain a healthy cluster. With the latest 4.3 release, we added an image security section to the cluster health dashboard card. This section will appear on the dashboard when the Container Security Operator gets installed.

  • Deploying OpenSCAP on Satellite using Ansible

    In many environments today, security is one of the top priorities. New information security vulnerabilities are discovered regularly, and these incidents can have a significant impact on businesses and their customers. Red Hat customers I talk to are frequently looking for tools they can use to help evaluate and secure their environments. One of these tools is OpenSCAP, which is included in Red Hat Enterprise Linux (RHEL), and can perform compliance and vulnerability scanning on RHEL servers. Satellite makes OpenSCAP easier to use by allowing you to deploy the OpenSCAP agent to hosts, manage the OpenSCAP policies centrally, and to view OpenSCAP reports from the Satellite web interface.