Description of problem:
I had on a system to upgrade with three bind mounts listed in
/etc/fstab. Anaconda found only one. I am not sure what
criteria were used. It was the last in fstab of the three
which was recognized. All three lines looked the same with
obvious changes of what and where was mounted.
Maybe something else waa really responsible here? Even
after I did two missing mounts by myself after an upgrade
I found the original fstab in /etc/fstab-hal.save (or something
like that) and a replacement had the some one bind mount
again. Not the killer issue in the given sitation but
definitely a PITA.
Version-Release number of selected component (if applicable):
anaconda used in F7 installer
Have seen that before but I was not sure if something was
not messed up in /etc/fstab. Not this time.
What did your initial fstab look like?
Created attachment 158868 [details]
original fstab - attached to avoid mangling by bugzilla
Looking at this one more time I see that apart of the first two "bind"
lines whatever rewrote it lost also that line:
none /tmp tmpfs size=350M 0 0
and that one:
/dev/hdc /media/cdrom auto
pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0
If that is ok in the last case I would not expect for that to happen
in the remaining three situtations.
In particular gdm configuration in use requires various files from
/usr/local to be present so this was immediately visible after a reboot.
This should be fixed in the next build of anaconda.