<?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 SysAdmin Adventures</title>
	<atom:link href="http://blog.tpa.me.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tpa.me.uk</link>
	<description>Tech notes from a Systems Administrator</description>
	<lastBuildDate>Fri, 05 Mar 2010 14:24:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Compiling your own kernel in Slackware Linux in 10 easy steps&#8230; by Zordrak</title>
		<link>http://blog.tpa.me.uk/slackware-kernel-compile-guide/comment-page-1/#comment-909</link>
		<dc:creator>Zordrak</dc:creator>
		<pubDate>Fri, 05 Mar 2010 14:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?page_id=69#comment-909</guid>
		<description>&lt;a href=&quot;#comment-907&quot; rel=&quot;nofollow&quot;&gt;@Klein &lt;/a&gt; 
I guess you&#039;re talking about the make targets &quot;localmodconfig&quot; and &quot;localyesconfig&quot; introduced in 2.6.32:
&lt;a href=&quot;http://kernelnewbies.org/Linux_2_6_32#head-11f54cdac41ad6150ef817fd68597554d9d05a5f&quot; rel=&quot;nofollow&quot;&gt;http://kernelnewbies.org/Linux_2_6_32&lt;/a&gt;.

Personally, I do not use them. Generally, I do not recommend using them. They are simply a way of avoiding learning about what you are doing. Bypassing the learning is the Red Hat Way; it is not my way.

Also, you can get very unexpected results such as lacking any kernel support for hardware you use because the hardware wasn&#039;t plugged in or the module wasn&#039;t loaded when you did the configure.

