--f0KYrhQ4vYSV2aJu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2005.09.13 03:41:04 +1000, matthew green wrote:
|   =20
|    State-Changed-From-To: open->feedback
|    State-Changed-By: rpaulo@netbsd.org
|    State-Changed-When: Mon, 12 Sep 2005 00:52:06 +0000
|    State-Changed-Why:
|    Mouting file systems with the async is evil and very dangerous.
|    >From the mount(8) man page:
|                 async       All I/O to the file system should be done asy=
n-
|                             chronously.  In the event of a crash, it is
|                             impossible for the system to verify the integ=
rity of
|                             data on a file system mounted with this optio=
n.  You
|                             should only use this option if you have an ap=
plica-
|                             tion-specific data recovery mechanism, or are=
 willing
|                             to recreate the file system from scratch.
|   =20
|   =20
|    I think this PR should be closed.
|=20
|=20
| uh, doesn't sysinst already use -o async when it can?
|=20
|=20
| it isn't dangerous for fresh installs.  upgrades maybe, but not installs.

Hmm, I didn't know. Looking at the code I guess you are right.

		-- Rui Paulo

--f0KYrhQ4vYSV2aJu
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFDJcPrZPqyxs9FH4QRAoc7AJ9DUNJqoLKnnex6/PrbvGPdAODsKwCgiTjy
Jm3TWmW5B9QtGYYxIXwLInU=
=51sN
-----END PGP SIGNATURE-----

--f0KYrhQ4vYSV2aJu--