Description of problem:

mkbookdisk reports a problem from tail:

[root@teckla ~]# mkbootdisk --iso --device bootdisk.$(uname -r).iso $(uname -r)
tail: cannot open `+3' for reading: No such file or directory
tail: cannot open `+3' for reading: No such file or directory

It may or may not complete sucessfully. One failure mode is:

[root@charlesc bare.metal]# mkbootdisk --iso --device bootdisk.$(uname -r).iso
$(uname -r)
tail: cannot open `+3' for reading: No such file or directory
tail: cannot open `+3' for reading: No such file or directory
Cannot find root partition in /etc/fstab.



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

[root@teckla ~]# mkbootdisk --version
mkbootdisk: version 1.5.2


How reproducible:

The tail complaints are consistent. The fstab message will show up or not
depending on how the bug affects the output of tail.


Steps to Reproduce:
1. run mkbootdisk as above.
2.
3.
  
Actual results:

As above.

Expected results:

silent creation of a boot disk image in the working directory.

Additional info:

The relevant lines of the script, starting at line 106, are like so:


    list=$(tail +3 /proc/partitions | awk '{ print $4 '} | grep '^md')
    list="$list $(tail +3 /proc/partitions | 
			awk '{ print $4 '} | grep -v '^md')"
    rootdev=""

Fix: insert a -n between the "tail" and the "+3" in lines 107 and 108.


    list=$(tail -n +3 /proc/partitions | awk '{ print $4 '} | grep '^md')
    list="$list $(tail -n +3 /proc/partitions | 
			awk '{ print $4 '} | grep -v '^md')"

Rational: The arguments to tail have changed, and the +3 is no longer vaild
without the -n argument.

N.b.: There may be other scripts with this problem. I know it has affected some
of mine.