Date: Sat, 09 Sep 2006 08:45:39 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: "Marc G. Fournier" <scrappy@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD not popular in Asia? Message-ID: <45027123.8000004@infracaninophile.co.uk> In-Reply-To: <20060909001340.G981@ganymede.hub.org> References: <4501DE34.25561.1AFD75D6@dan.langille.org> <45022E30.4020905@infracaninophile.co.uk> <20060909001340.G981@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA9FDECF86268367DC98447CA
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Marc G. Fournier wrote:
=20
> Reported devices right now doesn't work on the other BSDs, as apparentl=
y
> we are the only one that has a pciconf command :( But, here is a
> sampling of systems information for those coming in from KR (that is
> Korea, right?):
>=20
> operating_system | release | architecture | count
> ------------------+-------------------+--------------+-------
> DragonFly | 1.6.0-RELEASE | amd64 | 17
> DragonFly | 1.0A-RELEASE | i386 | 16
> DragonFly | 1.1-Stable | i386 | 16
> DragonFly | 1.5.3-DEVELOPMENT | i386 | 16
> DragonFly | 1.3.7-DEVELOPMENT | amd64 | 16
> DragonFly | 1.1-Stable | amd64 | 12
> DragonFly | 1.3.7-DEVELOPMENT | i386 | 12
> DragonFly | 1.4.0-RELEASE | amd64 | 12
> DragonFly | 1.7.0-DEVELOPMENT | amd64 | 12
> DragonFly | 1.4.0-RELEASE | i386 | 12
> DragonFly | 1.7.0-DEVELOPMENT | i386 | 11
> DragonFly | 1.0A-RELEASE | amd64 | 10
> DragonFly | 1.5.3-DEVELOPMENT | amd64 | 9
> DragonFly | 1.6.0-RELEASE | i386 | 9
> OpenBSD | 3.8 | macppc | 4
> OpenBSD | 3.3 | zaurus | 4
> OpenBSD | 3.6 | luna88k | 3
> OpenBSD | 3.3 | mac68k | 3
> OpenBSD | 3.8 | mac68k | 3
> OpenBSD | 3.8 | mvme88k | 3
> OpenBSD | 3.6 | mac68k | 3
> OpenBSD | 4.0 | macppc | 3
> OpenBSD | 3.3 | vax | 3
> OpenBSD | 3.9 | sparc | 3
> OpenBSD | 3.4 | cats | 3
> OpenBSD | 3.3 | sparc | 3
> OpenBSD | 3.3 | i386 | 3
> OpenBSD | 3.8 | i386 | 3
> NetBSD | 3.1_RC1 | mmeye | 2
> OpenBSD | 3.5 | sparc64 | 2
> OpenBSD | 3.9 | sgi | 2
> OpenBSD | 3.3 | cats | 2
> OpenBSD | 3.3 | sparc64 | 2
> OpenBSD | 3.8 | hppa | 2
> OpenBSD | 3.2 | cats | 2
> OpenBSD | 3.8 | armish | 2
> OpenBSD | 3.9 | alpha | 2
> OpenBSD | 3.2 | hppa | 2
> OpenBSD | 3.3 | macppc | 2
> OpenBSD | 3.7 | mac68k | 2
> NetBSD | 3.1_RC2 | shark | 2
> OpenBSD | 4.0 | sgi | 2
> NetBSD | 3.0_RC3 | evbsh5 | 2
> NetBSD | 3.99.18 | i386 | 2
> NetBSD | 3.99.20 | evbsh3 | 2
> OpenBSD | 4.0 | i386 | 2
> NetBSD | 4.0_BETA | evbsh3 | 2
> OpenBSD | 3.6 | i386 | 2
> NetBSD | 3.0_RC3 | cats | 2
> OpenBSD | 3.3 | armish | 2
> OpenBSD | 3.8 | sgi | 2
> OpenBSD | 3.7 | sgi | 2
> OpenBSD | 3.2 | sgi | 2
> OpenBSD | 3.4 | amd64 | 2
> OpenBSD | 3.8 | luna88k | 2
> OpenBSD | 3.5 | mvme88k | 2
> OpenBSD | 3.9 | amd64 | 2
> OpenBSD | 4.0 | luna88k | 2
> OpenBSD | 3.6 | amd64 | 2
> NetBSD | 2.0.3 | algor | 2
> OpenBSD | 3.3 | luna88k | 2
> OpenBSD | 3.6 | zaurus | 2
> OpenBSD | 3.7 | vax | 2
> NetBSD | 2.0.3 | prep | 2
> NetBSD | 3.1_RC1 | amd64 | 2
> NetBSD | 3.0_RC3 | algor | 2
> OpenBSD | 3.4 | mvme88k | 2
> OpenBSD | 3.2 | sparc64 | 2
> NetBSD | 4.99.1 | next68k | 1
> OpenBSD | 4.0 | sparc | 1
> NetBSD | 3.99.13 | sbmips | 1
> OpenBSD | 3.8 | amd64 | 1
> OpenBSD | 3.9 | vax | 1
> OpenBSD | 3.2 | amd64 | 1
> NetBSD | 3.0_RC6 | sandpoint | 1
> OpenBSD | 4.0 | vax | 1
> NetBSD | 3.99.13 | playstation2 | 1
> NetBSD | 3.99.22 | hpcarm | 1
> OpenBSD | 3.5 | luna88k | 1
> OpenBSD | 4.0 | alpha | 1
> NetBSD | 2.0.3 | ews4800mips | 1
> NetBSD | 3.1_RC2 | cats | 1
> NetBSD | 2.1_STABLE | cats | 1
> NetBSD | 3.99.13 | pmppc | 1
> NetBSD | 3.0.1 | sgimips | 1
> OpenBSD | 3.2 | mvme88k | 1
>=20
> So if they are playing games, they are sure going to an awful lot of
> trouble to do it ...
Interesting. The 300.bsdstats script seems to except OpenBSD and NetBSD
from the device reporting stuff, but not DFly.
That does look extremely consistent with the known supported platforms
and versions of the various BSDs. As you say, if it is someone playing
games, then they have gone to a great deal of trouble to invent realistic=
data. On the other hand, if it is real, and since it seems to come from
a single IP so we can assume it's all from one project or corporate entit=
y,
then it sounds like a very interesting project I'd like to hear more abou=
t,
and I'm sure that the advocacy@ crowd would love to present as a 'BSD
Success Story'
Apropos nothing else though -- can you add 'operating_system' columns
along side the 'release' columns on the 'Releases' page. Counting
OpenBSD 4.0 along with FreeBSD 4.0 doesn't make a whole lot of sense.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enigA9FDECF86268367DC98447CA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFAnEp8Mjk52CukIwRCEYoAJ4ge3iofFeLh2DHualX51pfWnoL4QCeJ0gt
zvdIYeB4PCqsaYlVyFklx+w=
=smfL
-----END PGP SIGNATURE-----
--------------enigA9FDECF86268367DC98447CA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45027123.8000004>