Language Selection

English French German Italian Portuguese Spanish

openSUSE 10.3 Alpha 6 Report

Filed under

openSUSE 10.3 Alpha 6 appeared yesterday, the same day as the unveiling of the new openSUSE News portal. And that right after the big announcement that Andreas was handing over the reins of project manager to Coolo. I kinda expected Alpha 6 to be delayed by that latter news. It wasn't and it was a doozy too. The DVD deltaiso was over a one gig in size, so I was expecting some significant changes and improvements this time.

Testing Machine

Coincidently, the day that Alpha 6 was announced was the same day that I received a nice donation of a new (to me) server machine from a friend of tuxmachines. I was wanting to test it and I decided to kill two birds with one stone and install Alpha 6 on it. It consists of a Gigabyte GA-M51GM-S2G mobo, AMD Athlon 64 x2 4200+ cpu, two gig DDR2-667 RAM, on-board Marvell 88E1116 nic, and on-board Geforce 6100 graphics.


The install routine was pretty much unchanged, except I did spot a new item in the package selection. KDE 4 Base System is now listed. openSUSE had done marvelously with the new machine through the other setup routines, but when I chose that KDE 4 Base System it just stopped responding. I left the office and the hour glass for over 15 minutes, but decided it wasn't going any further. I hit reset and decided not to pick KDE 4 this time. I chose the ususal KDE as main desktop, then GNOME at the package selection, as well as C/C++ and Kernel development. At the end of the install, the downloading of release notes was successful. Another new element of the install process was when I was given a short list of online repositories to choose from if I wished to configure then. The one that was pre-selected is the OSS Factory repo, but I was also offered the non-oss repo. I chose it and again the process stopped at the hour glass and no twinkling hard drive indicator. I waited for about 15 minutes before ctrl+F2'in to /sbin/reboot. I cancelled out of that step completely the second time.


Package management is one of the major areas of change this release. Developers have been working on it throughout but some big changes happened this past month. With the freeze up during installation configuration, I was left with no repositories. Attempting to set this up manually using the Online Update Configuration didn't finish either. It too just sat there appearing to have stopped responding. Another aspect of the new package management is the elimination of the needing to recache the database each start. However, mine still did, or something that looked like it. After reparsing, it gave me the message that only the installed packages would appear, so apparently it didn't even add the install DVD to the local cache. Also at this point the packages are no longer compatible with YUM or Smart. So, all in all, it is a bit broken this time.

Also upon boot my network card which worked during the install no longer worked. ...or rather, it just wasn't started. However, my connection would come right up when started manually.

No new eye candy (or any change in appearance) was seen this release. However, I believe we will see some next release as I read somewhere about some being added to the factory tree after the creation of Alpha 6.

KDE worked rather well, but GNOME is back on the critical list. Tomboy crashes repetitively at start and the panel never finishes loading. We have desktop icons, the Update applet, and time and date, but no menu or quick launchers.

I had trouble with KDE's mount of removable media as user too. I received the error "the option "flush" is not allowed." I also had trouble ssh'in into or out of Alpha 6, which was a first.

Many of my findings correspond with some of the Most Annoying Bugs:

  • Network setup is broken, needs some manual repair or rcnetwork restart

  • Public key for checking release-notes.rpm is unavailable
  • Registration is broken
  • GNOME is W.I.P.
  • Adding default repositories crashes installation

Some of the new version highlights include:

  • kernel-default-2.6.22-5

  • xorg-x11-7.2-96
  • gcc-4.2-9
  • kdebase3-3.5.7-32
  • qt3-3.3.8-49
  • gnome-desktop-2.19.4-3
  • gtk2-2.11.5-3
  • OpenOffice_org-
  • MozillaFirefox-
  • gimp-2.2.13-90
  • ndiswrapper-1.47-5
  • Full RPM List

Some Changelog Highlights are:

++++ compiz:

- Updated to latest git version (0.5.1_git_xxx) to make compiz compile against
new libwnck.
- New schema system.
- Moved gnome-xgl-info and gnome-xgl-switch back to main package
- gnome-xgl-info and gnome-xgl-switch reside in /usr/bin now.

