Language Selection

English French German Italian Portuguese Spanish

SUSE 10.1 Beta 5 Report

Filed under
Reviews
SUSE
-s

Why? That one thought kept echoing through my thoughts as I installed and ran SUSE 10.1 Beta 5. Around the net several articles entitled something to the effect of "SUSE releases two betas within 4 days" as if it was an accomplishment of 10.0 proportions! Some progress was made, but it reminded me of the old saying "2 steps forward and 3 steps back."

If you look at the "Most Annoying Bugs" report and compare it to Beta4's, you'll find that not only was very little fixed, but they even introduced more bugs. As you can see, I've highlighted the left overs in blue and the new breakage in red.

  • 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.
  • Due to the integration of the new package manager which is not complete, note the following:
    • Some statistics do not work, e.g. you see "Size of packages to install: 0" - or "Number of packages to install: 0", or "Software: Default system (0)".
    • The graphical package manager frontend has only a limited list of "views", currently you get a list of all the packages and can only search in them.
    • After installation, if you go into the YaST packager, all installed packages are listed twice.
    • Adding a new installation source does not work.
    • Language dependend packages are not handled correctly. This results in the installation of one package-$lang package but not necessarily the one for the languages asked for.
    • An upgrade from a previous installation might fail, even one from 10.1 Beta3 Bug 153142
  • During an update from a previous release, packages that are not available anymore get deleted - once at the start of CD1 and then again at the end of CD1. Pressing Ignore a couple of times allows to continue. Bug 153135
  • 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 second part of the installation is done in text mode Bug 153066, but afterwards the graphical login manager is started.
  • X11 configuration during installation is totally broken in Beta5 due to a bug in package manager. Instead of the native X11 driver fbdev or even vesa driver will be configured. In order to create a valid X11 configuration stop xdm ("rcxdm stop") and use SaX2 for configuration ("sax2 -r"). ATI users should update the radeon driver first before executing SaX2. Otherwise the result will likely be a blank screen. Driver RPMs for i386/x86_64 are attached to Bug 153367 and are also on the ftp server in the fixed rpm directory.

Now I love betas, you know I do. I've been installing and testing linux betas for several years now, so I expect breakage. Sometimes it's so minor that some betas are more stable and usable than other's full releases. Some are comical or entertaining. But most of SUSE's latest betas should have delayed release until they are fixed, most notably the partitioner. Not that I got bit by that one myself, but worse case scenario, it could render someone's system inoperable or even result in data loss. However, giving credit where due, at least they advise the user and surely no one in their right mind would try to upgrade to or install this beta as their main system.

I'm not sure why they'd even want to release when their crowning jewel, YAST, is so broken. This seems to me like a bad judgement call. In addition, having the xconfig broken during install would be a definite brickwall to some. Vesa implementation would not be the end of the world, in fact with my video card it's the best choice with a lot of systems, but my install didn't even address X configuration. It was skipped altogether here. As such my first boot halted and hung at the point at which it would normally try to start the graphical login manager. It should have failed and left me at the command prompt. I ctrl+alt+del'd and restarted using init 3 to get to the commandline, at which point I installed the "fixed rpm" and ran xorgconfig. Next I ran startx and got in.

        

Another "most annoying bugs" of this beta's installer was the second stage in text form. They classify it text, I use the term "ascii-graphical." This isn't so much an annoyance as entertainment to me. I've always kinda marvelled at SUSE's text installer. It is almost a carbon copy of their beautiful graphical installer - only in text. I don't imagine there are too many people who appreciate that as much as I, but I have to wonder how much work was originally put into that considering how it compares to Slackware's and others. So, having to finish in text mode wasn't an annoyance here, in fact I enjoyed it, but it's an indication of how broken things really are.

