We are pleased to announce our openSUSE Weekly News Issue 155.
Table of Contents
- Status Updates
- In the Community
- New/Updated Applications @ openSUSE
- Security Updates
- Tips and Tricks
- Planet SUSE
- openSUSE Forums
- On the Web
We are pleased to announce our 155 issue of the openSUSE Weekly News.
From this Issue on we don’t publish the Weekly News just in HTML. Now we are pleased to announce a new PDF Version.
You can also read this issue in other formats. Just click here.
Enjoy the reading :-)
A Q & A with Jeff Hawn, chairman and CEO of Attachmate by Jos
Poortvliet, openSUSE Community Manager at Novell
I had a chance to speak with Jeff Hawn, chairman and CEO of
Attachmate Corporation about his views and intentions around SUSE and openSUSE. Jeff has
commented that SUSE is an important brand and business that he wants to strengthen. What are
his thoughts about the community and what does he see for SUSE and openSUSE? Here below are
the questions I put forward and Jeff’s current thoughts. –Jos
What is Attachmate’s history with
open source projects?
Attachmate does not have a corporate track record in the open source business.
However, we recognize the importance of open source technology, particularly Linux, and
the growing value it brings to enterprises globally. We also recognize and value the
openSUSE project, the contribution that the community makes to the SUSE business and
most importantly, the many ways in which the community benefits SUSE customers.
At the end of the day, we are a technology company that is customer-driven, made up
of engineers and technology enthusiasts. We have a lot of individuals that are long-time
users of open source and participants in the open source movement. We recognize and
understand what the community has developed, particularly over the last decade, and we
are excited to be part of its future.
What is Attachmate’s view of open
Attachmate recognizes that enterprises all over the world are utilizing more open
source technology in their infrastructures, data centers and desktops every year. We
believe this is a trend that will continue and that’s why we are excited about the Open
Platform Solutions business and in particular, the SUSE Linux community.
It is easy for people to assume that because we are not currently in the open source
business, we don’t value or understand it. This is far from the case. We are in the
business of meeting customer needs and they see great value in utilizing open source
technology solutions. Because of its open nature, open source is being adopted by
enterprises in all industries around the world. Our intent is to keep it that way and
continue to foster what has made it so successful for the Open Platforms Solutions
Ok, then what is the plan for
We cannot speak to specifics until after close, but what we can communicate now is
our intention to establish a SUSE business unit on par with the existing Attachmate and
NetIQ business units. We believe that establishing SUSE as its own business unit will
give greater focus and flexibility to grow within a competitive market. We view SUSE as
a well regarded and proven technology in the open source and enterprise Linux community
and we want to further build upon that. We intend for SUSE to continue to provide the
same high quality open source technology solutions, such as SUSE Linux Enterprise
Server, needed to meet users’ demands for scalability, interoperability and cost
What will the SUSE business unit
be – what do you mean by “business unit”?
A business unit brings together all the resources, IP, people and infrastructure
needed to operate – to build product, deliver solutions and support customers. So, what
is known today as Open Platform Solutions will now be centralized within the SUSE
business unit. In most respects SUSE will continue to operate as it did as OPS, but will
benefit from being a dedicated and more visible brand with a focused business unit
Does Attachmate intend to
immediately sell the SUSE business?
I want to be clear here: all of our efforts will be focused on doing the things
necessary to make SUSE the highest performing business with the strongest openSUSE
community that we can. This is a healthy, growing dynamic business. We want to continue
to nurture this business and grow it. This is why we want to elevate the SUSE brand and
operate that part of the business as a distinct unit where it will receive greater
visibility and focus.
How do you plan to compete in the
We’re excited about SUSE because of the great competitive advantages it already has.
With thousands of certified ISV applications, the best interoperability and unsurpassed
scalability, it provides the best value and the lowest cost of ownership on the market.
Attachmate intends to continue that commitment to high quality and cost-effective
What are your intentions for open
source initiatives sponsored by Novell today?
No decisions have been made regarding any specific projects or sponsorships. Much
more integration work needs to happen before discussions of changing the status of
individual projects can occur. But we can say that the new SUSE business unit will stay
committed to participating in the projects and initiatives that are most important to
the SUSE business and its customers.
Will Attachmate continue to
support Linux kernel development by employees as Novell has
Yes, we will. Key contributions to the Linux kernel are a benefit to everyone in the
community. This sort of contribution is a key element of what makes the synergy between
business and open source so successful and we intend to continue support it.
Will Attachmate increase or
decrease the investments in development and marketing for
There is a lot of integration work to do before those decisions are made and some of
that work cannot be done until after the transaction has closed. Our intent is to
continue to sponsor and participate in the openSUSE project.
Will this impact the initiative
to create an independent foundation for openSUSE?
No decisions on this initiative have been made. This is a complex topic that has
been actively debated in the community for some time. We look forward to continuing that
discussion with the community after the close of the transaction.
Will Attachmate continue to
support the openSUSE conference?
No decisions have been made about the ongoing sponsorship of openSUSE conference. It
is simply too early to reach conclusions on specific areas such as this – more
integration work and collaboration with the SUSE team is needed. Our overall intent is
to maintain the continuity of success we see within the SUSE business and that includes
continuing to work closely with the openSUSE community.
Will the acquisition have any
other effects on the openSUSE project or community?
We look forward to learning more about the project and working together with the
community to figure out what’s working well, what could be done differently or improved.
This will be a highly collaborative relationship.
Does Attachmate intend to shut
down the openSUSE community project?
No, we don’t. Attachmate intends to continue the sponsorship and collaboration with
the openSUSE project. We view the openSUSE project and its extended community as an
important part of the overall SUSE business and we value its contributions to the
technology that forms the heart of the SUSE offerings (see related statement on the
Attachmate website here).
What IP assets are being
purchased by CPTN Holdings LLC?
Attachmate cannot provide details on the IP assets being purchased, but we can
clarify that CPTN is NOT purchasing products. They are purchasing 882 patents and patent
applications as described in the initial 8-K filed by Novell.
The purchase does not include the Novell UNIX copyrights (see related statement on
the Novell website here). It does not include the product source code or product
Attachmate would not buy a company and not preserve what is working nor hamper our
ability to operate this business. So, SUSE will retain all the technology, rights and IP
needed to continue and grow.
Does the purchase by CPTN
Holdings impact the openSUSE project or the SUSE enterprise
After the merger is complete, the SUSE business unit will retain all the IP and
technology rights needed to operate, continue its sponsorship of the openSUSE project
and supporting SUSE customers.
What happens to the Novell UNIX
copyrights after the sale of IP assets to CPTN
No change. The purchase of IP assets by CPTN Holdings does not include the UNIX
copyrights and the copyrights will continue to be owned by Novell (see related statement
on the Novell website here).
This communication contains statements that constitute forward-looking statements within
the meaning of the Private Securities Litigation Reform Act of 1995. These statements are
based on current expectations and beliefs and are subject to a number of risks, uncertainties
and assumptions that could cause actual results to differ materially from those described in
the forward-looking statements. Any statements that are not statements of historical fact
(such as statements containing the words “believes,”
“estimates” and similar expressions) should be considered forward-looking
statements. Among others, the following risks, uncertainties and other factors could cause
actual results to differ from those set forth in the forward-looking statements: (i) the risk
that the merger may be delayed or may not be consummated; (ii) the risk that the definitive
merger agreement may be terminated in circumstances that require Novell to pay Attachmate a
termination fee of $60 million; (iii) risks related to the diversion of management’s attention
from Novell’s ongoing business operations; (iv) risks regarding the failure of Attachmate to
obtain the necessary financing to complete the merger; (v) the effect of the announcement of
the patent sale or the merger on Novell’s business relationships (including, without
limitation, partners and customers), operating results and business generally; and (vi) risks
related to obtaining the requisite consents to the patent sale and the merger, including,
without limitation, the timing (including possible delays) and receipt of regulatory approvals
from various governmental entities (including any conditions, limitations or restrictions
placed on these approvals) and the risk that one or more governmental entities may deny
approval. Additional risk factors that may affect future results are contained in Novell’s
filings with the U.S. Securities and Exchange Commission (the “SEC”), including
Novell’s Annual Report on Form 10-K for the fiscal year ended October 31, 2010, which are
available at the SEC’s website http://www.sec.gov. Because forward-looking statements involve
risks and uncertainties, actual results and events may differ materially from results and
events currently expected. Novell expressly disclaims any obligation or undertaking to update
or revise any forward-looking statements contained herein to reflect any change of
expectations with regard thereto or to reflect any change in events, conditions or
ADDITIONAL INFORMATION ABOUT THE MERGER AND WHERE TO FIND IT
In connection with the merger, Novell filed a preliminary proxy statement regarding the
merger with the SEC on December 14, 2010 and intends to file a definitive proxy statement
regarding the merger and other relevant documents with the SEC in the future. Investors and
security holders of Novell are urged to read these documents, including the definitive proxy
statement, if and when they become available, as well as any amendments or supplements to
those documents, because they contain or will contain important information about Novell, the
merger and the other parties to the merger. Investors and security holders may obtain these
documents (and any other documents filed by Novell and Attachmate with the SEC) free of charge
at the SEC’s website at http://www.sec.gov. In addition, the documents filed with the SEC by
Novell may be obtained free of charge by directing such request to: Novell Investor Relations
at 1-800-317-3195 or from the investor relations portion of Novell’s website at
http://www.novell.com/company/ir/. Investors and security holders are
urged to read the definitive proxy statement and the other relevant materials when they
become available before making any voting or investment decision with respect to the
merger. Novell and its directors and executive officers may be deemed to be
participants in the solicitation of proxies from Novell’s stockholders in respect of the
merger. Information regarding Novell’s directors and executive officers is contained in
Novell’s proxy statement for its 2010 Annual Meeting of Stockholders, dated February 26, 2010,
and subsequent filings which Novell has made with the SEC, including its Annual Report on Form
10-K for the fiscal year ended October 31, 2010. Stockholders may obtain additional
information about the directors and executive officers of Novell and their respective
interests with respect to the merger by security holdings or otherwise, which may be different
than those of Novell’s stockholders generally, by reading the preliminary proxy statement and
the definitive proxy statement and other relevant documents regarding the merger, when filed
with the SEC. Each of these documents is, or will be, available as described above. Other
For the full transcript of the last openSUSE Board meeting, see our logs.
Introduction of new openSUSE Board Chairman – Alan Clark
We opened with an introduction to new Board Chairman, Alan Clark who answered general
questions from the community about his role and goals. To the question of what Clark’s goals
are he answered:
The top goal is as a Board to get the Foundation up and operational. As we continue
to work towards this, I’m sure that we will uncover other issues that we will need to
Grow the Community
Is a personal goal: Tune up my decoder ring for all these alias cloaking and get to
know as many people as possible -simply because that is the fun part of being in a
Let people get their work done; er “have a lot of fun”
Alan also provided his background experience with open source projects, both within Novell
and outside Novell.
Several board members expressed a desire to develop a more open and transparent process in
communicating the development of the openSUSE Foundation than what currently exists. Some
believe there has been a disconnect in how we become aware of what everyone is doing and
keeping the momentum of the process going forward, as well as ensuring that all those with a
vested interest are able to participate in the process.
We all agreed that we must begin to identify who are the stakeholders and take steps
immediately to open up the process. To that end, a new open mailing list will be created and
Alan will create a wiki page where we will collect all the relevant information for the
foundation creation. Relevant points and concerns of the stakeholders will be listed and the
progress of the creation will be documented.
Membership Approval Concerns
Membership approval team members expressed concern about the clarity of the rules for
consideration and eligibility.
In the current rules, it states that a membership application is processed after receiving
four votes. It was unclear whether that meant four votes in sum or four votes of either
positive or negative. With a minor edit of the rules, we stated that an application is
considered processed once it has received either four positive votes or four negative
Additionally, there was concern about a recent email request to process a particular
application expeditiously. Team members felt this was an inappropriate breach of protocol and
that all applications are equal and that no single application should be placed ahead of
existing applications. We agreed and declared that henceforth, such requests should not be
Where do we fail?
Our regular topic to identify areas where we fail and can quickly remedy brought up a
topic of concern regarding communication. To this, we agreed that the Board will begin
regularly posting summaries of meetings (which is what you are reading now.)
We also took a general board action item to review opensuse.org product
category in openFATE to ensure we stay on top of “Where do we fail?” concerns that
are not brought up during board meetings.
Read here for the full meeting transcript.
With the holidays coming up, we will have our next Board meeting on 12 January,
The openSUSE project released the fifth of six milestones in the development of openSUSE
11.4 some days ago. Milestone 5 (M5) brings a wide range of
updates, both major and minor. As usual, you can get it here.
Kernel 2.6.37rc5-12 is the basis of M5, including the famous “200 line” per tty task
groups patch to improve desktop interactivity, and featuring the almost-complete removal
of the so-called ‘Big Kernel Lock’, which should improve scalability. This kernel supports
new drivers, including Broadcom wireless and updated open-source graphics drivers, and a
host of the usual other improvements.
Libzypp 8.10.2 adds improved support and fixes for metalinks, the multiple download
On the desktop, the KDE Platform makes the leap to version 4.6 beta with many
improvements in the UI and underlying infrastructure. This includes a complete rewrite of
Kontact and is undergoing heavy testing. There is a serious chance KDE PIM 4.6 will not
make it into the final openSUSE 11.4 release, testing and development is needed!
KOffice is updated to 2.3 RC superseding beta1, including the exciting Krita natural
media painting app. Meanwhile OpenOffice.org is removed, having been succeeded by
LibreOffice which is updated to 22.214.171.124.
GNOME 2.32.1 is now available as the 2.32.2 is the final version planned for openSUSE
11.4, which is notable for being the last stable release before GNOME 3 in March.
GNUCash 2.4 RC comes with a new complete dress-up.
Pidgin updates fixes several MSN and ICQ issues.
In the Virtualization area, available now are kernel-xen 2.5.37 features and
kernel-ec2 2.6.37 with improvements for cloud sync services and Virtual Box 4 Beta
including USB devices support and more than 2GB RAM support on 32 bit guest, Intel HD
Audio, asynchronous I/O for iSCSI, VMDK, VHD and Parallels image support.
systemd 15 provides aggressive parallelization capabilities to start multiple daemons
at the same time with dependencies which offers improvements to the boot times on some
systems. More testing (and porting of init scripts) is still needed for systemd, which
will most likely make it into 11.4 as experimental and optional feature.
A list of most annoying bugs is being compiled; please check it before installing. We look
forward to your bug reports and test experiences! Automated testing and the openSUSE Factory
team have been very active to ensure that your download of M5 will be at least minimally
functional, thanks for that! now go and download it!
The next milestone is scheduled for Thursday, Jan 20 2011, and will be the openSUSE 11.4
Milestone 6 release. The final openSUSE 11.4 is planned to be released in March 2011.
openSUSE Weekly News searches for contributors
Figure 1. Merry Christmas (c) Péronne vd Ham / pixelio.de
Hello Mates. The last year was a great year. We had seen many funny things. The Relaunch
of the openSUSE BuildService now provides many Features for packager. Then the
kde-obs-generator makes the life easier for cross packaging. The openSUSE Conference was
another interesting Highlight, and last but not least the sell of Novell.
The openSUSE Weekly News Team searches the whole week for new things. Now we searching one
or two new Contributors who are collecting news with us. In the past we have given one part
of the news to one person, and that person was responsible for this part of the Weekly News.
As Example you provide the Section “Tips and Tricks” so you can add and remove that Section
what do you think is the best.
ATM we can give the following Sections to a good Hand:
Tips and Tricks
In the Community
On the Web.
What do you need for working in the english newsletter? If you can read and a little bit
write XML, and you know how to svn up, then you’re the perfect Candidate. If you can’t this
things, and would like to learn it, you are a perfect Candidate.
If you’re interested in helping us, just send a Mail to: firstname.lastname@example.org
Last but not least the openSUSE Weekly News team with the translations into hungarian,
greek and japanese wishes merry cristmas to all people across the world.
SMBTA Stresstest is an appliance based on openSUSE 11.3
for long-time- or stress testing the SMB Traffic Analyzer
software suite. It is used mainly by the SMBTA development team to check the behaviour of
SMB Traffic Analyzer under certain traffic conditions. It also can easily be used to just
try out SMB Traffic Analyzer.
Figure 2. SMBTA Stresstest running in VirtualBox
With this first release, SMBTA Stresstest
Figure 2, “SMBTA Stresstest running in VirtualBox” comes with a Samba Server that
is configured for two shares, “Officespace” and “music”, and logs traffic on those shares
using SMB Traffic Analyzer. Two users are preconfigured, “holger” and “john”, and for those
two instances of the smbtatorture program is started,
producing infinite traffic on the shares.
The appliance is configured for port 3491 as the connection port for the smbtatools,
which allows to inspect the generated traffic from an other machine.
SMBTA Stresstester has been created using the fabulous SUSE Studio and comes in OVF format, and
should be able to run on KVM, VMware, and VirtualBox. The appliance is
completely self-contained, runs the smbtatorture processes directly after reaching runlevel
3,and Built with SUSE Studio if your virtual machine is setup to be reachable from the
host’s network, all the SMBTA tools like rrddriver or smbtaquery can be run against it, once
you know the IP adress of SMBTA Stresstester (the appliance root password is
“linux”):smbtaquery -i 3491 -h 192.168.178.26 -q ‘global, usage rw;’
SMBTA Stresstest is available in the SUSE Gallery, and we also
uploaded it to this place. For more information on SMB Traffic Analyzer, please check out it’s
Christmas and a happy new year.
If you have the last Milestone of openSUSE, thats already number 5, installed then you
can take a look into the history. You would see a dark splash as I planned them long time
ago. You also see the KDM in the color I planned in August.
2 weeks ago Coolo asked for some artwork for integrate it into the next Milestone, a
weekend with lot of work, for Javier and me. After that some people woke up. First the KDE
team wanted the color changed to celadon, whats also is the codename for 11.4. Thats ok
for me, its there choice and it would be work with the grey what I planned for the GNOME
But now the GNOME team also want it changed. And that becomes now harder to do. There
are some possibilities and also some borders for the work. Right now there is a little
discussion on the mailinglist. But the default background of GNOME would be definitly not
happen, he is nice but the blue works not with the celadon green tone. Also change that
background to celadon green, wouldnt work because I have to choose one of the backgrounds
for the bootsplash. Hope they find a solution I can work with. I would prefer a grey one,
with a celadon geeko on it and change the green tone in sonar to celadon green
Again thanks for participating in the collaboration day on Social Media. I have
written an overview, I hope one of the news editors on this list has time to take a look
and maybe find a pretty picture to accompany our success story.
Meanwhile there are a few things which are close to being finished, but aren’t there
just yet. My pet peeve: the short descriptions of openSUSE. They are here: http://ietherpad.com/idAZ997QVS
I have used part of that text to make a start on the two folders that we’ll
Both need a lot of work and any help here is appreciated too!
I really appreciated the work done on the feature guide, I worked on it some more and
I hope we can get it a bit further and finish it during the marketing meeting in Februari.
Anyone who has some spare time, check it out here: http://manugupt1.ietherpad.com/4
I can however hapilly tell you that the article we wanted to write about new openSUSE
projects is pretty much there now – some finishing touches and it can go live on
news.opensuse.org! Great work all involved!
Wow. That’s a large bunch of writing things. I know not all of you like that stuff, so
– who comes up with tasks that are less writy? ;-)
Let me name one: we need themes for Identi.ca, Blogger and Twitter! Shouldn’t be
incredibly hard to make and I’m sure Robert Lihm, gnokki, Javier and our other artists can
and will help here.
Features with highest vote, but no one has been assigned to yet. We are looking for volunteers to implement.
“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
“We need a replacement for sax2 in 11.3, as a safety measure for when auto
configuration fails to detect certain monitors/keyboards/mice. (…)”
“We need a feedback about packages that are preferred by users and actively
used. Debian already has a tool named Popularity contest (popcon) (…)”
“The YaST Qt package manager should provide as much information in the
“Installation Summary” view as zypper, esp the overall download size to expect
and how much disk space will be freed/used after performing the operation.”
“Idea from community member Raúl García. Same concept as MSI packages for
Windows but exploiting the One Click Install concept of openSUSE (and therefore
inheriting the simplicity, code and security. (…)”
Features newly requested last week. Please vote and/or comment if you get interested.
“Actually many distribution force scripts to have x privileges set. In KDE it will appear a dialog, when user try to run Desktop/Executable file.
I think, that we should also add a way to write checksums and fingerprints to scripts/executables. User won’t allow to run command if vendor are untrusted.”
“In openSUSE 11.0, when kernels were packaged, the developers used a -pae flag to show that the kernel had PAE enabled, so if I wanted a realtime kernel I could choose between kernel-rt and kernel-rtpae.
Now (from 11.2 up) it seems that all the kernels have PAE enabled, except kernel-default; and they are not marked as such, so kernel-rt STILL has PAE enabled. (…)”
“The partition manager allows backup and resotre of whole partitions, unfortunately it does a 1:1 copy, without compression.
Compression would be great to save some disk space on the image.”
“This feature is a continuation of
https://bugzilla.novell.com/show_bug.cgi?id=657607 I agreed with J.W. that there should be a “build-essential” meta-package that depends on things like gcc, make, automake. Those are always pre-installed in OBS and thus missing from the explicit BuildRequires list of packages.
Currently, the exact list of implicit BuildRequires might only be known in the osc build script.
This build-essential could then be fetched by “zypper si PACKAGENAME” and also be used in OBS to not have to maintain the list of packages in two places.”
“Xprint is an advanced printing system which enables X11 applications to use devices like printers, FAX or create documents in formats like PostScript, PDF, PCL, etc.”
“with yast->printer->edit there is at bottom of that window a little box “Enable Printing” which must be activated to print. (…)”
“I’ve long been amazed about the speed of DamnSmallLinux on a low spec machine when run completely in RAM.
I’ve also seen that this is possible with Gentoo and Ubuntu nowadays. (…)”
“Next openSUSE will be 11.4. How can we have a really good reason to go to *12* and not 11.5 there after.
We have to create something specially related to openSUSE (not GNOME, not Kde…). One thing or several, something that makes people say “wow!!” (…)”
“portable across multiple suse installations of the kde/gnome settings… everywhere is like home.”
“Many users are frustrated, that OpenSUSE don’t support He/She’s native language well.
Allow to load native language files on system startup. Simply initramfs/initrd could load very base system, create ramdisk and asks to remove system CD them insert language support CD.
System will install packages with additional language onto ramdisk and asks to insert base system CD again.
After this process is performed, system will boot normally.”
Statistics for openSUSE 11.4 in openFATE
The next Testing Core Team IRC meeting to discuss 11.4 Milestone 5 will be held
December 27 at 1800 UTC.
As most of you are aware, openSUSE 11.4 Milestone 5 was released on schedule.
Many of us have had a chance to test it, and found few problems. The only bug
added to the “most annoying” list is that zypper is slow on Live-installs (Bug
#659864). There is a workaround.
I repeat my plea for readers of these news to test, test, test, and and report
all bugs to the Novell bugzilla.
A very happy holiday for all.
The openSUSE Weekly News are available as livestream or podcast in German. You can hear it
or download it on Radiotux.
“puddletag is a tag editor for Linux loosely based on mp3tag. It uses a table layout
so that all the tags you want to edit by hand are visible and easily editable. puddletag
excels at automating repetitive tasks like extracting tag information from filenames,
tagging files from a text file or the clipboard, renaming or moving files and folders based
on tags by using patterns, and manipulating tags using actions and regular expressions.
Supported formats include id3v1, id3v2 (.mp3), AAC (.m4a), VorbisComments (.ogg, .flac), and
APEv2 (.ape). Much of mp3tag’s functionality has been replicated with added enhancements and
“XMMS2 is an audio framework, but it is not a general multimedia player – it will
not play videos. It has a modular framework and plugin architecture for audio processing,
visualisation and output, but this framework has not been designed to support video. Also
the client-server design of XMMS2 (and the daemon being independent of any graphics output)
practically prevents direct video output being implemented. It has support for a wide range
of audio formats, which is expandable via plugins. It includes a basic CLI interface to the
XMMS2 framework, but most users will want to install a graphical XMMS2 client (such as
gxmms2 or esperanza).”
This is a GTK+ based GUI for the libxine video player library. It provides gxine, a media
player that can play all the audio/video formats that libxine supports. Currently, this
includes MPEG1/2, some AVI and Quicktime files, some network streaming methods and disc based
media (VCD, SVCD, DVD).
Equalizer is the standard middleware to create and deploy parallel OpenGL-based
applications. It enables applications to benefit from multiple graphics cards, processors and
computers to scale the rendering performance, visual quality and display size. An Equalizer
application runs unmodified on any visualization system, from a simple workstation to large
scale graphics clusters, multi-GPU workstations and Virtual Reality installations.
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.
Have you ever tried WebYaST ? No ? Then it is time for.
We have noticed that WebYaST is not really known in the OpenSuSE community. One reason
for is that WebYaST is not really user friendly regarding the installation.
So we have investigate here some effort. Lets see….
The simplest way is the one-click installation which is already installed on your
Just use a web browser (like firefox) with the url: http://download.opensuse.org/repositories/YaST:/Web/openSUSE_11.3/webyast.ymp
The browser will ask you to start the installation via the one-click installation. Start
the installation and go through the installation workflow.
Starting and managing WebYaST
WebYaST is a web application which runs on two http servers on your system. For starting
and managing these servers Thomas Goettlicher has written a nice Qt-applet which can be
started e.g. in KDE:
After starting the WebYaST applet the WebYaST icon appears on the right edge of the
WebYaST is disabled WebYaST is enabled
With the right mouse click you can manage WebYaST:
With this applet you can start WebYaST in your browser too. After accepting the GPG-key
please login with your “root” account.
And that’s WebYaST:
(Yes, I know that sentence is written almost in every post here. Even in posts where
problems just starting after the sentence has been read. :-) )But I think that should be
really all. If not, please use bugzilla and blame us ! Have fun !
(Yes, I know that’s the second sentence which should be in every blog :-) )
Using Linux on a laptop has always been a hit and miss affair. With sometimes obscure proprietary hardware, many laptop manufacturers have showed no interest in supporting the free operating system. Nevertheless, through hard work by developers and support from some hardware manufacturers, Linux now supports a wide variety of laptops and netbooks. (…)
This is the second article in this series, and brings eight additional tips for working
faster with the shell. Here is the first
article of the series, containing 10 tips. (…)
Establishing a rigorous version control process is a standard part of any software project, and Git is a powerful system
for enabling such version control. But Git’s advantages extend beyond just software development. For instance, I use Git to manage all of my writing projects,
including books and my articles published on Developer.com (including this one). Git offers writers a fantastic set
of features for producing material in an impressively fast, efficient and organized manner. In this article I’ll introduce you to 10 Git tips and tricks I
regularly apply within my own writing projects! Even if you’re using Git solely for software development, you’ll still be able to apply these tips to
your projects! (…)
Ever wondered why your filesystems fill up so quickly and why those new discs aren’t as
big as advertised? While the latter may have several reasons (measuring units, the metric
system or just damn lies), it may also be just an overly precautious default filesystem
setting. On Linux, every filesystem gets some 5% of the available blocks reserved for the
root user. This way, you can still work on your machine even if you forgot to rotate your
log files Changing this default to something more realistic on today’s big hard discs may
come with a nice surprises. Here’s my laptops root partition before:saschpe@minime:~% df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 168G 144G 16G 91% /
Now let’s do a courageous tune2fs changing this to 0.2% (more than enough to be able to
login and remove logfiles):sudo tune2fs -m 0.2 /dev/sda1
And check again:saschpe@minime:~/download% df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 168G 144G 24G 86% /
How neat, 8 fresh new gigs of storage :-)
This describes how to set up ssl certificates to enable encrypted connections from PgAdmin on some client machine to postgresql on a server machine. The assumption is that postgresql (compiled with ssl support) and openssl are already installed and functional on the server (Linux). PgAdmin is already installed on the client (either Windows or Linux). (…)
“I am a good user of social networking sites, such as Facebook and Twitter. They
have used very interesting features on their websites, such as instant messaging. By that I
do not mean the chat application that Facebook uses, or the immediate update on Twitter
messages. I am talking about the idea of instant messaging on settled messages. For example,
when a person posts a comment on Facebook and is able to keep a conversation from one person
to the next. It is a minifeed that also includes the rest of the present contacts that are
involved in the message box.”
Figure 3. Facebook Minifeed
“Twitter is a little similar, you are able to scroll through the many messages on
your home page as well as the rest of the contacts who have posted messages on your Twitter.
(…)Figure 3, “Facebook Minifeed””
Use case: I want to create an appliance image for a build farm worker machine. I don’t
know its hardware configuration beforehand; in particular, it may have multiple network
interfaces and I don’t want to bother figuring out which is which. I will simply include
network-autoconfig.rpm and plug the cable into any socket
network-autoconfig helps setting up machines with multiple network interfaces. At the
first boot, all available Ethernet interfaces are cycled until one is successfully configured
I have submitted it to openSUSE:Factory now. Enjoy it in the upcoming openSUSE
I’ve finished with the base packages required for Unity, in fact Unity already builds,
though I’ve not really tested it yet as some components still need to take care… so far what’s
dee – is now properly packaged and ready for submission (no patching required);
bamf – is now properly packaged and ready for submission (includes a patch modified by
Adam Williamson based on a Debian patch);
ux – builds and in a way it’s ready, though I want to split this package in the nearby
unity – builds for the time being… though it requires proper integration on the
system. This build also builds with support for Indicators, since the dependencies are
already prepared. Will take now a bit of time due to integration. I will offer this
package installed on /opt/unity and not on usual system path.
While fighting for dependencies there emerged a small problem with ‘glewmx’, which builds
from the same sources of ‘glew’. I’m currently working on this package as a priority to fix it
and submit it to ‘multimedia:libs’ which also hosts ‘glew’. This package has also a small
patch by Adam Williamson which was already submitted upstream that allows the proper build of
‘libGLEWmx.so*’ and glewmx.pc. Currently I’ve built this package only offering the libs. I’ve
removed the binaries (and made a dependency on ‘glew’ for the binaries) and I’ve also removed
the headers from the includes which will be shared with ‘glew’ and made a proper dependency.
I’ve consulted Dimstar regarding this operation which promptly offered some quick guidance on
the process and showed a couple of useful examples on how to this ‘the openSUSE way’.
I hope that before the new year there’s a test package of Unity for Factory users. I would
also take this opportunity to thank everyone which has helped me so far on this ‘one man
inglorious rush’ towards bringing Unity to openSUSE as an option for those who want to check
My sincere thanks to the following:
Vincent Untz (openSUSE/Novell);
Ken Vandine (Canonical);
Cristopher Roges (Ubuntu);
Adam Williamson (Fedora/Red Hat);
openSUSE GNOME team;
The openSUSE community, specially those which have supported this effort since day
Arch Linux contributors (which were working on this and from which I got some guidance
from their ‘forums’);
Now I work for SLMS ( Suse Lifecycle Management Server ) project. It cooperate with SuSE
studio and use its API. I get idea that more people could benefit from easy access to studio
API from ruby so I extract functionality and improve behavior, documentation and testing and
now there is new rubygem studio_api. Why you should use this gem?
Actively maintained ( and will be due to SLMS support )
Tightly developed with guys from studio team
Well documented with yard
Good test coverage.
I think then a lot of glory words is better to show example. It is example based on
example from documentation. Example goal is simple. Create new appliance in studio, add own
cool rpm and build appliance with it. It can be useful to test your new version of software in
stable environment and have automatic appliance in which you can test it. (…)
On behalf of the openSUSE Forums Team I wish you a Merry Christmas and a very Happy en Open New Year. The threads above are the ones I found in the forums, read to get yourself in a holiday state of mind.
A question, asked a lot in the openSUSE Forums. This member needs to have both openSUSE and XP installed on a fresh new disk. The replies not only supply the answer to this question, they also help the thread’s starter to a good partitioning scheme of the new disk.
A nice example of a good thread opener: a clear title, a good description of what happens. Quote: “After setting up to print using wireless access, printing works fine, there is however no longer any internet access available, wired or wireless ( from PCLOS, Mandriva, openSUSE, win7, or whatever!) To restore internet access requires rebooting the router and turning off the printer (or disabling its networking) similar issues with wired network printing.”
This week’s subforum:
This forum of the openSUSE Forumsis a subforum of Get Help Here. Top thread on the list is a “sticky” : Getting your wireless to work , it’s writen in 2009, but still a very good set of instructions and explanations. Does your card not work after following this, use the search function of the forums, search for the brand of the wifi device. Chances are high you find a post that leads to a working device.
The Document Foundation has joined the Open Invention Network (OIN), to further extend
the free software ecosystems. By becoming a licensee, The Document Foundation – developer of
LibreOffice, a free office suite for personal and corporate productivity – has joined the
growing list of organizations that recognize the importance of participating in the Open
Invention Network, in order to protect the free software ecosystem from the risks associated
to software patents.
“The Document Foundation is a major free software project, and LibreOffice a key
office suite for creating, managing and sharing documents. By becoming a licensee of the
Open Invention Network, we fight software patents – which stifle innovation and encourage
predatory business practices – and at the same time we improve the protection of our
software projects,” said Charles Schulz, Member of TDF Steering Committee.
Patents owned by Open Invention Network are available royalty-free to whichever company,
institution or individual that agrees not to assert its patents against free software.
Through this network of developers, distributors, sellers, resellers and end-users that
license its patent portfolio, Open Invention Network is creating a supportive and shielded
ecosystem to ensure the growth and adoption of free and open source software. This enables
OIN licensees like The Document Foundation to make significant investments, helping to fuel
OIN has amassed a broad portfolio of patents, including patents held by nominees on its
behalf. These patents are available to all licensees as part of the patent portfolio that
OIN is creating in support of free software. The license agreement is at http://www.openinventionnetwork.com/pat_license_agreement.php
The home of The Document Foundation is at http://www.documentfoundation.org.
The Document Foundation has the mission to facilitate the evolution of the OOo Community
into a new open, independent, and meritocratic organization within the next few months. An
independent Foundation is a better match to the values of contributors, users and
supporters, and will enable a more effective, efficient, transparent, and inclusive
Community. TDF will protect past investments by building on the achievements of the first
decade, will encourage wide participation in the Community, and will co-ordinate activity
across the Community.
KDE e.V. is pleased to announce that we have joined the Open Invention Network community as a
Open Invention Network was founded as a way to help defend the Linux ecosystem, and by
extension much of the Free and Open Source software world, from the risks associated with
software patents. Patents owned by Open Invention Network are available royalty-free to any
company, institution or individual that agrees not to assert its patents against the Linux
System, creating an umbrella of protection for its members.
“We view an OIN license as one of the key methods through which open source
innovators can deter patent aggression,” said Adriaan de Groot, vice president of KDE. “We
are committed to freedom of action in Linux, and in taking a license we help to address
the threat from companies that support proprietary platforms to the exclusion of open
source initiatives, and whose behaviors reflect a disdain for inventiveness and
“Given its leadership in creating a user-friendly computing experience, including
its advanced graphical desktop for the Linux community, we are pleased to have KDE become
a licensee,” said Keith Bergelt, CEO of Open Invention Network. “By doing so, KDE affirms
its continued support for open source. We applaud their foresight in taking this step to
support both itself and the open source community broadly.”
While KDE maintains our position against software patents, this development provides an
additional safety net for KDE when it comes to the risks Free Software is facing from such
December 23rd, 2010. Right before christmas, KDE has published the first candidate for
the upcoming release of KDE 4.6.0. The focus at this stage is on fixing bugs and completing
translations and artwork. As such, the rework of the Oxygen icon set is nearing completion,
many bugs reported by testers in the past weeks have been fixed and stabilization is still
in full swing. KDE’s release team has decided to not include the new release of
KDE-PIM, containing the Kontact groupware client and the new KMail2 which is based on the
Akonadi groupware cache in this release due to open issue with migration of large sets of
data from the traditional client. These bugs are being worked on as we speak, but the risk
at this point is too high to include the new Kontact in the 4.6.0 release. Therefore, it has
been decided to release KMail2 and its companions together with one of the subsequent 4.6
releases, likely 4.6.1 one month later. A 3rd beta version of the kdepim module is available
already. As the other components of the frameworks, workspaces and applications are nearing
release date, KDE encourages testers to give their favorite software some final thorough
testing. The last chance for feedback will be the second release candidate, planned for
January, 5th 2011. The final release of 4.6.0 will be available on January, 26th 2011.
KDE, including all its libraries and its applications, is available for free under Open
Source licenses. KDE can be obtained in source and various binary formats from http://download.kde.org and can
also be obtained on CD-ROM or with any of the major GNU/Linux and UNIX systems shipping
Editors Note: The openSUSE Packages of KDE SC 4.6 RC1
are placed in KDE:Distro:Factory Repository.
Another month, another Winetricks.
Dan Kegel released winetricks 20101008 today. new verbs icodecs, msnasn1, opensymbol,
wmi, xmllite; removed obsolete verbs audioio, dcom98, eadm, urlmon
wsh57 now works with vb scripts, the code has undergone some spring cleaning, so watch
out for regressions. (We’ve fixed a few already.) In particular, the audioio, dcom98, eadm,
and urlmon verbs are gone, let me know if you really need those!
There’s a new –optin commandline option that will tells winetricks to phone home after
each run with info about which verbs really get used. Please consider using this, it will
help future winetricks development. (You only have to give that option once, it sticks. You
can turn it off with the –optout option, or by removing ~/.cache/winetricks.) (…)
Welcome to the Qtest Mobile App Port! As developers of applications using Qt, you
already know how great it is to work with – but how about on mobile platforms, such as
Symbian and MeeGo? How would you like to take that step you have been wanting to take, but
not been able to justify: Take your application from the desktop and bring it into the
hand-held world via the Ovi store. Let this contest be the justification, with the
possibility of a new phone or even 10,000 euros waiting at the end.
Dates: The contest starts on 20th of December, 2010,
and runs till 28th of February. The 31st of December is important for you if you wish to
take part in the Early Bird competition. If you do no win, you will still take part in the
main competition, and will be allowed to continue your work and submit new versions to the
Ovi Store. The 28th of February is the deadline for taking part in the main
Developer Sprint: There will be a sponsored developer
sprint organized together with the KDE e.V. during the competition. The travel and stay can
be paid for if you do not have the budget yourself. Further details will be made public at a
later time, and all participants will be notified of this information via email.
Judging and prizes: The Qtest Mobile App Port is
evaluated by a panel of judges which will be announced in the next few days. The jury will
pic 5 winners at 31th of December as the early bird winners. Every winner gets a free N900
phone. The main competition first prize is EUR 10,000, which will be awarded to the
application which the judges find to be the best ported application. The second to sixth
price will be another 5 N900 phones.
And, finally: Everybody who takes part in the competition will be awarded a gift bag,
with a T-shirt and other merchandise.
Eligibility: To be able to take part in the contest,
the ported application must be submitted for Ovi Store signing by one of the two deadlines:
– Early bird entries must be submitted by December 31st – Standard entries must be submitted
by February 28th.
You also have to submit your application to the “Mobile Contest” category on
Qt-Apps.org or MeeGo-Central.org
You can submit your application to the Ovi Store as many times as you wish during the
competition. This allows you to get feedback from the public on your software. It´s possible
to submit new or existing KDE/Qt applications.
So have fun and good luck everybody!
The X.org developers have released version X11R7.6 of their graphics system, which
contains the X Server version 1.9.3. One of the innovations in 7.6 is that it uses udev for
hardware detection and hot-plug notification; a HAL (Hardware Abstraction Layer) is no
Xorg configuration directories now allow the X Server configuration to be saved as
individual module files. For instance, the input device driver matching rules previously
provided in HAL .fdi files are now provided as InputClass sections in .conf files in
Google has launched an official
YouTube channel for its Open
Source Programs Office (OSPO). According to Google Open Source Team member Ellen
Ko, the new channel is aimed at organizing videos related to Google and other open source
projects in a single place.
A number of playlists with videos of, for example, Google Tech Talks that feature open
source projects have already been added. Other videos from Jeremy Allison’s Geek Time series,
as well as of Googlers speaking at open source conferences are also available. The Google
OSPO YouTube channel currently has 14 videos, with links to a variety of other videos from
other channels and users.
Last Thursday the European Commission took a major step forward on the “openness” scale.
The occasion was the release of a new version of the European Interoperability Framework
(EIF) which definitively endorsed the use of open source friendly standards when providing
“public services” within the EU. This result was rightly hailed by open source advocates
like Open Forum Europe. (…)
Ubuntu takes a lot of punches from time to time for its marketing and even its
interface. Some feel Ubuntu is dumbed down and oversimplified, while many others think
it’s innovative and user-friendly. Where ever you fall in the debate, one developer
thinks some elements of Ubuntu should land into openSUSE. In fact, he has packaged up and
pushed them to openSUSE:Contrib.
Nelson Marques, Fedora and openSUSE contributor, thinks
Ubuntu indicators are the bee’s knees. Actually, since Ubuntu is the dominant
distribution in his corner of the world he thinks using some of its more familiar elements
might help users migrate to openSUSE. He said, “We don’t want to make of openSUSE a
‘clone’ of Ubuntu, instead we want to make the openSUSE experience more close to what people
already use.” (…) Other Sources: ostatic
We have always been strong advocates of computer games. Rather than rotting the brain,
computer games are interactive, teach essential life skills, and can stimulate learning.
They also have been proven to enhance skills such as creativity, cooperation, teamplay, as
well as encouraging innovative and strategic thinking and improving hand-eye coordination.
Linux is not championed as a viable gaming platform in many communities, in part because
of its smaller user base and the relatively low number of commercially supported native
Linux games that are released each year. However, there are a number of encouraging
developments on this front. For example, the Unigine engine should enable developers to
produce high-quality 3D games with up-to-date visuals and advanced rendering. One title to
be released using this engine is OilRush. This eagerly awaited title fuses a classical real
time strategy with a Tower Wars genre.
Notwithstanding these developments, Linux has an ever-expanding library of tens of
thousands of free games, many of which are released under an open source license. A good
proportion of these titles are entertaining, highly addictive, offer captivating gameplay,
and are challenging. (…)
Ms. Carla Schroder shared a list of her “bestest distros” recently, so I
thought I might follow suit. She called hers “not-usual” and looking at her
list, I’d say my choices are probably a little more usual. In any case, here are my top
five favorite Linux distributions for 2010, in no real order.
SimplyMEPIS has always been one of my favorite distributions for several reasons.
SimplyMEPIS was one of the first to understand that looks do matter and so does out of
the box functionality. It includes proprietary drivers, codecs, and browser plugins
that make using Linux enjoyable. It leans toward the conservative side concerning new
version of its components, but that makes for an extremely stable operating system. In
all its years I only ran into one release that gave me any trouble, and that was about
three or four years ago – possibly when it went through its Ubuntu phase. It is truly
one of the best.
openSUSE has been one of my favorites since it first opened up to community
involvement in 2005. Novell’s agreement with Microsoft did damper my enthusiasm a
bit, but the distro itself remains one of the most polished and professional offerings
we have. It just has a commercial feel to it. Like SimplyMEPIS, I only encountered one
release that gave me any trouble. Otherwise, its been a slick and attractive distro. I
don’t run it full time mainly because I’d have to hunt up some one-clicks
(that are available for openSUSE) or install codecs and stuff myself to get going and
then worry about those updates. But it always remains high on my radar. I follow its
development very closely. I’m a little worried about what will become of it
despite assurances. But as long as it lives, so will my admiration. (…)
Different Linux distributions use their own tools for software, or more precisely,
package management. As an example, Ubuntu uses its Synaptic, Fedora uses Yum, Gentoo uses
Portage, and OpenSUSE uses YaST.
YaST stands for ‘Yet another Setup Tool’. YaST is an easy to use package management
system for Linux distributions that support rpm based packages. Although YaST features in
many commercial Linux distributions, it is free and open source software released under GPL.
Therefore, it is free to be used by any party interested.
YaST features many functionality the advanced package management tools offer. Let’s take
the appearance as an example. YaST offers the end users both a GUI front-end as well as CLI
front-end. The CLI front-end is especially useful for the installation done through networks
where everything is performed through a terminal or a command line interface. Due to this
support, the installation of OpenSUSE systems can be done over slow Internet connections and
while the X server is not present in the system (such as a server installation).
The past two weeks have been rough for users of the Yahoo-owned “social bookmarking”
service, Delicious. First, reports leaked out
that Yahoo was shutting the site down. Then the Delicious team fired back saying essentially don’t worry, all is
well — we’re simply getting sold off. That’s cold comfort if you use the service to manage
and tag a large collection of links, though. If you’re not comfortable with the uncertainty,
what better solution is there than installing your own open source replacement?
Running your own Web bookmarking application has two key advantages over a proprietary
commercial service. First, you can change and adapt the system to fit your way of working.
Don’t care about sharing your collection with the world at large? You can run a single-user
instance and keep your bookmarks private. Second, you can host it on your own server,
whether a small box in your closet at home, or on a co-located hosting plan — either way,
you’re in control.
There are several Web-based bookmarking applications suitable for running on a LAMP
server setup, but the option that most closely matches the Delicious service is Scuttle. It implements the
Delicious API, supports multiple user accounts, and even allows you to import your bookmark
collection from Delicious. Scuttle requires MySQL and PHP, and the most recent release is
version 0.8.0, from December 21st of 2010. That is recent enough that although some Linux
distributions provide builds through their package management systems, most will not have
caught up yet.
That means you’ll have to grab a source package from the
project’s Web site if you want to run the latest and greatest, but don’t let it frighten you
away. As a pure LAMP app, you don’t have to worry about compilation — the setup process is
straightforward. We’ll take a look at installing and configuring the basic Scuttle
application, then talk about some alternatives, including an interesting Scuttle derivative.
The development team behind ProFTPD has
released version 1.3.3d, which closes a critical security hole in the SQL module of all previous
versions. The flaw was reported
roughly a month ago in Phrack, the hacker magazine. A buffer overflow in the function
sql_prepare_where() allows attackers to remotely execute arbitrary code on the server. The
developers themselves suffered when this vulnerability was exploited by still unknown
parties, who entered the project server and installed a back door in the source code.
The new version also fixes a number of additional bugs; as a result, the GPL-licensed
server is reportedly now more stable. At the same time, the developers have also published
the first release candidate for version 1.3.4. (…)
This work is licensed under a Creative Commons Attribution-NonCommercial 2.5 License.
The Japanese have proven their techie prowess over the decades. Where would we be
without the transistor radio, the camcorder, or the Sony Walkman? But sometimes they jump
the technological shark with whimsical and weird gear, some of which is downright loopy.
Here are our favorite examples of oddball tech that could be made only in Japan.
We thank for this Issue:
Sascha Manns, Editor in Chief
Satoru Matsumoto, Editorial Office
Gertjan Lettink, Forums Section
Thomas Hofstätter, Eventeditor
Thomas Schraitle, DocBook-Consultant
Do you have comments on any of the things mentioned in this
article? Then head right over to the comment section and
let us know!
Or if you would like to be part of the openSUSE:Weekly news team then check out our team page
Or Communicate with or get help from the wider openSUSE community via IRC, forums, or
mailing lists see Communicate.
Visit our Facebook Fanpage: Fanpage
Since a few minutes you can use Bugzilla and
openFATE for give your Feedback.
You can subscribe to the openSUSE Weekly News RSS feed at news.opensuse.org.
Both comments and pings are currently closed.