{"id":91,"date":"2006-01-03T17:53:01","date_gmt":"2006-01-04T01:53:01","guid":{"rendered":"http:\/\/www.laurenwood.org\/anyway\/?p=91"},"modified":"2007-09-30T11:35:16","modified_gmt":"2007-09-30T18:35:16","slug":"woody-to-sarge","status":"publish","type":"post","link":"https:\/\/www.laurenwood.org\/anyway\/2006\/01\/woody-to-sarge\/","title":{"rendered":"Woody to Sarge"},"content":{"rendered":"

Ive been intend\u00ading on upgrad\u00ading my Debi\u00adan firewall\/blog box to the latest ver\u00adsion, called \u2018sarge\u2019 (a.k.a 3.1) for some months now. Today was the day I decided to finally bite the bul\u00adlet. Since I\u2019ve been using back\u00adports of unstable<\/em> ver\u00adsions of soft\u00adware, such as MySQL (see Upgrad\u00ading MySQL on Debi\u00adan<\/a> for that pro\u00adcess, and Enabling Thumb\u00adnails<\/a> for the pro\u00adcess to upgrade libgd) I figured this could be a little trick\u00adi\u00ader than I really like, and I should be pre\u00adpared. Here\u2019s the his\u00adtor\u00adic\u00adal record of actu\u00adally get\u00adting it run\u00adning. YMMV<\/span>, of course!<\/p>\n

First, the doc\u00adu\u00adment\u00ada\u00adtion on the Debi\u00adan web site is good. The upgrad\u00ading instruc\u00adtions<\/a> are writ\u00adten per hard\u00adware plat\u00adform and seem com\u00adplete. I star\u00adted, as recom\u00admen\u00added in Upgrad\u00ading your Woody sys\u00adtem<\/a> by repla\u00adcing the word \u201cstable\u201d in the \/etc\/apt\/sources.list<\/code> file with the word \u201cwoody\u201d and then check\u00ading I had woody\u2019s ver\u00adsion of aptitude installed.<\/p>\n

After copy\u00ading the recom\u00admen\u00added files to a safe loc\u00ada\u00adtion (that\u2019s a lot of files!), I deleted the \/etc\/preferences<\/code> file after sav\u00ading a copy \u2014 this is the file that says which ver\u00adsions of any soft\u00adware to use. Since to begin with I want to use a clean, stand\u00adard Debi\u00adan sarge dis\u00adtri\u00adbu\u00adtion, I don\u2019t need this file. Then it was on to sec\u00adtion 4.2.2, \u201cCheck\u00ading pack\u00adages status\u201d. I found that apt-get showed no holds, but aptitude showed that php4 was on hold (I can\u00ad\u2019t ima\u00adgine why). So I got rid of the hold.<\/p>\n

After that, I just fol\u00adlowed the steps, tak\u00ading the defaults mostly (since I did\u00adn\u2019t under\u00adstand some of the ques\u00adtions, that was an easy choice! One day I might under\u00adstand what pango and defoma are all about, but in the mean\u00adtime I\u2019ve decided not to both\u00ader). There were a couple of mes\u00adsages that mostly seemed ignor\u00adable (note to self: upgrade exim3 to exim4 at some stage in the future) and all in all the pro\u00adcess ran smoothly, if not par\u00adtic\u00adu\u00adlarly fast on my old, slow Pen\u00adti\u00adum box. <\/p>\n

Time to check the res\u00adults \u2014 try my web site and find it\u2019s been replaced by a gen\u00ader\u00adic \u201cwel\u00adcome to an Apache web site\u201d mes\u00adsage. The web serv\u00ader has been magic\u00adally upgraded to Apache 2.0, which I had\u00adn\u2019t quite expec\u00adted or planned for. Oh well, time to hit the Apache documentation.<\/p>\n

There\u2019s a big dif\u00adfer\u00adence between Debi\u00adan upgrade doc\u00adu\u00adment\u00ada\u00adtion and Apache upgrade doc\u00adu\u00adment\u00ada\u00adtion. Where the Debi\u00adan upgrade instruc\u00adtions are exactly that (\u201cDo this, then this. Run this com\u00admand and if you get this out\u00adput, do this, oth\u00ader\u00adwise do that\u201d), the Apache doc\u00adu\u00adment\u00ada\u00adtion on Upgrad\u00ading to 2.0 from 1.3<\/a> is basic\u00adally a list of fea\u00adture changes, rather than instruc\u00adtions on how to upgrade or what modi\u00adfic\u00ada\u00adtions need to be made to the con\u00adfig\u00adur\u00ada\u00adtion files. Look\u00ading at the con\u00adfig\u00adur\u00ada\u00adtion files them\u00adselves in the Debi\u00adan Sarge Apache 2 dis\u00adtri\u00adbu\u00adtion you can see, for example, that httpd.conf<\/em> has changed markedly from being the main con\u00adfig\u00adur\u00ada\u00adtion file to con\u00adtain\u00ading simply a com\u00adment say\u00ading it exists for back\u00adwards com\u00adpat\u00adib\u00adil\u00adity only. The README<\/span> file does have some clues to the new files, with short descrip\u00adtions of what they\u2019re used for. The most inter\u00adest\u00ading new dir\u00adect\u00adory to me was sites-enabled<\/em>, which seemed to have some\u00adthing to do with set\u00adting up vir\u00adtu\u00adal hosts. So I typed sites-enabled<\/em> into the Apache doc\u00adu\u00adment\u00ada\u00adtion search engine and found no hits what\u00adso\u00adever. The Vir\u00adtu\u00adal\u00adHost part of the doc\u00adu\u00adment\u00ada\u00adtion for Apache 2.0 says \u201cBelow is a list of doc\u00adu\u00adment\u00ada\u00adtion pages which explain all details of vir\u00adtu\u00adal host sup\u00adport in Apache ver\u00adsion 1.3 and later.\u201d Hmmm, things do seem to have changed some\u00adwhat between Apache 1.3 and Apache 2.0. On the oth\u00ader hand, it\u2019s always pos\u00adsible that this par\u00adtic\u00adu\u00adlar con\u00adfig\u00adur\u00ada\u00adtion and choice of dir\u00adect\u00adory names etc is due to Debi\u00adan rather than Apache; the Debi\u00adan dis\u00adtri\u00adbu\u00adtions do have a repu\u00adta\u00adtion for put\u00adting files in places that are unex\u00adpec\u00adted and maybe this has exten\u00added to the names used in the Debi\u00adan fla\u00advour of the Apache install\u00ada\u00adtions. If this is the case it\u2019s not sur\u00adpris\u00ading it isn\u2019t doc\u00adu\u00admented on the Apache web site.<\/p>\n

For\u00adtu\u00adnately oth\u00aders have writ\u00adten this up; I found Upgrad\u00ading to Apache 2<\/a> which described the pur\u00adpose of the sites-enabled<\/em> and sites-avail\u00adable<\/em> dir\u00adect\u00ador\u00adies in ways that make sense and worked when I tried them out. The same prin\u00adciples apply to mak\u00ading the mod_rewrite<\/em> mod\u00adule avail\u00adable, which Word\u00adPress uses for rewrit\u00ading the URLs for archives and categories.<\/p>\n

So far, so good. My web site is avail\u00adable again, just not my blog. The error mes\u00adsage is \u201cYour PHP<\/span> install\u00ada\u00adtion appears to be miss\u00ading the MySQL which is required for Word\u00adPress\u201d. When I check, all the neces\u00adsary pack\u00adages are installed. A quick search through the Word\u00adPress sup\u00adport site<\/a> turns up that I\u2019ve for\u00adgot\u00adten to uncom\u00adment the MySQL mod\u00adule in the php.ini<\/em> file. I\u2019m so used to Debi\u00adan just doing the right thing that it seems odd to have to make that change, some\u00adhow. Now my blog is back as well, everything else seems to be work\u00ading, no files seem to have been lost, and over\u00adall the upgrade was a lot less pain\u00adful than I had anticipated.<\/p>\n","protected":false},"excerpt":{"rendered":"

Ive been intend\u00ading on upgrad\u00ading my Debi\u00adan firewall\/blog box to the latest ver\u00adsion, called \u2018sarge\u2019 (a.k.a 3.1) for some months now. Today was the day I decided to finally bite the bul\u00adlet. Since I\u2019ve been using back\u00adports of unstable ver\u00adsions of soft\u00adware, such as MySQL (see Upgrad\u00ading MySQL on Debi\u00adan for that pro\u00adcess, and Enabling \u2026 Con\u00adtin\u00adue read\u00ading \u201cWoody to Sarge\u201d<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":3,"activitypub_interaction_policy_quote":"","activitypub_status":"","footnotes":""},"categories":[6,4],"tags":[],"class_list":["post-91","post","type-post","status-publish","format-standard","hentry","category-technology","category-wp-mechanics"],"_links":{"self":[{"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/posts\/91","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/comments?post=91"}],"version-history":[{"count":0,"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/posts\/91\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/media?parent=91"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/categories?post=91"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.laurenwood.org\/anyway\/wp-json\/wp\/v2\/tags?post=91"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}