Bug 694648

Summary:	[RHEL6] Blank line at head of fstab
Product:	Red Hat Enterprise Linux 6	Reporter:	Frank Hirtz <fhirtz>
Component:	util-linux-ng	Assignee:	Karel Zak <kzak>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-daemons
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2	CC:	azelinka, jmarko, rvokal
Target Milestone:	rc
Target Release:	6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 17:10:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Frank Hirtz 2011-04-07 20:35:49 UTC

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:

Comment 1 Chris Lumens 2011-04-11 15:16:47 UTC

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.

Comment 2 Karel Zak 2011-04-12 08:07:06 UTC

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

Comment 6 errata-xmlrpc 2011-12-06 17:10:50 UTC

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