> separating mechanism from policy as a key component of unix philosophy Can you please elaborate on this? It sounds like a very desirable approach, but I don'

> separating mechanism from policy as a key component of unix philosophy Can you please elaborate on this? It sounds like a very desirable approach, but I don't really see it "in unix". (I can think of a few program suites that use processes and piping between them as the "protocol", eg. cups, the executable files in a directory that are then launched in a loop pattern is more common, but that seems to lack the policy part. Whereas OpenSSH for example lacks this.)