Comment 12 for bug 479429

My system was configured to use tmpfs for /var/log, /var/log/apt and /var/tmp before upgrading to karmic. On the first boot after the upgrade the message "waiting for tmpfs" was reported for /var/log/apt. Disabling the entries for /var/log/apt and /var/tmp allowed for an uninterrupted boot. Still /var/log was mounted as tmpfs! Today I changed /etc/fstab to also mount /var/tmp as tmpfs, which also works.

This is the current /etc/fstab I use:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=f1698a06-f89d-4438-a887-a4205ae1f8bf / ext2 noatime,errors=remount-ro 0 1
# /dev/sda5
UUID=efc9ca27-b198-4827-a223-68248ad3d7bb none swap sw 0 0
#tmpfs /var/log/apt tmpfs defaults 0 0
tmpfs /var/log tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
tmpfs /var/tmp tmpfs defaults 0 0

mountall-Version is 1.0

The only difference I see to the original bug description are the missing options. In a second try, I inactivated the /var/tmp mount and added options to the /var/log mount:

tmpfs /var/log tmpfs defaults,noatime,size=50%,mode=1777 0 0

Still the system boots uninterrupted and /var/log is mounted as tmpfs (as shown by mount).

Conclusion: I can't reproduce the bug given the original description.

Thanks.