What standards should one adhere to when tailoring their install in order to keep an upgrade course?
In the past, I've gone hog wild tailoring my Ubuntu installment, just to be incapable to upgrade it once the moment came. So just how does one deal with tailoring their install without facing concerns updating? Is it feasible to do so without counting only on the Ubuntu databases for software program?
One vital consider making upgrades run smooth is not to do anything which perplexes the plan supervisor. That is, you should not on your own touch locations of the system which the plan supervisor anticipate to be its domain name. A couple of concrete instances.
If you compile/install programs on your own making use of the./ set up ; make ; make install method, do not place them straight under
/usr. It is far better to make use of
/opt, conversely (also much better) to roll your very own deborah plans.
When you remove plans you can either do a regular elimination or a specific cleanup. Unless you remove the plan the plan supervisor could leave documents behind under
/var and more. Do not delete these documents on your own, as the plan supervisor anticipates them to be there. Rather utilize your plan supervisor to clearly remove the remains of the plan.
Making use of deborah plan from 3rd party databases need to in theory be secure, thinking they are meticulously constructed etc Yet, to be on the secure side you could intend to take into consideration getting rid of those plans and/or databases prior to you execute an upgrade to a new Ubuntu release.
Ok, allow me see if I can add some even more meat to this solution ...
First of all, every little thing you carry out in your residence directory site is flawlessly secure in relation to the plan supervisor. It will certainly never ever touch anything under
(Of training course, you can still create on your own a lot of complication by doing negative point to your residence directory site. The good news is that is generally be recouped from by getting rid of the busted configuration documents from your residence directory site, and also allow them be re - developed from default at the next usage. Do note that the automated re - production of default config just goes with your individual configuration documents, not the system vast things under
In the duty of a (power) desktop computer customer I presume one of the most usual system vast creative thinking will be mounting added applications, collections, emacs settings, etc? Once more, the actually integral part is to constantly place none deborah plan things under
/usr/local as opposed to under
/usr ; to make use of
/usr/local/bin as opposed to
/usr/bin, to make use of
/usr/local/share/emacs/23.1 as opposed to
/usr/share/emacs/23.1 and more.
As soon as you start experimenting with server daemons you will certainly quickly be challenged by the system vast configuration under
/etc. While you usually can change documents under
/etc, you need to "never ever" in fact remove a documents or a directory site there, unless it was you that developed it on your own. Furthermore need to you take care concerning on your own developing new documents therein, in instance they would certainly later ram a configuration documents the plan supervisor intend to create. That being claimed, there are most definitely documents which you can (and also need to) be developed under
/etc. On of the extra usual instances is specifying your Apache VirtualHosts under
There could be times when you desire create documents or directory sites under
/var. While it is an entirely various area than
/etc, still take into consideration the very same regulations concerning taking care and also doing points on specific factor to consider.
In instance you need to know extra, it will not injure you to take a peek at the Filesystem Hierarchy Standard (FHS) or in the Debian Policy Manual. While it could be entirely excessive in addressing your initial inquiry, it is still an excellent read.