This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.
To have your blog added to this aggregator, please read the instructions.
Note that you may use those keys with or without pressing the alt key.
|The brand new app scaffolding tool in our app store|
zypper in php5 php5-ctype php5-curl php5-dom php5-fileinfo php5-gd php5-iconv php5-json php5-ldap php5-mbstring php5-openssl php5-pdo php5-pear php5-posix php5-sqlite php5-tokenizer php5-xmlreader php5-xmlwriter php5-zip php5-zlib
apt-get install php5 php5-json php5-gd php5-sqlite curl libcurl3 libcurl3-dev php5-curl php5-common php-xml-parser php5-ldap bzip2
chmod 777the folder they are in, usually something like
php -S localhost:5000
It’s been about 3 months now since I switched over to Medium from Wordpress. Now that I have had a chance to experience it a bit I think I can provide a comparison between Medium and Wordpress.
Another development sprint is over. Time flies! In our previous post we already reported about the branching of Tumbleweed and the upcoming releases and about the expected consequences: the landing of some cool features in a less conservative Tumbleweed.
We are still dedicating quite some effort to polish the upcoming stable releases (SLE12-SP2 and Leap 42.2), but in this sprint we finally found some time to play. Which is great because blogging about new features is more fun than doing it about bug fixes.
When logging in via SSH, public key authentication should be preferred over password authentication. Until now, the best way of setting up the required authorized_keys files in AutoYaST was using the files section.
However, that approach is tedious and error prone, as you need to make sure you set the correct owner, permissions, etc. Moreover you need to keep in sync the user definition (username and home directory) with the file definition.
AutoYaST now supports the specification of a set of public keys for each user with a pretty straightforward syntax:
<user> <username>suse<username> <authorized_keys config:type="list"> <listentry>ssh-rsa your-public-key-1</listentry> <listentry>ssh-rsa your-public-key-2</listentry> <authorized_keys> <user>
AutoYaST takes care of writing the files and setting the ownership and the proper permissions.
While documenting this new feature we realized the AutoYaST documentation about users management could be more detailed, which leads us to…
Usually developers love to create programs loaded with cool features but hate to write documentation. Fortunately there are people out there who enjoy writing documentation and bringing all those features to light. We have already mentioned in previous reports how grateful we are for having the SUSE documentation team polishing and publishing our documentation drafts and how open and straightforward the process is.
We updated the YaST documentation to include information about the installer self-update feature, which will debut in SUSE Linux Enterprise 12 SP2 and openSUSE Leap 42.2. As part of the same pull request and in the AutoYaST side, some additional improvements were made, including cleaning-up some duplicated information about SUSE registration.
On the other hand and as a consequence of the above mentioned new feature, the AutoYaST documentation regarding users management has been rewritten adding missing information like groups, user defaults and login settings.
All our pull requests are already merged in the
doc-sle repository. At a later point in time, the SUSE documentation team will review and polish all the new content (including ours) and will publish an up-to-date version of the online documentation. If you don’t want to wait, you can easily generate an HTML or PDF version of the documentation including all the non-reviewed contributions just following the very simple instructions in the README file of the
Did we already mention we love the open source, programmer-friendly processes of the documentation team?
We promised news about the storage reimplementation and here they are. Our customized Tumbleweed …
Well if your like me and you have been sick of this Error: Failed to get gcc information. for awhile now when installing VMware Workstation on the major Linux distributions out there then you likely will want to automate the process of compiling it correctly and doing the rest of the tasks once your compile is complete.
Download my script here and run it after each time your kernel changes of course.
Let me know how your experience is with this or you would like to see some additions or adjustments.
Brian Krebs is a well-known and respected reporter who covers many different topics in the security industry, often involving data breaches and ATM skimmers. However, Krebs has always been unpopular among the financial and cyber criminals of the world given his uncanny ability to uncover the dirt on how they perform their criminal operations. He is also the author of the NYT Best Seller Spam Nation, a book detailing the operations of cyber criminals who use spam emails to make money as well as their wars with competing spammers. Check out this video below for a great talk by Krebs regarding his book.https://medium.com/media/ffb13a77b9656f35a8fe0a62ebfa6dd2/href
Over the past week, Kreb’s website, KrebsOnSecurity was under a remarkably severe DDoS attack. It is clearly a target attack from someone/some group that wants to shut down his website. Attacks at this scale have never really been seen before (read further below for details). As a result it’s important that the security industry develop some method to provide protection to journalists like Krebs against attacks that in the past would have been classified as a nation state capability.
If you are not familiar with the term, DDoS stands for Distributed Denial of Service attack. The idea behind the attack is simple, but to understand it you need to have a basic understanding of computer networks. This is a simplified explanation but it should get the following point across.
When two computers want to communicate on the internet, they send each other messages called “packets”. These packets contain all the information needed to allow communication between the two systems. When a computer receives a packet, it must allocate some CPU and network processing time to determine the contents of the packet. Normally the computer performs these tasks so fast that they are not noticed by the user.
When a website is hosted on a server, it needs to be able to respond to multiple visitors quickly and efficiently. As such, servers are given a very high ceiling in bandwidth so they can scale to a very large amount of requests. Think of bandwidth as a pipeline, the bigger it is the more data can flow from one end to the other, but ultimately there is a finite limit (the size of the pipe).
A DDoS attack preys on this property and attempts to fill, or use up, the server’s available bandwidth. When this happens, the server is unable to respond to legitimate visitors and the website ends up appearing as offline. These attacks can be devastating for websites because they are difficult to stop and can be launched simultaneously from all over the world. Often times, the senders of these DDoS attacks are compromised computers or smart devices which are being controlled from some centralized Command & Control infrastructure operated by …
Documentation for audio on Linux... is pretty much nonexistent.
Snapshot 20160921 made 3.22 available to user, but there were plenty of other snapshots during the week that brought new packages to Tumbleweed users.
Dominique Leuenberger, a member of the openSUSE release team, wrote that there were five snapshots this week in an email to developers on the openSUSE Factory Mailing List.
Even though Tumbleweed is built on GNU Composite Compiler 6.2.1, for user relying on GCC 5, snapshot 20160917 provided an update to GCC 5.4.1 and there was a major version update for Vim, which is the first major update for the project in a decade and updated from version 7.4.2045 to version 8.0.3.
Dear Tumbleweed users and hackers,
Another week comes to an end – and what a week this was for Tumbleweed! A full set of 5 snapshots (0914, 0916, 0917, 0920 and 0921) has been released, with some much anticipated and large changes:
And if all this was not enough yet, there are things already piling up in Staging and Testing areas:
The following few things moved to the backlog due to insufficient manpower to get resulting issues fixed:
With all those updates, don’t forget to still leave your desk once in a while – and in any case: have a lot of fun!
The highly anticipated release of Plasma 5.8 LTS will be the default desktop for openSUSE Leap 42.2 and its beta (5.7.95), which was just released last week, is in openSUSE’s newest beta release.
“The quality of the distribution at this point looks quite good,” said Ludwig Nussel, Leap’s release manager. “Since Plasma 5.8 is still a beta version, it deserves more attention and thorough testing. We can help upstream to release a good 5.8.0 and get a decent quality default desktop in return.”
KDE and openSUSE slightly adjusted release schedules to be able to include Plasma 5.8 in the release of openSUSE Leap 42.2 because Plasma 5.8 is an LTS and complement one another as well as appeal to conservative adapters.
The new Plasma Beta is only in English because of its beta status. Translations for 5.8 and several openSUSE specific components and infrastructure are needed before the final releases.
“If you want to help with your language, feel free to join the mailing list or contact your localization team,” Nussel said.
People who want to help with translations can help translate easily through Weblate, which manages translations in a git repository a respective project. All translated strings are tracked and stored. All people have to do it create an account and start translating in their browser if they would like to contribute to translations for Leap.
Other packages that had version upgrade in openSUSE’s latest beta are KDE Applications to version 16.08.0, Frameworks to version 5.26.0, GStreamer to version 1.8.3, gtk2 to 2.24.31, gtk3 to 3.20.9, json-glib to 1.2.2, Wireshark to 2.2.0 and Xen to version 4.7.0_12.
Testers of the Beta are encourage to submit bugs they find on openSUSE Bugzilla.
The release of the Beta 2 was delayed by one day, but the road map for the release of Leap 42.2 is still scheduled for Nov. 16, which is one week after SUSECon. The next beta, Beta 3, is scheduled for Oct. 6 and the submission deadline for it is Sept. 29. The Release Candidate is scheduled for Oct. 18.
Leap is a community-enterprise distribution that focuses on stability. Leap has hundreds of SUSE Linux Enterprise (SLE) Service Pack (SP) 2 packages and the thousands of community-built packages. The distribution gives developers and organizations an ability to bridge to the faster release cycles of openSUSE Tumbleweed or to a more Long Term Support enterprise solution with SLE.
Media who are interested in more information should contact Douglas DeMaio at email@example.com.
Full list of changes:
wlc is built on API introduced in Weblate 2.6 and still being in development. Several commands from wlc will not work properly if executed against Weblate 2.6, first fully supported version is 2.7 (it is now running on both demo and hosting servers). You can usage examples in the wlc documentation.
ownCloud is even more hiring. In my last post I wrote that we need PHP developers, a security engineer and a system administrator.
For all positions we got interesting inquiries already. That’s great, but should not hinder you from sending your CV in case you are still interested. We have multiple positions!
But there is even more opportunity: Additionally we are looking for an ownCloud Desktop Client developer. That would be somebody fluid in C++ and Qt who likes to pick up responsibility for our desktop client together with the other guys on the team. Shifted responsibilities have created this space, and it is your chance to
jump into the desktop sync topic which makes ownCloud really unique.
The role includes working with the team to plan and roll out releases, coordinate with the server- and mobile client colleagues, nail out future developments, engage with community hackers and help with difficult support cases. And last but not least there is hacking fun on remarkable nice Qt based C++ code of our desktop client, together with high profile C++ hackers to learn from.
It is an ideal opportunity for a carer type of personality, to whom it is not enough to sit in the basement and only hack, but also to talk to people, organize, and become visible. Having a Qt- and/or KDE background is a great benefit. You would work from where you feel comfortable with as ownCloud is a distributed company.
The ownCloud Client is a very successful part of the ownCloud platform, it has millions of installations out there, and is released under GPL.
If you want to do something that matters, here you are! Send your CV today and do not forget to mention your github account
Dear Tumbleweed users and hackers,
Last week, the list of things ‘in the makings’ was rather long – yet, I can happily announce that the four snapshots released this week (0909, 0911, 0912 and 0913) contain pretty much what was promised last week. That means no large, unforeseen issues came up which the maintainers did not already anticipate before submission. Great job everybody!
So, what DID we get in those 4 snapshots:
There has been some big item regarding KDE on last weeks announcement. This is currently in openQA and, unless something very weird is found, will be part of the upcoming snapshot 0914.
What else is being molded:
Those things will keep us all busy for the next couple days again
Our upcoming release, Plasma 5.8 will be the first long-term supported (LTS) release of the Plasma 5 series. One great thing of this release is that it aligns support time-frames across the whole stack from the desktop through Qt and underlying operating systems. This makes Plasma 5.8 very attractive for users need to that rely on the stability of their computers.
In the middle layer of the software stack, i.e. Qt, KDE Frameworks and Plasma, the support time-frames and conditions roughly look like this:
Qt 5.6 has been released in March as the first LTS release in the Qt 5 series. It comes with a 3-year long-term support guarantee, meaning it will receive patch releases providing bug fixes and security updates.
In tune with Plasma, during the recent Akademy we have decided to make KDE Frameworks, the libraries that underlie Plasma and many KDE applications 18 months of security support and fixes for major bugs, for example crashes. These updates will be shipped as needed for single frameworks and also appear as tags in the git repositories.
The core of our long-term support promise is that Plasma 5.8 will receive at least 18 months of bugfix and security support from upstream KDE. Patch releases with bugfix, security and translation updates will be shipped in fibonacci rhythm.
To make this LTS extra reliable, we’ve concentrated the (still ongoing) development cycle for Plasma 5.8 on stability, bugfixes, performance improvements and overall polish. We want this to shine.
There’s one caveat, however: Wayland support excluded from long-term-support promises, as it is too experimental. X11 as display server is fully supported, of course.
You can enjoy these LTS releases from the source through a Neon flavor that ships an updated LTS stack based on Ubuntu’s 16.04 LTS version. openSuse Leap, which focuses on stability and continuity also ships Plasma 5.8, making it a perfect match.
The Plasma team encourages other distros to do the same.
After the 5.8 release, and during its support cycle, KDE will continue to release feature updates for Plasma which are supported through the next development cycle as usual.
Lars Knoll’s Qt roadmap talk (skip to 29:25 if you’re impatient and want to miss an otherwise exciting talk) proposes another Qt LTS release around 2018, which may serve as a base for future planning in the same direction.
It definitely makes a lot of sense to align support time-frames for releases vertically across the stack. This makes support for distributions considerably easier, creates a clearer base for planning for users (both private and institutional) and effectively leads to less headaches in daily life.
Snapshots this week added new sensations for Tumbleweed users, but there were plenty of other updates in the repositories to get people excited.
While snapshot 20160907 added some subpackages to enhance PulseAudio and updated telepathy-qt5 to version 0.9.7, GStreamer fixed quite a few bugs in its update to version 1.8.3 to improve media processing. Wine’s 32-bit subpackage update in the snapshot, bringing it to version 1.9.18, added support for multiple kernel drivers in a single process.
Mesa’s update to version 12.0.2 in the 20160909 snapshot improved imagery as well as driver crashes. An update to doxygen 1.8.12, which helps generate documentation from annotated C sources, showed several bug fixes in its changelog and glibc updated to version 2.24 in the 20160909 snapshot.
Academic, researchers, and high-performance computer users will be happy to see a new version of openmpi in the snapshot, which provides several upstream bug fixes, improvements and documentation updates in version 1.10.3.
Systemd provided a small fix in snapshot 20160911 and Tumbleweed is now on the same upstream version of wayland-protocols with version 1.7. Gawk, the AWK programming language, which provides more recent Bell Laboratories awk extensions, and a number of GNU-specific extensions, updated to version 4.1.4 in the 20160911 snapshot.
GNOME 3.22 has yet to make it into a Tumbleweed snapshot. It has some new testing issues and is still working its way through staged testing.