| Summary: | change options in fstab | ||
|---|---|---|---|
| Product: | [OLD] Docs on www.gentoo.org | Reporter: | droide02 <droide> |
| Component: | Other documents | Assignee: | nm (RETIRED) <nightmorph> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | docs-team |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.gentoo.org/doc/en/security/security-handbook.xml?part=1&chap=5#doc_chap3 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
droide02
2010-09-24 11:51:56 UTC
Please show the code block you refer to. What does it look like now, and what should the whole fstab look like? The whole section should be re-written to better reflect current state of how quotas are activated. For example, the XFS way should be better integrated into the document instead of being mentioned just as a <warn>. Fine. Let's get a patch posted, or else you can do the work. Otherwise this'll be closed as NEEDINFO, since the doc is still correct as-is. I had to dig through several manpages and kernel documentation, but I finally figured out what the reporter was trying to communicate. Our example wasn't the best idea for journaled filesystems, including ext3 as featured in the code listing. Journaled quotas needed a modified config. While I was at it, I dug around and determined that there is a newer format (version 1) of the vfs, so the line should end with jqfmt=vfsv1, not v0. Fixed in CVS. vfsv1 did not work for me, had to use vfsv0 with hardened-sources-2.6.32.x. (In reply to comment #5) > vfsv1 did not work for me, had to use vfsv0 with hardened-sources-2.6.32.x. This bug is closed. Please report that bug to the hardened team against that kernel version. |