Consider your ordinary journaling filesystem. For simplicity andreliability you have a single, global log in which you put transactionsfor all of your filesystem activity, instead of anything morecomplicated. One useful consequence of this global log is that you havenow created a filesystem-wide global order of all filesystem events(sometimes called a 'total order'), which will be preserved even ifyou crash and restart.

(You implicitly had a total order before, but it didn't necessarilysurvive crashes.)

This sounds

Modern versions of NFS have a variety of authentication methods, andso one of the errors that a NFS server can give a client is 'yourauthentication method is too weak'; for example, the client couldbe sending plain old Unix UIDs and GIDs to a server that requiresKerberos to get strong distributed filesystem authentication . When this happens, the Linux kernelhelpfully prints an error message about it:

call_verify: server somehost.cs requires stronger authentication.

In fact, it prints this message every time it gets

People who want to charge relatively low fees for things often make theargument that people will pay because the charge is such a small amountof money that it is easily afforded, and people get great value for it.One of the problems of charging for things is that it doesn't work thisway.

When you charge, you're not competing to be a great value, you'recompeting to be the most attractive thing for people to do with thatmoney. Want to get two dollars from someone