I discovered that this is because they hacked up /etc/fedora-release
with their own stuff instead of just leaving it as-is. On Fedora, ohai
reads this file to determine node['platform'] and
I hacked it back to what Fedora 18 looks like and everything is fine.
I'm not sure if Pidora is abandonware now, in light of Fedora
supporting ARM? There hasn't been a new Pidora release for F19, and
F20 is almost out, so I'm wondering what's happening with the project.
On Thu, Nov 28, 2013 at 12:45 AM, Alan Milligan
I know there have been a number of discussions about platforms, platform
families and 'flavours' over the last couple of months. I'm not sure
anything much has been resolved yet though.
To add a little more petrolium product to the discussion, I hacked up
BastionLinux on Raspberry Pi the other day:
The most excellent thing is I only had to build a couple of gems to get our
chef-client stack running (10.28.0). But a vanilla Pidora release has
It's rather a PITA hacking chef/platforms.rb to get through a run-list (and
it seems raspberian is the only Pi-based distro supported out of the box).
Note also, in this rather unfortunate case, the Platform family *should* be
fedora, and worse, the platform_version should be '18' (it's a remix of
Fedora 18) - instead the Pidora crew elected to go with kernel version.
Is there any plan perhaps to use/have an ohai hint even to readily sort out
anomalies like this?
Archive powered by MHonArc 2.6.16.