Posts Tagged ‘linux’

DistroWatch Weekly, Issue 438

This week in DistroWatch Weekly: Reviews: First look at VectorLinux 7.0 News: Mandriva in bankruptcy threat, latest on Ubuntu-powered devices, CentOS on CR repository Sneak Peeks: The Razor-qt desktop environment Released last week: Gentoo Linux 12.0, Porteus 1.1, FreeNAS 8.0.3 Upcoming releases: FreeBSD 9.0, PC-BSD 9.0, Linux Mint….

Distribution Release: Webconverger 11.0

Kai Hendry has announced the release of Webconverger 11.0, a web browser-only specialist distribution for Internet kiosks. The new version comes with updated Linux kernel version 3.1.8, Firefox 9.0.1, and several minor security-related tweaks. From the release notes: “I’m very proud to announce Webconverger 11, with the following….

Development Release: DEFT Linux 7 RC1

Stefano Fratepietro has announced the availability of the first release candidate for DEFT Linux 7, a specialist Ubuntu-based live DVD for digital forensics and penetration testing: “Finally we were able to realize a very stable DEFT Linux 7 release, solving all problems responsible for postponing the release date….

Development Release: Frugalware Linux 1.6 RC1

Miklós Vajna has announced the availability of the first of the two planned release candidates for Frugalware Linux 1.6, a general-purpose distribution for desktops and servers designed with intermediate Linux users in mind: “Frugalware 1.6rc1 (Fermus) released. The Frugalware developer team is pleased to announce the immediate availability….

DistroWatch Weekly, Issue 439

This week in DistroWatch Weekly: Reviews: First look at Kororaa Linux 16 News: FreeBSD 9.0 update, testing Unity 5.0, new features in Fedora 17, interviews with Debian’s Steve McIntyre and openSUSE’s Frédéric Crozat, Linux Mint overview Questions and answers: SOPA and open-source software Released last week: FreeBSD 9.0,….

Distribution Release: ExTiX 9

Arne Exton has announced the release of ExTiX 9, an Ubuntu-based desktop distribution for 64-bit computers with GNOME Shell and Razor-qt as the available desktop environments and the latest stable Linux kernel: “ExTiX 9 x64 is a remastered build of Ubuntu 11.10. The original system includes the Unity….

DistroWatch Weekly, Issue 437

This week in DistroWatch Weekly: Reviews: An enlightening experience – Bodhi Linux 1.3.0 News: Bodhi release plans, Deepin Software Centre, Linux Mint’s Cinnamon, Pardus “restructuring”, end of LinEx, SELinux tips, overview of Clonezilla Statistics: Page Hit Ranking in 2010 and 2011 Questions and answers: Creating ISO images Released….

Distribution Release: BackBox Linux 2.01

Raffaele Forte has announced the release of BackBox Linux 2.01, an Ubuntu-based distribution and live DVD tailored to penetration testing and security assessment tasks: “The BackBox team is proud to announce the release 2.01 of BackBox Linux.The new release includes features such as Ubuntu 11.04, Linux Kernel 2.6.38….

My 5 Favorite New Intel® Software Development Product Features of 2011

