Copr is an easy build service for Fedora which can make you your own repo very easily. I have been contributing to this project since March 2014 and this month has been the best in terms of new features: you can track your builds much better, it is bit easier to use and also got much faster in some cases.
This is a simple story about a logo design process for an open source project in case it might be informative or entertaining to you.
A little over a month ago, Tomas Redej contacted me to request a logo for DevAssistant. DevAssistant is a UI aimed at making developers’ lives easier by automating a lot of the menial tasks required to start up a software project – setting up the environment, starting services, installing dependencise, etc. His team was gearing up for a new release and really wanted a logo to help publicize the release. They came to me for help as colleagues familiar with some of the logo work I’ve done.
Is the default image viewer in your desktop environment just not working the way you want? need more features (or maybe something simpler) from an image viewer? Well, you are in luck, as there is no shortage of choices when looking at alternative image viewers in Fedora. This article covers 15 image viewers in Fedora.
Typically, an image viewer does one thing — shows you the images in a directory (sometimes in a thumbnail view), and lets you quickly flip through them. Some image viewers also allow you do simple edits of an image, and will also show you some added details of your pictures (like metadata, and color histograms).
Beginning in 2011, Red Hat began providing assistance to the fledgling Fedora ARM distribution. I was Red Hat’s project manager for this initiative. Back then it was a humble secondary architecture under the stewardship of Seneca College. Seneca was working on an OS distribution for the Raspberry Pi, a promising educational tool. Red Hat partnered with Seneca, provided resources to advance development and helped build a community, the open source way. Though Linux had been used on ARM for many years, kernel ports tended to exist in different source trees. Likewise, many userspace packages had been written without multi-core, thread-safe ARM code, so there was a lot of work to be done.
The Anaconda OS installer used by Fedora, RHEL and their derivatives have been many times criticized for its memory requirements being bigger than memory requirements of the installed OS. Maybe a big surprise for users who don’t see too deep into the issue, no surprise for people who really understand what’s going on in the OS installation and how it all works. The basic truth (some call it an issue) about OS installation is that the installer cannot write to physical storage of the machine before user tells it to do so. However, since the OS installation is quite a complex process and since it has to be based on the components from the OS itself there are many things that have to be stored somewhere for the installer to work. The only space for data that for sure doesn’t contain any data the installer shouldn’t overwrite or leave some garbage in is RAM.
In aiming towards an on-time release of Fedora 21, developers have spun the first test candidate for the upcoming development release.
Per the official release schedule, Fedora 21 is expected to see its alpha release on 5 August while next week (22 July) is the software string freeze and the alpha change deadline. Following that alpha release is a planned Fedora 21 Beta on 9 September, final change deadline on 30 September, and hopes to ship Fedora 21 final on 14 October.
0.5.4 has been released today.
A major improvement in this release is the repo priorities config option. With it the admin can enforce packages of a certain repository to take precedence over other ones during an upgrade even when the prioritized packages have lower version. The original DNF bug is here, the functionality is known from Yum Utils as “priority plugin”.
The second Alpha version of Scientific Linux 7.0, a recompiled Red Hat Enterprise Linux put together by various labs and universities around the world, is now available for download and testing.
The developers of Scientific Linux 7.0 have moved very fast and, just a week after the first Release Candidate, a new development release has been made available. Given the short development period since the first Alpha, it's actually surprising that the devs managed to get all those changes and improvements in.
“Fermilab's intention is to continue the development and support of Scientific Linux and refine its focus as an operating system for scientific computing. Today we are announcing an alpha release of Scientific Linux 7. We continue to develop a stable process for generating and distributing Scientific Linux, with the intent that Scientific Linux remains the same high quality operating system the community has come to expect.”
The CentOS 7 Linux operating system became generally available July 7, providing users with a freely available desktop, server and cloud operating system platform. CentOS, an acronym for Community Enterprise Operating System, is based on the Red Hat Enterprise Linux (RHEL) 7 enterprise OS, released June 10. Unlike RHEL 7, which is a commercially supported enterprise Linux release that requires users to have a paid subscription, CentOS is free. That said, CentOS lacks the support, services and certifications that Red Hat provides its RHEL subscribers. CentOS does, however, provide the same basic technologies as RHEL 7, but for those who don't need or want the additional enterprise-grade commercial services, CentOS is a free alternative. Red Hat is now an official support and partner of the CentOS community, as well, ever since a surprise announcement in January. CentOS inherits the same XFS file system used in RHEL 7, which provides a file system that can scale up to 500 terabytes. Docker container virtualization support is also part of the CentOS 7 platform. In this slide show, eWEEK examines the CentOS 7 Linux operating system.
A few weeks ago, I covered the news that Google had released Kubernetes under an open-source license, which is software to manage computing workloads across thousands of computer servers and leverage docker containers. We've also covered Google's announcement that some vey big contributors have joined the Kubernetes project, including IBM, Microsoft, Red Hat, Docker, CoreOS, Mesosphere, and SaltStack. They are working in tandem on open source tools and container technologies that can run on multiple computers and networks.
RedHat Enterprise Linux is an enterprise-grade Linux distribution, which is frequently used in corporate data centers as an operating system for NAS storage devices. From the performance point of view, the new Linux kernel and the new default file system may have a significant impact on a NAS storage device and therefore it is very important to understand how the newly released RedHat Enterprise Linux version 7.0 compares to the last stable version 6.5.
In this article just for putting the initial CentOS/SL results into some perspective, I have some initial data from a single Intel Core i7 system running these new releases plus Fedora and Ubuntu Linux. Just as some initial metrics to get started with our benchmarking, from an Intel Core i7 4770K system with 8GB of RAM, 150GB Western Digital VelociRaptor HDD, and Intel HD Graphics 4600, I tested the four Linux distributions. The hardware and its settings were maintained the same during testing.
Originally for this first article I also hoped to test Scientific Linux / CentOS 6.5 too, but after doing the 7.0 tests and trying to boot the 6.5 releases, there was a kernel error preventing the testing from being realized (on initial boot was the i915 DRM error about detecting more than eight display outputs; when booting without DRM/KMS mode-setting support, there would be an agpgart error.) The i915 issue is corrected on future kernel revisions but for this system it was preventing the 6.5 releases from running nicely. From an older, more workstation focused system I will be running the new vs. old CentOS/SL releases.