DebianThis 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.
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.
DVD-1. The others are for offline installations of more than the base system.
Quote:
Will I need to edit the sources.list to ensure that the repo's say testing or will that already be the default after a fresh installation?
You will need to edit it, as by default those installs are for stable, aka jessie
Quote:
Are upgrades achieved during an update or do I need to run the upgrade cmd everyday/once a week?
apt update only updates the repositories, it doesn't actually install anything. When using testing, it's suggested you do a dist-upgrade, not an upgrade. This is due to the often changing nature of the testing repository. Also, make sure you're familiar with reading the latest notifications, as there are often broken packagges that could break the entire system.
Quote:
Have you ever had Debian Testing break and not be able to fix what was broken and had to perform a fresh install?
No, but I've had it break X or some other system leaving it mostly unusable for a week or 2 until it was sorted out or I found the fix.
Last edited by Timothy Miller; 08-30-2016 at 03:45 PM.
So replacing 'jessie' with 'testing' will solve that?
Or> do I need to enter the testing name which I think now is 'stretch'?
Either/or. 'stretch' would allow you to automatically transition to the stable environment when stretch was released, while 'testing' would make it into a semi-rolling release that would continue to track testing after stretch's release.
Using stretch is probably safer, as testing becomes extremely unstable a few months after a new release.
You only need the first disc. If you don't have any other discs, then any packages from the other discs will instead be downloaded from the repositories over the internet.
The install will have /etc/apt/sources.list point to the current testing branch (by default, it is by name - "stretch" rather than "testing", so when stretch gets officially released as "stable", your system will naturally transition to "stable").
By default, updates are initiated manually. You can do them as often or as infrequently as you like.
I used Debian Testing for a while because I wanted to use aufs and aufs was not in Stable at the time. I wasn't so happy with the experience, but this was more to do with the fact that I was using aufs in a way that wasn't really intended than problems with Debian Testing itself.
But generally, I think most people use either Debian Stable or Debian Unstable. Debian Stable is the one which will give you the least trouble, and Debian Unstable will at least have bugs sorted out quickly. Debian Testing is more of a proving ground for staging official releases. So, you have to be more patient to get the latest updates, as well as more patient to get fixes when something is broken (i.e. a package in a state where it won't install).
Basically, if down time is a real concern for you, just go with Debian Stable. If you're willing to sacrifice the risk of downtime for the latest versions of software, go with Debian Unstable. If you want to help the Debian project work out kinks for official releases, go with Debian Testing.
You only need the first disc. If you don't have any other discs, then any packages from the other discs will instead be downloaded from the repositories over the internet.
The install will have /etc/apt/sources.list point to the current testing branch (by default, it is by name - "stretch" rather than "testing", so when stretch gets officially released as "stable", your system will naturally transition to "stable").
By default, updates are initiated manually. You can do them as often or as infrequently as you like.
I used Debian Testing for a while because I wanted to use aufs and aufs was not in Stable at the time. I wasn't so happy with the experience, but this was more to do with the fact that I was using aufs in a way that wasn't really intended than problems with Debian Testing itself.
But generally, I think most people use either Debian Stable or Debian Unstable. Debian Stable is the one which will give you the least trouble, and Debian Unstable will at least have bugs sorted out quickly. Debian Testing is more of a proving ground for staging official releases. So, you have to be more patient to get the latest updates, as well as more patient to get fixes when something is broken (i.e. a package in a state where it won't install).
Basically, if down time is a real concern for you, just go with Debian Stable. If you're willing to sacrifice the risk of downtime for the latest versions of software, go with Debian Unstable. If you want to help the Debian project work out kinks for official releases, go with Debian Testing.
Thanks for the details IsaacKuo.
I appreciate that.
I'm off to read the documentation on Testing and Sid.
After reading I may consider stable after all but I like fixing things that get broken:-
If you like fixing things that are broken, then run sid and don't read the upgrade notifications before kicking off your upgrades. While it'll stay up and running for months at a time, it's guaranteed to break at least a few times a year.
If you like fixing things that are broken, then run sid and don't read the upgrade notifications before kicking off your upgrades. While it'll stay up and running for months at a time, it's guaranteed to break at least a few times a year.
Got it:- Thanks-
I'll decide after reading all of the Debian documentation on Sid and Testing.
Have you ran Sid and were you successful with fixes?
Got it:- Thanks-
I'll decide after reading all of the Debian documentation on Sid and Testing.
Have you ran Sid and were you successful with fixes?
I usually run testing, but I've ran sid also quite a bit. If you're good about proactively reading the notifications BEFORE kicking off upgrades, then you can run it for years without issues. My one machine has been runnig testing since jessie was released, and it's never broken because I actually read the upgrade warnings and hold off when there are major showstopper issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.