|
| Home | Accessibility | Courses | Diary | The Mouth | Forum | Resources | Site Map | About Us | Contact |
|
Linux / Unix - layout of operating system files
At the top level .. Typically "read only" bin - binaries - executable programs sbin - system admin binaries - programs for the system / admin lib - library files (needed by binaries and shared between them) usr - the bulk of the operating system (the bit that is not needed to boot) Typically "read write" by admin or system dev - device files (how devices are handled) etc - config files, startup files, etc proc - "everything is a file" in 'nix - these are the current processes var - read/write area for OS utilities / daemons Open Season! home - User's home directories and typically data areas mnt - Mounts of discs from other computers (also media) tmp - scratch area for anyone / everyone In /usr - this is where parts that are NOT needed at boot up time are kept bin - binaries - executable programs sbin - system admin binaries - programs for the system / admin lib - library files (needed by binaries and shared between them) include - "Programmer's header files" share - things common between architectures etc - config files, startup files, etc src - source man - manual local - local enhancements to OS - i.e. extra software you load (also /opt) In /usr/local - this is where your own local additions are kept bin - binaries - executable programs sbin - system admin binaries - programs for the system / admin lib - library files (needed by binaries and shared between them) include - "Programmer's header files" share - things common between architectures etc - config files, startup files, etc and others which are complete apps In /usr/local/apache2 (for example) - this is within a particular open source product bin - binaries - executable programs lib - library files (needed by binaries and shared between them) logs - log files man - unix man pages modules - extra code modules (similar to lib) conf - configuration stuff in this case ... web site at htdocs, icons, cgi-bin, manual etc Ever wondered why the executables are mixed /bin, /sbin, /usr/bin, /usr/sbin, /usr/local/bin, /usr/local/apache2/bin, /usr/local/java/bin and so on ... perhaps the table above helps explain it a bit! (written 2007-11-20 12:12:56) Associated topics are indexed under A162 - Web Application Deployment - Backups and File System Management
Some other Articles
Christmas is coming very earlyReading a file multiple times - file pointers On cancellations, rebooking, and pricing schemes Useful command or messy screen? Linux / Unix - layout of operating system files Copy and paste / cut and paste and other vi techniques Above the fold with First Great Western A little touring help during a business trip to England Object Oriented Programming in Perl - Course Market survey - to learn, to prove a point, or to sell your product? |
1892 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38 at 50 posts per pageThis is a page archived from The Horse's Mouth at http://www.wellho.net/horse/ - the diary and writings of Graham Ellis. Every attempt was made to provide current information at the time the page was written, but things do move forward in our business - new software releases, price changes, new techniques. Please check back via our main site for current courses, prices, versions, etc - any mention of a price in "The Horse's Mouth" cannot be taken as an offer to supply at that price.
Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).
PH: 0800 043 8225 or 01225 708225 • FAX: 0845 8382 405 or 01225 707126 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho