<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Install &#8211; Harry Jackson</title>
	<atom:link href="http://127.0.0.1:8090/tag/install/feed" rel="self" type="application/rss+xml" />
	<link>http://127.0.0.1:8090</link>
	<description>Parent, Painter, Programmer</description>
	<lastBuildDate>Sat, 11 Jun 2005 06:06:04 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>Upgrading Woody to Sarge</title>
		<link>http://127.0.0.1:8090/upgrading_woody_to_sarge.htm</link>
					<comments>http://127.0.0.1:8090/upgrading_woody_to_sarge.htm#respond</comments>
		
		<dc:creator><![CDATA[harry]]></dc:creator>
		<pubDate>Sat, 11 Jun 2005 06:06:04 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Install]]></category>
		<guid isPermaLink="false">http://www.hjackson.org/wp/?p=273</guid>

					<description><![CDATA[Debian have just released sarge as the new stable distribution which means I need to start upgrading my machines. Before I upgraded the main machine though I decided to run through it on a UML machine first to see where the gotchas are. Things to watch out for 1. The sshd config file gets an &#8230; <p class="link-more"><a href="http://127.0.0.1:8090/upgrading_woody_to_sarge.htm" class="more-link">Continue reading<span class="screen-reader-text"> "Upgrading Woody to Sarge"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>Debian have just released sarge as the new stable distribution which means I need to start upgrading my machines. Before I upgraded the main machine though I decided to run through it on a UML machine first to see where the gotchas are.<br />
Things to watch out for<br />
1. The sshd config file gets an extra parameter added to it ie.<br />
UsePAM yes<br />
When I tested ssh after the upgrade I was unable to log into the machine and I found that I had to remove this option or set it to &#8220;no&#8221; to get ssh to work. This surprised me because I was not expecting Debian to modify config file without my knowledge.<br />
2. The <b>RECORD</b> option is no longer valid<br />
xinetd[5691]: Bad log_on_failure flag: RECORD [file=/etc/xinetd.conf] [line=13]<br />
xinetd[5691]: A fatal error was encountered while parsing the default section. xinetd will exit.<br />
xinetd[5691]: Exiting&#8230;<br />
this prevents xinetd from starting up. This was also noticed while testing the machine after the upgrade.<br />
What follows is roughly the files the upgrade offered to update to new versions. Since I had modified most of these I selected the default option which is &#8220;N&#8221; ie do not upgrade to the maintainers version. This may have been the reason the ssh upgrade wasn&#8217;t too smooth. However I would not recommend taking the maintainers version if you have customized the files.<br />
Configuration file `/etc/pam.d/login&#8217;<br />
Configuration file `/etc/securetty&#8217;<br />
Configuration file `/etc/pam.d/passwd&#8217;<br />
Configuration file `/etc/bash.bashrc&#8217;<br />
Configuration file `/etc/init.d/sysklogd&#8217;<br />
Configuration file `/etc/services&#8217;<br />
Configuration file `/etc/init.d/bind9&#8242;<br />
Configuration file `/etc/bind/named.conf&#8217;<br />
Configuration file `/etc/bind/db.root&#8217;<br />
Configuration file `/etc/init.d/xinetd&#8217;<br />
Configuration file `/etc/xinetd.conf&#8217;<br />
During the upgrade you may also be asked to add any users and groups that are<br />
missing from the default debian lot. The following bits are just the output of some other configurations options and warnings of things that have changed between the woody and sarge.<br />
Configuring ssh<br />
Environment options on keys have been deprecated This version of OpenSSH<br />
disables the environment option for public keys by default, in order to avoid<br />
certain attacks (for example, LD_PRELOAD). If you are using this option in an<br />
authorized_keys file, beware that the keys in question will no longer work<br />
until the option is removed. To re-enable this option, set<br />
&#8220;PermitUserEnvironment yes&#8221; in /etc/ssh/sshd_config after the upgrade is<br />
complete, taking note of the warning in the sshd_config(5) manual page.</p>
<p>Configuring man-db<br />
This version of man-db is incompatible with your existing database of manual<br />
page descriptions, so that database needs to be x rebuilt. This may take some<br />
time, depending on how many pages you have installed; it will happen in the<br />
background, possibly slowing down the installation of other packages. If you do<br />
not build the database now, it will be built the next time<br />
/etc/cron.weekly/mandb runs, or you can do it yourself using &#8216;mandb -c&#8217; as user<br />
&#8216;man&#8217;. In the meantime, the &#8216;whatis&#8217; and &#8216;apropos&#8217; commands will not be able to<br />
display any output. Incompatible changes like this should happen rarely. Should<br />
mandb build its database now?</p>
<p>So far I have upgraded two machines and had the same trouble with ssh and xinetd both times. If I encounter any mmore trouble I will add more here.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://127.0.0.1:8090/upgrading_woody_to_sarge.htm/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>AMD64 and MSI K8T</title>
		<link>http://127.0.0.1:8090/amd64_and_msi_k8t.htm</link>
					<comments>http://127.0.0.1:8090/amd64_and_msi_k8t.htm#comments</comments>
		
		<dc:creator><![CDATA[harry]]></dc:creator>
		<pubDate>Sun, 18 Apr 2004 05:48:45 +0000</pubDate>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Install]]></category>
		<category><![CDATA[Nvidia]]></category>
		<guid isPermaLink="false">http://www.hjackson.org/wp/?p=96</guid>

					<description><![CDATA[Well, I got the AMD64 today and got it all put together with a few little mishaps. I am using an MSI K8T Neo motherboard which was bought simply because I couldn&#8217;t wait 5 days for the Asus which I would have preferred simply because it can take an extra gig of RAM over the &#8230; <p class="link-more"><a href="http://127.0.0.1:8090/amd64_and_msi_k8t.htm" class="more-link">Continue reading<span class="screen-reader-text"> "AMD64 and MSI K8T"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>Well, I got the AMD64 today and got it all put together with a few little mishaps. I am using an MSI K8T Neo motherboard which was bought simply because I couldn&#8217;t wait 5 days for the Asus which I would have preferred simply because it can take an extra gig of RAM over the MSI. I also had a problem with the power supply that was in the tower. Who would have thought that an ATX power supply wouldn&#8217;t have the proper 4 pin connector required to power the chip. I ripped Jen&#8217;s power supply out and used it. I can now safely say that an AMD 64 with 1 SATA 160Gb two 20Gb hard disks, CD player and 32Mb nvidia video card will run on a 300Watt power supply or at least it will on mine. I will be ordering a bigger quieter one but more on that later.<br />
I uses an old netinst CD that I had laying around to put woody on and the immediately upgraded to sarge. All this went with very little mishap and so far the hardware has been running fine. All I need now is SATA support, I&#8217;ll do that tomorrow.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://127.0.0.1:8090/amd64_and_msi_k8t.htm/feed</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
