Please see my responses in line.
> Since VMware ESX is an operating system, I would not judge a server's
> membership by the presence of an rpm, rather than by the kernel, but thats
> just me.
I am fine what ever way works best. I threw out the rpm as a possibility,
but if folks come up with another way to do it it's fine with me.
> now that we got that straightened out, why does your machine register as
> ESX box?
All of my servers (Solaris 7, Solaris 8, Solaris 9, HPUX 11, RHEL3, RHEL4)
now have a VMWare_ESX class set.
> Well if cfengine is truly just running 'stat' on the /etc/issue then
> everything is going to be an ESX server. So that begs the question, what
> in your /etc/issue ?
It's a rather long warning message about authorized use, and being
subjected to monitoring, etc. The result of a checkbox on a security
audit more than anything. I can provide an example on Monday, or if any
of you are familiar with Sun's JASS toolkit, we are using the example
motd/issue that comes in that, with some slight content modification.
> So is there anything weird in your /etc/issue?
The first line is 79 "#" characters. Which as you can guess means that I
also get a class set that is 79 "_" characters.
If there is more info you need from me please let me know. I am also set
up to be able to feed new versions of cfengine into a build system of
sorts to build on all of our operating systems (listed above, ends up with
native pkg for that OS) with very little pain, so if you need build
testers for this or any new release of cfengine just let me know.