Need Recommendation for Debian Etch sources.list ( /etc/apt/sources.list )
Hi,
Is there any recommendation for Debian Etch /etc/apt/sources.list files. If you would like to have Etch + non-US content + latest security update, would the source.list file below be working? Is there a better source.list? # cat /etc/apt/sources.list deb http://http.us.debian.org/debian testing main non-free contrib deb http://non-us.debian.org/debian-non-US sarge/non-US main non-free contrib deb http://security.debian.org/ stable/updates main contrib non-free thanks |
non-us is obsolete, when Sarge went stable the content was moved into main.
From what I understand Testing/etch has security updates now. Take a look at the sources.lits in my sig. |
Should I be listing etch or stable in my source.list. Slightly confused as I thought etch was stable, what difference am I getting ?
|
Etch=Stable. Sarge is oldstable. Woody is obsolete, Lenny is the new Testing.
^^^this is a mathematical equation ;) For suitable contents of your sources.list, look here: http://www.linuxquestions.org/questi...d.php?t=330913 |
Yeah was just a bit confused cause the mirrors featured both etch and stable which is like doubling up I thought.
|
It depends on your needs. If you want to run stable forever, you use "stable". As soon as a new version gets into stable, you will be updated. And you'll still be running stable.
In some of my desktop machines I use "testing". I will always have the testing version regardless of what the current name is. However, there *are* some issues with unexpected upgrades, even if they are in stable. That's why for example I use "Sarge" in my production servers. Only when I am ready I will install "Etch", taking into account that things might crash. Usually it means that I install a new server. On a desktop machine you can tolerate that. Not on a production server. I admit, it is extreme flexibility. jlinkels |
uh huh...
Quote:
|
All times are GMT -5. The time now is 07:03 AM. |