<br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 4:37 PM, Scott Castaline <span dir="ltr"><<a href="mailto:hscast@charter.net">hscast@charter.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div>Yep, here we go again back in the olden days. We used to (dating back to<br>
the early 80's) made separate partitions as follows:<br>
/<br>
/boot<br>
/tmp<br>
/var<br>
/usr<br>
/usr/home<br>
/use/local<br>
<div><div></div></div></blockquote><div><br>And back before that each _file_ was on a separate line in core.... <br><br>oh. <br><br>Real stuff: Most current distros have so much stuff that very little is handled outside of the distro packaging. That said, the need still exists. The file-system group decreed a while back that /usr/local was the place to install admin compiled binaries built from source, /opt was where pre-compiled binaries NOT part of the distro packaging was to go, and /opt _can_ also be used for admin-compiled binaries. <br>
<br>Here's the thing, by placing the custom stuff in /usr/local and /opt, distro upgrades will not directly affect the custom app. However, a full system upgrade (version foo -> version bar) with a ritual unmounting of the/usr/local and /opt directories will probably be a problem for the compiled binaries in those directories as the core libs on the system may change during the upgrade. It is still a good idea to put all non-distro stuff either in /opt or /usr/local .<br>
<br>Of course a bit of package seeking may be a good choice as well.<br></div></div><br clear="all"><br>-- <br>-- <br>James P. Kinney III <br><br>