++++ kdebase3:

- update from 3.5 branch to include bugfixes

++++ perl-Crypt-SSLeay:

- version update to 0.56

++++ wine:

- Upgraded to upstream 0.9.41

++++ glibc:

- Update to head of glibc-2.6 branch.

++++ flash-player:

- update to

++++ Full Changelog

All told this release is kinda broken, but it is an alpha. You have to break a few eggs to make a souffl'e, and hopefully it won't fall next release. This is the first release for which Coolo took responsibility, but he came along late in the game. Let's hang this one on Andreas. (jk) Actually, Coolo is said to have stated that this is the first alpha to feel like an alpha. Well, I don't know about that.

Network problems lead to rash judgement?

I think most of your criticisms, whilst valid, derive only from a failure to properly install and configure drivers for your network card (during the install process). Whilst this doesn't help yourself, I don't think this should lead us to write off this distro as 'broken'.

re: Network problems lead to rash judgement?

The network connection was barely mentioned alongside the other half dozen or so broken or malfunctioning systems. But it's an alpha, it's supposed to be broken. Big Grin

Give her (and us) a break

winchuff wrote:
I think most of your criticisms, whilst valid, derive only from a failure to properly install and configure drivers for your network card (during the install process).

In an alpha release, you'd expect for there to be some show-stopping bugs. "Network setup is broken" and "Adding default repositories crashes installation" are both enough to tell you that this alpha release.

winchuff wrote:
I don't think this should lead us to write off this distro as 'broken'.

Obviously, openSUSE as a distro isn't broken. Nobody said that. This alpha release, however, is. That's why it' alpha release.

re: openSUSE 10.3 Alpha 6 Report

I've tried it too, i thought i might as well give the new one cd installation a try while i'm at it... (big mistake)

i'm a gnome lover, so i chose the gnome 2.19 CD despite the W.I.P warning that coolo gave us, i just have to learn the hard way, if i wasn't like that, life would be too easy for me to handle. what i found was that THE WHOLE FREAKIN SYSTEM IS BROKEN, you can't add repos with the new zypper (if you used yast it will hang, and if you used zypper CL it will JUST not work) and, of course, no sound, no control center or gnome-main-menu (SUSE menu) for gnome, half of the applets are not working, gdm is broken, blah, blah, blah...

