Here is the list of all the detail (tech notes):
You can see updated and deprecated packages as well as issues so far in beta.
This is so companies can sell compliant RHEL7-based solutions to military and other government organizations.
Looks like there is a major shift in that they will support containers out of the box now. Hopefully we will see some type of GUI to create containers and manage cgroups. There has also been major effort assigned to getting containers working with OpenStack and Docker. You can manually download/compile LXC today, on RHEL 6.4, but it seems like a bit of a hack, since you need to figure out networking and LVM on your own, never mind building base container images. Should be interesting.
The GUI for libvirt is called virt-manager: http://virt-manager.org/
I’m not sure what Systemd version they’ll end up shipping though.
The best part about Systemd is that the default framework for launching and monitoring services is essentially LXC without the padding (extra PID0 etc). This means every service can benefit and there’s no need for the unnecessary abstraction (the container) and all the (mental not necessary performance) overhead that goes with it.
Needless to say, I’m quite excited about what is happening on Linux nowadays :)
This means every service can benefit and there’s no need for the unnecessary abstraction
Of course you could run software on bare metal ;-) But containers are a nice way to ship whole projects including the dependencies. Especially if you deploy to lots of machines.
Relevant interview w/ Alexander Larsson: http://opensource.com/business/13/11/docker-fedora-red-hat-c...
I know that RHEL is mainly used on servers, but this development looks significant to me. I look forward to an eventual CentOS 7 release with a choice of desktops.
For me, it's the only Linux desktop which I can find which is reliable and works out of the box with all my hardware.
My point was giving a choice of desktops is a new departure for Red Hat. Remember that they employ, or have employed, a number of the Gnome developers, and that I gather Red Hat has been a major sponsor of Gnome in the past.
Is it? I've only used RHEL on servers but I've used CentOS on my desktops and laptops for a long time with many re-installs - I've always seen the choice to use KDE as part of the base install.
I've tended to associate CentOS with Gnome, and I installed from live CD with a reduced package set. I still think it is significant that Red Hat are publicising the choices.
I usually prefer that. I'm actually using fedora with MATE to get a similar UX.
Btrfs is still being actively evaluated for stability during the Red Hat Enterprise Linux 7.0 beta. The following target use cases will only be fully supported if it passes our tests:
* The system partition only use case. This will allow btrfs only to get used for system installation, not only for a user's data. Currently it is unclear whether this will be restricted to this single disk or not.
* Use btrfs for desktop and laptop users including their data partitions.
* Use btrfs as the base file system under scale out "big data" file systems, such as gluster and Ceph.
Why do you suppose they went with XFS? Ext4 seems like the defacto file system these days, but I know a lot of people seem to prefer XFS for one reason or another. It's a surprise to me that RHEL decided to default too it.
Anybody care to shed some light?
It also had a bug, in that a power failure or kernel crash was liable to truncate some freshly-written open files to zero size. Anyone knows if this problem has been eliminated?
This sounds pretty convenient to me.
What I recall from a while ago is finding systems with just openjdk and having to install the 'official' version manually. That could have been Fedora though.
You should be able to flip into CentOS 7 fairly easily when they release, though.
"Red Hat Enterprise Linux 7 beta includes three desktops to match different work styles and
preferences: GNOME 3, GNOME Classic, and KDE"
XFS is the default filesystem.
"Multiple required authentications" in OpenSSH. Nifty.
To some that may mean Thunderbird is complete and mature, but RedHat must believe that Thunderbird is now a dead end.
Suggests Fedora 19 package set and 3.10 kernel.
RHEL 4 beta: Sep 27, 2004 / GA: Feb 15, 2005
RHEL 5 beta: Sep 7, 2006 / GA: Mar 15, 2007
RHEL 6 beta: Apr 21, 2010 / GA: Nov 9, 2010
With the next SLES also going systemd by default, Do you think this will force the hand of the few holdouts left? Going I can't see vendors wanting to support all of systemd, upstart, sysvinit.
If a root password is required, the KB recommends using 'guestfish --rw -a <image>', mounting the filesystem, and running vi against /etc/shadow.
If you really wanted, you could run RHEL with no subscription and compile your own updates from the source that they release. In practice, this is next to impossible to maintain as an individual, but it is exactly what CentOS, Scientific Linux, and other related EL distributions do. They remove the RHEL trademarked logos, compile the code released by RHEL, and make it available through a generic yum repository that doesn't require a RHEL subscription.
So, in short, RHEL doesn't cost money, support and packaged patches do. CentOS gives you binary and version compatibility of RHEL without the cost.
Enterprise. You kind of answered your own question.
> Slackware for most of my servers
Ya, you're not the target market. Also, you might be a masochist.
One market that it seems to be strong in is the defense world, since RHEL is one of the few OS' that get various certifications for safety and security.
For personal use, you can get similar stability from either CentOS or Scientific Linux, although the bug fixes will lag behind Red Hat by a few days (although some critical updates have been released only a few hours after Red Hat).
In essence, you pay for their excellent support.
11.1. GCC Toolchain
In Red Hat Enterprise Linux 7.0 Beta, the gcc toolchain is based on the gcc-4.8.x release series, and includes numerous enhancements and bugfixes relative to the Red Hat Enterprise Linux 6 equivalent. Similarly, Red Hat Enterprise Linux 7 includes binutils-2.23.52.x.
These versions correspond to the equivalent tools in Red Hat Developer Toolset 2.0; a detailed comparison of Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 gcc and binutils versions can therefore be seen here:
Notable highlights of the Red Hat Enterprise Linux 7.0 Beta toolchain are the following:
- Experimental support for building applications compliant with C++11 (including full C++11 language support) and some experimental support for C11 features.
- Improved support for programming parallel applications, including OpenMP v3.1, C++11 Types and GCC Built-ins for
Atomic Memory Access and experimental support for transactional memory (including Intel RTM/HLE intrinsics, built-ins, and code generation)
- A new local register allocator (LRA), improving code performance.
- DWARF4 is now used as the default debug format.
A variety of new architecture-specific options.
- Support for AMD family 15h and 16h processors.
- Link-time optimization support.
- Enhanced warnings and diagnostics.
- A variety of new Fortran features.