# Ohai 0.6.12.rc.1 released

**URL:** https://discourse.chef.io/t/ohai-0-6-12-rc-1-released/2434
**Category:** Chef Infra (archive)
**Created:** [February 9, 2012, 6:12pm UTC](https://discourse.chef.io/t/ohai-0-6-12-rc-1-released/2434 "2012-02-09T18:12:32Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Bryan\_McLellan1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan1/32/426_2.png) [@Bryan\_McLellan1](https://discourse.chef.io/u/Bryan_McLellan1)
#### Post date: [February 9, 2012, 6:12pm UTC](https://discourse.chef.io/t/ohai-0-6-12-rc-1-released/2434/1 "2012-02-09T18:12:32Z")

</div>

Hey Chef’ers

Ohai 0.6.12.rc.1 is up on [Rubygems.org](http://Rubygems.org)

You can install it on a system with ‘sudo gem install ohai --pre’ or  
of course across all the systems with ‘knife ssh _:_ sudo gem install  
ohai --pre’

We don’t usually get as much testing with Ohai as I’d like, and it  
often means that we release one or two immediate re-releases as people  
who didn’t bother to test it start building production system from the  
latest version on [rubygems.org](http://rubygems.org). Please, don’t be surprised by a  
regression and try this release candidate out. Our policy is to let  
three days without a regression go by before we release a final  
version.

One huge feature in this release is the new "platform\_family"  
attribute which is currently a hardcoded list of platforms that are  
alike. If you write a cookbook to run on CentOS, but it should also  
run on Scientific Linux, RHEL and Oracle, you can test for  
platform\_family == “rhel” instead of testing for all the individual  
platforms.

Here is the current list:

when /debian/, /ubuntu/, /mint/  
platform\_family "debian"  
when /fedora/, /amazon/  
platform\_family "fedora"  
when /oracle/, /centos/, /redhat/, /scientific/, /enterpriseenterprise/  
platform\_family "rhel"  
when /suse/  
platform\_family "suse"  
when /gentoo/  
platform\_family "gentoo"  
when /slackware/  
platform\_family "slackware"  
when /arch/  
platform\_family “arch”

There is also fixed support for Scientific Linux, added support for  
Oracle, and an important iproute2 fix for Arch users.

Below is the list of issues in this release:

OHAI-325 Add support for iproute2 for linux networking  
OHAI-324 Add specs for linux network, precursor to some other bug fixes  
OHAI-323 spec failure in sigar/network\_route\_spec.rb failure  
OHAI-319 ohai detects “scientific” as "scientificsl"  
OHAI-316 venet0 IP address detected incorrectly on newer versions of OpenVZ  
OHAI-314 plugins/os.rb RbConfig / Config warning in Ruby 1.9.3  
OHAI-312 OpenBSD uptime.rb plugin does not generate output  
OHAI-308 Can not detect oracle server linux platform during chef installation  
OHAI-303 filesystem uuid support

–  
Bryan McLellan | opscode | technical program manager  
© 206.607.7108 | (t) @btmspox | (b) [http://blog.loftninjas.org](http://blog.loftninjas.org)

---

<div class="post-metadata">

### Author: ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)
#### Post date: [February 10, 2012, 5:20pm UTC](https://discourse.chef.io/t/ohai-0-6-12-rc-1-released/2434/2 "2012-02-10T17:20:47Z")

</div>

On Thu, Feb 9, 2012 at 1:12 PM, Bryan McLellan [btm@opscode.com](mailto:btm@opscode.com) wrote:

> There is also fixed support for Scientific Linux, added support for  
> Oracle, and an important iproute2 fix for Arch users.

Caleb Tennis reminded me on twitter this morning that the iproute2  
change [8] actually switches to use the 'ip' command over the  
'ifconfig' command to gather network information for all Linux  
distributions, not just Arch.a

The net-tools package, which includes ifconfig, has apparently been  
abandoned as no release has been made since version 1.60 on April 15,  
2001 [1]. Last year Arch Linux, known as a leading edge Linux  
distribution, decided to deprecate net-tools [2] and begin the switch  
to using iproute2. It appears that Arch no longer includes net-tools  
and ifconfig in a default install now.

Trying to research this history of this is surprisingly difficult. On  
the surface most people are claiming it is deprecated because  
wikipedia says so [6] but wikipedia uses the deprecation by Arch Linux  
[2] as its source, hardly enough to support the project itself being  
deprecated. Bernd Eckenfels is the last known net-tools maintainer,  
but his personal website doesn't mention it any longer. It appears  
that he was maintaining the debian package and provide patches in the  
packaging for debian bugs. Around 2005 he planned a 1.65 release [3]  
that never happened. From that same thread it looks like he was  
getting frustrated with maintaining net-tools in debian. Debian [4]  
and Redhat [5] were both struggling with maintaining a large number of  
patches on top of the last release as of a few years ago. openSuSE  
went so far as to add a warning to the ifconfig man page about its  
deprecation [9][10] although that decision appears to not have been  
thought out.

However the git repository [7] from the new sourceforge site for the  
project [6] which replaces the [berlios.de](http://berlios.de) site [1] has recent commits  
by Bernd Eckenfels. It does seem possible that net-tools is not  
abandoned per se. Perhaps the maintainers are disenfranchised with the  
distribution communities. I sent Bernd a note to see if he could clear  
any of this up.

There are some arch folks who complained on forums about ifconfig  
disappearing when it worked perfectly fine for them. As I've always  
taken Arch to be for people who wanted cutting edge, this seemed odd  
but underscores that change always makes someone unhappy. Ten years  
without a net-tools release, while iproute2 has been in active  
development and versioning alongside the kernel [11] and plenty of  
activity on the netdev kernel list.

We're going to see increased use of iproute2 simply because it  
supports features of the kernel that ifconfig never will. For  
instance, you can add a second IP address to an existing interface  
with iproute2, but cannot manage it with ifconfig [12]. Many existing  
scripts and users will continue using ifconfig, so I expect it to be  
around for some time. However, the purpose of Ohai is to provide you  
with information, and we're starting to need iproute2 to get that  
information, which is what justifies the switch.

This switch includes a provision to fallback and use ifconfig, so it  
should be painless and error-free. As we joke at Opscode, "no bugs  
will be found in production." Lets give this some testing and make  
sure this is true together.

Bryan McLellan

Please forgive my footnotes not being sorted properly.

[1] [https://developer.berlios.de/projects/net-tools/](https://developer.berlios.de/projects/net-tools/)  
[2] [Arch Linux - News: Deprecation of net-tools](http://www.archlinux.org/news/deprecation-of-net-tools/)  
[3] [Re: net-tools maintenance status](http://lists.debian.org/debian-devel/2005/09/msg00426.html)  
[4] [http://packages.debian.org/changelogs/pool/main/n/net-tools/current/changelog](http://packages.debian.org/changelogs/pool/main/n/net-tools/current/changelog)  
[5] [http://www.redhat.com/archives/rhl-devel-list/2007-March/msg00554.html](http://www.redhat.com/archives/rhl-devel-list/2007-March/msg00554.html)  
[6] [net-tools download | SourceForge.net](http://sourceforge.net/projects/net-tools/develop)  
[7] git://net-tools.git.sourceforge.net/gitroot/net-tools/net-tools  
[8] [http://tickets.opscode.com/browse/OHAI-325](http://tickets.opscode.com/browse/OHAI-325)  
[9] [http://tickets.opscode.com/browse/OHAI-209](http://tickets.opscode.com/browse/OHAI-209)  
[10] [Access Denied](https://bugzilla.novell.com/show_bug.cgi?id=366477)  
[11] ['[announce] iproute2 update' - MARC](http://marc.info/?l=linux-netdev&m=109122713104140&w=2)  
[12] [http://tickets.opscode.com/browse/OHAI-109](http://tickets.opscode.com/browse/OHAI-109)

---

<div class="post-metadata">

### Author: ![Erik\_Hollensbe](https://avatars.discourse-cdn.com/v4/letter/e/9de053/32.png) [@Erik\_Hollensbe](https://discourse.chef.io/u/Erik_Hollensbe)
#### Post date: [February 10, 2012, 5:24pm UTC](https://discourse.chef.io/t/ohai-0-6-12-rc-1-released/2434/3 "2012-02-10T17:24:35Z")

</div>

On Feb 10, 2012, at 9:20 AM, Bryan McLellan wrote:

> On Thu, Feb 9, 2012 at 1:12 PM, Bryan McLellan [btm@opscode.com](mailto:btm@opscode.com) wrote:
> 
> > There is also fixed support for Scientific Linux, added support for  
> > Oracle, and an important iproute2 fix for Arch users.
> 
> Caleb Tennis reminded me on twitter this morning that the iproute2  
> change [8] actually switches to use the 'ip' command over the  
> 'ifconfig' command to gather network information for all Linux  
> distributions, not just Arch.a

I know I'm late to the party, but I have some code that solves this problem in C. Would you find it useful?

[https://github.com/erikh/unixinfo/blob/master/ext/unixinfo/unixinfo\_native.c#L50-172](https://github.com/erikh/unixinfo/blob/master/ext/unixinfo/unixinfo_native.c#L50-172)

No need for scanning ifconfig, iproute, etc -- just ask the kernel; it's working currently on FreeBSD, Linux, and OS X. 🙂

-Erik

---

<div class="post-metadata">

### Author: ![Bryan\_McLellan](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/bryan_mclellan/32/81_2.png) [@Bryan\_McLellan](https://discourse.chef.io/u/Bryan_McLellan)
#### Post date: [February 10, 2012, 7:03pm UTC](https://discourse.chef.io/t/ohai-0-6-12-rc-1-released/2434/4 "2012-02-10T19:03:54Z")

</div>

On Fri, Feb 10, 2012 at 12:24 PM, Erik Hollensbe  
[erik.hollensbe@wildfireapp.com](mailto:erik.hollensbe@wildfireapp.com) wrote:

> I know I'm late to the party, but I have some code that solves this problem  
> in C. Would you find it useful?

OHAI-92 [1] considers doing this very thing using sigar. I wouldn't  
want to put C in Ohai itself when we have alternatives, because we  
save ourselves the complexity of building extensions and doing so on  
multiple platforms. There was not enough energy at the time to cover  
all the use cases to justify a switch of framework though.

Requiring a development environment to install a library dependency  
was a little painful, particularly on Windows when we started using  
YAJL. The Omnibus client really resolves that issue for those who  
simply want to use Chef rather than hack on and develop it.

Bryan

[1] [http://tickets.opscode.com/browse/OHAI-92](http://tickets.opscode.com/browse/OHAI-92)
