{
	"id": "bceb0acf-2189-47d0-ba33-efa2507aeb9d",
	"created_at": "2026-04-06T00:16:05.471204Z",
	"updated_at": "2026-04-10T13:12:30.18813Z",
	"deleted_at": null,
	"sha1_hash": "ac09612e4de92769cf7f0b0bbeb25cfb5f612668",
	"title": "CodeBuilder User's Guide - 6.0 File Systems",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 118177,
	"plain_text": "CodeBuilder User's Guide - 6.0 File Systems\r\nArchived: 2026-04-05 22:01:56 UTC\r\n6.0 The CodeBuilder File Systems\r\n6.1 UNIX Fast File System Overview\r\n6.1.1 File System Organization\r\n6.1.2 File Names\r\n6.1.3 Access Permissions\r\n6.1.4 Time Stamps\r\n6.1.5 Link Counts\r\n6.1.6 Hard Links\r\n6.1.7 Symbolic Links\r\n6.2 Macintosh Hierarchical File System Overview\r\n6.2.1 File System Organization\r\n6.2.2 File Names\r\n6.2.3 Access Permissions\r\n6.2.4 Time Stamps\r\n6.2.5 Aliases\r\n6.3 CodeBuilder FFS\r\n6.3.1 FFS Within a File\r\n6.3.2 FFS Within a Partition\r\n6.4 CodeBuilder UFS\r\n6.4.1 File Names\r\n6.4.1.1 Maximum Number of Characters\r\n6.4.1.2 Case Sensitive File Names\r\n6.4.1.3 Component Separators\r\n6.4.1.4 Non-Printable Characters\r\n6.4.2 Linked Files\r\n6.4.2.1 Hard Links\r\n6.4.3 Directory Link Counts\r\n6.4.4 Locked Files\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 1 of 14\n\n6.4.5 File Types\r\n6.4.6 File Permissions\r\n6.4.7 Time Stamps\r\n6.5 CodeBuilder Root File System Layout\r\n6.5.1 The root Directory Tree\r\n6.5.2 The usr Directory Tree\r\n6.5.3 The var Directory Tree\r\n6.5.4 Major System Administration Files\r\nChapter 6.0 continues...\r\nIn the traditional UNIX world, disks are devices that can be formatted into file systems and mounted for access by\r\nUNIX applications. In the Macintosh world, disks are called volumes. The Macintosh File Manager is the entity\r\nresponsible for formatting disks into volumes and controlling access to the files on those volumes. CodeBuilder\r\naugments the MacOS HFS file system with two UNIX file system implementations, a native fast file system (FFS)\r\nand a UNIX file system that sits on top of the MacOS HFS (UFS).\r\nThe first, known as FFS, implements a traditional native UNIX fast file system either within a single Macintosh\r\nfile or in a SCSI disk partition. There is no need to reformat or partition a volume to create a FFS within a file, but\r\nthat will be necessary for FFS on a partition. For an FFS within a file, CodeBuilder continues to use the services\r\nof the Macintosh File Manager, but only for basic I/O operations. For an FFS on a partition, CodeBuilder interacts\r\ndirectly with the Macintosh SCSI Manager. Macintosh files may be stored on an FFS, but they are not available\r\nfor access by Macintosh applications. A future extension of FFS will permit desktop mounting and use by\r\nMacintosh applications.\r\nThe second file system, known as UFS, implements the UNIX file system on top of the Macintosh hierarchical\r\nfile system. CodeBuilder imposes UNIX file system semantics on the Macintosh by mapping the UNIX file\r\nsystem requests onto the appropriate Macintosh File Manager routines. UNIX files are stored alongside Macintosh\r\nfiles, so there is no requirement to reformat/partition existing HFS volumes.\r\n6.1 UNIX Fast File System Overview\r\nCodeBuilder's FFS is derived from the Berkeley BSD UNIX high-performance file system. It is a simple and\r\nelegant file system that has its roots in the original UNIX file system developed at Bell Labs. Detailed information\r\nmay be found in two supplementary documents: (1) A Fast File System for UNIX, and (2) Fsck - The UNIX File\r\nSystem Check Program. These are located in the Documentation folder under /CodeBuilder UNIX Docs/Sys\r\nAdmin's Docs (SMM)/fastfs.pdf or fsck.pdf.\r\n6.1.1 File System Organization\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 2 of 14\n\nUNIX disks are divided into one or more partitions. Each partition may contain one file system, and a file system\r\nnever spans multiple partitions. Critical file system sizing parameters are stored in a super-block, which is\r\nreplicated to protect against catastrophic loss.\r\nThe file system stores files. Certain files are designated as directories which contain pointers to other files, some\r\nof which may be other directory files. Every file has an associated descriptor called an inode, which contains\r\nownership, permissions, time stamps, and pointers to assigned data blocks.\r\nA disk partition is divided into one or more areas called cylinder groups. A small percentage of each cylinder\r\ngroup is taken for some bookkeeping information, including a redundant copy of the super-block, inode slots, a\r\nbitmap of available data blocks, and data block usage summary information. A static number of inodes is allocated\r\nwhen the file system is created. The default policy is to create one inode per 2048 bytes of space in the cylinder\r\ngroup, which is expected to be far more than will be needed.\r\nUNIX files are a single stream of bytes, with no operating system imposed format. Text files use the ASCII 'LF'\r\ncharacter ('\\n') to denote an end-of-line. Binary files often begin with a four byte code identifying the format of the\r\ndata that follows.\r\n6.1.2 File Names\r\nUNIX file and directory names are limited to 255 characters. MacOS file names are limited to 31 characters.\r\nNames may not include the '/' character because it is used in pathnames to separate directory and file name\r\ncomponents. An absolute pathname begins with a '/'; anything else is relative to the current working directory.\r\nName matching is case sensitive. (MacOS file names are NOT case sensitive, however Tenon's extension enables\r\ncase sensitivity in Tenon's UFS file system.)\r\n6.1.3 Access Permissions\r\nUNIX file and directory access rights are divided into read, write, and execute permissions. Read permission\r\nallows a user to examine the contents of a file. Write permission allows a user to change or append data to a file.\r\nExecute permission for binary files allows a user to execute the file as a program, and for directories allows a user\r\nto search the directory. Each file and directory is tagged with a user and group ID. Three levels of permissions are\r\nspecified, one for the owner of a file, a second for the members of the designated group, and a third for \"everyone\r\nelse\".\r\n6.1.4 Time Stamps\r\nUNIX saves three time stamps for each file: (1) the time the file's data was modified, (2) the time the file's\r\nattributes were last modified, and (3) the time the file was last accessed (i.e. the data was read).\r\n6.1.5 Link Counts\r\nPhysical files are uniquely identified by their inode, but they may be identified by multiple names. The link count\r\nis simply the number of references to an inode.\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 3 of 14\n\n6.1.6 Hard Links\r\nThe mapping of a file name in a directory to an inode is known as a hard link. Hard links are not allowed to cross\r\nfile system boundaries.\r\n6.1.7 Symbolic Links\r\nSymbolic links are special files whose content is the pathname of the intended file or directory. The pathname may\r\nbe absolute or relative, and may refer to other file systems. Symbolic links may point to other symbolic links.\r\n6.2 Macintosh Hierarchical File System Overview\r\nThe MacOS method of organizing files is known as the hierarchical file system (HFS). Detailed information about\r\nthe Macintosh file system and File Manager may be found in the Files manual which is part of the Inside\r\nMacintosh documentation series, published by Addison-Wesley.\r\n6.2.1 File System Organization\r\nEach Macintosh hard disk is formatted into a number of 512-byte addressable units known as logical blocks. A\r\nvolume is a consecutive sequence of these blocks. Small disks are typically used whole as a single volume, while\r\nlarge disks are often partitioned into two or more volumes.\r\nA volume consists of overhead, file storage, and free space. The overhead includes boot blocks, bitmap, master\r\ndirectory blocks, catalog and extents files. The catalog file maintains the hierarchy of directories and files on a\r\nvolume, and the extents overflow file tracks assignment of allocation blocks to files which cannot be stored in the\r\ncatalog file. File storage is assigned in units of allocation blocks, which are one or more consecutive logical\r\nblocks. A volume has at most 65,536 allocation blocks. This addressing constraint dictates the ratio of logical\r\nblocks to an allocation block. Files are stored in directories (also known as folders), which are themselves stored\r\nin directories. Each directory and file is assigned an integer ID which uniquely identifies it on a given volume.\r\nEvery volume has a top directory known as the root directory, with a directory ID of 2. When a volume is\r\nmounted for use, the MacOS assigns a volume reference number which remains valid as long as the volume is\r\nmounted. Macintosh files are uniquely specified with a volume reference number, a parent directory ID, and a file\r\nname.\r\nA Macintosh file has two forks, a data fork and a resource fork. File data resides in the data fork, while file\r\nresources are stored in the resource fork. An application would typically have resources such as menus, dialog\r\nboxes, icons, and even code segments. A document file could have resources such as preference settings, window\r\nlocations, fonts and icons. Files are marked with a four byte creator and type, usually shown as alphanumeric tags,\r\nsuch as APPL, TEXT, BINA. The creator identifies the application that created the file, and the type generally\r\nindicates the file content. Text files use the ASCII 'CR' character ('\\r') to denote an end-of-line.\r\n6.2.2 File Names\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 4 of 14\n\nMacintosh file and folder names are limited to 31 characters. Names may not include the ':' character because it is\r\nused in pathnames to separate volume, directory, and the file name components. An absolute pathname begins\r\nwith a volume name. A pathname relative to the current working directory begins with a ':'. The File Manager is\r\nnot case sensitive when matching file names, however, it does not ignore diacritical marks. (MacOS file names are\r\nNOT case sensitive, however Tenon's extension enables case sensitivity in Tenon's UFS file system.)\r\n6.2.3 Access Permissions\r\nPermissions for files on local volumes are based on the order and manner in which programs open them. Files can\r\nbe opened for reading, writing, or exclusive read/write. Write access can be denied on an individual file basis by\r\nsetting its lock via Finder's Get Info dialog box. The File Manager also prevents locked files in the Trash can from\r\nbeing deleted on an\" Empty Trash\" request. Setting a volume to read-only (by hardware or software) prevents any\r\nchange to all files on that volume.\r\n6.2.4 Time Stamps\r\nThe Macintosh File Manager saves three time stamps for each file: (1) the time the file was created, (2) the time\r\nthe file was last modified, and (3) the time the file was last backed up (rarely used in the Macintosh world).\r\n6.2.5 Aliases\r\nAn alias is a special kind of file that represents a file, folder, or volume.\r\n6.3 CodeBuilder FFS\r\nCodeBuilder's implementation of the UNIX Fast File System (FFS) allows it to be stored within a Macintosh HFS\r\nfile, or on a SCSI disk partition. Using files allows existing volumes to be used as is, provided they have sufficient\r\nspace to meet file system sizing requirements. Using partitions provides higher performance, but may require\r\nreformatting/partitioning disks.\r\n6.3.1 FFS Within a File\r\nMacintosh files which contain an FFS are treated as block devices by CodeBuilder. They are set with creator\r\n'MUMM' and type 'BLK '. These files are visible to Finder and may be moved or copied to other folders or\r\nvolumes. They may also be dragged to the Trash can for removal. Be sure that this is intended before requesting\r\n\"Empty Trash\"! These files should never be selected for write access by other Macintosh applications. Even minor\r\nchanges by other Macintosh applications could render the fast file system file unusable by CodeBuilder! See also\r\nsection 6.9.1.1 Creating an FFS Within a File.\r\n6.3.2 FFS Within a Partition\r\nTo establish an FFS in a partition, you must first create an A/UX partition a disk with a Macintosh formatting\r\napplication. This partition cannot be mounted on the Macintosh desktop, so its content is not accessible by the\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 5 of 14\n\nFinder or other Macintosh applications. See also section 6.9.1.2 Creating an FFS on a Partition.\r\n6.4 CodeBuilder UFS\r\nCodeBuilder's implementation of the local UNIX file system (UFS) uses the Macintosh File Manager (HFS),\r\nenabling CodeBuilder's UNIX files to be stored alongside Macintosh files. However, there are some constraints\r\nimposed by the Macintosh File Manager that the astute user should be aware of when porting other UNIX\r\napplications to CodeBuilder.\r\n6.4.1 File Names\r\n6.4.1.1 Maximum Number of Characters\r\nThe Macintosh File Manager allows a maximum of 31 characters in a file name; hence, CodeBuilder UFS file\r\nnames are limited to 31 characters.\r\n6.4.1.2 Case Sensitive File Names\r\nCodeBuilder supports case sensitive file names by appending a 4 byte integer to the end of any case sensitive file\r\nname that collides with an existing case insensitive name. HFS stores the length of the file name, hence the names\r\nare unique within HFS. UNIX requests use a null terminated string comparison for identifying files, hence the\r\nappropriate file is matched as long as the first of the four appended bytes is NULL. CodeBuilder guarantees that\r\nthis is the case. For subsequent collisions, a new integer is used.\r\nSince the HFS limit on file name length is 31 characters, this method of resolving case sensitivity is limited to file\r\nnames of length 27 characters or less. Attempting to create a new file that collides with an existing case insensitive\r\nfile name of greater than 27 characters will fail.\r\n6.4.1.3 Component Separators\r\nThe Macintosh File Manager uses the character \":\" to separate names into volume, folder, and file name\r\ncomponents. Thus, Macintosh file names cannot contain that character. UNIX uses the character \"/\" for the same\r\npurpose. CodeBuilder automatically maps all occurrences of \":\" (which is valid in UNIX file names) into \"/\"\r\n(which is valid in Macintosh file names) before passing UNIX file names to the Macintosh File Manager.\r\n6.4.1.4 Non-Printable Characters\r\nMacintosh file names often include unprintable characters (the trademark symbol, for example). Although these\r\ncharacters are not invalid in UNIX file names, they are impossible to type or display on a UNIX command line.\r\nFor this reason, non-printable ASCII characters in Macintosh file names are translated according to the\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 6 of 14\n\nAppleSingle 7-bit ASCII naming conventionÝ. Basically, non-printable characters are translated to a percent sign\r\n(%) followed by a 2 digit hexadecimal representation of the character's value. The following are some examples:\r\nFile Name as Viewed by MacOS File Name as Viewed by CodeBuilder\r\nFilenameTM Filename%aa\r\nFilename® Filename%a8\r\nFilename© Filename%a9\r\nÝ: For more information on Apple Single, refer to section 6.7.1 AppleSingle Encapsulation.\r\n6.4.2 Linked Files\r\nIn UNIX, linking allows several file names to be associated with the same physical file. CodeBuilder properly\r\nsupports UNIX hard and soft links via the link(2) and symlink(2) system calls.\r\n6.4.2.1 Hard Links\r\nCodeBuilder provides a file system paradigm that permits copying or moving either UNIX or Macintosh files with\r\neither UNIX or Macintosh tools with equal results. However, the UNIX implementation of hard links prohibits\r\ncross disk hard links. Using the Finder to copy CodeBuilder's hard links from one volume to another will not\r\nwork. Therefore, you cannot use the Finder (or any other Macintosh tool) to copy or move CodeBuilder hard links\r\nfrom one Macintosh volume to another. This restriction is similar to the traditional UNIX restriction - no cross\r\ndisk hard links.\r\nCodeBuilder's implementation of hard links uses a hidden folder at the root level of a volume, and uses the\r\nMacintosh HFS equivalent of inode numbers to find targets of hard links in this folder. When the source of a hard\r\nlink is moved to another volume, the link will be unresolvable. Even if the correct target of the link is copied from\r\nthe source volume's hidden folder, it will be assigned a new inode number and the source link will still be\r\nunresolvable.\r\nIn general, unless an application requires specific semantics of hard links that are not also supplied by soft links,\r\nsoft links should be the preferred method of linking UFS files.\r\n6.4.3 Directory Link Counts\r\nThe stat() system call does not return the correct number of links for a directory. The Macintosh File Manager\r\ndoes not keep a directory link count for Macintosh folders, and CodeBuilder does not attempt to fabricate a correct\r\ndirectory link count for UNIX directories on local Macintosh File SystemsÝ.Ý: CodeBuilder always returns a link\r\ncount of 2 for UFS directories.\r\n6.4.4 Locked Files\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 7 of 14\n\nThe Macintosh File System has the ability to lock individual files, effectively making the file 'read only'. The\r\nUNIX file system has no notion of locking for individual files, although it does support the locking of entire file\r\nsystems by mounting them as 'read only'. If a UNIX application attempts to modify or remove a locked file,\r\nCodeBuilder will return the error EROFS. Although this error implies that the entire file system is 'read only', it\r\nmay be only the individual file that is locked. In this case it is necessary to unlock the file (use the Finder's Get\r\nInfo entry in the File menu) before CodeBuilder can modify or remove the file.\r\n6.4.5 File Types\r\nThe Macintosh File Manager saves a file type and file creator as part of the attributes for every file. CodeBuilder\r\nuses the identifier 'MUMM' for UNIX files. In CodeBuilder documentation the term \"UNIX file\" is used to refer\r\nto any file with a creator 'MUMM' and the term \"Macintosh file\" is used to refer to all other files. Note that\r\nMacintosh applications can see and access the UNIX files, since they are simply Macintosh files with a creator\r\n'MUMM'. Only CodeBuilder makes the distinction between UNIX files and Macintosh files.\r\nAll CodeBuilder documents and files are owned by the application named CodeBuilder. CodeBuilder uses file\r\ntypes for the different classes of files in UNIX. Each file type has a unique icon, easing identification of UNIX\r\nfiles when using the Macintosh Finder.\r\n BINA - Binary Files\r\nBinary files are streams of data. They may be UNIX executable files, text files, database files, or others. No\r\ntranslation of the data is done on binary files when accessed via CodeBuilder. This is the simplest, fastest, and\r\nmost common type of file. When CodeBuilder creates a new file, it always creates files of type BINA.\r\n TEXT - Text Files\r\nFiles containing only ASCII printable characters are referred to as \"text\" files. The Macintosh and UNIX formats\r\nfor text files have subtle differences. Macintosh uses the character 'cr' (0xD) to terminate a line of text and UNIX\r\nuses the character 'nl' (0xA). CodeBuilder files with a type 'TEXT' are stored on the disk in the native Macintosh\r\ntext file format (the line terminator is 'cr').\r\nWhen UNIX applications access type TEXT files, CodeBuilder automatically translates the 'cr' character to 'nl', so\r\nthe UNIX applications see these files in the expected UNIX text file format. A result of this automatic translation\r\nis that both Macintosh word processors and UNIX editors can be used to edit 'MUMM'/'TEXT' files. Note that\r\nsome Macintosh word processors may inadvertently add resource forks to the UNIX text files, but these resource\r\nforks will always be ignored by CodeBuilder. For more information on the handling of text files in CodeBuilder,\r\nrefer to the chapter \"Text File Manipulation\".\r\n LINK - Symbolic Links\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 8 of 14\n\nThis file type is used to identify UNIX symbolic links. The path to follow for the symbolic link is stored in the\r\ndata fork of the file.\r\n CHR - Character Devices\r\nThis file type is used to identify UNIX character devices. UNIX assigns two numbers to each device. The 'major'\r\nnumber describes the device type, and the 'minor' number uniquely identifies the device. The major and minor\r\nnumbers for this device are packed in four bytes and are stored in the data fork of the file.\r\n BLK - Block Devices\r\nThis file type is used to identify UNIX block devices. The major and minor numbers for this device are packed in\r\nfour bytes and are stored in the data fork of the file.\r\n SOCK - Sockets\r\nThis file type is used to identify UNIX sockets. Sockets are communication endpoints used for sending and\r\nreceiving data.\r\n FIFO - Pipes\r\nThis file type is used to identify named UNIX pipes. A pipe is a special type of file that is created by UNIX\r\nprocesses in order to pass information to other processes. Pipes enforce a first-in, first-out (FIFO) mechanism on\r\ndata.\r\n HLNK - Hard Links\r\nThis file type is used to identify hard links. Hard linking allows several file names to be associated with the same\r\nphysical file.\r\n SHLB - Shared Libraries\r\nThis file type is used to identify a shared library file. Many of the traditional UNIX shared libraries (libc, libm,\r\netc.) will have two versions in CodeBuilder - one for the compile time Header Call definitions and the other for\r\nthe run time dynamic linking.\r\n6.4.6 File Permissions\r\nCodeBuilder stores the user id, group id, and mode bits in a reserved area of the resource fork for each UNIX file.\r\nCodeBuilder can also set these attributes for Macintosh filesÝ. Note that this protection only applies to file access\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 9 of 14\n\nfrom CodeBuilder; it does not apply to the Finder or other Macintosh applications.\r\nCodeBuilder stores the protection attributes for a directory in a special file within the folder. This file has the name\r\n'\r\n/' and is invisible to the Finder. However, other Macintosh applications may see this file. It should not be deleted\r\nor changed.\r\nFigure 20. Example of File Permissions\r\nÝ: The CodeBuilder application has resources which allow the user to configure the default UNIX access\r\nprivilege modes for Macintosh files and folders; see the CodeBuilder Resources Appendix B.\r\n6.4.7 Time Stamps\r\nWhen CodeBuilder examines the time stamps of a Macintosh file, the file's Macintosh creation time is used for the\r\nUNIX data modification time. The file's Macintosh modification time is used for the UNIX attribute modification\r\ntimes. The file's Macintosh last-backed-up time is used for the UNIX last-accessed-time. When CodeBuilder\r\nmodifies the time stamps of a Macintosh file, the file's Macintosh creation time is set to the UNIX data\r\nmodification time. The file's Macintosh last-backed-up time is set to the UNIX last-accessed-time. The file's\r\nMacintosh modification time is set to the UNIX attribute modification time.\r\nFile Time Stamps\r\nMacintosh UNIX\r\nfile created data last modified\r\nfile modified attributes last modified\r\nfile backed up data last accessed\r\nSince most of the interaction between UNIX and Macintosh programs depends on only the \"modified\" timestamp,\r\nthe CodeBuilder interpretation of the Macintosh timestamps provides Mac/UNIX interoperability. For example,\r\nchanging a source file with a UNIX tool (like vi) results in a change to the file's \"modified\" timestamp. A\r\nMacintosh application which subsequently accesses this file will notice the change in the modified time, and will\r\nbehave accordingly (e.g., a Macintosh development tool will rebuild a project if the project depends on the\r\nmodified source file). In the reverse situation, a Macintosh editor will also change the file's \"created\" and\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 10 of 14\n\n\"modified\" timestamp, which will be interpreted by UNIX programs in the proper, \"the-data-(or attribute)-has-been-modified\" sense. In some cases, the Macintosh editor may only change the UNIX attribute modification\r\ntime. In this case, it may be necessary to touch(8) the file from within CodeBuilder to rebuild the project correctly.\r\n6.5 CodeBuilder Root File System Layout\r\nThe CodeBuilder root file system is delivered as an FFS within a file. The FFS file is named CodeBuilder_FFS,\r\nand resides in the same folder as the CodeBuilder application. A companion folder named CodeBuilder_HFS\r\nprovides for UFS oriented storage.\r\nAt the top of the CodeBuilder File System hierarchy is the UNIX root directory, also referred to as \"\r\n/\". The path \"//\" is a special case in CodeBuilder that allows UNIX processes to refer to files and folders outside\r\nof the CodeBuilder root. \"//\" is interpreted to mean \"the real root of the HFS volume that contains the\r\nCodeBuilder file system hierarchy\". The corresponding routines in the CodeBuilder libraries (getwd(3)) have been\r\nmodified to understand a pathname that begins with \"//\".\r\n6.5.1 The root Directory Tree\r\nThe root directory is represented by a \"/\" and contains the following directories:\r\nName Description\r\nCDROM Mount point for CodeBuilder CD-ROM.\r\nbase Base of source code and place for building binaries in CodeBuilder distribution.\r\nbin Basic user utilities.\r\nbootvol Symbolic link or mount point for the root of the MacOS boot volume.\r\ndev Block, character and other special device files.\r\netc System configuration files and scripts..\r\nhfs Symbolic link to CodeBuilder_HFS\r\nlost+found Storage for files lost or corrupted by file system damage.\r\nbin Basic user utilities.\r\nmnt Temporary mount point.\r\nsbin Basic system administration utilities.\r\ntmp Directory for temporary files.\r\nusr Contains majority of system utilities and files.\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 11 of 14\n\nvar Multi-purpose log, temporary, transient and spool files.\r\nvolume macmntd creates subdirectory mount points for removable volumes.\r\n6.5.2 The usr Directory Tree\r\nName Description\r\nX11 Symbolic link to CodeBuilder X Window software.\r\nX11R6 CodeBuilder X11R6 software.\r\nbin Binaries.\r\ndoc Miscellaneous documentation.\r\ninclude include files.\r\ninfo Documentation for GNU programs.\r\nlib Libraries.\r\nlibexec Catchall for system daemons.\r\nlocal Mount point for file system containing local applications and support files.\r\nmacppc PowerPC-specific files go here.\r\nman troff source for man pages.\r\nsbin System administrator binary files.\r\nshare Text and database files readily shared among 4.4BSD systems.\r\nsrc rpm support tree.\r\n6.5.3 The var Directory Tree\r\nName Description\r\nadm Administrative files.\r\nat Timed command scheduling files.\r\nbackups Miscellaneous backup files.\r\ncron cron data files.\r\ndb Database files.\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 12 of 14\n\ngames Miscellaneous game status and log files.\r\nlib Dynamic, machine specific application support files.\r\nlock Storage for emacs file locking.\r\nlog Miscellaneous system log files.\r\nmsgs System messages.\r\nobj Object files.\r\npreserve Temporary home of files preserved when editors fail.\r\nrun System information files, rebuilt after each reboot.\r\nspool Miscellaneous printer spooling directories.\r\ntmp Temporary files that are not discarded between system reboots.\r\n6.5.4 Major System Administration Files\r\nFor details about these files, see on-line man pages.\r\nName Description\r\n/etc/fstab Contains file system mount information [fstab(5)].\r\n/etc/group Defines mapping of group numbers to names and authorized users [group(5)].\r\n/etc/hosts Defines host names, aliases and IP address.\r\n/etc/master.passwd\r\nDefines the set of users authorized to log in; provides mapping between user id\r\nand name, default group, home directory, and shell [passwd(5)].\r\n/etc/printcap\r\nContains the list of available printers and the parameters used by the line printer\r\ndaemon [printcap(5)].\r\n/etc/rc\r\nContains the script of commands init(8) is to execute to establish the desired\r\nenvironment [rc(8)] .\r\n/etc/rc.conf\r\nContains variables derived from information entered in the CodeBuilder Control\r\nPanel for use by /etc/rc when starting CodeBuilder.\r\n/etc/syslog.conf /usr/sbin/syslogd configuration file [syslog(8)].\r\n/etc/ttys Specifies terminal support information for init(8) [ttys(5)].\r\n/usr/share/misc/termcap\r\nDefines the capabilities for numerous terminal types [termcap(5)]. Being phased\r\nout by ncurses.\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 13 of 14\n\n[ Top of Page ][ 6.6 Mounting Macintosh Volumes ][ Table of Contents ]\r\nSource: http://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nhttp://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553\r\nPage 14 of 14",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"http://tenon.com/products/codebuilder/User_Guide/6_File_Systems.html#anchor520553"
	],
	"report_names": [
		"6_File_Systems.html#anchor520553"
	],
	"threat_actors": [
		{
			"id": "eb3f4e4d-2573-494d-9739-1be5141cf7b2",
			"created_at": "2022-10-25T16:07:24.471018Z",
			"updated_at": "2026-04-10T02:00:05.002374Z",
			"deleted_at": null,
			"main_name": "Cron",
			"aliases": [],
			"source_name": "ETDA:Cron",
			"tools": [
				"Catelites",
				"Catelites Bot",
				"CronBot",
				"TinyZBot"
			],
			"source_id": "ETDA",
			"reports": null
		}
	],
	"ts_created_at": 1775434565,
	"ts_updated_at": 1775826750,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/ac09612e4de92769cf7f0b0bbeb25cfb5f612668.pdf",
		"text": "https://archive.orkl.eu/ac09612e4de92769cf7f0b0bbeb25cfb5f612668.txt",
		"img": "https://archive.orkl.eu/ac09612e4de92769cf7f0b0bbeb25cfb5f612668.jpg"
	}
}