qa/067 - tweak filter for Mac OS X
qa/514 - rm 514.out, missed in earlier commit
qa/520 - rm 520.out, missed in earlier commit
qa/172 - massage netstat -an output for Mac OS X
qa/273 - sed -e /pat/,+1d is not portable

Translate filter into classical sed syntax.

Found on Mac OS X.
qa/287 - chose x86_64 output for Mac OS X

Even though the processor looks i586, the apps are 64-bit and
so the floating point precision is closer to that than the
32-bit output.
qa_hosts.master - add line for Colleen's Mac
qa/375 - add qualified output for Mac OS X and current PCP
qa/common.check - ifconfig output format changed in Fedora 18

Grr .. more gratuitous changes in output format that break
PCP QA tests.
Merge branch 'dev' of git://oss.sgi.com/pcp/pcp into dev
qa/066 - more helpful notrun message
qa/287 - uname -m more reliable than uname -p
qa/369 - sort symbol table dump in output
qa/200 - a couple of changes

1. rm 200.out that was missed when the expected output was split into
   200.out.1 and 200.out.2
2. Filter out the (recently added) libpcp diagnostic
	__pmConnect(fd=..., 127.0.0.1) -> ...
   as the status reported is not deterministic and does not
   change the correctness of this test
qa/087 - relax one of the expected number of log reads ranges

Seems you can be lucky in creating the archive, and sometimes
require a couple of less log reads for one of the test cases.
qa/admin - fiddling about .. more packages to check, cosmetics
qa/GNUmakefile - localconfig.h depends on ../localconfig
qa/066 - ipv6 wildcard changes
qa/308 - accommodate Fedora 18 and proc PMDA changes

In Fedora 18, the process with pid 1 is not "init" but
/usr/lib/systemd/systemd (with some complicated arguments).

Also the PMID we're filtering has probably been wrong since the
proc metrics were split into a separate PMDA.

Only started to fail when a couple of QA hosts had the proc PMDA
installed by default, and this moved from a "notrun" to "failing
most places" state.
qa/308 - more broken than I first thought

Needs the proc PMDA installed locally and on 2 remote machines.

Make it so locally, clean up when you're done and harden the test
with better integrity checks for the expected instance in the proc
pid indom.