[issue1253] mount -p reports bogus errors in chroot

[Stathis Kamperis (via DragonFly issue tracker)]

Stathis Kamperis <ekamperi at gmail.com> added the comment:

jail(8) says that you must create an empty /etc/fstab to suppress the warnings:

"Create an empty /etc/fstab to quell startup warnings about missing fstab"

Indeed:
# mount -p
fstab: /etc/fstab:0: No such file or directory
fstab: /etc/fstab:0: No such file or directory
/dev/ad0s3f     /       ufs rw  1 1
# touch /etc/fstab
# mount -p
/dev/ad0s3f     /       ufs rw  1 1
# 

sjg at #drafonflybsd suggested that a "fix" (if agree there is a need for one)
woule be to only check for fstab once; if it doesn't exist, print an error, and
fall back to the non- "p" case.

What do you think ?

----------
status: unread -> chatting

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1253>
_____________________________________________________