Description of problem:
Kickstart documentation in the "RHEL Installation Guide" does not document the
'part|partition' option's "--fsoptions" option.
Version-Release number of selected component (if applicable):
RHEL 5.5 and earlier.
Steps to Reproduce:
1. Read the installation guide's section on kickstart from start to finish.
2. Read through it again looking for a way to specify mount options.
3. Observe that there isn't any such option documented for the 'part' option.
Write your own ugly script in %post to munge fstab because you can't find a
built in method to specify mount options. Hit corner cases that don't quite work right and have to special case them while your nose hairs fall out. ;o)
Accidentally stumble upon the --fsoptions option documented in the 'raid' and 'logvol' options, and then notice it also on the Fedoraproject website anaconda documentation.
Test the option out in a dummy kickstart install and discover that it actually works with 'part' and not just with 'raid' and 'logvol'. Rejoice and remove a screenful of unnecessary bash scripting from %post. ;o)
For --fsoptions to be documented under the 'part' option, and any other missing options that there might be left to discover. ;o)
I'd paste my fstab_munge() function here for completeness but it'd make you barf.
Here's what docs/kickstart-docs.txt on rhel5-branch has to say:
Specifies a free form string of options to be used when
mounting the filesystem. This string will be copied into the
/etc/fstab file of the installed system and should be enclosed
I probably didn't file this bug report against the right component as it is technically not an anaconda bug. The problem is specifically the RHEL 5 Installation Guide does not mention the option, so anyone using that as their basis for writing a kickstart file, will not see the --fsoptions documented for the 'part' command, and may resort to writing their own /etc/fstab mangling routines in %post. When I discovered this and mentioned it in IRC, 3 or 4 other competent admins mentioned that they did the same type of mangling and were happy to find out about --fsoptions.
It is good that it is documented elsewhere, but all documentation should be consistent. I suspect most admins, in particular newer admins will look either directly in the RHEL Installation Guide, or to Google, and "docs/kickstart.txt" doesn't come up high in the search list. ;o)
I'll try to reassign this to the proper component if I can figure that out.
Doh, my bad... I didn't notice it was already reassigned. Good stuff. Now that I'm aware of the option, this isn't for me, but rather for other admins out there who might not ever go looking beyond the installation guide for kickstart documentation. It's a minor issue, but would still be nice to see it fixed in the next documentation update.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Thanks for the feedback Mike; fixed in build 3.1-9
Thanks for the update.