From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

Description of problem:
After a non-LVM installation of phoebe,
/proc/lvm and /etc/lvmtab are created,
which they probably shouldn't be.

This also causes the machine boot sequence to
report a message from vgchange that
there are no volume groups.

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


How reproducible:
Always

Steps to Reproduce:
1. Install phoebe, but make sure you don't use LVM.
2. Look at the boot sequence to look for vgchange messages.
3. Look for the existence of /proc/lvm and /etc/lvmtab.
    

Actual Results:  /proc/lvm and /etc/lvmtab (the latter is a 1-byte "empty" file)
are created, plus a vgchange warning message is also displayed during
the phoebe boot sequence because of this.

Expected Results:  In a non-LVM Red Hat 8.0 system, /proc/lvm and /etc/lvmtab don't
exist and there is no vgchange warning message.

Additional info:

My suspicion is that anaconda is running "vgscan" at some point during
the installation of phoebe when it probably shouldn't if a non-LVM
system is being installed. It is "vgscan" that creates /proc/lvm
and /etc/lvmtab in case you're wondering.

Also note that the tests in /etc/rc.d/rc.sysinit that decide whether
to run "vgscan" and possibly "vgchange" now become true in phoebe's
case, even on a non-LVM system:

if [ -e /proc/lvm -a -x /sbin/vgchange -a -f /etc/lvmtab ]; then
        action $"Setting up Logical Volume Management:" /sbin/vgscan &&
/sbin/vgchange -a y
fi

This is where the vgchange warning about no volume groups comes from.