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

LibreOffice Office Suite Celebrates 6 Years of Activity with LibreOffice 5.2.2

Today, September 29, 2016, Italo Vignoli from The Document Foundation informs Softpedia via an email announcement about the general availability of the first point release of the LibreOffice 5.2 open-source and cross-platform office suite. On September 28, the LibreOffice project celebrated its 6th anniversary, and what better way to celebrate than to push a new update of the popular open source and cross-platform office suite used by millions of computer users worldwide. Therefore, we would like to inform our readers about the general availability of LibreOffice 5.2.2, which comes just three weeks after the release of LibreOffice 5.2.1. "Just one day after the project 6th anniversary, The Document Foundation (TDF) announces the availability of LibreOffice 5.2.2, the second minor release of the LibreOffice 5.2 family," says Italo Vignoli. "LibreOffice 5.2.2, targeted at technology enthusiasts, early adopters and power users, provides a number of fixes over the major release announced in August." Read more

OSS Leftovers

  • But is it safe? Uncork a bottle of vintage open-source FUD
    Most of the open source questioners come from larger organisations. Banks very rarely pop up here, and governments have long been hip to using open source. Both have ancient, proprietary systems in place here and there that are finally crumbling to dust and need replacing fast. Their concerns are more oft around risk management and picking the right projects. It’s usually organisations whose business is dealing with actual three dimensional objects that ask about open source. Manufacturing, industrials, oil and gas, mining, and others who have typically looked at IT as, at best, a helper for their business rather than a core product enabler. These industries are witnessing the lighting fast injection of software into their products - that whole “Internet of Things” jag we keep hearing about. Companies here are being forced to look at both using open source in their products and shipping open source as part of their business. The technical and pricing requirements for IoT scale software is a perfect fit for open source, especially that pricing bit. On the other end - peddling open source themselves - companies that are looking to build and sell software-driven “platforms” are finding that partners and developers are not so keen to join closed source ecosystems. These two pulls create some weird clunking in the heads of management at these companies who aren’t used to working with a sandles and rainbow frame of mind. They have a scepticism born of their inexperience with open source. Let’s address some of their trepidation.
  • Real business innovation begins with open practices
    To business leaders, "open source" often sounds too altruistic—and altruism is in short supply on the average balance sheet. But using and contributing to open source makes hard-nosed business sense, particularly as a way of increasing innovation. Today's firms all face increased competition and dynamic markets. Yesterday's big bang can easily become today's cautionary tale. Strategically, the only viable response to this disruption is constantly striving to serve customers better through sustained and continuous innovation. But delivering innovation is hard; the key is to embrace open and collaborative innovation across organizational walls—open innovation. Open source communities' values and practices generate open innovation, and working in open source is a practical, pragmatic way of delivering innovation. To avoid the all-too-real risk of buzzword bingo we can consider two definitions of "innovation": creating value (that serves customer needs) to sell for a profit; or reducing what a firm pays for services.
  • This Week In Servo 79
    In the last week, we landed 96 PRs in the Servo organization’s repositories. Promise support has arrived in Servo, thanks to hard work by jdm, dati91, and mmatyas! This does not fully implement microtasks, but unblocks the uses of Promises in many places (e.g., the WebBluetooth test suite). Emilio rewrote the bindings generation code for rust-bindgen, dramatically improving the flow of the code and output generated when producing Rust bindings for C and C++ code. The TPAC WebBluetooth standards meeting talked a bit about the great progress by the team at the University of Szeged in the context of Servo.
  • Servo Web Engine Now Supports Promises, Continues Churning Along
    It's been nearly two months since last writing about Mozilla's Servo web layout engine (in early August, back when WebRender2 landed) but development has kept up and they continue enabling more features for this next-generation alternative to Gecko. The latest is that Servo now supports JavaScript promises. If you are unfamiliar with the promise support, see this guide. The latest Servo code has improvements around its Rust binding generator for C and C++ code plus other changes.
  • Riak TS for time series analysis at scale
    Until recently, doing time series analysis at scale was expensive and almost exclusively the domain of large enterprises. What made time series a hard and expensive problem to tackle? Until the advent of the NoSQL database, scaling up to meet increasing velocity and volumes of data generally meant scaling hardware vertically by adding CPUs, memory, or additional hard drives. When combined with database licensing models that charged per processor core, the cost of scaling was simply out of reach for most. Fortunately, the open source community is democratising large scale data analysis rapidly, and I am lucky enough to work at a company making contributions in this space. In my talk at All Things Open this year, I'll introduce Riak TS, a key-value database optimized to store and retrieve time series data for massive data sets, and demonstrate how to use it in conjunction with three other open source tools—Python, Pandas, and Jupyter—to build a completely open source time series analysis platform. And it doesn't take all that long.
  • Free Software Directory meeting recap for September 23rd, 2016

