Language Selection

English French German Italian Portuguese Spanish

openSUSE 10.3 Beta 3 Report

Filed under
Reviews
SUSE
-s

Welp, we're in the homestretch now. Beta 3 of openSUSE 10.3 was released a few days ago, and with only one more developmental release before final, we were hoping things were starting to shape up. This release doesn't bring too many surprises or any new eye candy, but most subsystems are stablizing. With 587 MB of changes, developers are homing in on their goal.

As stated I didn't see any new eye candy or other new components. I did two major tests: a fresh install on my HP laptop and an upgrade of Alpha 7 on my desktop. The upgrade process seemed to take longer than the fresh install, but for the most part it seemed to go fairly smooth. The system appears to fully functional even if I think I experience a second of lag between clicking the mouse and the resulting action. The update applet doesn't appear on the KDE desktop, but the one in the GNOME panel seems to work. I applied most of updates during the install, so there was only test packages left by the time I got to the desktop, but the process did complete without problems. One was an update to Sax2 and one was a kernel update (due to an bug with setfont interaction). This kernel update erased all previous kernels and only left the newest, but there didn't seem to be any negative issues with the upgrade.

The only quirk noted in the process was with the installer itself. On my desktop I have more than 15 partitions, so I decide to boot with the parameter hwprobe=-modules.pata as suggested. But when it came time to read the packages database off the DVD, the installer kept asking for CD 1 and finally aborted the install. So, I had to end up installing using sata.

The fresh install on the laptop went smoothly as well. Again the Grub installation didn't see my Slackware install, but my other installs were added to the Grub configuration and this time they worked - albeit through another Grub screen (chainloaded).

On the laptop, I'm still having trouble with the Online Updates. Since it uses a ethernet chip that requires loading through Ndiswrapper, I had to put off setting up Online Repositories until after the completion of the install and I had booted the new system. I supposed that is the difference (between why the Updater works with the desktop and doesn't on the laptop). Setting up this repo seemed to work at first, but it could never finish checking for updates. Then on subsequent logins, it says it doesn't have a repo set up. Re-running the set up wizard doesn't help.

The software manager worked well, as did the online 1-Click service - although it was far from one click. I must have clicked okay about 8 times throughout the process. Big Grin This starts at software.openSUSE.org/search where you will choose your openSUSE version. From there you will search for the package you're interested in installing. It will then list matches and once you determine which is your package, you click the "1-Click" button. This downloads a .ymp file to your machine and a window opens to walk you through the rest of the installation.

        


The Release Notes contain some interesting tidbits this release. The first of note is the decision to use "bigsmp" kernel as default on x86 systems now. I first noticed this upon the upgrade of my desktop, but the release notes explains that this allows the hardware "NX" (no-execute) feature to be utilized on supported hardware. Another development is that Ctrl+Alt+Backspace doesn't kill X now. Apparently there were a high number of users who killed X by accident, so it has been disabled. There is a cheat code one can use to put this functionality back. Comment out Option "DontZap" "yes" in /etc/X11/xorg.conf. Another point is the different YaST interfaces for KDE and GNOME that I mentioned last report. By default KDE will use the qt front-end and GNOME will use a gtk frontend. If you prefer one over the other and wish it use it at all times, you can change WANTED_GUI="auto" to WANTED_GUI="???" in the /etc/sysconfig/yast2 file (where ??? is either qt or gtk). So that's neato.

It was revealed by beineri that "openSUSE 10.3 [will] not shipping KDE 4.0 as default KDE desktop" as previously hoped. This is probably due to the updated release schedule of KDE 4. I'm sure everyone's heard by now that KDE 4 won't be finalized until just before Christmas. They will still probably include the latest developmental release at least on mirrors.

Some Changelog Highlights:

++++ OpenOffice_org:

- updated to milestone oog680-m3 (OOo-2.3.rc1)
- updated ooo-build to 2.3.0.1

++++ gnome2-SuSE:

- update session splash to 10.3 artwork

++++ kdebase3-SuSE:

- prepare for Live Installer desktop icon handling (#297617)
- SUSEgreeter: use white for the close button label in header

++++ splashy:

- do not put /etc/suspend.conf into the initrd

++++ suspend:

- updated to current CVS (0.7rc, will be 0.7 soon)

++++ kdebase4:

- update to KDE 4.0 Beta 2

++++ gimp:

- update branding to 10.3 artwork

++++ gnome-desktop:

- Update to version 2.19.90

++++ hal:

- updated hal/hal-info to current git (20070831)

++++ php5:

- update to PHP 5.2.4

++++ release-notes:

- Add more entries

++++ wesnoth:

- updated to maintenance release 1.2.6

++++ evolution:

- Update to version 2.11.91

++++ Full Changelog since Beta 2

Some RPM Highlights:

  • OpenOffice_org-2.3.0.1-2

  • MozillaFirefox-2.0.0.6-9
  • SDL-1.2.12-16
  • alsa-1.0.14-27
  • amarok-1.4.7-22
  • apache2-2.2.4-62
  • cairo-1.4.10-19
  • cmake-2.4.7-12
  • compiz-0.5.4-11
  • cups-1.2.12-13
  • gcc-4.2-21
  • gimp-2.2.17-25
  • glibc-2.6.1-12
  • gnome-desktop-2.19.90-3
  • gtk2-2.11.6-20
  • hal-0.5.9_git20070831-2
  • kdebase3-3.5.7-67
  • kdebase4-3.93.0-3
  • kernel-bigsmp-2.6.22.5-10 (2.6.22.5-12 available)
  • make-3.81-62
  • mysql-5.0.45-15
  • ndiswrapper-1.47-22
  • perl-5.8.8-73
  • php5-5.2.4-3
  • python-2.5.1-32
  • qt3-3.3.8-67
  • rpm-4.4.2-136
  • udev-114-10
  • xorg-x11-7.2-126
  • Full RPM List

Outstanding Most Annoying Bugs

* Kernel update doesn't create initrd if bootloader is on another partion Bug #308970
Workaround: run mkintrd manually before reboot.
* YaST Software Management complains of not having enough disk space even though there is lots to be had (Bug #308362)
* Newer logitech mice that use evdev cause SaX2 to fail

Remaining RoadMap

* Thu, Sep 20: openSUSE 10.3 Release Candidate 1 release
* Thu, Sep 27: openSUSE 10.3 Goldmaster release (internal)
* Thu, Oct 4: openSUSE 10.3 public release

So, it's getting there. There is no new eye candy this release except a coupla application splashes, but overall functionality is improving. There were a few changes under the hood, but fortunately some have some user configuration options. The Online Update is improving and the bootloader system detection and installation is working better. There is one more test release before final, so we are looking forward to a great release.

I have more screenshots in the gallery and my previous coverage can be found here.

    


1-Click Install

Just a note behind the naming:

It was called one-click install since you only require one click to initiate the whole process, then it's just a wizard. While typically you would need to:
(Sleepy hunt down the package you need
(ii) add the repository that it's in
(iii) add it to YaST's 'Software Repositories'
(iv) start up YaST's 'Software Management'
(v) Select the Packages to be Installed

Now you don't have to worry about all the repository adding, or the appropriate package-selecting. I can i.e. create a Compiz.ymp or a Codecs.ymp and then it will do all the work for you, installing all the necessary dependencies, etc. It's very convenient, for users and developers Smile

1 click install very

1 click install very helpful, i luv it!

Comment viewing options

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

More in Tux Machines

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers

today's howtos