Bug 429592 – Allows setting 'encrypt' flag for /boot

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 429592 - Allows setting 'encrypt' flag for /boot

Summary:	Allows setting 'encrypt' flag for /boot

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	anaconda (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Anaconda Maintenance Team
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-01-21 15:48 EST by Bill Nottingham
Modified:	2014-03-16 23:12 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-01-21 16:12:22 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bill Nottingham 2008-01-21 15:48:08 EST

Description of problem:

anaconda lets me try to encrypt /boot. It throws an error later if I try to
proceed with that partitioning, but it should probably disallow it to start with.

Version-Release number of selected component (if applicable):

rawhide-20080121

Comment 1 Bill Nottingham 2008-01-21 15:48:42 EST

Then again, we allow you to select xfs, etc. there as well and only bounce you
later.

Comment 2 Jeremy Katz 2008-01-21 16:12:22 EST

Yeah, this is generally how we do the checking.  While for /boot we could
disallow early, then people would want the same for /.  But doing it for / is a
lot less obvious as you can add / and then add /boot afterwards.  So this way
we're consistent overall.

Note You need to log in before you can comment on or make changes to this bug.