Language Selection

English French German Italian Portuguese Spanish

SUSE 10.1 Beta 4 Report

Filed under
Linux
Reviews
-s

Beta 4 finally made onto servers yesterday, and onto my machine today. It took some doing, I admit, but I have it installed. I hate to be the bearer of bad tidings, and rather than make you wait til the end, I'll state up-front that there is no xgl included. Although rumor had it that was one of the reasons for the delay, the rpm packages needed are not included on the 5 cd set. They are still available from the factory tree repository, but don't expect any fancy screenshots for this "as installed" report.

In fact, don't expect a whole lot of screenshots at all. Very little has changed since beta 3 in the appearance of SUSE 10.1. Beta 3 sported lots of new images and backgrounds, but beta 4 is just sporting breakage. Big Grin (j/k/a)

Another reason for the delay in the release of Beta 4 was a new package management system. I'm not sure if the new display during install is a result, but this is where one begins to see some changes from last time. Now the package selection screen is somewhat simplified with the individual packages being hidden by default. One can press the "Details" button and get it back. Another change for at least this release was a warning that developers are aware of breakage and please only file bug reports on the resolver.

On two occasions during the install, I walked away from the computer to come back and find myself at a login screen. The first time occurred during cd 2! Needless to say that wasn't a pretty sight. The second time was during cd 4 and it appeared most of the system was pretty much installed at that point. In both cases, a restart with cd 1 in the drawer allowed me to continue the install. shewww!

One other little goodie during install is now the hostname for your machine is a step all its own right after package installation. Now rather than trying to remember to root around in the networking options to change it, it's offered up right there for you to change. That's rather nice as I've forgotten a time or two to dig around and change that setting myself.

Another glitch that delayed my install was the "hanging" of searching for 'available kernel modules.' During the hardware summary screen where one can adjust configurations for their hardware, I foolishly decided to input the parameters for my tvcard, as I always do with SUSE and Mdv (as they are the only two with options for it). This time after I chose my card and tuner and clicked "expert settings," it began searching for all the kernel modules pertaining to this task, as it always does. Only this time, it hung for 15 or 20 minutes before I finally gave up and hit reset. Bear in mind this task is usually a 30 second operation. Now naturally this caused a bit of hardware trouble such as having to configure X and sound after first boot.

After install the package management breakage is very apparent from the yast software management suite. Any new media added is not kept and packages are not available to install. The only options in the install software portion is "installed." I suppose one could remove packages if they so desired.

        

I was aware of issues with beta 4, and in fact, I encountered most of them. Here's an excerpt of a post from one of the developers:

"Beta4 is really for the adventurous experts and not for anybody
without a good Linux experience:

* 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 non working pieces:

o Only a fresh installation is supported. Update from a previous
installation is not working!

o ncurses installation is not supported right now

o 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)".

o 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.

o Only adding of selections works. If you want to remove a
selection, remove all packages in that selection and run the
resolver manually with the "Check" button.

o 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.

o It is not possible to abort installation while installing
packages.

o Network Installations: smb/cifs does not work, http, nfs and ftp
should work.

o There are cases where during a ftp installation from the FACTORY
tree packages for the wrong architecture get installed

* The partitioner is broken in some cases which might result in:
o mixed up filesystem types - for example one chooses ext2 and the
partition is getting formatted with reiserfs
o creates double or totally obscure entries within the fstab of the
system
o makes improper proposals for a standard partitioning

* There are no Release Notes shown - and the download of them fails.

Summing up: The installer is in a rather bad shape, only INSTALLATION
is supported - and the partitioner has some regressions as well. The
rest of the system should be stable. "

Here's are some highlights from the changelog this time:

++++ NetworkManager:

