Created attachment 358726 [details]
Description of problem:
The fstab man page says that all filesystems without noauto will be mounted on boot time, just as "mount -a" does.
That NFS and proc is handled in a special way by rc.sysinit is an implementation detail.
It must thus be a bug that bind mounts not are mounted automatically.
It seems like bind (and perhaps other missing types?) just should be added to the mount -a in rc.sysinit.
Version-Release number of selected component (if applicable):
You're misunderstanding that statement. By adding bind to the list, you're telling it to not mount filesystems that have 'bind' as the filesystem type.
What does your fstab look like? A line like:
/var /usr/local/var none bind 0 0
works fine for me on boot.
notting: You are absolutely right. My bad. Thanks for the hints on IRC.
I was probably mostly confused by not being aware that Live CDs /mnt/live is mounted _after_ /etc/rc.sysinit and "mount -a" has been executed. Seeing that the bind-mounted mount point was empty I must have concluded that nothing had been mounted.
I misunderstood the -t option from the manpage. Not knowing the exclusive list of file systems by heart I assumed that -t was an exclude list (which surprised me) and that nomsdos (and nonfs) was file systems. Assuming that the -t option was just a list I randomly but "bind" before or after the "no", so my test results were completely broken and supported my wrong conclusions.
After having tried "none" as file system type in fstab and concluded that it didn't work for the reasons above I changed to "bind". Apparently anything can be specified as file system type for bind mounts, and it will (only?) be used for filtering when doing "mount -a -t". So "mount -a -t bind" works just as well as "mount -a -t foo" if the fstab file system type is specified accordingly.