On Oct 16, 2010, at 9:00 AM, Don Jackson wrote:
>
> A bit of followup here:
>
> I changed my approach to build a more acceptable certname that would be
> acceptable as a hostname, using code like this:
>
> MACADDR=`facter macaddress_en0 | tr "[:upper:]" "[:lower:]" | sed 's/://g' `
> MACADDRH
A bit of followup here:
I changed my approach to build a more acceptable certname that would be
acceptable as a hostname, using code like this:
MACADDR=`facter macaddress_en0 | tr "[:upper:]" "[:lower:]" | sed 's/://g' `
MACADDRHOSTNAME="macaddr-${MACADDR}"
This results in something like this:
On Fri, Oct 15, 2010 at 11:57 AM, Nigel Kersten wrote:
> On Thu, Oct 14, 2010 at 10:23 PM, Don Jackson
> wrote:
>>
>> I'd like to extend my use of puppet to manage my desktop/notebook macs.
>>
>> As others have noted, the hostname of the mobile machines tends to change
>> frequently, so basing t
On Thu, Oct 14, 2010 at 10:23 PM, Don Jackson
wrote:
>
> I'd like to extend my use of puppet to manage my desktop/notebook macs.
>
> As others have noted, the hostname of the mobile machines tends to change
> frequently, so basing the node name (in my site.pp) and the corresponding
> cert and pr
On Oct 14, 2010, at 10:23 PM, Don Jackson wrote:
>
> I'd like to extend my use of puppet to manage my desktop/notebook macs.
>
> As others have noted, the hostname of the mobile machines tends to change
> frequently, so basing the node name (in my site.pp) and the corresponding
> cert and pri
I'd like to extend my use of puppet to manage my desktop/notebook macs.
As others have noted, the hostname of the mobile machines tends to change
frequently, so basing the node name (in my site.pp) and the corresponding cert
and private key names seems to be an issue.
I seem to recall somewhat