- Fix VPN GUI dialog when successively editing entries of two
or more different VPN types (Novell bug #150854)
- Improve debugging output

++++ audacity:

- Build with portaudio19

++++ gnome-applets:

- Fixed battery -1 minute notice

++++ gnome-session:

- Added MOTD on login, as requested by customer.

++++ kernel-default:

- Disable CONFIG_EFI on x86 since it's broken
- patches.drivers/sata-acpi-check-sata: Fix SATA/PATA checks.
- Update to 2.6.16-rc3-git3:
- usb fixes
- i2c fixes
- cpufreq fixes
- network fixes
- bluetooth fixes
- reiserfs fix
- drm oops fix

++++ metacity:

- Fix dual-head bug

++++ MozillaFirefox:

- modified lockdown patches (#67281, #67282)
- applied set of security patches (#148876)

++++ MozillaThunderbird:

- applied set of security patches

++++ beagle:

- added upstream patch to quit beagled on unknown parameter

++++ bootsplash-theme-SuSE:

- Fix the SLES bootsplash paths

++++ gaim:

- added gnome-keyring-devel to BuildRequires

++++ Full Changelog.



Some package highlights include:

  • xorg-x11-6.9.0-12.i586.rpm

  • kdebase3-3.5.1-22.i586.rpm
  • gnome-desktop-2.12.2-6.i586.rpm
  • MozillaFirefox-1.5.0.1-9.i586.rpm
  • MozillaThunderbird-1.5-12.i586.rpm
  • MozillaSunbird-0.2.1-4.i586.rpm
  • gaim-1.5.0-29.i586.rpm
  • gcc-4.1.0_20060210-3.i586.rpm
  • kernel-default-2.6.16_rc3_git3-2.i586.rpm
  • Full RPMList

In conclusion, don't bother with this release. There is a lot of breakage and not much new on the surface. I can state without reservation that it'd be best to wait til next beta even for the most adventurous folk who like to test betas. In fact, I'm not sure of the point of this release. The roadmap says that we can expect Beta 5 on the 23 and Beta 6 on March 2. We'll keep ya posted.

Previous coverage:

Bad

If it was me, I think I would have cancelled this release until I got more things worked out. They rushing too hard.

Re: Bad

Texstar wrote:

If it was me, I think I would have cancelled this release until I got more things worked out. They rushing too hard.

Yeah, that's what I was saying, they should have skipped this one, waited, and called beta5 beta4.

It's still a beta

I'll reserve judgement until 10.1 final is released. I personally applaud Novell/Suse's efforts to move things forward... that's why I'm not running something less progressive (I.E. Debian). If 10.1 final is brutal I may then change my opinion but for now I'm optimistic they can pull if off.

re: It's still a beta

Oh yeah, no doubt. They have 2 more betas and what? 2 to 4 release candidates? to get things all polished up. You know when it goes gold, it'll be all slick and shiny! I have no doubts.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

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

More in Tux Machines

NuTyX 10.1-rc1 Available

I'm very please to propose you the first release candidate version of the next version 10.1 stable version of NuTyX As they have been so many security issues, I took the chance to recompile all the collections (1701 packages) for this coming next stable NuTyX version. Read more

Android Leftovers

Events: FOSDEM Samba Talks, USENIX Enigma, LCA (linux.conf.au) and FAST18

  • Authentication and authorization in Samba 4
    Volker Lendecke is one of the first contributors to Samba, having submitted his first patches in 1994. In addition to developing other important file-sharing tools, he's heavily involved in development of the winbind service, which is implemented in winbindd. Although the core Active Directory (AD) domain controller (DC) code was written by his colleague Stefan Metzmacher, winbind is a crucial component of Samba's AD functionality. In his information-packed talk at FOSDEM 2018, Lendecke said he aimed to give a high-level overview of what AD and Samba authentication is, and in particular the communication pathways and trust relationships between the parts of Samba that authenticate a Samba user in an AD environment.
  • Two FOSDEM talks on Samba 4
    Much as some of us would love never to have to deal with Windows, it exists. It wants to authenticate its users and share resources like files and printers over the network. Although many enterprises use Microsoft tools to do this, there is a free alternative, in the form of Samba. While Samba 3 has been happily providing authentication along with file and print sharing to Windows clients for many years, the Microsoft world has been slowly moving toward Active Directory (AD). Meanwhile, Samba 4, which adds a free reimplementation of AD on Linux, has been increasingly ready for deployment. Three short talks at FOSDEM 2018 provided three different views of Samba 4, also known as Samba-AD, and left behind a pretty clear picture that Samba 4 is truly ready for use. I will cover the first two talks in this article, and the third in a later one.
  • A report from the Enigma conference
    The 2018 USENIX Enigma conference was held for the third time in January. Among many interesting talks, three presentations dealing with human security behaviors stood out. This article covers the key messages of these talks, namely the finding that humans are social in their security behaviors: their decision to adopt a good security practice is hardly ever an isolated decision. Security conferences tend to be dominated by security researchers demonstrating their latest exploits. The talks are attack-oriented, they keep a narrow focus, and usually they close with a dark outlook. The security industry has been doing security conferences like this for twenty years and seems to prefer this format. Yet, if you are tired of this style, the annual USENIX Enigma conference is a welcome change of pace. Most of the talks are defense-oriented, they have a horizon going far beyond technology alone, and they are generally focused on successful solutions.
  • DIY biology
    A scientist with a rather unusual name, Meow-Ludo Meow-Meow, gave a talk at linux.conf.au 2018 about the current trends in "do it yourself" (DIY) biology or "biohacking". He is perhaps most famous for being prosecuted for implanting an Opal card RFID chip into his hand; the Opal card is used for public transportation fares in Sydney. He gave more details about his implant as well as describing some other biohacking projects in an engaging presentation. Meow-Meow is a politician with the Australian Science Party, he said by way of introduction; he has run in the last two elections. He founded BioFoundry, which is "Australia's first open-access molecular biology lab"; there are now two such labs in the country. He is also speaks frequently as "an emerging technology evangelist" for biology as well as other topics.
  • Notes from FAST18

    I attended the technical sessions of Usenix's File And Storage Technology conference this week. Below the fold, notes on the papers that caught my attention.

Security: Vista10 and uTorrent Holes Found by Google

  • Google drops new Edge zero-day as Microsoft misses 90-day deadline

    Google originally shared details of the flaw with Microsoft on 17 November 2017, but Microsoft wasn’t able to come up with a patch within Google’s non-negotiable “you have 90 days to do this” period.

  • Google Goes Public with Another Major Windows 10 Bug
    After revealing an Edge browser vulnerability that Microsoft failed to fix, Google is now back with another disclosure, this time aimed at Windows 10 Fall Creators Update (version 1709), but potentially affecting other Windows versions as well. James Forshaw, a security researcher that’s part of Google’s Project Zero program, says the elevation of privilege vulnerability can be exploited because of the way the operating system handles calls to Advanced Local Procedure Call (ALPC). This means a standard user could obtain administrator privileges on a Windows 10 computer, which in the case of an attack, could eventually lead to full control over the impacted system. But as Neowin noted, this is the second bug discovered in the same function, and both of them, labeled as 1427 and 1428, were reported to Microsoft on November 10, 2017. Microsoft said it fixed them with the release of the February 2018 Patch Tuesday updates, yet as it turns out, only issue 1427 was addressed.
  • uTorrent bugs let websites control your computer and steal your downloads

    The vulnerabilities, according to Project Zero, make it possible for any website a user visits to control key functions in both the uTorrent desktop app for Windows and in uTorrent Web, an alternative to desktop BitTorrent apps that uses a web interface and is controlled by a browser. The biggest threat is posed by malicious sites that could exploit the flaw to download malicious code into the Windows startup folder, where it will be automatically run the next time the computer boots up. Any site a user visits can also access downloaded files and browse download histories.

  • BitTorrent Client uTorrent Suffers Security Vulnerability (Updated)

    BitTorrent client uTorrent is suffering from an as yet undisclosed vulnerability. The security flaw was discovered by Google security researcher Tavis Ormandy, who previously said he would reveal a series of "remote code execution flaws" in torrent clients. BitTorrent Inc. has rolled out a 'patch' in the latest Beta release and hopes to fix the stable uTorrent client later this week.