Summary: | geli(8) needs to mention unencrypted /etc/fstab requirement for encrypted root | ||||||
---|---|---|---|---|---|---|---|
Product: | Documentation | Reporter: | rsimmons0 | ||||
Component: | Manual Pages | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | Open --- | ||||||
Severity: | Affects Some People | CC: | allanjude, doc, fk, grahamperrin | ||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
rsimmons0
2012-04-29 18:00:26 UTC
Responsible Changed From-To: freebsd-doc->eadler I'll take it. Responsible Changed From-To: eadler->freebsd-doc I won't be looking at this PR for a while and I need to clear some out of my queue An unencrypted /etc/fstab isn't actually necessary, you can specify the root partition/pool with vfs.root.mountfrom. For details see: /boot/defaults/loader.conf and /usr/src/sys/kern/vfs_mountroot.c. I agree that geli(8) could be a bit more specific about how to boot from an encrypted root partition/pool, though. Also, geliboot support now exists, which works with an encrypted /etc/fstab Close as overcome by events? I still think geli(8) should be improved. The "geliboot support" Allan mentioned seems to lack documentation as well. (In reply to Fabian Keil from comment #6) > I still think geli(8) should be improved. … Agreed (coincidentally, I asked a question in Discord not long before your comment). If I understand correctly, such improvements will be out of scope for this bug report: >> geli(8) needs to mention unencrypted /etc/fstab requirement for encrypted root I have no strong feelings about whether or not this bug report stays open, but at least on stable/13 geli(8) still doesn't mention /etc/fstab so IMHO the report has not actually been "overcome by events". |