Scientific Linux

  Closed TopicStart new topicStart Poll

> SL 7.4 x86_64 is officially released
 Posted: Oct 2 2017, 04:40 PM
Quote Post

SL Developer

Group: Moderators
Posts: 93
Member No.: 837
Joined: 14-September 11

Scientific Linux 7.4 x86_64 - Oct 2 2017

== Information ==

NOTE: Please review the SL Release Notes along with
The Upstream Vendor's Release Notes:

There is a great deal of information within those documents not listed here.

Please run: yum clean expire-cache

== Media ==
You can find the release media at:

Due to the size of the release, the 4.7gb Install media is discontinued.
We have retained the Dual Layer Install media.

Alternatively the livecd-iso-to-disk utility is able to convert
this to USB successfully. A USB device of sufficient size is

Alternatively you can utilize the dd command to write the
raw image to a USB device.

== SL Specific Updates ==

.UEFI Secure Boot Chain
The boot packages (shim, grub2, kernel) are now signed by the
new Scientific Linux Secure Boot key.
If you use UEFI Secure Boot, you MUST import this new key
into your Machine Owner Key database.
If you do not use UEFI Secure Boot, no action is required.

For more information about Scientific Linux and Secure Boot
please review;2776c184.1707

iptables has been rebuilt with the fixes from RHBZ 1481207.
These patches resolve a bug where the iptables services report the
firewall is loaded when it is not. This bug primarily impacts dual
stack (IPv4 and IPv6) systems.
The upstream fix is still pending release.

OpenAFS has been updated to version 1.6.21 from

.Anaconda User Help
The anaconda user help files are now correctly debranded.
Thanks for the bug report Michael Tiernan!

== Known Issues ==
Users of the EPEL libgpod package may need to run
yum downgrade libgpod
before running yum update

.MATE and Cinnamon
We have encountered some display issues with the MATE and
Cinnamon desktops as provided by EPEL-7.
The exact causes are unclear.

== UEFI Secure Boot ==
The status of UEFI Secure Boot for Scientific Linux is noted in detail at:

Booting SL7 with Secure Boot enabled works but requires a manual step.
This is because the "shim" has not been signed by the UEFI CA.
Instructions are included within the SL7 Release Notes.

Pat Riehecky

Scientific Linux developer
The best way to get my attention is over the official lists.
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

Topic Options Closed TopicStart new topicStart Poll