Tree: 6685d99448

master

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

001

002

003

004

005

006

007

008

009

010

011

012

013

014

015

016

017

018

019

020

021

022

023

024

025

026

027

028

029

030

031

032

033

033-502

034

035

036

037

038

039

040

041

042

043

044

045

046

047

048

049

050

051

052

053

054

055

056

RHEL-7.1

RHEL-7.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '6685d99448'

${ noResults }

Commit Graph

5 Commits (6685d99448665a1fd29d8b123bbb7255a501fea0)

Author	SHA1	Message	Date
Jiri Konecny	0d609ae274	Support only fips=1 not fips ... It looks like only the 'fips=1' is really supported and it is working correctly. So instead of failing on 'fips' not clear way give user information why we are failing.	5 years ago
Jiri Konecny	7ff0fcb723	Fix boot with `fips` without a value ... If you boot system with `fips` and not `fips=1` then you will get unary operator expected error. This will fix this problem.	5 years ago
Harald Hoyer	967cc19ab1	remove all vim and emacs code format comments	11 years ago
Harald Hoyer	32bd2fbb4c	use "rm --" to guard against filenames beginning with "-"	12 years ago
Harald Hoyer	4257798f8a	fips: forward port RHEL-6 fips changes ... - also support FIPS on separate LVM partition - use small settle loop to get /boot - "set -e" has no effect, if we use "||" - make fips work with encrypted root and seperate boot - moved to pre-pivot to support /boot in /	14 years ago