Language Selection

English French German Italian Portuguese Spanish

Suse 10.1 alpha3 Report

Filed under
Reviews
SUSE
-s

SUSE 10.1 alpha 3 was released this week and I thought I'd see if there was much new and exciting. As we look at the guis and applications, it appears as if most of the work must have taken place under the hood. When we examine the changelog, we find that's the case.

The installer was pretty much the same as encountered in SUSE 10.0 with the possible addition of MONO in the package selection. I perhaps suffered a few hardware detection/setup glitches, but they could almost be user error or related.

The first little glitch was due to my having added an extra tulip ethernet card to my machine a few weeks back for a specific reason, but I still use the on-board via-rhine fulltime. YAST wanted to use the add-in as primary. I preceded to set up the on-board as default, and then ended up deleting the extraneous card. It shouldn't have been an issue, and I'm not sure it was. However, during boot dhcpcd runs, but my eth0 wasn't functional upon login. I had to kill dhcpcd and re-run it. And then, it kept losing the connection. Sometimes it'd come back after trying to connect to the same site more than a coupla times, in gnome I used the net connection panel applet to reconnect, and I restarted dhcpcd a time or two. So, I think this issue wouldn't have cropped up if that other card had not been installed.

Then another ooops was with the video setup. I failed (read: forgot) to adjust for my preferences during install and booted into a 800x600 resolution desktop. This won't do and I fired up yast to adjust. I changed the settings to vesa 1280x1024x60 16-bit and saved. When I restarted (or attempted to) I got a "no screens found" error. Looking at the xorg.conf file, the syncs were badly underrated, but that's almost normal as my latest monitor is never detected correctly. "nv" was still showing as the driver but the showstopper was the 4 bit depth. Where did that come from? Anyway, manaully editing that file for my horizonal and vertical refresh rates and that bit depth got me back into X pretty fast. Now, one of the thing most people might like to do is adjust their video settings. This should work, but it didn't in my case. Good news, however, is I stuck with the "nv" driver as I noticed 10.1 alpha3 was using 6.9/7.0 rc2 of Xorg and that part worked out pretty good for my nvidia 6800 graphics chip.

KDE is at 3.5 rc1 in SUSE 10.1a3 and it was looking good. I covered most of it in my first look at the 10.1 series and my source install of 3.5r1 on my gentoo system. So, it's been pretty much covered. It was quite stable and performed admirably.

        

Gnome on the other hand was a buggy excruciating experience. The file manager worked, but that's about it. Just about everything else I tried to open or launch crashed. I'm not sure why suse has such a hard time getting gnome to play nice. It was quite buggy throughout the 10.0 developmental cycle, but did work well in the final. I suppose this is the recipe to expect this time as well.

        

We're still looking at that SUSE Lizard wallpaper. ho-hum, come on guys, give us a new wallpaper! Big Grin Actually, they did make the SUSE logo a bit more opaque.

About the only thing new I spied in YAST2 was the UML. "User Mode Linux installation allows you to start independent Linux virtual machines in the host system." As it only supported network sources at this time, testing didn't get too far here. But it looks promising.

    

Some package highlights include:

  • kernel-default-2.6.14.2-2

  • xorg-x11-6.9rc2-3
  • kdebase3-3.5.0-2
  • gnome-desktop-2.12.1-3
  • gcc-4.1.0_20051110-3
  • mozilla-1.7.12-6
  • MozillaFirefox-1.4.99-3
  • gaim-1.5.0-10
  • OpenOffice_org-1.99.3-2
  • qt3-3.3.5-17
  • gtk2-2.8.6-7
  • glibc-2.3.5-46
  • perl-5.8.7-6
  • python-2.4.2-3
  • mysql-shared-4.1.13-5
  • mono-core-1.1.10-3
  • cdrecord-2.01-9
  • gimp-2.2.9-7
  • evolution-2.4.1-7
  • beagle-0.1.2-5
  • alsa-1.0.10-4
  • Full RPMlist

        

Some recent changelog highlights are:

  • autofs: Bugfix: bad example ldif.

  • beagle: Fixed lib64 patch & Remove upstreamed patch.
  • gnome-session: Updated autostart patch to support per user's autostart directory and to remove duplicated entries.
  • icewm: updated to 1.2.23.
  • nautilus: Add patch to hide the zoom and "view as" controls from the location bar.
  • sax2: added domain information to BusID setup.
  • xorg-x11: updated to X.Org 6.9 RC2 & mouse driver fix from CVS.
  • jack: Fix use of atomic builtins.
  • kdelibs3: link with -O1
  • digikamimageplugins: fix filelist.
  • kernel: update to 2.6.14.2, prism54 : Fix frame length, ipvs: fix connection leak if expire_nodest_conn=1, Fix ptrace self-attach rule, & fix signal->live leak in copy_process()
  • mkinitrd: Fix mount --move to really have /dev on tmpfs.
  • powersave: added runtime powermanagement.
  • wine: Upgraded to 0.9.1 release & Lots of bug fixes.
  • gcc: Update to current SVN head & Check if we accidentially end up with make -j0 and fix it.
  • Full Changelog since about alpha1

If you look at the changelog and/or compare the rpmlist to the last one you can clearly see that the developers having been toiling away, probably in some dark dungeon somewhere with only food and water to sustain them while some ogre cracks a leather whip. Most changes are under the hood as always, so it's not so easy to show in screenshots.

This is an alpha release and in the thick of major version upgrades and new feature introductions. We understand and even expect issues. Next month brings alpha 4. In January we can expect the first beta and things will really start to get exciting. The release schedule will get bumped up to highway speeds and we can expect the first release candidate on or about Feb. 16, 2006. We hope to bring you updated reports as developments happen.

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more