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

Android Leftovers

today's leftovers

  • Upcoming SAVVY-V Open Source RISC-V Cluster Board Supports 10GbE via Microsemi PolarFire 64-bit RISC-V SoC

    RISC-V based PolarFire SoC FPGA by Microsemi may be coming up in the third quarter of this year, but Ali Uzel has been sharing a few details about SAVVY-V advanced open-source RISC-V cluster board made by FOSOH-V (Flexible Open SOurce Hardware for RISC-V) community of developers. It’s powered by Microsemi Polarfire RISC-V SoC MPFS250T with four 64-bit RISC-V cores, a smaller RV64IMAC monitor core, and FPGA fabric that allows 10GbE via SFP+ cages, and exposes six USB Type-C ports. The solution is called a cluster board since up to six SAVVY-V boards can be stacked via a PC/104+ connector and interfaced via the USB-C ports.

  • Some PSAs for NUC owners

    I’ve written before, in Contemplating the Cute Brick, that I’m a big fan of Intel’s NUC line of small-form-factor computers. Over the last week I’ve been having some unpleasant learning experiences around them. I’m still a fan, but I’m shipping this post where the search engines can see it in support of future NUC owners in trouble. Two years ago I bought an NUC for my wife Cathy to replace her last tower-case PC – the NUC8i3BEH1. This model was semi-obsolete even then, but I didn’t want one of the newer i5 or i7 NUCs because I didn’t think it would fit my wife’s needs as well. What my wife does with her computer doesn’t tax it much. Web browsing, office work, a bit of gaming that does not extend to recent AAA titles demanding the latest whizzy graphics card. I thought her needs would be best served by a small, quiet, low-power-consumption machine that was cheap enough to be considered readily disposable at the end of its service life. The exact opposite of my Great Beast… The NUC was an experiment that made Cathy and me happy. She especially likes the fact that it’s small and light enough to be mounted on the back of her monitor, so it effectively takes up no desk space or floor area in her rather crowded office. I like the NUC’s industrial design and engineering – lots of nice little details like the four case screws being captive to the baseplate so you cannot lose them during disassembly. Also. Dammit, NUCs are pretty. I say dammit because I feel like this shouldn’t matter to me and am a bit embarrassed to discover that it does. I like the color and shape and feel of these devices. Someone did an amazing job of making them unobtrusively attractive. [...] When I asked if Simply NUC knew of a source for a fan that would fit my 8i3BEH1 – a reasonable question, I think, to ask a company that loudly claims to be a one-stop shop for all NUC needs – the reply email told me I’d have to do “personal research” on that. It turns out that if the useless drone who was Simply NUC “service” had cared about doing his actual job, he could have the read the fan’s model number off the image I had sent him into a search box and found multiple sources within seconds, because that’s what I then did. Of course this would have required caring that a customer was unhappy, which apparently they don’t do at Simply NUC. Third reason I know this: My request for a refund didn’t even get refused; it wasn’t even answered.

  • GNU Binutils 2.35 Preparing For Release

    Binutils 2.35 was branched this weekend as this important component to the open-source Linux ecosystem. Binutils 2.35 has been branched meaning feature development is over for this next version of this collection of GNU tools. GNU Binutils 2.356 drops x86 Native Client (NaCl) support with Google having deprecated it in favor of WebAssembly, new options added for the readelf tool, many bug fixes, and an assortment of other changes albeit mostly on the minor side.

  • Using CPU Subsets for Building Software

    NetBSD has a somewhat obscure tool named psrset that allows creating “sets” of cores and running tasks on one of those sets. Let’s try it: [...]

  • What a TLS self signed certificate is at a mechanical level

    To simplify a lot, a TLS certificate is a bundle of attributes wrapped around a public key. All TLS certificates are signed by someone; we call this the issuer. The issuer for a certificate is identified by their X.509 Subject Name, and also at least implicitly by the keypair used to sign the certificate (since only an issuer TLS certificate with the right public key can validate the signature).

  • Security Researchers Attacked Google’s Mysterious Fuchsia OS: Here’s What They Found

    A couple of things that Computer Business Review has widely covered are important context for the security probe. (These won’t be much surprise to Fuchsia’s followers of the past two years.)

    i.e. Fuschsia OS is based on a tiny custom kernel from Google called Zircon which has some elements written in C++, some in Rust. Device drivers run in what’s called “user mode” or “user land”, meaning they’re not given fully elevated privileges. This means they can be isolated better.

    In user land, everything that a driver does has to go via the kernel first before hitting the actually computer’s resources. As Quark Labs found, this is a tidy way of reducing attack surface. But with some sustained attention, its researchers managed to get what they wanted: “We are able to gain kernel code execution from a regular userland process.”

  • What have you been playing on Linux? Come and have a chat

    Ah Sunday, that special day that's a calm before the storm of another week and a time for a community chat here on GOL. Today, it's our birthday! If you didn't see the post earlier this week, GamingOnLinux as of today has hit the big 11 years old! Oh how time sure flies by. Onto the subject of gaming on Linux: honestly, the majority of my personal game time has been taken up by Into the Breach. It's so gorgeously streamlined, accessible, fun and it's also ridiculously complex at the same time. Tiny maps that require a huge amount of forward thinking, as you weigh up each movement decision against any possible downsides. It's like playing chess, only with big mecha fighting off aliens trying to take down buildings. [...] I've also been quite disappointed in Crayta on Stadia, as it so far hasn't lived up to even my smallest expectations for the game maker. It just seems so half-baked, with poor/stiff animations and a lack of any meaningful content to start with. I'll be checking back on it in a few months but for now it's just not fun.

