Great news! Thanks for all the hard work, can't wait for the final go ..:]

On 09/26/2014 04:29 PM, Pat Riehecky wrote:
> Scientific Linux 7.0 x86_64 RELEASE CANDIDATE 1 - Sep 26, 2014
>
> == Information ==
>
> 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 a release candidate 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.
>
> THIS IS NOT A PRODUCTION RELEASE OF SCIENTIFIC LINUX 7.0
>
> NOTE: Please review the SL Release Notes along with
>        The Upstream Vendor's Release Notes:
>
> http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/release-notes/
>
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/index.html
>
>
> There is a great deal of information within those documents not listed
> here.
>
> Send comments/issues/test reports to:
>   [log in to unmask]
>
> == Media ==
> You can find the release media at:
> http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/iso/
>
> NOTE: The 'everything' dvd image requires a Dual-Layer (DL) compatible
>        drive for both burning and booting off of.
>
>        Alternatively the livecd-iso-to-disk utility is able to convert
>        this to USB successfully.  A USB device of sufficient size is
>        required.
>
>        Alternatively you can utilize the dd command to write the
>        raw image to a USB device.
>
> http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/release-notes/#_how_to_make_a_bootable_usb_installer
>
>
> == UEFI Secure Boot ==
> The status of UEFI Secure Boot for Scientific Linux is noted in detail at:
>
> http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/release-notes/#_about_uefi_secure_boot
>
>
> 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.
>
> NOTE: The kernels in sl7-security have not yet been built with
>        the SL7 Secure Boot Certificate and may not function
>        in secure boot environments.
>