It’s been a big year for us in the Intel Developer Products Division. We released Intel® Cluster Studio XE and Intel® Parallel Studio XE Service Pack 1 . We continued to plan and design our products to provide support for the compute continuum. And of course we worked to grow our community of developers. Throughout the year there have been several new features and developments in some of my favorite products – below I list my personal top 5 and tell you why. This list is of course heavily biased by my particular area of expertise (performance) and is by no means a complete list of all the new products or features that went into Intel® Software Development products in 2011! So, without further ado, my favorites: 5. Intel® Cilk Plus open source port to GCC – Intel® Cilk Plus was announced in 2010, and an open source specification has been out since late 2010 as well. However this year we began, along with the open source community, to port Cilk Plus to GCC. Some of the first items ported were the parallelism keywords, which is significant to me because it makes our Cilk Plus parallelism model available to a greater audience. 4. Intel® VTune™ Amplifier XE and Intel® Inspector XE MPI Support – In the new Cluster Studio XE product, VTune Amplifier XE and Inspector XE are now MPI-enabled. This is important because we are beginning to see more hybrid programming in the HPC and cluster world – which means the applications use a combination of MPI and another threading model (such as OpenMP, Cilk Plus, or Intel® Threading Building Blocks ). We have an existing product, Intel® Trace Analyzer and Collector , that analyzes MPI efficiency for a cluster app, but analyzing performance of an individual process running on an MPI rank was more difficult. Now we make it easier to use VTune Amplifier XE or Inspector XE to analyze the threading model used within a rank, which helps us support more cluster customers. 3. Intel® Threading Building Blocks Flow Graph – I was introduced to flow graph this year, when I worked with my colleague Victoria Gromova to create some TBB labs for Intel Developer Forum. Victoria wanted to highlight flow graph as one of the new features of TBB 4.0 . Flow graph is a new construct that supports many more types of control algorithms, like dependency graphs, event-based models or reactive-based flows. In short, it opens up TBB to more customers while maintaining or improving the TBB performance we have come to expect. 2. VTune Amplifier XE attach to running process on Linux* – This is a great example of our development team responding to customer feedback. Being able to analyze a running process for a defined period of time (instead of launching it) has been requested by many of our clients. We first got this implemented on Windows*, then this September provided the feature for Linux* in Intel® Parallel Studio XE Service Pack 1 . I have already been visiting some users who requested this and it is great to be able to share that the feature they have been asking for is here! 1. VTune Amplifier XE interface for Intel® Microarchitecture Codename Sandy Bridge – For readers of my blog this one should not be a surprise! I have created quite a bit of training material on these new Sandy Bridge features. We now provide an analysis type for Sandy Bridge that helps users easily identify the most common software performance issues at the microarchitectural level, and it includes pre-coded metrics, thresholds, and issue highlighting for usability. This is my favorite new feature because, even though I am not a developer, I got to help a little with making this interface by helping define some performance metrics and thresholds and validating them on workloads. It is very cool to see my contributions in the product. There you have it! I hope you have a chance to try out some of our new product features now or in the coming year. Let us know your favorites, or your requests.

Why Maintenance Releases Matter

I’m cross-posting this from my blog on the Yocto Project web site . Please go there to learn more about embedded Linux and the work we’re doing in the Yocto Project to make it easier for you to develop embedded devices. As the calendar year winds down, I find myself tapping away at the keyboard at my sister’s house in Denver, Colorado in a snowstorm. I just spent the morning digging out our rental car and shoveling my sister’s driveway and her next-door neighbors. It is a time like this to reflect and, yes, to remember that one of the reasons I moved to Portland, Oregon was to escape the snow! This has been a busy month in the Yocto Project, with all kinds of activity jumping along: We launched a maintenance release 1.0, dubbing it Yocto Project v1.0.2. Our 1.0 release was last April, but we try to provide update support for at least a year after release. This release includes security patches as promised and some fixes to make sure the build works with more recent Linux distributions. We’re also working on a maintenance release for 1.1, which came out last October. Nobody should ever fear that compatability has been broken in a maintenance release. My mental rule of thumb after a few decades in the software game is that you should have no more than 10 – 12 bug fixes in a maintenance release, which also constrains the amount of QA you need to do. 1.1.1 though will have a few more changes in place because we want to address some issues raised by Matthew at FreeScale and to make sure that the release meets their needs. More on this later. Our development, QA and release engineers also produced the first milestone from our 1.2 release, due this coming April. We produce these milestone releases every 6 weeks or so. Our idea is to constrain the length of time that the development window is open to make sure we can freeze, stabilize and run a full QA sweep. Then we provide these little milestone releases to you so that you can have some demonstratable features to use in a somewhat more stable form. At least, it should be more stable than developing on the Master branch! As I wrote this, we decided to go ahead and release the M1 milestone. It may seem like we’re putting an inordinate effort into producing these maintenance releases. In fact, we had hoped to have 1.1.1 out in December, but putting three releases out in one month was just too much for our release engine to handle. Why make the effort to do maintenance releases? Here’s the way I think about it: The Yocto Project is an open source project, not a software product. So we’re not supporting our releases for years and years. We’re looking for our friends at Mentor Graphics, Montavista, Timesys, Wind River and others to produce software products which use Yocto as the upstream. On the other hand, by providing these additional stable releases, it shows that we care about the developers who base their products on the Yocto Project. We know not every product development cycle perfectly aligns with the every six month Yocto Project cycle. Having these maintenance releases helps to support them. As I mentioned, we try to keep these releases as stable as possible, just fixing critical bugs or security patches from upstream. So we think these maintenance releases matter, to demonstrate that we care about you the developer who uses the Yocto Project to make the magic happen on your devices. By the way, I’d like to offer a shout out to Joshua Lock, who has been spearheading the development side of these maintenance releases, Beth Flanagan for release engineering work, Jiajun and the project-wide QA team. And also to Paul Eggleton for reminding us to get the 1.0.2 maintenance release on the schedule.