Bug 119719
Summary: | SELinux FAQ - suggested questions on FC1 compatability | ||
---|---|---|---|
Product: | [Fedora] Fedora Documentation | Reporter: | George Moody <george> |
Component: | selinux-faq | Assignee: | Karsten Wade <kwade> |
Status: | CLOSED DUPLICATE | QA Contact: | Tammy Fox <tammy.c.fox> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | devel | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://people.redhat.com/kwade/fedora-docs/selinux-faq-en/ | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:02:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 118757 |
Description
George Moody
2004-04-01 19:42:37 UTC
Adding blocking (back?) against 118757 for tracking purposes. Research on answers currently occuring on fedora-selinux-list: http://www.redhat.com/archives/fedora-selinux-list/2004-April/msg00012.html I'm going to make tie this together with an answer for 119461, as they address similar issues. Two or more questions and answers may come out of this. I'll duplicate this information in that bug. *** This bug has been marked as a duplicate of 119461 *** Well, this was a hackish way to create a connection between two bugs without having it be an actual dependency. Reopening this bug to answer just the first question: Q: If I relabel my existing /home partition after upgrading to FC2, will I still be able to read it if I need to revert to FC1? (In other words, am I burning my bridges when I run setfiles or fixfiles?) The second question is a duplicate of 119461 and will be answered there. Well (again), this actually is a duplicate of 119461. Sorry about the confusion and noise in the mbox. Everything is answered in 119461. *** This bug has been marked as a duplicate of 119461 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |