<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for ghostar</title>
	<atom:link href="http://www.ghostar.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ghostar.org</link>
	<description>brick by brick.</description>
	<lastBuildDate>Thu, 21 Jan 2010 22:01:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on So, some Solaris updates by hcoyote</title>
		<link>http://www.ghostar.org/2009/06/so-some-solaris-updates/comment-page-1/#comment-22</link>
		<dc:creator>hcoyote</dc:creator>
		<pubDate>Thu, 21 Jan 2010 22:01:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=39#comment-22</guid>
		<description>I&#039;ll let Alex and Dave know so we can figure something out.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll let Alex and Dave know so we can figure something out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So, some Solaris updates by Charles Soto</title>
		<link>http://www.ghostar.org/2009/06/so-some-solaris-updates/comment-page-1/#comment-21</link>
		<dc:creator>Charles Soto</dc:creator>
		<pubDate>Thu, 21 Jan 2010 21:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=39#comment-21</guid>
		<description>So, I&#039;d like to do this.  Any chance we can meet up as a group again to discuss it?

Thanks,
Charles</description>
		<content:encoded><![CDATA[<p>So, I&#8217;d like to do this.  Any chance we can meet up as a group again to discuss it?</p>
<p>Thanks,<br />
Charles</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ugh.  Four hours wasted. by hcoyote</title>
		<link>http://www.ghostar.org/2009/09/ugh-four-hours-wasted/comment-page-1/#comment-45</link>
		<dc:creator>hcoyote</dc:creator>
		<pubDate>Mon, 12 Oct 2009 16:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=93#comment-45</guid>
		<description>Yeah, I did something very similar, but specific for bcfg2.  Part of the problem was that I had the  console= ordering incorrect on the kernel command line so I wasn&#039;t able to get to the password prompt during reboot whenever init was failing.  That made it more difficult to actually get to my logs.  Once I realized it, things got much simpler.

I&#039;ll check out the rpmforge mirror, thanks for pointing it out!</description>
		<content:encoded><![CDATA[<p>Yeah, I did something very similar, but specific for bcfg2.  Part of the problem was that I had the  console= ordering incorrect on the kernel command line so I wasn&#8217;t able to get to the password prompt during reboot whenever init was failing.  That made it more difficult to actually get to my logs.  Once I realized it, things got much simpler.</p>
<p>I&#8217;ll check out the rpmforge mirror, thanks for pointing it out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crazy &#8230; bcfg2 for netapp? by hcoyote</title>
		<link>http://www.ghostar.org/2009/09/crazy-bcfg2-for-netapp/comment-page-1/#comment-50</link>
		<dc:creator>hcoyote</dc:creator>
		<pubDate>Mon, 12 Oct 2009 16:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=99#comment-50</guid>
		<description>@Nick:

It&#039;s not uncommon to have to do this.  We built a platform for doing this at AMD with just a bunch of make files for some of the more common files (snap mirror stuff, for example).

The bigger reason to do this is to enforce consistency and regularize the change management process.  If everyone plays by the same rules, it makes it easier to understand what&#039;s going on with the systems in the long term.

DFM sort of provides the capability to do this for you, but it was very onerous and was more for auditing the correctness of configurations vs having long term change management and logging of changes.

bcfg2 was here before I arrived.  I believe cfengine and puppet were also evaluated but this one won out because of features and usability.  I don&#039;t have any of the details really.  Coming from a cfengine background, it takes a 180 degree shift in ideology to understand bcfg2&#039;s &quot;define the end state&quot; vs cfengine&#039;s &quot;define the path&quot; mentality.

I&#039;ve come across cases where I wished bcfg2 had the ability to just define the path, especially for events that only ever need to be run once on a system (eg, configuring LVM for my MySQL partitions).</description>
		<content:encoded><![CDATA[<p>@Nick:</p>
<p>It&#8217;s not uncommon to have to do this.  We built a platform for doing this at AMD with just a bunch of make files for some of the more common files (snap mirror stuff, for example).</p>
<p>The bigger reason to do this is to enforce consistency and regularize the change management process.  If everyone plays by the same rules, it makes it easier to understand what&#8217;s going on with the systems in the long term.</p>
<p>DFM sort of provides the capability to do this for you, but it was very onerous and was more for auditing the correctness of configurations vs having long term change management and logging of changes.</p>
<p>bcfg2 was here before I arrived.  I believe cfengine and puppet were also evaluated but this one won out because of features and usability.  I don&#8217;t have any of the details really.  Coming from a cfengine background, it takes a 180 degree shift in ideology to understand bcfg2&#8242;s &#8220;define the end state&#8221; vs cfengine&#8217;s &#8220;define the path&#8221; mentality.</p>
<p>I&#8217;ve come across cases where I wished bcfg2 had the ability to just define the path, especially for events that only ever need to be run once on a system (eg, configuring LVM for my MySQL partitions).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ugh.  Four hours wasted. by Nick Silkey</title>
		<link>http://www.ghostar.org/2009/09/ugh-four-hours-wasted/comment-page-1/#comment-44</link>
		<dc:creator>Nick Silkey</dc:creator>
		<pubDate>Mon, 12 Oct 2009 16:06:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=93#comment-44</guid>
		<description>I assume you tee the ks-%post spray to something reviewable?  Its pretty useful:

%post
#### Directory to throw install logs in
mkdir -m700 /usr/local/kickstart
(
*** bunch of %post magic ***
) 2&gt;&amp;1 &#124; tee /usr/local/kickstart/kickstart.log

Also, I think ftp.utexas mirrors rpmforge (possibly under the dag.wieers namespace).  If its not there, a quick note to TN will have a mirror on your behalf.  If its out of date, also ping and demand it be watched more closely.  Oscar is great at helping make ftp.utexas a worthwhile resource for the campus at-large.

Cheers from ct.us.</description>
		<content:encoded><![CDATA[<p>I assume you tee the ks-%post spray to something reviewable?  Its pretty useful:</p>
<p>%post<br />
#### Directory to throw install logs in<br />
mkdir -m700 /usr/local/kickstart<br />
(<br />
*** bunch of %post magic ***<br />
) 2&gt;&amp;1 | tee /usr/local/kickstart/kickstart.log</p>
<p>Also, I think <a href="http://ftp.utexas" rel="nofollow">http://ftp.utexas</a> mirrors rpmforge (possibly under the dag.wieers namespace).  If its not there, a quick note to TN will have a mirror on your behalf.  If its out of date, also ping and demand it be watched more closely.  Oscar is great at helping make <a href="http://ftp.utexas" rel="nofollow">http://ftp.utexas</a> a worthwhile resource for the campus at-large.</p>
<p>Cheers from ct.us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Crazy &#8230; bcfg2 for netapp? by Nick Silkey</title>
		<link>http://www.ghostar.org/2009/09/crazy-bcfg2-for-netapp/comment-page-1/#comment-49</link>
		<dc:creator>Nick Silkey</dc:creator>
		<pubDate>Mon, 12 Oct 2009 15:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=99#comment-49</guid>
		<description>Very interesting approach.  Do you find it often that you need to push site-wide config bits to all n number of filers?  Or are most of your configuration changes atomic wrt yay on filer n, nay on filer n+1, etc?

Also what made unix@utexas.edu/its/ pick bcfg2 and not the smattering of other cfgmgmt solutions out there?

Cheers from ct.us.</description>
		<content:encoded><![CDATA[<p>Very interesting approach.  Do you find it often that you need to push site-wide config bits to all n number of filers?  Or are most of your configuration changes atomic wrt yay on filer n, nay on filer n+1, etc?</p>
<p>Also what made <a href="mailto:unix@utexas.edu">unix@utexas.edu</a>/its/ pick bcfg2 and not the smattering of other cfgmgmt solutions out there?</p>
<p>Cheers from ct.us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Duct Tape Programmer &#8211; Joel on Software by unwesen</title>
		<link>http://www.ghostar.org/2009/09/the-duct-tape-programmer-joel-on-software/comment-page-1/#comment-46</link>
		<dc:creator>unwesen</dc:creator>
		<pubDate>Sat, 10 Oct 2009 15:03:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/2009/09/24/the-duct-tape-programmer-joel-on-software/#comment-46</guid>
		<description>It&#039;s perfectly possible to do the right thing first. You just need to break it into small steps, and ship a step at a time.

That&#039;s a lot different from mediocre solutions, which is what Joel praises. Easily confused when you&#039;re starting out work on something, but one will has better chances at being maintainable in the long run.</description>
		<content:encoded><![CDATA[<p>It&#8217;s perfectly possible to do the right thing first. You just need to break it into small steps, and ship a step at a time.</p>
<p>That&#8217;s a lot different from mediocre solutions, which is what Joel praises. Easily confused when you&#8217;re starting out work on something, but one will has better chances at being maintainable in the long run.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So, some Solaris updates by kb.hurricane-ridge.com / Bookmarks for October 5, 2009</title>
		<link>http://www.ghostar.org/2009/06/so-some-solaris-updates/comment-page-1/#comment-20</link>
		<dc:creator>kb.hurricane-ridge.com / Bookmarks for October 5, 2009</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=39#comment-20</guid>
		<description>[...] &#187; So, some Solaris updates Just Another ITS Systems Guy &#8211; &quot;Problems [seen] with VLV support between Solaris and Active Directory.&quot;    Post a comment &#8212; Trackback URI RSS 2.0 feed for these comments This entry (permalink) was posted on Wednesday, October 7, 2009, at 9:26 am by admin. Filed in Links and tagged active directory, vlv. [...]</description>
		<content:encoded><![CDATA[<p>[...] &raquo; So, some Solaris updates Just Another ITS Systems Guy &#8211; &quot;Problems [seen] with VLV support between Solaris and Active Directory.&quot;    Post a comment &mdash; Trackback URI RSS 2.0 feed for these comments This entry (permalink) was posted on Wednesday, October 7, 2009, at 9:26 am by admin. Filed in Links and tagged active directory, vlv. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So, some Solaris updates by hcoyote</title>
		<link>http://www.ghostar.org/2009/06/so-some-solaris-updates/comment-page-1/#comment-19</link>
		<dc:creator>hcoyote</dc:creator>
		<pubDate>Tue, 06 Oct 2009 14:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=39#comment-19</guid>
		<description>Officially, no, we haven&#039;t resolved it.  In theory we have, we just haven&#039;t tested it.  The solution we&#039;re going with right now is to create an ADAM instance populated with the things we need from AD.  We&#039;re configuring the ADAM so it doesn&#039;t allow VLV.

So, in theory, it works.  I was waiting for some changes to be made in our ADAM infrastructure before going forward with our testing (which, coincidentally, have finalized this week so I should be able to test again soon).

&lt;a href=&quot;http://blogs.utexas.edu/alex/&quot; rel=&quot;nofollow&quot;&gt;Alex&lt;/a&gt; are actively working on this (he&#039;s handling the AD/ADAM side).  I&#039;ll poke him to see if he&#039;s got any instructions for setting up ADAM in the way we&#039;re talking about.</description>
		<content:encoded><![CDATA[<p>Officially, no, we haven&#8217;t resolved it.  In theory we have, we just haven&#8217;t tested it.  The solution we&#8217;re going with right now is to create an ADAM instance populated with the things we need from AD.  We&#8217;re configuring the ADAM so it doesn&#8217;t allow VLV.</p>
<p>So, in theory, it works.  I was waiting for some changes to be made in our ADAM infrastructure before going forward with our testing (which, coincidentally, have finalized this week so I should be able to test again soon).</p>
<p><a href="http://blogs.utexas.edu/alex/" rel="nofollow">Alex</a> are actively working on this (he&#8217;s handling the AD/ADAM side).  I&#8217;ll poke him to see if he&#8217;s got any instructions for setting up ADAM in the way we&#8217;re talking about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So, some Solaris updates by Andy Leonard</title>
		<link>http://www.ghostar.org/2009/06/so-some-solaris-updates/comment-page-1/#comment-18</link>
		<dc:creator>Andy Leonard</dc:creator>
		<pubDate>Mon, 05 Oct 2009 23:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.utexas.edu/hcoyote/?p=39#comment-18</guid>
		<description>I ran into the same issue with Solaris/AD and VLV today.  Did you ever resolve this?  If so, what route did you go?</description>
		<content:encoded><![CDATA[<p>I ran into the same issue with Solaris/AD and VLV today.  Did you ever resolve this?  If so, what route did you go?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

