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

    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