Debian This forum is for the discussion of Debian Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-27-2005, 06:30 AM
|
#1
|
LQ Newbie
Registered: Jul 2004
Posts: 27
Rep:
|
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
|
|
|
09-27-2005, 11:00 AM
|
#2
|
Senior Member
Registered: Apr 2005
Location: Heaven
Distribution: Debian Sid/RPIOS
Posts: 4,919
|
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.
|
|
|
05-02-2007, 06:33 AM
|
#3
|
Member
Registered: Jan 2005
Location: Newcastle, Australia
Distribution: debian stable
Posts: 394
Rep:
|
Should I be listing etch or stable in my source.list. Slightly confused as I thought etch was stable, what difference am I getting ?
|
|
|
05-02-2007, 06:40 AM
|
#4
|
Senior Member
Registered: Dec 2005
Posts: 1,686
Rep: 
|
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
|
|
|
05-02-2007, 07:40 AM
|
#5
|
Member
Registered: Jan 2005
Location: Newcastle, Australia
Distribution: debian stable
Posts: 394
Rep:
|
Yeah was just a bit confused cause the mirrors featured both etch and stable which is like doubling up I thought.
|
|
|
05-02-2007, 09:41 PM
|
#6
|
LQ Guru
Registered: Oct 2003
Location: Bonaire, Leeuwarden
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,196
|
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
|
|
|
05-05-2007, 01:57 PM
|
#7
|
Member
Registered: Nov 2004
Location: Colorado
Distribution: Ubuntu mostly...
Posts: 100
Rep:
|
uh huh...
Quote:
Originally Posted by jlinkels
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
|
ya, what he said...
|
|
|
All times are GMT -5. The time now is 07:30 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|