The boot partition isn't mounted

[science.geek]

Everything seems to boot properly but the boot partition doesn't get mounted, I have to manually mount it.
My fstab

# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# <fs> <mountpoint> <type> <opts> <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noauto,noatime 1 2
/dev/hda3 / ext3 noatime 0 1
/dev/hda2 none swap sw 0 0
/dev/hdc /mnt/cdrom iso9660 noauto,ro 0 0
/dev/hdd /mnt/burn iso9660 noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0

# NOTE: The next line is critical for boot!
proc /proc proc defaults 0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
_________________
Everything is proceeding as I have foreseen it.

[Keruskerfuerst]

[jasm]

Why do you need the /boot partition mounted automatically at boot time?
In setups like I know them, a booting/running kernel doesn't need the content of /boot at all. Under normal operation, that is solely the domain of your bootloader. In fact, having /boot *not* mounted can even be seen as a security thing. There is no way to accidentally remove your kernel image and find out that your machine won't boot anymore. The one thing you must not forget to do then is to mount /boot before copying your freshly build kernel ... been there; done that;