the only thing i did get working was 'smart' - after manually downloading and installing it from the factory repo, i thought maybe i could fix the system by updating faulty packages and installing the missing dependencies, but no, that would have been too easy (and we don't want that)

so i gave up..

i know it's an alpha and all, but as far as i know it's supposed to be the last one, i mean the former alphas were far more stable than this, we're supposed to be heading forward, not falling down on our asses, or am i making a big fuss about nothing? i don't know, i just can't let myself be more assed about it, i just installed the new compiz-fusion along with the new screenlets-0.8, and i just wanna say "MACs, watch out!" Tongue

re: SUSE 10.3 ALPHA 6

You'd a thunk that by now - almost everyone would understand WHAT ALPHA MEANS?

Apparently not.

Comment viewing options

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

More in Tux Machines

Linux 4.8.4

I'm announcing the release of the 4.8.4 kernel. And yeah, sorry about the quicker releases, I'll be away tomorrow and as they seem to have passed all of the normal testing, I figured it would be better to get them out earlier instead of later. And I like releasing stuff on this date every year... All users of the 4.8 kernel series must upgrade. The updated 4.8.y git tree can be found at: git:// linux-4.8.y and can be browsed at the normal git web browser: Read more Also: Linux 4.7.10 Linux 4.4.27

New Releases: Budgie, Solus, SalentOS, and Slackel

  • Open-Source Budgie Desktop Sees New Release
    The pet parakeet of the Linux world, Budgie has a new release available for download. in this post we lookout what's new and tell you how you can get it.
  • Solus Linux Making Performance Gains With Its BLAS Configuration
    - Those making use of the promising Solus Linux distribution will soon find their BLAS-based workloads are faster. Solus developer Peter O'Connor tweeted this week that he's found some issues with the BLAS linking on the distribution and he's made fixes for Solus. He also mentioned that he uncovered these BLAS issues by using our Phoronix Test Suite benchmarking software.
  • SalentOS “Luppìu” 1.0 released!
    With great pleasure the team announces the release of SalentOS “Luppìu” 1.0.
  • Slackel "Live kde" 4.14.21
    This release is available in both 32-bit and 64-bit architectures, while the 64-bit iso supports booting on UEFI systems. The 64-bit iso images support booting on UEFI systems. The 32-bit iso images support both i686 PAE SMP and i486, non-PAE capable systems. Iso images are isohybrid.

Security News

  • Free tool protects PCs from master boot record attacks [Ed: UEFI has repeatedly been found to be both a detriment to security and enabler of Microsoft lock-in]
    Cisco's Talos team has developed an open-source tool that can protect the master boot record of Windows computers from modification by ransomware and other malicious attacks. The tool, called MBRFilter, functions as a signed system driver and puts the disk's sector 0 into a read-only state. It is available for both 32-bit and 64-bit Windows versions and its source code has been published on GitHub. The master boot record (MBR) consists of executable code that's stored in the first sector (sector 0) of a hard disk drive and launches the operating system's boot loader. The MBR also contains information about the disk's partitions and their file systems. Since the MBR code is executed before the OS itself, it can be abused by malware programs to increase their persistence and gain a head start before antivirus programs. Malware programs that infect the MBR to hide from antivirus programs have historically been known as bootkits -- boot-level rootkits. Microsoft attempted to solve the bootkit problem by implementing cryptographic verification of the bootloader in Windows 8 and later. This feature is known as Secure Boot and is based on the Unified Extensible Firmware Interface (UEFI) -- the modern BIOS.
  • DDOS Attack On Internet Infrastructure
    I hope somebody's paying attention. There's been another big DDOS attack, this time against the infrastructure of the Internet. It began at 7:10 a.m. EDT today against Dyn, a major DNS host, and was brought under control at 9:36 a.m. According to Gizmodo, which was the first to report the story, at least 40 sites were made unreachable to users on the US East Coast. Many of the sites affected are among the most trafficed on the web, and included CNN, Twitter, PayPal, Pinterest and Reddit to name a few. The developer community was also touched, as GitHub was also made unreachable. This event comes on the heels of a record breaking 620 Gbps DDOS attack about a month ago that brought down security expert Brian Krebs' website, KrebsonSecurity. In that attack, Krebs determined the attack had been launched by botnets that primarily utilized compromised IoT devices, and was seen by some as ushering in a new era of Internet security woes.
  • This Is Why Half the Internet Shut Down Today [Update: It’s Getting Worse]
    Twitter, Spotify and Reddit, and a huge swath of other websites were down or screwed up this morning. This was happening as hackers unleashed a large distributed denial of service (DDoS) attack on the servers of Dyn, a major DNS host. It’s probably safe to assume that the two situations are related.
  • Major DNS provider Dyn hit with DDoS attack
    Attacks against DNS provider Dyn continued into Friday afternoon. Shortly before noon, the company said it began "monitoring and mitigating a DDoS attack" against its Dyn Managed DNS infrastructure. The attack may also have impacted Managed DNS advanced service "with possible delays in monitoring."
  • What We Know About Friday’s Massive East Coast Internet Outage
    Friday morning is prime time for some casual news reading, tweeting, and general Internet browsing, but you may have had some trouble accessing your usual sites and services this morning and throughout the day, from Spotify and Reddit to the New York Times and even good ol’ For that, you can thank a distributed denial of service attack (DDoS) that took down a big chunk of the Internet for most of the Eastern seaboard. This morning’s attack started around 7 am ET and was aimed at Dyn, an Internet infrastructure company headquartered in New Hampshire. That first bout was resolved after about two hours; a second attack began just before noon. Dyn reported a third wave of attacks a little after 4 pm ET. In all cases, traffic to Dyn’s Internet directory servers throughout the US—primarily on the East Coast but later on the opposite end of the country as well—was stopped by a flood of malicious requests from tens of millions of IP addresses disrupting the system. Late in the day, Dyn described the events as a “very sophisticated and complex attack.” Still ongoing, the situation is a definite reminder of the fragility of the web, and the power of the forces that aim to disrupt it.
  • Either IoT will be secure or the internet will be crippled forever
    First things first a disclaimer. I neither like nor trust the National Security Agency (NSA). I believe them to be mainly engaged in economic spying for the corporate American empire. Glenn Greenwald has clearly proven that in his book No Place to Hide. At the NSA, profit and power come first and I have no fucking clue as to how high they prioritize national security. Having said that, the NSA should hack the Internet of (insecure) Things (IoT) to death. I know Homeland Security and the FBI are investigating where the DDoS of doomsday proportions is coming from and the commentariat is already screaming RUSSIA! But it is really no secret what is enabling this clusterfuck. It’s the Mirai botnet. If you buy a “smart camera” from the Chinese company Hangzhou XiongMai Technologies and do not change the default password, it will be part of a botnet five minutes after you connect it to the internet. We were promised a future where we would have flying cars but we’re living in a future where camera’s, light-bulbs, doorbells and fridges can get you in serious trouble because your home appliances are breaking the law.
  • IoT at the Network Edge
    Fog computing, also known as fog networking, is a decentralized computing infrastructure. Computing resources and application services are distributed in logical, efficient places at any points along the connection from the data source (endpoint) to the cloud. The concept is to process data locally and then use the network for communicating with other resources for further processing and analysis. Data could be sent to a data center or a cloud service. A worthwhile reference published by Cisco is the white paper, "Fog Computing and the Internet of Things: Extend the Cloud to Where the Things Are."
  • Canonical now offers live kernel patching for Ubuntu 16.04 LTS users
    Canonical has announced its ‘Livepatch Service’ which any user can enable on their current installations to eliminate the need for rebooting their machine after installing an update for the Linux kernel. With the release of Linux 4.0, users have been able to update their kernel packages without rebooting, however, Ubuntu will be the first distribution to offer this feature for free.
  • ​The Dirty Cow Linux bug: A silly name for a serious problem
    Dirty Cow is a silly name, but it's a serious Linux kernel problem. According to the Red Hat bug report, "a race condition was found in the way the Linux kernel's memory subsystem handled the copy-on-write (COW) breakage of private read-only memory mappings. An unprivileged local user could use this flaw to gain write access to otherwise read-only memory mappings and thus increase their privileges on the system."
  • Ancient Privilege Escalation Bug Haunts Linux
  • October 21, 2016 Is Dirty COW a serious concern for Linux?
  • There is a Dirty Cow in Linux
  • Red Hat Discovers Dirty COW Archaic Linux Kernel Flaw Exploited In The Wild
  • Linux kernel bug being exploited in the wild
  • Update Linux now: Critical privilege escalation security flaw gives hackers full root access
  • Linux kernel bug: DirtyCOW “easyroot” hole and what you need to know
  • 'Most serious' Linux privilege-escalation bug ever discovered
  • New 'Dirty Cow' vulnerability threatens Linux systems
  • Serious Dirty Cow Linux Vulnerability Under Attack
  • Easy-to-exploit rooting flaw puts Linux PCs at risk
  • Linux just patched a vulnerability it's had for 9 years
  • Dirty COW Linux vulnerability has existed for nine years
  • 'Dirty Cow' Linux Vulnerability Found
  • 'Dirty Cow' Linux Vulnerability Found After Nine Years
  • FakeFile Trojan Opens Backdoors on Linux Computers, Except openSUSE
    Malware authors are taking aim at Linux computers, more precisely desktops and not servers, with a new trojan named FakeFile, currently distributed in live attacks. Russian antivirus vendor Dr.Web discovered this new trojan in October. The company's malware analysts say the trojan is spread in the form of an archived PDF, Microsoft Office, or OpenOffice file.

today's howtos