|
|
We are pleased to announce Issue 197 from openSUSE Weekly News.
openSUSE Weekly News
openSUSE Weekly News Team
197 Edition
Legal Notice
This work (compilation) is licenced under Creative Commons attribution-ShareAlike 3.0 Unported License.
The rights [...] We are pleased to announce Issue 197 from openSUSE Weekly News.
Legal Notice
This work (compilation) is licenced under Creative Commons attribution-ShareAlike 3.0 Unported License.
The rights for the compilation itself are copyright by Sascha Manns.
Opt-Out: If you are an Author and don’t want to be included in the openSUSE Weekly News, just send a Mail to: <news@opensuse.org>.
Copyrights of the referenced articles are owned by original authors or copyright owners. If you want to reuse those articles, ask each original copyright owner which
license should be applied. We don’t reprint any Article without a free license, we just introduce it then under the Agreement of the German Copyright Law.
If you are an author and want to set your blog under a free License just visit: http://goo.gl/Tw3td
We are thanking the whole openSUSE Weekly News Team and the open-slx gmbh for spending time and power into the openSUSE Weekly News.
Published:
2011-10-16
We are pleased to announce our 197 issue of the openSUSE Weekly News.
You can also read this issue in other formats here.
Enjoy reading :-)
“
The openSUSE Project announces the 1.0 release of the unique cross-distribution-capable,
fully automated testing framework openQA. openQA is the only
comprehensive testing tool which can run tests on every level of the OS, from core
functionality like the bootloader and booting the kernel up to testing applications like
Firefox and LibreOffice. It shows the results in a convenient web interface and allows testers
to see screenshots and even videos of the issues found.
openQA is used to run nightly tests of the ‘Factory’ development repository for the upcoming
openSUSE 12.1 release. openQA is
available under the GPL version 2 or later. (…)
”
“
Last week, openQA 1.0 was released. We
did an interview with Bernhard Wiedeman, the main developer of openQA.
First of all, whatýs your job regarding the openQA project?
My role in the project was to wish for, envision, design, organize and implement most of
openQA and OS-autoinst (the test-engine powering the openQA service). I made it do what was
needed most and added things others wanted as well. Actually, my job at SUSE (doing cloud
stuff) is completely unrelated to openQA, which is still my hobby project. (…)
”
Build Service Statistics. Statistics can found at Buildservice
“
Network installation could be improved by running package download and package
installation in parallel.
”
“
I wanted to open a fate feature about this when I first heard of plymouth, but
reading
http://fedoramagazine.wordpress.com/2008/10/21/interview-fedora-10s-better-startup/
really makes me think we should go this way.
Ray’s comment starting with “Every flicker and mode change in the boot
process takes away from the whole experience.” is especially interesting. Is it
okay to track the “don’t show grub by default” here?
”
“
An easy way to remove Software! For example: you installed an application with “1-click install” (which will install all the packages that you need), there should be an easy way (also with 1 click) to remove what you have installed with that 1-click operation… in another words: an “1-click Uninstall” to remove installed software (dependencies and packages included).
”
“
Every single bug or feature that anyone has developed for GRUB 0.97 has been
rejected by the upstream project in favor of using GRUB 2. There has been resisitence in
the distribution community to switching boot loaders, but this stalemate isn’t
going to go away. The code itself isn’t well written or well maintained. Adding a
new feature involves jumping through a lot of hoops that may or may not work even if you
manage to work around all the runtime limitations. For example, a fs implementation has
a static buffer it can use for memory management. It’s only 32k. For complex file
systems, or even a simple journaled file system, we run into problems (like the reiserfs
taking forever to load bug) because we don’t have enough memory to do block mapping
for the journal so it needs to scan it for every metadata read. (Yeah, really.)
(…)
”
“
We need a feedback about packages that are preferred by users and actively used. Debian already has a tool named Popularity contest (popcon)
* reusing popcon will give us results that are directly comparable with Debian and Ubuntu
* packagers team can take care of the package
* we need a configuration dialog in YaST that is visible enough
* we need a server infrastructure on opensuse.org. (There are certain privacy issues, see Debian FAQ for details)
”
Recently requested features
Features newly requested last week. Please vote and/or comment if you get interested.
“
Why does not require a password to unlock the screen with the same login screen of KDM or GDM, instead of a dialog box? Such as Windows XP.
”
“
This is a dependency for tracker (and possibly gstreamer).
Libcue is intended to parse a so called cue sheet from a char string or a file pointer. For handling of the parsed data a convenient API is available. This project is meant as a fork of cuetools by Svend Sorensen which saw it last release in 02/2006.
http://sourceforge.net/projects/libcue/
”
“
This is an extension of Feature #312871, but because it’s a little more involved than changing a simple default, I thought it would be better to have a separate feature request.
The screen-saver settings for time-out and “require password” are security settings that really should not be freely available to the individual user. I propose that we
1) set a reasonable default (60sec, 15sec, always require passwd) (see Feature #312871) and
2) only let these settings be modified by someone with root-access.
To a regular user, the timeout and “require password” settings should appear “greyed out”, clearly indicating “not available”.
”
“
Remove the very old unmantained QCAD (it requires QT3!!!) and add LibreCAD a mantained port to QT4
http://librecad.org
”
“
Adobe just released Flash 11 which has a native 64-bit version for Linux, OS X and Windows. It should be included with OpenSuse 12.1 in the same way that Flash 10.x is included in 11.4. I know it’s very new but I think the removal of the nsplugginwrapper requirement on 64-bit makes it worthwhile. Flash is also know to have many security bugs, so keeping 12.1 at 10.3 for it’s entire lifecycle would be more dangerous than including 11.0.
”
“
When doing a kernel patch or update (as in eg zypper dup), the upgrade process re-writes the menu.lst entries for the kernel parameters with the default string from /etc/sysconfig/boot-something.conf
Not a lot of end-users are aware of that file (in my case it took 5 years to realise what was happening), and are instead constantly having to re-write missing kernel paraemters into the menu.lst file.
For instance, most sane folks would use splash=verbose as opposed to splash=silent, and for anyone using console=, brokendriver=, etc this is quite disasterous in the case of remote systems that suddenly become unreponsive / unreachable as a result of the kernel upgrade changing very important parameters.
Instead of taking the default from an obscure config file that no other distro even uses, I’d suggest that the kernel param line is taken as-is from the menu.lst / elilo.conf files, not set to some static value.
”
The Section provides the Game of the Week, and Updates in the Game Repository
“
While the Unknown Horizons developers
are working hard fixing bugs and preparing the new release, 2011.3, I’ve went ahead and
started to update all the dependencies to bring this wonderful game to openSUSE users.
Here’s a few things that were changed to support this release:
-
FIFE – Unknown Horizons now requires FIFE 0.3.3 (released
a few days ago). This was a bit of a pain-in-butt package, that started to build
properly after a SCons update (also forwarded to the openSUSE devel project in
devel:tools:builders).
-
Updated guichan to the latest release (0.8.2) and backported a commit that enables
UTF-8;
-
Updated SCons to 2.1.0;
-
ENet was updated to latest version (1.3.3).

