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

today's howtos

Leftovers: OSS

  • Report: If DOD Doesn't Embrace Open Source, It'll 'Be Left Behind'
    Unless the Defense Department and its military components levy increased importance on software development, they risk losing military technical superiority, according to a new report from the Center for a New American Security. In the report, the Washington, D.C.-based bipartisan think tank argues the Pentagon, which for years has relied heavily on proprietary software systems, “must actively embrace open source software” and buck the status quo. Currently, DOD uses open source software “infrequently and on an ad hoc basis,” unlike tech companies like Google, Amazon and Facebook that wouldn’t exist without open source software.
  • The Honey Trap of Copy/Pasting Open Source Code
    I couldn’t agree more with Bill Sourour’s article ‘Copy.Paste.Code?’ which says that copying and pasting code snippets from sources like Google and StackOverflow is fine as long as you understand how they work. However, the same logic can’t be applied to open source code. When I started open source coding at the tender age of fourteen, I was none the wiser to the pitfalls of copy/pasting open source code. I took it for granted that if a particular snippet performed my desired function, I could just insert it into my code, revelling in the fact that I'd just gotten one step closer to getting my software up and running. Yet, since then, through much trial and error, I’ve learned a thing or two about how to use open source code effectively.
  • Affordable, Open Source, 3D Printable CNC Machine is Now on Kickstarter
    The appeals of Kickstarter campaigns are many. There are the rewards for backers, frequently taking the form of either deep discounts on the final product or unusual items that can’t be found anywhere else. Pledging to support any crowdfunding campaign is a gamble, but it’s an exciting gamble; just browsing Kickstarter is pretty exciting, in fact, especially in the technological categories. Inventive individuals and startups offer new twists on machines like 3D printers and CNC machines – often for much less cost than others on the market.
  • Open Standards and Open Source
    Much has changed in the telecommunications industry in the years since Standards Development Organization (SDOs) such as 3GPP, ITU and OMA were formed. In the early days of telecom and the Internet, as fundamental technology was being invented, it was imperative for the growth of the new markets that standards were established prior to large-scale deployment of technology and related services. The process for development of these standards followed a traditional "waterfall" approach, which helped to harmonize (sometimes competing) pre-standard technical solutions to market needs.

Leftovers: BSD

  • The Voicemail Scammers Never Got Past Our OpenBSD Greylisting
    We usually don't see much of the scammy spam and malware. But that one time we went looking for them, we found a campaign where our OpenBSD greylisting setup was 100% effective in stopping the miscreants' messages. During August 23rd to August 24th 2016, a spam campaign was executed with what appears to have been a ransomware payload. I had not noticed anything particularly unusual about the bsdly.net and friends setup that morning, but then Xavier Mertens' post at isc.sans.edu Voice Message Notifications Deliver Ransomware caught my attention in the tweetstream, and I decided to have a look.
  • Why FreeBSD Doesn't Aim For OpenMP Support Out-Of-The-Box

Security Leftovers

  • FBI detects breaches against two state voter systems
    The Federal Bureau of Investigation has found breaches in Illinois and Arizona's voter registration databases and is urging states to increase computer security ahead of the Nov. 8 presidential election, according to a U.S. official familiar with the probe. The official, speaking on condition of anonymity, said on Monday that investigators were also seeking evidence of whether other states may have been targeted. The FBI warning in an Aug. 18 flash alert from the agency's Cyber Division did not identify the intruders or the two states targeted. Reuters obtained a copy of the document after Yahoo News first reported the story Monday.
  • Russians Hacked Two U.S. Voter Databases, Say Officials [Ed: blaming without evidence again]
    Two other officials said that U.S. intelligence agencies have not yet concluded that the Russian government is trying to do that, but they are worried about it.
  • FBI Says Foreign Hackers Got Into Election Computers
    We've written probably hundreds of stories on just what a dumb idea electronic voting systems are, highlighting how poorly implemented they are, and how easily hacked. And, yet, despite lots of security experts sounding the alarm over and over again, you still get election officials ridiculously declaring that their own systems are somehow hack proof. And now, along comes the FBI to alert people that it's discovered at least two state election computer systems have been hacked already, and both by foreign entities.
  • Researchers Reveal SDN Security Vulnerability, Propose Solution
    Three Italian researchers have published a paper highlighting a security vulnerability in software-defined networking (SDN) that isn't intrinsic to legacy networks. It's not a showstopper, though, and they propose a solution to protect against it. "It" is a new attack they call Know Your Enemy (KYE), through which the bad guys could potentially collect information about a network, such as security tool configuration data that could, for example, reveal attack detection thresholds for network security scanning tools. Or the collected information could be more general in nature, such as quality-of-service or network virtualization policies.
  • NV Gains Momentum for a Secure DMZ
    When it comes to making the shift to network virtualization (NV) and software-defined networking (SDN), one of the approaches gaining momentum is using virtualization technology to build a secure demilitarized zone (DMZ) in the data center. Historically, there have been two major drawbacks to deploying firewalls as a secure mechanism inside a data center. The first is the impact a physical hardware appliance has on application performance once another network hop gets introduced. The second is the complexity associated with managing the firewall rules. NV technologies make it possible to employ virtual firewalls that can be attached to specific applications and segregate them based on risk. This is the concept of building a secure DMZ in the data center. The end result is that the virtual firewall is not only capable of examining every packet associated with a specific application, but keeping track of what specific firewall rules are associated with a particular application becomes much simpler.