One of the "most annoying bugs" for me is that any installation method other than straight "5 burned cds" is totally broken. I hate to contribute to the pollution problem and empty my own pocket in the process as well, so I first attempted a harddrive install which would error out before probing of the mouse. Next I tried the dvd remaster, but it would bomb out just when it was supposed to begin the package installation. Harddrive installs have been officially broken for the last two betas, but truth be known, it's been broken this whole beta cycle. I could coax a hard drive install from betas 1 - 3, but I had to walk all the way around the barn to do it. In actuality, all manual installation methods are broken. In fact, their "one path to installtion" had several packages fail to install properly. I hope they get that one fixed pronto!

I noted above that most of the "Most Annoying Bugs" are still present in this beta, however if you examine the changelog you'll find the developers were not taking the week off. They have been busy fixing a lot of bugs and working hard hard hard on yast2. In fact, yast seems to dominate the changelog this time.

Although the package manager is still broken on several levels, it is coming along. Now we can see that we have the choice of our "Selections" and the catagories show up, albeit twice. However at this point the individual packages did not. The Software Catalog allowed me to add a repository, retained it this time, and then the indivdual packages appeared. However it was not usable as I still couldn't install any additional packages. This rendered setting up extra hardware inoperative if it required additional packages.

        

        

Two of the required packages for xgl was included this time, but two still need to be downloaded from a "Factory" repository. rpm at the commandline still works, so it's possible to install these packages. The xgl and compiz packages are in the suse/i586 directory of your cd5. libsvg can be downloaded here and libsvg-cairo can be had from here. I followed the directions from SUSE, but I wasn't successful in implementing this feature at this time. I may keep pluggin' away at it, but if anyone else has had better luck, feel free to submit your screenshots.

If you're interested in the lastest version number of your favorite application, you can consult the complete package list or my rpmlist as tested. I usually install everything considered desktop and developer related. I usually skip the advanced servers, xen, and mobile computing.

All in all, I'm of the opinion that betas 4 and 5 should have been delayed until less things are broken. I have a friend who has called SUSE "the new Mandrake" more than once. And I agree. We mean that in the sense of, ...do you remember when Mandrake was innovative, bold, even groundbreaking? They were the first to implement new technology and were always on the cutting edge. Their hardware support was always the very best. SUSE is "the new Mandrake" but we wish they didn't stick to their release roadmap so stringently. Sometimes it is best to delay.

Not too many new screenshots were taken this time, as the interface remained unchanged. You might want to peruse the beta 3 shots for a more complete overview or even the beta 4 if you're interested in the progress of the Software Management.

Previous coverage:


Well done