Regarding Unknown Horizons packaging, I’ve also fixed some pending issues:
-
Added python-enet package: we now provide this so we can drop the binary blob
bundled with Unknown Horizons (depends on libenet >= 1.3.3);
-
UH now requires FIFE >= 0.3.3, which is no longer backward compatible;
-
Updated %post and %postun scriptlets.
-
Sources are a bit fatter now, using .xz now.
To install Unknown Horizons 2011.3rc3 please use one of the available 1-Click installers
for openSUSE:
”
To view the security announcements in full, or to receive them as soon as they’re released,
refer to the openSUSE Security Announce mailing list.
“
Table 1. SUSE Security Announcement
|
|
| Package: |
Update to Mozilla Seamonkey 2.4.1
|
| Announcement ID: |
openSUSE-SU-2011:1076-3 |
| Date: |
Fri, 14 Oct 2011 15:08:20 +0200 (CEST) |
| Affected Products: |
openSUSE 11.4 openSUSE 11.3 |
| Description: |
fixing various bugs and security issues. |
”
“
Kernel version 3.1 will probably be released in the next few days. After
a break of more than four weeks, Greg Kroah-Hartman has released new stable kernels. The
X.org developers are thinking about merging the most important graphics drivers into the
X-Server.
Late last Tuesday night, Linus Torvalds issued the ninth release
candidate of Linux 3.1. Since then, some further corrections have been integrated into the
main development branch; however, in the past few days there have not been any new hints on
when Linux 3.1 might get released – but it is likely to be released some time this week, or
next week at the latest, as indicated by Torvalds when releasing RC7.
Linus Torvalds explained in his release email that in RC9,
a new GPG key for signing Git tags has been used for the first time. The new key is said to be
stronger than the old one and has already been signed by more developers who are known to
Torvalds; however, the tag has also been signed with the old key.
”
“
As is the case every month, Jon Masters looks at the latest
developments in the Linux kernel community, including work on new architecture and ABI
support, not to mention Kernel.org disruptions…
In spite of the recent security attacks on kernel.org and other Linux community
infrastructure, the show must go on and kernel development continued – albeit heavily
disrupted at first by the various outages. That didn’t stop patches being posted adding
support for two brand new architectures to the Linux kernel. One of these architecture patch
postings targets a new DSP (Digital Signal Processor) design from Qualcomm called Hexagon that
is commonly found in combination with a more powerful ARM processor within Qualcomm
system-on-chip (SoC) processors – that’s two cores, both running different Linux kernels on
the same chip.
”
“
Rares gives his weekly Kernel Review with openSUSE Flavor.
”
For Commandline/Script Newbies
“
Well here we are again, at part two of the ‘Getting Help from Linux’ series. In this blog post I’ll be talking about using Info to get help from Linux. In my previous post I spoke about how Info came about, but just in case you missed it I’ll give you another quick lesson. Gnu Info was created by the Free Software Foundation and in my experience is used by all of Gnu’s software for their version of ‘man’ pages. Info may contain much more information than what you can find in Man pages, and sometimes contains much more than you ever really need. The good thing about Info is that it is a hypertext markup utility. This makes it much easier to navigate through via hyperlinks embedded in emacs, than simply using arrow keys to navigate through information. While Man uses the Less utility to control the display, the info utility itself is designed to display Info pages. For those of you familiar with emacs, it appears the layout may be the same, along with some of the basic navigation. But that’s where the two applications can differ. If you’re using the Info application then your commands will be different than if you’re viewing info files in Emacs. This article is about reading Info pages inside of info. (…)
”
For Developers and Programmers
“
This is going to be just a brief blog post with one important image. You probably all
already know that there is bunch of people in openSUSE community who are working on getting ARM supported by distribution. And
you probably already seen many blog posts about how great it is working. Well this is one of
them. I’m happy owner of ASUS Transformer machine. As a geek I have root on my android
machine. And since not long time ago, I also had a Debian chroot there to be able to run my
favorite applications. But not any more. I replaced my Debian chroot with openSUSE one and
now I can use zypper happily and forget everything about apt-get.
How did I did that? I started with a simple package in obs, changed BuildRequires to the
set of packages I wanted to have, run osc build armv7l standard and after
osc created chroot for me, I just took it away. And fixed few things after switching to it
on my Transformer. I’m still missing some packages, but hopefully they will be available
soon
”
For System Administrators
“
Snort, the open source intrusion detection and prevention system, is immensely powerful, but to get the most out of it, you need to configure it correctly for your own setup. My previous Snort article looked at Snort’s own performance monitoring provision and how to use it to tune Snort to get the best throughput at the detection end. Here are some performance tips for dealing well with alerts, looking at alert monitoring, streamlining false positives and genuine but frequent real positives, and logical rule optimization.
The last article looked at monitoring rule performance – that is, how well the Snort detection engine deals with the traffic it sees. The next stage concerns what to do with traffic that Snort flags as suspicious: alerts of various sorts. I won’t go into detail about how to deal with specific alerts, but talk instead about some good Snort management practices. (…)
”
“
By using MySQL replication, you can distribute MySQL queries over multiple servers to improve application performance, provide high availability (HA), and distribute data across diverse physical locations. The process involves one or more master servers, which send databases or tables asynchronously to slave servers. For all of its potential benefits, MySQL replication can cause serious trouble, especially in complex environments. Follow the advice here to get off to a healthy start.
In MySQL replication each participating server may be a master, a slave, or both. Master servers handle database transactions and write them to a binary log (binlog). Slaves connect to masters and request copies of their binary logs. Servers can act both as master and slave thanks to features such as different auto increment, which sets the interval between successive column values. (…)
”
“
As many of you know the most used packages on GNU/Linux are deb and rpm.
deb is the extension of the Debian software package format and the most often used name for such binary packages.
Debian packages are standard Unix ar archives that include two gzipped, bzipped or lzmaed tar archives: one that holds the control information and another that contains the data.
The accepted program for handling these packages is dpkg, commonly used via other programs such as apt/aptitude or Gdebi.
RPM Package Manager (RPM) is a package management system. The name RPM variously refers to the .rpm file format, files in this format, software packaged in such files, and the package manager itself. RPM was intended primarily for GNU/Linux distributions; the file format is the baseline package format of the Linux Standard Base. (…)
”
“
In preparation for taking the Linux Professional Institute Certification exam LPI-302 for systems administrators, learn how to set up and store passwords, integrate Samba with LDAP, and use ACLs to protect your Linux installation. (…)
”
“
Let’s say you want to CIFS mount a windows share — say “//server01/it stuff$”, but your
Windows admin put spaces in the path. Replace the spaces with | | |