<?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 Tom&#039;s FreeBSD blog</title>
	<atom:link href="http://blogs.freebsdish.org/tmclaugh/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.freebsdish.org/tmclaugh</link>
	<description>I&#039;d rather be doing something than writing about it.</description>
	<lastBuildDate>Sat, 13 Mar 2010 20:38:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Verizon FIOS Actiontec MI424WR and multiple subnets by tmclaugh</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2008/12/01/verizon-fios-actiontec-mi424wr-and-multiple-subnets/comment-page-1/#comment-1606</link>
		<dc:creator>tmclaugh</dc:creator>
		<pubDate>Sat, 13 Mar 2010 20:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=33#comment-1606</guid>
		<description>The images look to have been lost unfortunately.  They&#039;re listed in wordpress but the files are missing.  Sorry about that.</description>
		<content:encoded><![CDATA[<p>The images look to have been lost unfortunately.  They&#8217;re listed in wordpress but the files are missing.  Sorry about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Verizon FIOS Actiontec MI424WR and multiple subnets by Ken</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2008/12/01/verizon-fios-actiontec-mi424wr-and-multiple-subnets/comment-page-1/#comment-1605</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Sat, 13 Mar 2010 15:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=33#comment-1605</guid>
		<description>Do you have the images relating to the blog. I would like to subnet my actiontec.</description>
		<content:encoded><![CDATA[<p>Do you have the images relating to the blog. I would like to subnet my actiontec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by Ken</title>
		<link>http://blogs.freebsdish.org/tmclaugh/about/comment-page-1/#comment-1604</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Sat, 13 Mar 2010 15:01:42 +0000</pubDate>
		<guid isPermaLink="false">#comment-1604</guid>
		<description>I am looking to subnet my Actiontec router and came across your blog entry - DEcember 2008.  The links to the images are broken. I would like to take a look at the images so if you have them I would appreciate you sending them. I hope this is not too much of a bother. Thank you.

Ken.</description>
		<content:encoded><![CDATA[<p>I am looking to subnet my Actiontec router and came across your blog entry &#8211; DEcember 2008.  The links to the images are broken. I would like to take a look at the images so if you have them I would appreciate you sending them. I hope this is not too much of a bother. Thank you.</p>
<p>Ken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware serial consoles. by tmclaugh</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2010/02/02/vmware-serial-consoles/comment-page-1/#comment-1327</link>
		<dc:creator>tmclaugh</dc:creator>
		<pubDate>Wed, 03 Feb 2010 14:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=160#comment-1327</guid>
		<description>@Ivan: I&#039;ve tracked it down to probably either r203047 or r203073 as the culprits.  Both were in the time frame between me being able to build a working kernel and then having a broken kernel after testing yesterday.  Can you try an amd64 VM?  I should try an i386 VM and see what happens.

@Tim: If there was something like that or even physical serial port pass through then ESXi would be come a possible option for use in the FreeBSD cluster.</description>
		<content:encoded><![CDATA[<p>@Ivan: I&#8217;ve tracked it down to probably either r203047 or r203073 as the culprits.  Both were in the time frame between me being able to build a working kernel and then having a broken kernel after testing yesterday.  Can you try an amd64 VM?  I should try an i386 VM and see what happens.</p>
<p>@Tim: If there was something like that or even physical serial port pass through then ESXi would be come a possible option for use in the FreeBSD cluster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by Tutoriel : Debuger FreeBSD en liaison série sous VMWare at FreeBSD-fr: Les nouvelles du géant en français</title>
		<link>http://blogs.freebsdish.org/tmclaugh/about/comment-page-1/#comment-1320</link>
		<dc:creator>Tutoriel : Debuger FreeBSD en liaison série sous VMWare at FreeBSD-fr: Les nouvelles du géant en français</dc:creator>
		<pubDate>Wed, 03 Feb 2010 08:59:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-1320</guid>
		<description>[...] Tom McLaughlin à mis en place la récupération des traces système via une liaison série, voici son tutoriel.      &#171; BSDMagazine : Un BSD comme [...]</description>
		<content:encoded><![CDATA[<p>[...] Tom McLaughlin à mis en place la récupération des traces système via une liaison série, voici son tutoriel.      &laquo; BSDMagazine : Un BSD comme [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware serial consoles. by Tim</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2010/02/02/vmware-serial-consoles/comment-page-1/#comment-1319</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 03 Feb 2010 08:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=160#comment-1319</guid>
		<description>Thanks, a useful post. What I&#039;d find even more useful is a way to connect the first VM&#039;s serial port to an IP port on the VM host. Then it could be connected to from any remote system over the network to access the console of the VM. And it could be done for as many VMs as there were on the host.</description>
		<content:encoded><![CDATA[<p>Thanks, a useful post. What I&#8217;d find even more useful is a way to connect the first VM&#8217;s serial port to an IP port on the VM host. Then it could be connected to from any remote system over the network to access the console of the VM. And it could be done for as many VMs as there were on the host.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware serial consoles. by Ivan Voras</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2010/02/02/vmware-serial-consoles/comment-page-1/#comment-1316</link>
		<dc:creator>Ivan Voras</dc:creator>
		<pubDate>Wed, 03 Feb 2010 02:59:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=160#comment-1316</guid>
		<description>Did you find the problem? I should add that I also have 7-stable machines running on ESXi 3.5 (only u3) without problems.</description>
		<content:encoded><![CDATA[<p>Did you find the problem? I should add that I also have 7-stable machines running on ESXi 3.5 (only u3) without problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Some VMware ESXi post install notes by matt</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2009/02/17/some-vmware-esxi-post-install-notes/comment-page-1/#comment-1039</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Tue, 27 Oct 2009 15:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=73#comment-1039</guid>
		<description>For ESXi 4.0, the dhcp client changed - so for Step 2, use the below instead:

2) Create /tmp/oem/etc/rc.local.d/send-hostname:
if [ -r /var/run/dhcp-vmk0.pid ]; then
kill $(cat /var/run/dhcp-vmk0.pid)
/sbin/dhclient-uw -pf /var/run/dhcp-vmk0.pid -rt 90 -lf /var/lib/dhcp/dhclient-vmk0.leases -cf /etc/dhclient-vmk0.conf -4 -nw -d vmk0 -hn $(hostname)
fi</description>
		<content:encoded><![CDATA[<p>For ESXi 4.0, the dhcp client changed &#8211; so for Step 2, use the below instead:</p>
<p>2) Create /tmp/oem/etc/rc.local.d/send-hostname:<br />
if [ -r /var/run/dhcp-vmk0.pid ]; then<br />
kill $(cat /var/run/dhcp-vmk0.pid)<br />
/sbin/dhclient-uw -pf /var/run/dhcp-vmk0.pid -rt 90 -lf /var/lib/dhcp/dhclient-vmk0.leases -cf /etc/dhclient-vmk0.conf -4 -nw -d vmk0 -hn $(hostname)<br />
fi</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware ESXi on an HP Proliant ML115 G5 by Khairul Aizat Kamarudzzaman (fenris) 's status on Tuesday, 18-Aug-09 19:12:55 UTC - Identi.ca</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2008/11/11/vmware-esxi-on-an-hp-proliant-ml115-g5/comment-page-1/#comment-939</link>
		<dc:creator>Khairul Aizat Kamarudzzaman (fenris) 's status on Tuesday, 18-Aug-09 19:12:55 UTC - Identi.ca</dc:creator>
		<pubDate>Tue, 18 Aug 2009 19:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=13#comment-939</guid>
		<description>[...]  http://blogs.freebsdish.org/tmclaugh/2008/11/11/vmware-esxi-on-an-hp-proliant-ml115-g5/  [...]</description>
		<content:encoded><![CDATA[<p>[...]  <a href="http://blogs.freebsdish.org/tmclaugh/2008/11/11/vmware-esxi-on-an-hp-proliant-ml115-g5/" rel="nofollow">http://blogs.freebsdish.org/tmclaugh/2008/11/11/vmware-esxi-on-an-hp-proliant-ml115-g5/</a>  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Verizon FIOS Actiontec MI424WR and multiple subnets by Ben</title>
		<link>http://blogs.freebsdish.org/tmclaugh/2008/12/01/verizon-fios-actiontec-mi424wr-and-multiple-subnets/comment-page-1/#comment-923</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 03 Aug 2009 16:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/tmclaugh/?p=33#comment-923</guid>
		<description>I&#039;m having the same problem as Frank and Ike.  Anyone make any progress with this?  I&#039;d rather not go ahead and put the router into bridge mode.</description>
		<content:encoded><![CDATA[<p>I&#8217;m having the same problem as Frank and Ike.  Anyone make any progress with this?  I&#8217;d rather not go ahead and put the router into bridge mode.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