Congrats for the speed! (You've got much more time than me! Smile )

The most annoying remaining issue should be:
"Adding a new installation source does not work."

The good thing is that Factory is supposed to work.
The bad thing is that it doesn't seem trivial to get new things to work (xgl).

Re: Well done

Béranger wrote:

Congrats for the speed! (You've got much more time than me! Smile )

It'd been out sooner if I hadn't spent my Sunday replacing my son's motherboard and trying to get his windows installs to adjust. What a mess windows is!

Quote:

The most annoying remaining issue should be:
"Adding a new installation source does not work."

Yep, that's bad. But they're making progress. [/quote]

Quote:

The good thing is that Factory is supposed to work.
The bad thing is that it doesn't seem trivial to get new things to work (xgl).

Yeah, the steps seemed quite straightforward and easy to follow, it just didn't work out this time for me.

Comment viewing options

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

More in Tux Machines

OpenSUSE fonts – The sleeping beauty guide

Pandora’s box of fonts is one of the many ailments of the distro world. As long as we do not have standards, and some rather strict ones at that, we will continue to suffer from bad fonts, bad contrast, bad ergonomics, and in general, settings that are not designed for sustained, prolonged use. It’s a shame, because humans actually use computers to interface with information, to READ text and interpret knowledge using the power of language. It’s the most critical element of the whole thing. OpenSUSE under-delivers on two fonts – anti-aliasing and hinting options that are less than ideal, and then it lacks the necessary font libraries to make a relevant, modern and pleasing desktop for general use. All of this can be easily solved if there’s more attention, love and passion for the end product. After all, don’t you want people to be spending a lot of time interacting, using and enjoying the distro? Hopefully, one day, all this will be ancient history. We will be able to choose any which system and never worry or wonder how our experience is going to be impacted by the choice of drivers, monitors, software frameworks, or even where we live. For the time being, if you intend on using openSUSE, this little guide should help you achieve a better, smoother, higher-quality rendering of fonts on the screen, allowing you to enjoy the truly neat Plasma desktop to the fullest. Oh, in the openSUSE review, I promised we would handle this, and handle it we did! Take care. Read more

Today in Techrights

Direct Rendering Manager and VR HMDs Under Linux

  • Intel Prepping Support For Huge GTT Pages
    Intel OTC developers are working on support for huge GTT pages for their Direct Rendering Manager driver.
  • Keith Packard's Work On Better Supporting VR HMDs Under Linux With X.Org/DRM
    Earlier this year Keith Packard started a contract gig for Valve working to improve Linux's support for virtual reality head-mounted displays (VR HMDs). In particular, working on Direct Rendering Manager (DRM) and X.Org changes needed so VR HMDs will work well under Linux with the non-NVIDIA drivers. A big part of this work is the concept of DRM leases, a new Vulkan extension, and other changes to the stack.

Software: Security Tools, cmus, Atom-IDE, Skimmer Scanner

  • Security Tools to Check for Viruses and Malware on Linux
    First and foremost, no operating system is 100 percent immune to attack. Whether a machine is online or offline, it can fall victim to malicious code. Although Linux is less prone to such attacks than, say, Windows, there is no absolute when it comes to security. I have witnessed, first hand, Linux servers hit by rootkits that were so nasty, the only solution was to reinstall and hope the data backup was current. I’ve been a victim of a (very brief) hacker getting onto my desktop, because I accidentally left desktop sharing running (that was certainly an eye opener). The lesson? Even Linux can be vulnerable. So why does Linux need tools to prevent viruses, malware, and rootkits? It should be obvious why every server needs protection from rootkits — because once you are hit with a rootkit, all bets are off as to whether you can recover without reinstalling the platform. It’s antivirus and anti-malware where admins start getting a bit confused. Let me put it simply — if your server (or desktop for that matter) makes use of Samba or sshfs (or any other sharing means), those files will be opened by users running operating systems that are vulnerable. Do you really want to take the chance that your Samba share directory could be dishing out files that contain malicious code? If that should happen, your job becomes exponentially more difficult. Similarly, if that Linux machine performs as a mail server, you would be remiss to not include AV scanning (lest your users be forwarding malicious mail).
  • cmus – A Small, Fast And Powerful Console Music Player For Linux
    You may ask a question yourself when you see this article. Is it possible to listen music in Linux terminal? Yes because nothing is impossible in Linux. We have covered many popular GUI-based media players in our previous articles but we didn’t cover any CLI based media players as of now, so today we are going to cover about cmus, is one of the famous console-based media players among others (For CLI, very few applications is available in Linux).
  • You Can Now Transform the Atom Hackable Text Editor into an IDE with Atom-IDE
    GitHub and Facebook recently launched a set of tools that promise to allow you to transform your Atom hackable text editor into a veritable IDE (Integrated Development Environment). They call the project Atom-IDE. With the release of Atom 1.21 Beta last week, GitHub introduced Language Server Protocol support to integrate its brand-new Atom-IDE project, which comes with built-in support for five popular language servers, including JavaScript, TypeScript, PHP, Java, C#, and Flow. But many others will come with future Atom updates.
  • This open-source Android app is designed to detect nearby credit card skimmers
    Protecting our data is a constant battle, especially as technology continues to advance. A recent trend that has popped up is the installation of credit card skimmers, especially at locations such as gas pumps. With a simple piece of hardware and 30 seconds to install it, a hacker can easily steal credit card numbers from a gas pump without anyone knowing. Now, an open-source app for Android is attempting to help users avoid these skimmers.