RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Anaconda leaves a blank like at the beginning of /etc/fstab:

<snip>

#
# /etc/fstab
# Created by anaconda on Fri Jun 11 00:48:49 2010
#
</snip>

From the man page, it's not clear that blank lines are valid in the file, and indeed some (external) programs that parse it have issues with the blank line. I'd request that we either change anaconda so we don't get the blank like at the head, or change the manpage so that we indicate that blank lines are valid. 

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

How reproducible:
Always

Steps to Reproduce:
1. Install
2. Check fstab
3.
  
Actual results:

File starts with a blank line


Expected results:

File shouldn't (or we should document that it can have blank lines)

Additional info:

my_getmntent from the util-linux-ng source indicates it knows how to skip blank lines.  That should at least be noted in the documentation.

OK, upstream man page has been updated (commit ca6182333e1417bde216abd8e223f23989a45445).

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1691.html