syslog messages

kernel messages

initial RAM disk and early boot messages

messages sent to standard output and standard error output

yum group and yum groups are now top level commands, to improve the consistency of command line yum use. For example, where previously you would use yum groupinfo, you can now use yum group info.

yum group list now includes additional optional parameters to alter its output. The new options are language and ids.

The default value for the group_command parameter in /etc/yum.conf has been changed from compat to objects. Previously, the default behavior of yum group install was to install all members of a package group and upgrade both previously installed packages and packages that had been added to the group since the previous upgrade. The new default behavior is that yum keeps track of the previously installed groups and distinguishes between packages installed as a part of the group and packages installed separately.

The yum-security and yum-presto plug-ins have been integrated into yum.

yum can now download multiple packages simultaneously.

yum now includes support for environment groups. This allows you to install and remove multiple package groups listed under an environment group as a single entity.

yum can now treat a repository as a set of packages, allowing users to treat all packages in a repository as a single entity, for example, to install or remove all packages in that repository. This capability is provided by the repository-packages subcommand.

yum now includes a --disableincludes option, which allows you to disable include statements defined in your configuration files. You can either disable all include statements with the all value, or disable the include statements defined for a specific repository by providing that repository identifier.

yum now includes an --assumeno option, which assumes that the answer to any question asked by yum is 'no'. This option overrides the --assumeyes option, but is still subject to the behavior prescribed by alwaysprompt.

Conflict detection is now stricter and more correct. Some packages that would have installed on Red Hat Enterprise Linux 6 may not install on Red Hat Enterprise Linux 7 because of this heightened conflict sensitivity.

A package that conflicts with other versions of itself can now be set up as a singleton using alternatives, so that multiple versions of a single package can be installed alongside each other.

If an installed package lists another package as obsolete, the second package is not installed.

Obsolete rules now include all matching packages regardless of other attributes such as architecture.

Dependency calculations no longer consider files that were not installed or files that were replaced, for example, with the --nodocs, --noconfig, or --force options, as being provided.

There is no longer a need to manually execute rm -f /var/lib/rpm/__db. when rebuilding a panicked (DB_RUNRECOVER) RPM Package Manager database.

Public keys created with OpenPGP 3 are no longer supported.

The --info option now outputs individual tag–value pairs per line to improve human readability. Any scripts that rely on the previous --info format need to be rewritten.

The spec parser is now stricter and more correct, so some previously-accepted spec files may fail to parse, or give warnings.

%license can now be used to mark files in the %files section of a spec file as licenses that must be installed even when --nodocs is specified.

Version comparison now supports the dpkg-style tilde (~) operator to handle pre-release software better. For example, foo-2.0~beta1 is considered older than foo-2.0, removing the need for tricks with the Release field to handle these common upstream version practices.

The automatic dependency generator has been rewritten into an extensible, customizable rule-based system with built in filtering.

It is now possible to query the files installed from a package (INSTFILENAMES), the number of hard links to a file (FILENLINKS), package version control system details (VCS), and formatted dependency string shortcuts (PROVIDENEVRS, REQUIRENEVRS, CONFLICTNEVRS, OBSOLETENEVRS).

A number of new commands are provided, including:

RPM Package Manager now includes new switches to scriptlets to enable runtime macro expansion or runtime query format expansion.

Pre- and post-transaction scriptlet dependencies can now be correctly expressed with Requires(pretrans) and Requires(posttrans).

RPM Package Manager now includes the OrderWithRequires tag to allow users to supply additional ordering information. This new tag uses the same syntax as the Requires tag, but does not generate dependencies. If mentioned packages are present in the same transaction, the ordering hints are treated like Requires when calculating transaction order.

Line continuations and macro expansions in spec files are no longer limited to a specified length.

RPM Package Manager now allows users to specify upstream version control repository information.

RPM Package Manager now includes an %autosetup macro to assist in automating the process of applying patches.

Control groups are now mounted under /sys/fs/cgroup instead of /cgroup.

Some file systems are now mounted by default.

systemd does not yet fully support migration from libcgroup to systemd. As such, the cgred service should be used only to move processes to groups not managed by systemd. The cgconfig.conf file should be used to configure a control group hierarchy for file systems or file controllers not managed by systemd.

The net directive is no longer supported. Users must now explicitly define either ssh or nfs.

The blacklist option is no longer supported. Instead, users can specify rd.driver.blacklist as a parameter in the /etc/sysconfig/kdump file of their capture kernel.

The default mount_root_run_init action, which was performed if dumping to an intended target failed, has been replaced by the dump_to_rootfs action. Instead of mounting the real root file system, running init scripts, and attempting to save the vmcore when the kdump service has started, this new action mounts the root file system and saves the vmcore to it immediately.

A new directive, dracut_args, allows you to specify additional dracut arguments when configuring kdump.

The debug_mem_level option is no longer included in kdump. This functionality has been moved to dracut. Users can achieve the same functionality by specifying rd.memdebug as a parameter in the /etc/sysconfig/kump file of their capture kernel.

The options directive was previously used to include parameters specific to the kernel module in the initial ram file system (initramfs). This method is not supported in Red Hat Enterprise Linux 7. Instead, users can specify relevant parameters in the /etc/sysconfig/kdump file of their capture kernel.

The link_delay and disk_timeout parameters are no longer necessary or supported, as dracut contains udev, which addresses the use case for which these parameters were previously required.

Any file system back-end dump targets must be mounted in the crashed kernel before the kdump service is started and the initial RAMDdisk image is created. You can achieve this by adding these targets to /etc/fstab to be automatically mounted at boot time.

If you specify a path, but do not specify a target, and any directory in the path that you specify is a mount point for a separate device, the vmcore is saved to the path, not the device mounted somewhere along that path. Therefore when your system reboots, and the device mounts, the vmcore is inaccessible, because the device has mounted over the top of its location. Red Hat Enterprise Linux 7 now warns about this issue when you specify a path without specifying a target.