On Aug 1, 2011, at 11:30 AM, Daniel Piddock wrote:
You need to have the lsb_release command installed for the lsb* results
to appear.
Fedora/Redhat have it in the redhat-lsb package, so it possibly has a
similar name under CentOS.
Thanks to you and everyone else who pointed it out.
We just started testing CentOS 6.0 here, and I'm using Facter 1.6.0
If I run this command from my CentOS 5.x test machine:
[root@puppetclient.nj1:~]# facter --version
1.6.0
[root@puppetclient.nj1:~]# facter | grep lsb
lsbdistcodename = Final
lsbdistdescription = CentOS release 5.3 (Final)
On 30/07/11 05:26, Derek J. Balling wrote:
We just started testing CentOS 6.0 here, and I'm using Facter 1.6.0
If I run this command from my CentOS 5.x test machine:
[root@puppetclient.nj1:~]# facter --version
1.6.0
[root@puppetclient.nj1:~]# facter | grep lsb
lsbdistcodename = Final
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is this a known issue? Is there any work-around? It's really breaking my
CentOS 6 servers' ability to find their REPOs. :-)
You need to have the lsb_release command installed for the lsb* results
to appear.
Fedora/Redhat have it in the
Is the redhat-lsb package installed? IIRC it provides the necessary info
for the lsb facts.
On Aug 1, 2011 8:27 AM, Derek J. Balling dr...@megacity.org wrote:
We just started testing CentOS 6.0 here, and I'm using Facter 1.6.0
If I run this command from my CentOS 5.x test machine:
Peter Meier wrote :
Is this a known issue? Is there any work-around? It's really breaking my
CentOS 6 servers' ability to find their REPOs. :-)
You need to have the lsb_release command installed for the lsb* results
to appear.
Fedora/Redhat have it in the redhat-lsb package, so
