Just a shot, Lugaru HD has been released as opensource, we can build and give it to all of you…
well.. done 😀
i just packaged it, so just wait for servers to sync
http://packman.links2linux.org/package/lugaru/
Have fun players
Just a shot, Lugaru HD has been released as opensource, we can build and give it to all of you…
well.. done 😀
i just packaged it, so just wait for servers to sync
http://packman.links2linux.org/package/lugaru/
Have fun players
Guest Blog
Greetings, and welcome!
-Starting this week’s news, The H Online have , since the 24th of March, a series of articles titled “What’s new in 2.6.34”. You can find it here: http://www.h-online.com/open/features/Linux-Kernel-2-6-34-tracking-962586.html
-Frederic Weisbecker posted perf fixes for 2.6.34, James Bottomley came up with SCSI fixes for -rc6, Paul E. McKenney had some RCU fixes for 2.6.35; perf fixes came also from Arnaldo Carvalho de Melo.
-Christoph Hellwig posted a XFS status update for April 2010; we will paste his report here in its’ entirety to let you get a clear picture : “In April 2.6.34 still was in the release candidate phase, with a hand full of XFS fixes making it into mainline. Development for the 2.6.35 merge window went ahead full steam at the same time.
While a fair amount of patches hit the development tree these were largely cleanups, with the real development activity happening on the mailing list. There was another round of patches and following discussion on the scalable busy extent tracking and delayed logging features mentioned last month. They are expected to be merged in May and queue up for the Linux 2.6.35 window. Last but not least April saw a large number of XFS fixes backported to the 2.6.32 and 2.6.33 -stable series.
In user land xfsprogs has seen few but important updates, preparing for a new release next month. The xfs_repair tool saw a fix to correctly enable the lazy superblock counters on an existing filesystem, and xfs_fsr saw updates to better deal with dynamic attribute forks. Last but not a least a port to Debian GNU/kFreeBSD9 got merged. The xfstests test suite saw two new test cases and various smaller fixes.”
-As usual, Rafael J. Wisocki announced the series of reported regressions from 2.6.33 (referring to 2.6.34-rc6-git6).
-No doubt, the most important news of this week is Linus’ announcement of 2.6.34-rc7 : “I think this is the last -rc – things have been pretty quiet on the patch front, although there’s been some rather spirited discussions.Random fixes all around, some of them RCU related (people fixing various RCU sanity check warnings), but most of them just random driver fixes. And there’s some MIPS, microblaze and ARM updates, and ocfs2 and ceph fixes. The shortlog is about as informative as anything else – nothing there stands out in my mind, it’s just a lot of small random stuff.”
-OpenSUSE’s Jiri Kosina posted HID fixes, while H. Peter Anvin posted a RFC regarding virtualization – the hypervisor layer pertaining Hyper-V and VMware code cleanups.
-Robert Richter came up with oprofile hotplug fixes for x86, sound fixes came from Takashi Iwai, perf from Arnaldo Carvalho de Melo, wireless by John W. Linville, drm fixes by Dave Airlie and networking fixes by David Miller.
-The H Online features another interesting kernel log; you can read it, along with its interesting links, here http://www.h-online.com/open/features/Kernel-Log-New-stable-kernels-and-drivers-995820.html .
-Paul McKenney posted fixes for the RCU tree (for 2.6.35, rebased for -rc7), hwmon fixes appeared courtesy of Jean Delvare, some new perf fixes by Ingo Molnar and later by Arnaldo Carvalho de Melo, tracing by Steven Rostedt, AMD iommu by Joerg Roedel, patches for the s390 series for -rc7 by Martin Schwidefsky and some perf_event fixes for powerpc by Benjamin Herrenschmidt.
-Greg Kroah-Hartman posted the “start of the stable review cycle for the 2.6.32.13 release”, stating that “There are 98 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let us know. If anyone is a maintainer of the proper subsystem, and wants to add a Signed-off-by: line to the patch, please respond with it.”
-The same Greg started the review process for 2.6.33.4, with the same message to anyone involved/interested.
-Pierre Tardy informed the community about PyTimechart by posting a RFC : “PyTimechart is another implementation of two very useful tools available for the linux community: perf-timechart ( http://blog.fenrus.org/?p=5 ) and bootchart (http://www.bootchart.org/ ) The two tools share a common idea of making their output to SVG files. While it is a very good idea for small traces, the generated SVG can be very heavy, and turns out to be good stress tests for inkscape developers…
PyTimechart is a tool that parses ftrace text traces, and display them with the help of a very powerful dynamic plot framework, Chaco (http://code.enthought.com/chaco/ ) The GUI makes the best it can to ease the browsing of huge traces.”
All in all, the respondents to this mail seemed to welcome the application as being useful.
-In the latest fixes/patches/pull requests section, we have Paul E McKenny with an RCU lockdep splat fix, Sage Weil with ceph fixes for 2.6.34-final, Frederic Weisbecker has perf/nmi fixes (uniform lockup detector), Takashi Iwai with some sound fixes; Samuel Ortiz has some MFD fixes and Steve French came up with some minor cifs fixes.
-Greg Kroah-Hartman of OpenSUSE made the announcement of the release of kernels 2.6.32.13 and 2.6.33.4 .
-Marcello Tosatti announced a series of fixes for the kvm targetting 2.6.34-rc7, Greg Kroah-Hartman posted patches for the -git kernel regarding TTY, Steven Rostedt had some tracing updates, perf fixes by Arnaldo Carvalho de Melo were posted too, and Dmitry Korokhov has fixes for the input tree.
-Mathieu Desnoyers announced the release of LTTng 0.213, with various bugfixes and improvements.
-As usual, at least lately, Michal Simek has some patches/fixes for arch/microblaze, this time for -rc8.
-Michael S. Tsirkin posted “a last minute vhost-net fix” which fixes barrier pairing.
Well, that’s it for this week’s OpenSUSE-flavoured kernel news!
I’m off, enjoy the weekend!
We all know we are doing well, we see that from your feedbacks, bugreports, obs submitreqs, and IRC. So guys.. Thank you a lot for supporting and helping us.
But do you think there is something better to see your work on a magazine? a national magazine? I guess it’s really exciting isn’t it?
Well we did it! The Italian Linux Magazine wrote two entire pages for us, and our live cd (together with XFCE one) was into the attached DVD or CD!
That was cool!!!
Andrea
Have you ever thought how users should configure their systems, deployed by AutoYaST or kiwi? One of possible answers is called YaST Firstboot.
The YaST firstboot utility is a special kind of configuration workflow that can be run after the basic system is installed. It is started on the first boot of the system and guides a user through a series of steps that allow for easier configuration of their desktops. YaST firstboot does not run by default and has to be configured to run by the user or the system administrator. It is useful for image deployments where the system in the image is already configured (read: AutoYaST, SUSE_Studio, KIWI), and end-user should do only the last few steps, like setting the root password.
To enable running firstboot configuration sequence on the machine, it is necessary to:
There are two files that control the behavior of Firstboot: the firstboot control file (firstboot.xml) and the sysconfig file /etc/sysconfig/firstboot. The control file defines the steps that should be part of your configuration sequence, in the sysconfig file it is possible to define custom messages and paths to various files.
Most important texts configurable in sysconfig file is the text shown in the License Agreement screens. For license texts, there are sysconfig variables FIRSTBOOT_LICENSE_DIR and FIRSTBOOT_NOVELL_LICENSE_DIR.
The license text is read from the file ‘license.txt’ or from ‘license_<locale>.txt’. The license texts of the Novell base product are by default installed to the directory /etc/YaST2/licenses/base/ — you can set different value to FIRSTBOOT_NOVELL_LICENSE_DIR if they are elsewhere. Use FIRSTBOOT_LICENSE_DIR to indicate a path to directory containing vendor licence texts; it is preferred to put these license texts into another subdirectory of /etc/YaST2/licenses/.
To show two license texts in one dialog (typically the one from vendor and one from Novell), use ‘firstboot_license_novell’ step in your firstboot.xml file. This client will use the license texts specified by both FIRSTBOOT_LICENSE_DIR and FIRSTBOOT_NOVELL_LICENSE_DIR.
The default firstboot workflow can be controled using one single file which uses the same syntax as the control.xml file used to control the complete installation. The firstboot control file consists of workflow and proposal configurations and can be used to add or remove configuration screens depending on the end configuration of the system. The file firstboot.xml is installed with the yast2-firstboot package and can be found at the following location: /etc/YaST2/firstboot.xml.
This file can be modified to match the post installation requirements of the product in question. In addition to the default and pre-installed components, custom screens can be added to enable maximal flexiblity during post installation. Look into the example firstboot.xml file coming with your yast2-firstboot package for more available steps.
Not everything can be achieved with already prepared steps, and it is usually not necessary to write your own ycp dialogs.
You can add schell scripts to be executed at the end of the firstboot configuration. Scripts should be placed in /usr/share/firstboot/scripts or in a custom location that can be set using the variable SCRIPT_DIR of /etc/sysconfig/firstboot configuration file. The scripts are executed in alphabetical order of their names.
It is possible to configure the firstboot process as a part of autoinstallation, so the system can be installed with most of the default values set via AutoYaST profile, leaving the rest to the end user during the firstboot sequence.
As a part of autoinstallation configuration, you need to provide all the changes mentioned above:
<firstboot> <firstboot_enabled config:type="boolean">true</firstboot_enabled> </firstboot>
to your AutoYaST profile.
This is the shortened version of the article published at http://en.opensuse.org/YaST_Firstboot
During the last week blogs, twitter, facebook and other means of communication for the users experienced a lot of traffic related to the Humble Indie Bundle. This bundle was nothing more than a package composed of 6 DRM-Free games developed by 6 Independent game developers that could be obtained at a price set by the user. This bundle included the games World of Goo, Aquaria, Gish, Lugaru HD, Penumbra Overture and Samorost 2. The bundle was available for one week and the earnings went to the developers, The Child’s Play Charity and Electronic Frontier Foundation depending on the will of the buyer. At the end of the week the bundle reached 1’000.000 US$ of income, reason for which Aquaria, Gish, Lugaru HD and Penumbra Overture are releasing their code under FLOSS licenses. As you can see here was already released under GPL2, and the other games source code is being prepared to be released within this week.
In addition to this, it was officially announced that Steam will be available for Linux at the end of this summer, which means lots of games and lots of fun is coming to gnu/linux and the breach in gaming between gnu/linux and other OSs is getting smaller.
Here some trailers of the games that will be released as FLOSS from the Humble Indie Bundle
Aquaria | Gish | Lugaru HD | Penumbra Overture
Linux gamers it is time to have even more fun
jaom7
Hello, and welcome. Here goes :
-This first one is hot after the closing of the last weeks’ edition, courtesy of LWN.net (I had not access to vger.kernel.org because of their downtime) : Linus Torvalds announced 2.6.34-rc6 (http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc6) and here is the link from LWN : http://lwn.net/Articles/385535/rss
-On the fixes side, we begin with Trond Myklebust’s NFS client bugfixes , and continue with a small fix from Jens Axboe regarding the block tree; in related news, other fixes are : xfs (Alex Elder), kgdb for -rc5 (Alex Elder), perf (Arnaldo Carvalho de Melo), spi/gpio (Grant Likely), USB for -rc4-git (Greg Kroah-Hartman), who also sent fixes for the tty and staging trees.
-Stefan Bader announced linux-2.6.32.y-drm33.z with the following comment : “As many of us now have a distribution which is based on a 2.6.32 kernel but are forced to update DRM to the version in 2.6.33 to obtain good graphics experience. In support of this I went ahead and created a tree on kernel.org[1] which brings together the two and which I will maintain following the upstream stable trees from Greg. This hopefully will not only be beneficial to us but also to all that are in the need of running this combination of code.”
-Tim Gardner of Canonical proposed some of the updates to the r8169 driver should be merged into stable; Francois Romieu agreed, so we’ll see these fixes in .32 and .33 stable versions.
-Darrick j. Wong posted a RFC in regard of the ext4 tree with the following intro-duction : “Hmm. A while ago I was complaining that an evil program that calls fsync() in a loop will send a continuous stream of write barriers to the hard disk. Ted theorized that it might be possible to set a flag in ext4_writepage and clear it in ext4_sync_file; if we happen to enter ext4_sync_file and the flag isn’t set (meaning that nothing has been dirtied since the last fsync()) then we could skip issuing the barrier. Here’s an experimental patch to do something sort of like that. From a quick run with blktrace, it seems to skip the redundant barriers and improves the ffsb mail server scores. However, I haven’t done extensive power failure testing to see how much data it can destroy. For that matter I’m not even 100% sure it’s correct at what it aims to do.”
-John W. Linville asked Dave Miller to pull some of his fixes applied to the wireless-2.6 tree (30.04.2010).
-Linux Weekly’s editor-in-chief, Jonathan Corbet, RFC’d some fixes for the viafb tree (OLPC).
-Paul E. McKenney announced fixes for the RCU tree in .34 and changes for .35, Frederic Weisbecker sent Ingo Molnar and the list some new fixes for perf, lockdep and hw-breakpoints, Michael S. Tsirkin came up with vhost-net improvements, just like Sage Weil, who posted ceph fixes for -rc7; other fixes include lockdep, RCU, i2c, tracing and core.
-Joel Becker wrote fixes for the ocfs tree, while H. Peter Anvin posted x86 fixes for -rc7, including David Howell’s rwsem patch.
-Another series of small fixes for the drm and gpu trees by Dave Airlie were posted, as well as other fixes for the following trees/components : input by Dmitry Torokhov, sound by Takashi Iwai, networking by David Miller, wq (workqueue) by Tejun Heo and perf by Arnaldo Carvalho de Melo.
-Pankaj Thakkar of Vmware posted a RFC in regard of NPA for vmxnet3, with the following words : “Device passthrough technology allows a guest to bypass the hypervisor and drive the underlying physical device. VMware has been exploring various ways to deliver this technology to users in a manner which is easy to adopt. In this process we have prepared an architecture along with Intel – NPA (Network Plugin Architecture). NPA allows the guest to use the virtualized NIC vmxnet3 to passthrough to a number of physical NICs which support it. The document below provides an overview of NPA. We intend to upgrade the upstreamed vmxnet3 driver to implement NPA so that Linux users can exploit the benefits provided by passthrough devices in a seamless manner while retaining the benefits of virtualization. The document
below tries to answer most of the questions which we anticipated. Please let us know your comments and queries.”
-On opensuse-kernel@ Larry Finger patched the script allowing the downloading of firmware for b43 (Broadcom).
-Another series of fixes were posted as follows : SLAB for -rc7 by Pekka J. Enberg, libata and zerolen (misc) by Jeff Garzik, RCU for 2.6.34 by Paul E. McKenney, sh by Paul MUndt, arch/microblaze by Michal Simek, oprofile by Robert Richter, RCU, this time by Ingo Molnar, vrl/dvb by Mauro Carvalho Chehab, nfs client fixes by Trond Myklebust, sched/core by Tejun Heo, drm by Dave Airlie, ACPI for -rc6 by Len Brown, perf and tracing by Steven Rostedt, block for 2.6.34 by Jens Axboe, PCMCIA by Dominic Brodowski and md for 2.6.34 by Neil Brown.
-Soeren Sandmann announced the release of Sysprof 1.1.6 with the following words : “Sysprof 1.1.6 is now available. This is a development release leading up to a stable 1.2.0 release. Sysprof is a sampling system-wide CPU profiler for Linux. This version is based on the perf counter interface in 2.6.31 kernels and will not work with earlier kernels.”
-Mikulas Patocka asked for testers in the matter of performance degradation in the Maxtor Atlas 15K2 SCSI disks, due to buggy firmware, posting a script that limits the request size to 256k, since the degradation appears when requests exceed this 256k boundary
That’s all, folks! If you’re in Europe, have a rainless weekend, and may all
of you have a fantastic weekend!
Universidad de Panamá, Facultad de Informática, Electrónica y Comunicación. Conmemoración del X aniversario de la Facultad. On May 3, 2010 the openSUSE Ambassador was invited to talk about “Introducción a las características y ventajas de openSUSE, su relación con NOVELL y la comunidad de usuarios” (“An Introduction to New Features and Advantages on openSUSE 11.2, the openSUSE Project Community and the relationship with NOVELL”). When I did talk about openSUSE. People came from a few persons in the room to suddenly filling the whole space available for that room. Surprisingly, I had the opportunity to watch several girls between the audience so I thought there is a chance to organize a chix open source community or users group. Click on the link to watch photos
FLISoL 2010 at Ciudad del Saber looked good with several Linux Distributions and different open source applications. It was a small building with a lot people in transit. With three people and only two months to organize this event it was a successful achievement because our goal was accomplished: be on the eyes of governmental organizations, ONG, business, academics, students, users, professionals. Some media communications groups give some interviews. After this event we are receiving more invitations to give a talks for education and participate on some projects than ever before. Click on link below to watch the photos
Universidad Interamericana de Panamá on March 25, 2010 was the scenario for an opensource and Linux party. Several Linux Distros like Ubuntu, CAELinux, Fedora, Gentoo, Debian, openSUSE and organizations like CIDETYS and business like ELCONIX did make presence and their users and members gave a Talk for students, academics, users and professionals. Those Talks were transmited simultaneously by video streaming to the Laureate Universities Network to promote opensource software contributions, trainings, certifications and community participation, job opportunities. Click on to watch photos
http://picasaweb.google.com/RICARDO.A.CHUNG/UIP_250310#
This event did open a collaboration between communities , enterprises and Universidad Interamericana de Panama to promote open source and Linux certifications and Linux diplomados.
All open source communities ambassadors will organize their groups looking to keep their members up to date with knowledge.
Some CAPATEC (Cámara Panameña de Tecnología) members, like ELCONIX, has showed higher intention to support some Open Source communities sponsoring education, certification, and some events like FLISoL and Freedom Software Day.
Mirtha Rodriguez, UIP, Systems Engineering Faculty Dean, did give us a great liaison and invited us to keep working with their students at UIP for future events.
A little more than two weeks ago we released Kraft version 0.40, the first version of Kraft based on KDE 4 software platform. The release went fine as far as I can tell, no terrible bugs were reported yet. Some work went into the new website since then, but in general I need a few weeks break from Kraft and spend my evenings outside enjoying spring time.
Today, Sourceforge posted a blog about Kraft after they kind of mail-interviewed me. It’s nice, it really focuses on the things also important to me. This might be another step towards a broader user base for Kraft. I say that because one could have the impression that the number of people actually really using Kraft could be larger. A high number of users is one of the fundamental criteria for a successful free software project and thus I am constantly trying to understand whats the reason for the impression or the fact.
The first idea is that the Kraft project simply does something wrong in the way a project should be driven. But there are releases, there is a so far ok website, there are communication channels with information on it and people answering questions. Of course, it always could be done better, but I hope and believe we are not doing too bad. Marketing could be more, that’s granted.
The next thing could be that nobody needs this kind of software. But there are quite some companies doing this kind of software in the commercial space. So there must be a market. Actually I think the market is huge. People are writing invoices all over the world and I bet many of them are not really satisfied with the way they do it usually which makes Kraft at least an option to try for them.
And this might lead to better path: Probably these people do not know that the option exists. They simply haven’t heard about Kraft yet and if they would there is a good chance that they would not believe that it is free etc pp. And this is probably not specific to Kraft but also applies, of course much more weaker, to larger projects like openSUSE or KDE: A lot of people from the ‘real world’ don’t know about free software communities, the ideas behind and the benefits for users of the software. That sounds strange to us, as this is our daily reality, but start with asking your parents or non computer related friends if they really understand what it is about. Imagine what people know who have no computer job nor -hobby nor know you!
What consequences can that have for us? Well, we could decide to skip this group of people. That would mean, beside some other effects, that Kraft would not make sense any more and I don’t like that. It probably should influence the way we see the ‘product management’ aspect of our projects. For me, ‘product management’ is often equivalent to “take care that the result is especially useful to non computer scientists” (which is probably not what PM really is about) and the focus on that is very important and the precondition for the next point.
We might have to take our projects even more out of the geek niche and go to places where the ‘real world’ happens. That is difficult for various reasons. First, it means that we have to start to explain again from start, and maybe also get questions where the answer is not obvious. Furthermore it might have practical issues, because for example fairs for handcrafter utilities charge seriously for software boothes which is not the case if we present projects on FOSS events.
On the other hand its easy because we all just have to spread the word even more and tell everybody about free software, our projects and free culture. And try to think as if we weren’t free software people. I know, most of us do already what they can and that’s great 🙂