Re: Just to add to the confusion: async

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

On 2006-09-04 20:22, John Andrewartha <[e-mail]> wrote:
> Try this version.
> Good English 5 lines and says it all

Sorry but no.

First of all, make sure you Cc: me and use *reply* to the message,
otherwise your message/followup may be lost in the noise.  This would be
a terrible shame, if the suggestions you are making are cool :-/
> async
>=20
> Caution is advised when using this command.
> All I/O to the file system should be done asynchronously to
> ensuring maintaining the full integrity of the file system.
> The use of the 'async' flag by an application may cause unrecoverable
> data loose and corrupt the disk beyond recovery.

Unfortunately, there are quite a few points which are not so good here:

    + "to ensuring" ?

    + "ensuring maintaining" ?

    + What is "full integrity" and how does it compare to "non-full"?

    + The "async" flag is not used by an application, but it a property
      of a mount point

    + "data loss" is spelled differently

    + The disk is not corrupted by 'async'.  The disk should still work
      fine after a newfs operation.  The filesystem though, is another
      story.

If you fix the above points, and *still* want to help, I would be
honestly grateful to see the fixed version, as this part of the manpage
has already caused far too many people to waste too much time, so we
should just fix it and move on.

Thank you for taking the time to write.  I really appreciate any help
and I am grateful that you did spend the time to think about a good way
to write this :)

-- Giorgos


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFE/Dn/1g+UGjGGA7YRAnn3AJ4mpEywhYSfO4SwVStBeaYFtFmTSACfQ/Rh
ZV3jcNAG3XK3K3gYfAV4nl8=
=vDBU
-----END PGP SIGNATURE-----

--EVF5PPMfhYS0aIcm--