<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 23, 2009, at 10:24 PM, <<a href="mailto:dmcnash@charter.net">dmcnash@charter.net</a>> <<a href="mailto:dmcnash@charter.net">dmcnash@charter.net</a>> wrote:</div><blockquote type="cite"><div>I changed the sources.list to the from<br>deb <a href="http://ftp.gtlib.gatech.edu/debian/">http://ftp.gtlib.gatech.edu/debian/</a> etch main non-free contrib<br>to<br>deb <a href="http://http.us.debian.org/debian">http://http.us.debian.org/debian</a> stable main contrib non-free<br><br>and ran apt-get update;apt-get update<br><br>so the update from etch to lenny is in progress. I assume I will be back in business soon.<br><br>I guess the etch in the first line should be stable (not etch) or on change over to a new major release things break. <br></div></blockquote></div><br><div>Without going into to much detail, there are times when you want to specifically define the release you want instead of defaulting to stable. Otherwise, you may find yourself faced with doing an impromptu OS upgrade when you didn't really mean to. Most of the time, this isn't a big issue, but for some installs, it can break things to the point where you have to get down and dirty with dpkg to make everything play nice again. If this happens in the middle of the customers peak business hours, they tend to be very unhappy about it.</div><div><br></div></body></html>