Programming Leftovers (LLVM Clang, R, Perl and Python)

  • Arm Cortex-A77 Support Upstreamed Finally To LLVM Clang 11

    While the Arm Cortex-A77 was announced last year and already has been succeeded by the Cortex-A78 announcement, support for the A77 has finally been upstreamed to the LLVM Clang compiler. The Cortex-A77 support was added to the GCC compiler last year while seemingly as an oversight the A77 support wasn't added to LLVM/Clang until this week.

  • Dirk Eddelbuettel: Rcpp now used by 2000 CRAN packages–and one in eight!

    As of yesterday, Rcpp stands at exactly 2000 reverse-dependencies on CRAN. The graph on the left depicts the growth of Rcpp usage (as measured by Depends, Imports and LinkingTo, but excluding Suggests) over time. Rcpp was first released in November 2008. It probably cleared 50 packages around three years later in December 2011, 100 packages in January 2013, 200 packages in April 2014, and 300 packages in November 2014. It passed 400 packages in June 2015 (when I tweeted about it), 500 packages in late October 2015, 600 packages in March 2016, 700 packages last July 2016, 800 packages last October 2016, 900 packages early January 2017, 1000 packages in April 2017, 1250 packages in November 2017, 1500 packages in November 2018 and then 1750 packages last August. The chart extends to the very beginning via manually compiled data from CRANberries and checked with crandb. The next part uses manually saved entries. The core (and by far largest) part of the data set was generated semi-automatically via a short script appending updates to a small file-based backend. A list of packages using Rcpp is available too.

  • YouTube: The [Perl] Weekly Challenge - 067
  • The [Perl] Weekly Challenge #067

    This week both tasks had one thing in common i.e. pairing two or more list. In the past, I have taken the help from CPAN module Algorithm::Combinatorics for such tasks.

  • Weekly Python StackOverflow Report: (ccxxxiv) stackoverflow python report
  • Flask project setup: TDD, Docker, Postgres and more - Part 1

    There are tons of tutorials on Internet that tech you how to use a web framework and how to create Web applications, and many of these cover Flask, first of all the impressive Flask Mega-Tutorial by Miguel Grinberg (thanks Miguel!). Why another tutorial, then? Recently I started working on a small personal project and decided that it was a good chance to refresh my knowledge of the framework. For this reason I temporarily dropped the clean architecture I often recommend, and started from scratch following some tutorials. My development environment quickly became very messy, and after a while I realised I was very unsatisfied by the global setup. So, I decided to start from scratch again, this time writing down some requirements I want from my development setup. I also know very well how complicated the deploy of an application in production can be, so I want my setup to be "deploy-friendly" as much as possible. Having seen too many project suffer from legacy setups, and knowing that many times such issues can be avoided with a minimum amount of planning, I thought this might be interesting for other developers as well. I consider this setup by no means better than others, it simply addresses different concerns.

Linux Graphics and File Systems

  • DRM Scheduler Improvement, New Epoch Counter, Other DRM Work For Linux 5.9

    Following the drm-misc-next pull request to DRM-Next last week that exposes VRR ranges via DebugFS and other improvements, another round of DRM-Misc-Next material has now been sent in for queuing ahead of the Linux 5.9 cycle.

  • Frame-Buffer Compression Support For Vintage Intel i865 Graphics Revived

    Back in April I wrote about patches for enabling FBC on the Intel 865 chipset nearly two decades after that chipset first shipped. Those patches didn't yet hit the mainline Linux kernel but they were revived again this week. These patches are for enabling frame-buffer compression support on the Intel Extreme 2 Graphics found with the i865 "Springdale" chipset. Frame-buffer compression can yield performance and power efficiency advantages thanks to the reduced bandwidth. Newer generations of Intel graphics hardware have squared away their FBC support for a while but the i865 era support was overlooked until recent patches improving the state pushed it forward enough where it could finally be enabled by default.

  • Reiser5 Pursuing Selective File Migration For Moving Hot Files To High Performance Disks

    Edward Shishkin continues pursuing development of new file-system functionality for Reiser5, the next-generation evolutionary advancement over the controversial Reiser4 file-system. Reiser5 has been working on new features like local volumes with parallel scaling out, data tiering and burst buffers, and other new features. The latest feature being worked on by Shishkin for Reiser5 is selective file migration.