Am 06.02.2015 um 01:55 schrieb Martin Gregorie:
On Fri, 2015-02-06 at 00:38 +0100, Reindl Harald wrote:you did not get the point there is also /usr/local/bin, /usr/local/sbin and so onYou don't. You avoid name and version clashes by NOT putting distro packages on /usr/local and ONLY putting local and 3rd party developed non-standard software in /usr/local. Haven't you been paying attention?
no idea what *you* are talking abouti talk about UsrMove and why they did /bin -> /usr/bin and not the other way round and if you would not strip away all the context you may have not lost the track while reply
IMO any properly configured system does that and also: - includes the /usr/local/* hierarchy in PATH and its chums - makes a habit of putting config files for non-standard software in /usr/local/etc* and writing it to search ., /usr/local/etc and /etc in that order for its config files.where do you move them in case of a migration?Personally, long ago I did: mkdir /home/local mv /usr/local /home/local ln -s /home/local /usr/local
what has that to do with UsrMove?
where /home is a separate partition that is never reformatted (unless the disk needs replacing). What do you do? Seeing that you have quite a farm I think I'd expect to find /usr/local mapped to some central, mirrored disk array for easy maintenance./local/bin and /local/sbin is far away from any FHS anything refer /usr/local would break unconditionallyYep, and that would seem to be a sensible way to go, but then I think this sort of separation between vanilla distro packages and 'the rest' makes sense. YMMV, but I'd be interested to know why
you better step back what we talked about.....
signature.asc
Description: OpenPGP digital signature
