From owner-cvs-usrbin  Fri Apr 25 05:13:05 1997
Return-Path: <owner-cvs-usrbin>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA10796
          for cvs-usrbin-outgoing; Fri, 25 Apr 1997 05:13:05 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10789;
          Fri, 25 Apr 1997 05:13:00 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA28172; Fri, 25 Apr 1997 21:58:23 +1000
Date: Fri, 25 Apr 1997 21:58:23 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199704251158.VAA28172@godzilla.zeta.org.au>
To: ache@nagual.pp.ru, bde@zeta.org.au
Subject: Re: cvs commit:  src/usr.bin/vacation vacation.c
Cc: cvs-all@FreeBSD.org, CVS-committers@FreeBSD.org, cvs-usrbin@FreeBSD.org
Sender: owner-cvs-usrbin@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>I think that vfork() must be supported by compiler instead.
>
>So, right now we already have some sort of this support by default
>based on current gcc behaviour. If this behaviour will be changed (more
>general case you speak about), such compiler must support vfork
>especially, i.e. not cross-optimizing, keeping stack frame, etc.

I just noticed that gcc already has some support.  Put back the vfork()
in mount.c and compile with -Wall, and you will see the useful warnings
that `optbuf' and `name' might be clobbered by `longjmp' or `vfork'.

Bruce