Chris's Wiki :: blog/unix/BinDirectoryOrigins Commentshttps://utcc.utoronto.ca/~cks/space/blog/unix/BinDirectoryOrigins?atomcommentsDWiki2009-03-12T05:06:10ZRecent comments in Chris's Wiki :: blog/unix/BinDirectoryOrigins.By Chris Siebenmann on /blog/unix/BinDirectoryOriginstag:CSpace:blog/unix/BinDirectoryOrigins:62ea65f7a64e802cf0199194a8528a7ecc61b565Chris Siebenmann<div class="wikitext"><p>Department of very belated replies: although I can't tell if early versions
of SunOS did it this way, you don't need to have <code>/usr</code> mounted to
use dynamically linked executables. All you have to do is put the
core dynamically linked libraries in <code>/lib</code> instead of <code>/usr/lib</code>.</p>
<p>(This is what pretty much everyone does these days.)</p>
</div>2009-03-12T05:06:10ZFrom 164.55.254.106 on /blog/unix/BinDirectoryOriginstag:CSpace:blog/unix/BinDirectoryOrigins:69296e9c0618fd31532ef200f135d89d1bc648d0From 164.55.254.106<div class="wikitext"><p>sbin originated when shared libs came about. When booting, the shared libs in /usr/lib might not be mounted yet and you need a statically linked version of the program to get something to run. Hence sbin, which had only statically linked binaries in it.</p>
</div>2008-10-02T20:38:54Z