Security News

  • security things in Linux v4.5
  • Time to Kill Security Questions—or Answer Them With Lies
    The notion of using robust, random passwords has become all but mainstream—by now anyone with an inkling of security sense knows that “password1” and “1234567” aren’t doing them any favors. But even as password security improves, there’s something even more problematic that underlies them: security questions. Last week Yahoo revealed that it had been massively hacked, with at least 500 million of its users’ data compromised by state sponsored intruders. And included in the company’s list of breached data weren’t just the usual hashed passwords and email addresses, but the security questions and answers that victims had chosen as a backup means of resetting their passwords—supposedly secret information like your favorite place to vacation or the street you grew up on. Yahoo’s data debacle highlights how those innocuous-seeming questions remain a weak link in our online authentication systems. Ask the security community about security questions, and they’ll tell you that they should be abolished—and that until they are, you should never answer them honestly. From their dangerous guessability to the difficulty of changing them after a major breach like Yahoo’s, security questions have proven to be deeply inadequate as contingency mechanisms for passwords. They’re meant to be a reliable last-ditch recovery feature: Even if you forget a complicated password, the thinking goes, you won’t forget your mother’s maiden name or the city you were born in. But by relying on factual data that was never meant to be kept secret in the first place—web and social media searches can often reveal where someone grew up or what the make of their first car was—the approach puts accounts at risk. And since your first pet’s name never changes, your answers to security questions can be instantly compromised across many digital services if they are revealed through digital snooping or a data breach.
  • LibreSSL and the latest OpenSSL security advisory
    Just a quick note that LibreSSL is not impacted by either of the issues mentioned in the latest OpenSSL security advisory - both of the issues exist in code that was added to OpenSSL in the last release, which is not present in LibreSSL.
  • Record-breaking DDoS reportedly delivered by >145k hacked cameras
    Last week, security news site KrebsOnSecurity went dark for more than 24 hours following what was believed to be a record 620 gigabit-per-second denial of service attack brought on by an ensemble of routers, security cameras, or other so-called Internet of Things devices. Now, there's word of a similar attack on a French Web host that peaked at a staggering 1.1 terabits per second, more than 60 percent bigger. The attacks were first reported on September 19 by Octave Klaba, the founder and CTO of OVH. The first one reached 1.1 Tbps while a follow-on was 901 Gbps. Then, last Friday, he reported more attacks that were in the same almost incomprehensible range. He said the distributed denial-of-service (DDoS) attacks were delivered through a collection of hacked Internet-connected cameras and digital video recorders. With each one having the ability to bombard targets with 1 Mbps to 30 Mbps, he estimated the botnet had a capacity of 1.5 Tbps. On Monday, Klaba reported that more than 6,800 new cameras had joined the botnet and said further that over the previous 48 hours the hosting service was subjected to dozens of attacks, some ranging from 100 Gbps to 800 Gbps. On Wednesday, he said more than 15,000 new devices had participated in attacks over the past 48 hours.

Android Leftovers