Stick to the manual way that keeps you on top of your system.</description>
		<content:encoded><![CDATA[<p><a href="#comment-907" rel="nofollow">@Klein </a><br />
I guess you&#8217;re talking about the make targets &#8220;localmodconfig&#8221; and &#8220;localyesconfig&#8221; introduced in 2.6.32:<br />
<a href="http://kernelnewbies.org/Linux_2_6_32#head-11f54cdac41ad6150ef817fd68597554d9d05a5f" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/kernelnewbies.org/Linux_2_6_32_head-11f54cdac41ad6150ef817fd68597554d9d05a5f?referer=');">http://kernelnewbies.org/Linux_2_6_32</a>.</p>
<p>Personally, I do not use them. Generally, I do not recommend using them. They are simply a way of avoiding learning about what you are doing. Bypassing the learning is the Red Hat Way; it is not my way.</p>
<p>Also, you can get very unexpected results such as lacking any kernel support for hardware you use because the hardware wasn&#8217;t plugged in or the module wasn&#8217;t loaded when you did the configure.</p>
<p>Stick to the manual way that keeps you on top of your system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compiling your own kernel in Slackware Linux in 10 easy steps&#8230; by Klein</title>
		<link>http://blog.tpa.me.uk/slackware-kernel-compile-guide/comment-page-1/#comment-907</link>
		<dc:creator>Klein</dc:creator>
		<pubDate>Fri, 05 Mar 2010 12:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?page_id=69#comment-907</guid>
		<description>i read in somewere that new kernel compilation process use information about lsmod and another things to automatic built in the modules that are loaded in the system.. but I dont know details and haven&#039;t tried...</description>
		<content:encoded><![CDATA[<p>i read in somewere that new kernel compilation process use information about lsmod and another things to automatic built in the modules that are loaded in the system.. but I dont know details and haven&#8217;t tried&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compiling your own kernel in Slackware Linux in 10 easy steps&#8230; by Zordrak</title>
		<link>http://blog.tpa.me.uk/slackware-kernel-compile-guide/comment-page-1/#comment-905</link>
		<dc:creator>Zordrak</dc:creator>
		<pubDate>Fri, 05 Mar 2010 10:16:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?page_id=69#comment-905</guid>
		<description>&lt;a href=&quot;#comment-899&quot; rel=&quot;nofollow&quot;&gt;@Klein &lt;/a&gt; 
I have no idea what you mean.. can you be a little more clear?</description>
		<content:encoded><![CDATA[<p><a href="#comment-899" rel="nofollow">@Klein </a><br />
I have no idea what you mean.. can you be a little more clear?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compiling your own kernel in Slackware Linux in 10 easy steps&#8230; by Klein</title>
		<link>http://blog.tpa.me.uk/slackware-kernel-compile-guide/comment-page-1/#comment-899</link>
		<dc:creator>Klein</dc:creator>
		<pubDate>Thu, 04 Mar 2010 22:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?page_id=69#comment-899</guid>
		<description>Hey Zordrak,

about new kernels (2.6.33 as example), there are new ways to get the modules compiled right?
you have already tried?
you will update this post to complain with new rules?</description>
		<content:encoded><![CDATA[<p>Hey Zordrak,</p>
<p>about new kernels (2.6.33 as example), there are new ways to get the modules compiled right?<br />
you have already tried?<br />
you will update this post to complain with new rules?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DRBD 8.3.7 SlackBuilds by SysAdmin Adventures &#187; DRBD 8.3.6 SlackBuild</title>
		<link>http://blog.tpa.me.uk/2010/03/04/drbd-8-3-7-slackbuilds/comment-page-1/#comment-895</link>
		<dc:creator>SysAdmin Adventures &#187; DRBD 8.3.6 SlackBuild</dc:creator>
		<pubDate>Thu, 04 Mar 2010 12:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?p=328#comment-895</guid>
		<description>[...] 20100304: DRBD 8.3.7 has been released and a new SlackBuild is available: http://blog.tpa.me.uk/2010/03/04/drbd-8-3-7-slackbuild/   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] 20100304: DRBD 8.3.7 has been released and a new SlackBuild is available: <a href="http://blog.tpa.me.uk/2010/03/04/drbd-8-3-7-slackbuild/" rel="nofollow">http://blog.tpa.me.uk/2010/03/04/drbd-8-3-7-slackbuild/</a>   Share and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DRBD 8.3.6 SlackBuild by SysAdmin Adventures &#187; DRBD 8.3.7 SlackBuild</title>
		<link>http://blog.tpa.me.uk/2009/11/09/drbd-8-3-6-slackbuild/comment-page-1/#comment-894</link>
		<dc:creator>SysAdmin Adventures &#187; DRBD 8.3.7 SlackBuild</dc:creator>
		<pubDate>Thu, 04 Mar 2010 12:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?p=254#comment-894</guid>
		<description>[...] DRBD SlackBuild has been updated for [...]</description>
		<content:encoded><![CDATA[<p>[...] DRBD SlackBuild has been updated for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on High-Availability Storage with Slackware, DRBD &amp; Pacemaker by Wheelybird</title>
		<link>http://blog.tpa.me.uk/high-availability-storage-with-slackware-drbd-pacemaker/comment-page-1/#comment-875</link>
		<dc:creator>Wheelybird</dc:creator>
		<pubDate>Tue, 02 Mar 2010 10:20:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?page_id=179#comment-875</guid>
		<description>Thanks a lot for this guide.   I don&#039;t know what I&#039;d have done without it.  I&#039;d certainly be messing around, tearing my hair out still.
I&#039;m building a failover pair of servers that act as NFS storage and also as reverse proxying Apache servers that serve static content and load balance to a number of Tomcat servers.
I&#039;d started on the project without coming across this blog, and I&#039;d managed to compile all the various stacks and even get corosync working, but after that the Pacemaker stuff just wouldn&#039;t work. I suspect it&#039;s because I didn&#039;t compile the OpenAIS package before that it didn&#039;t work; the Pacemaker site suggests that as corosync is a cut-down version of it, you don&#039;t need to.

I tried again from scratch using your slackbuilds and managed to get it working.  It still took days of messing around with the CIB configuration for it to actually failover.  One thing I found is that the CIB I created based on yours failed over when putting the master node into standby, but didn&#039;t failover when I simulated a crash.

Like you, I also found the documentation to be poor (and sometimes misleading).  I never really found a good overview of all the components, and mostly it just gives you example CIB configs and says &#039;adapt this for your purposes&#039; without explaining all the various bits.
The best documentation I found is on the Novell site at: http://www.novell.com/documentation/sles11/book_sleha/?page=/documentation/sles11/book_sleha/data/sec_ha_manual_config_create.html but of course, that doesn&#039;t help you compile it all for Slackware.

A final thing; you really do need the SuSE checkproc command for the nfs script to work.  I found the source code for this at http://ftp.nluug.nl/os/Linux/distr/pardusrepo/sources/killproc-2.11.tar.gz  It&#039;s part of the killproc package.

Once again, thanks for sharing your trials with the rest of us - it&#039;s an invaluable aid.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for this guide.   I don&#8217;t know what I&#8217;d have done without it.  I&#8217;d certainly be messing around, tearing my hair out still.<br />
I&#8217;m building a failover pair of servers that act as NFS storage and also as reverse proxying Apache servers that serve static content and load balance to a number of Tomcat servers.<br />
I&#8217;d started on the project without coming across this blog, and I&#8217;d managed to compile all the various stacks and even get corosync working, but after that the Pacemaker stuff just wouldn&#8217;t work. I suspect it&#8217;s because I didn&#8217;t compile the OpenAIS package before that it didn&#8217;t work; the Pacemaker site suggests that as corosync is a cut-down version of it, you don&#8217;t need to.</p>
<p>I tried again from scratch using your slackbuilds and managed to get it working.  It still took days of messing around with the CIB configuration for it to actually failover.  One thing I found is that the CIB I created based on yours failed over when putting the master node into standby, but didn&#8217;t failover when I simulated a crash.</p>
<p>Like you, I also found the documentation to be poor (and sometimes misleading).  I never really found a good overview of all the components, and mostly it just gives you example CIB configs and says &#8216;adapt this for your purposes&#8217; without explaining all the various bits.<br />
The best documentation I found is on the Novell site at: <a href="http://www.novell.com/documentation/sles11/book_sleha/?page=/documentation/sles11/book_sleha/data/sec_ha_manual_config_create.html" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.novell.com/documentation/sles11/book_sleha/?page=/documentation/sles11/book_sleha/data/sec_ha_manual_config_create.html&amp;referer=');">http://www.novell.com/documentation/sles11/book_sleha/?page=/documentation/sles11/book_sleha/data/sec_ha_manual_config_create.html</a> but of course, that doesn&#8217;t help you compile it all for Slackware.</p>
<p>A final thing; you really do need the SuSE checkproc command for the nfs script to work.  I found the source code for this at <a href="http://ftp.nluug.nl/os/Linux/distr/pardusrepo/sources/killproc-2.11.tar.gz" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/ftp.nluug.nl/os/Linux/distr/pardusrepo/sources/killproc-2.11.tar.gz?referer=');">http://ftp.nluug.nl/os/Linux/distr/pardusrepo/sources/killproc-2.11.tar.gz</a>  It&#8217;s part of the killproc package.</p>
<p>Once again, thanks for sharing your trials with the rest of us &#8211; it&#8217;s an invaluable aid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on NetBackup 7 Server on Slackware64 13.1 by Zordrak</title>
		<link>http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/comment-page-1/#comment-846</link>
		<dc:creator>Zordrak</dc:creator>
		<pubDate>Tue, 23 Feb 2010 10:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?p=308#comment-846</guid>
		<description>&lt;a href=&quot;#comment-839&quot; rel=&quot;nofollow&quot;&gt;@tim burlowski &lt;/a&gt; 

WRT X64 support, I was under the impression it was IA64 only, not x86_64. The FTP server you linked to doesn&#039;t seem to be working properly at the mo:

Connected to exftpp.symantec.com.
421 Service not available

While the PAM issue is a pain that ought to be fixed, migration really is the killer; can&#039;t wait to see what you come up with for making it easier :)

Thanks for stopping by.</description>
		<content:encoded><![CDATA[<p><a href="#comment-839" rel="nofollow">@tim burlowski </a> </p>
<p>WRT X64 support, I was under the impression it was IA64 only, not x86_64. The FTP server you linked to doesn&#8217;t seem to be working properly at the mo:</p>
<p>Connected to exftpp.symantec.com.<br />
421 Service not available</p>
<p>While the PAM issue is a pain that ought to be fixed, migration really is the killer; can&#8217;t wait to see what you come up with for making it easier <img src='http://blog.tpa.me.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks for stopping by.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on NetBackup 7 Server on Slackware64 13.1 by tim burlowski</title>
		<link>http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/comment-page-1/#comment-839</link>
		<dc:creator>tim burlowski</dc:creator>
		<pubDate>Mon, 22 Feb 2010 20:44:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?p=308#comment-839</guid>
		<description>Thanks for the write up. I love the shout-out for voting ideas up on the Ideas portal.

Glad to hear about your adventures. We did have Linux X64 server support prior to NetBackup 7. You can check out the SCL for yourself if you like http://bit.ly/cWIks7

We are experimenting with ways to make migration easier in the future.</description>
		<content:encoded><![CDATA[<p>Thanks for the write up. I love the shout-out for voting ideas up on the Ideas portal.</p>
<p>Glad to hear about your adventures. We did have Linux X64 server support prior to NetBackup 7. You can check out the SCL for yourself if you like <a href="http://bit.ly/cWIks7" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/cWIks7?referer=');">http://bit.ly/cWIks7</a></p>
<p>We are experimenting with ways to make migration easier in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on NetBackup 7 Server on Slackware64 13.1 by SysAdmin Adventures &#187; Veritas NetBackup &#38; Slackware</title>
		<link>http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/comment-page-1/#comment-837</link>
		<dc:creator>SysAdmin Adventures &#187; Veritas NetBackup &#38; Slackware</dc:creator>
		<pubDate>Mon, 22 Feb 2010 12:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tpa.me.uk/?p=308#comment-837</guid>
		<description>[...] 20100222: NetBackup 7 has been released and I have it running as a server on Slackware64-13.1: http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] 20100222: NetBackup 7 has been released and I have it running as a server on Slackware64-13.1: <a href="http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/" rel="nofollow">http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/</a>   Share and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
