Cengage Chapter 7 -Linux and Macintosh File Systems

Question 1

The file system introduced in macOS High Sierra. It was designed to be used with flash memory and offers better security, encryption, and performance speeds than HFS+.

Answer 1

Apple File System (APFS)

Question 1

In the macOS file system, a group of consecutive logical blocks assembled in a volume when a file is saved. See also logical block.

Answer 1

allocation block

Question 2

A macOS file that organizes the directory hierarchy and file block mapping for File Manager. Files are represented as nodes (objects); leaf nodes contain the actual file data.

Answer 2

B*-tree

Question 3

In the Linux file system, the inode that tracks bad sectors on a drive.

Answer 3

bad block inode

Question 4

A block in the Linux file system containing the bootstrap code used to start the system.

Answer 4

boot block

Question 5

An area of the macOS file system used to maintain the relationships between files and directories on a volume.

Answer 5

catalog

Question 6

In the macOS file system, groups of contiguous allocation blocks used to keep file fragmentation to a minimum.

Answer 6

clumps

Question 7

A block in the Linux file system where directories and files are stored on a drive.

Answer 7

data block

Question 8

The part of a macOS file containing the file’s actual data, both usercreated data and data written by applications, as well as resource map and header information, window locations, and icons. See also resource fork.

Answer 8

data fork

Question 9

The inode pointers in the second layer or group of an OS. See also inodes.

Answer 9

double-indirect pointers

Question 10

File system used by Mac OS 8.1 and later. HFS+ supports smaller file sizes on larger volumes, resulting in more efficient disk use.

Answer 10

Extended Format File System (HFS+)

Question 11

A file in HFS and HFS+ that’s used by the catalog to coordinate file allocations to a volume when the list of a file’s contiguous blocks becomes too long. Any file extents not in the MDB or a VCB are also contained in this file. See also catalog, Master Directory Block (MDB), and Volume Control Block (VCB).

Answer 11

extents overflow file

Question 12

A Linux file system that added support for partitions larger than 16 TB, improved management of large files, and offered a more flexible approach to adding file system features.

Answer 12

Fourth Extended File System (Ext4)

Question 13

In the Linux file system, a pointer that allows accessing the same file by different filenames, which refer to the same inode and physical location on the drive.

Answer 13

hard link

Question 14

A node that stores information about the B-tree file. See also B-tree.

Answer 14

header node

Question 15

An older Mac OS file system, consisting of directories and subdirectories that can be nested.

Answer 15

Hierarchical File System (HFS)

Question 16

A B*-tree node that stores link information to the previous and next nodes.

Answer 16

index node

Question 17

The inode pointers in the first layer or group of an OS. See also inodes.

Answer 17

indirect pointers

Question 18

Blocks in the Linux file system that contain the first data after the superblock and consist of a grouping of inodes. See also inodes.

Answer 18

inode blocks

Question 19

A key part of the Linux file system, these information nodes contain descriptive file or directory data, such as UIDs, GIDs, modification times, access times, creation times, and file locations.

Answer 19

inodes

Question 20

A macOS feature used to track a user’s passwords for applications, Web sites, and other system files.

Answer 20

keychains

Question 21

A field in each inode that specifies the number of hard links. See also hard link.

Answer 21

link count

Question 22

In the macOS file system, a collection of data that can’t exceed 512 bytes. Logical blocks are assembled in allocation blocks to store files in a volume. See also allocation block.

Answer 22

logical block

Question 23

In the macOS file system, the actual ending of a file’s data.

Answer 23

logical EOF

Question 24

A B*-tree node that stores a node descriptor and map record.

Answer 24

map node

Question 25

On older Mac OS systems, the location where all volume information is stored. A copy of the MDB is kept in the next-to-last block on the volume. Called the Volume Information Block (VIB) in HFS+.

Answer 25

Master Directory Block (MDB)

Question 26

In the macOS file system, the number of bytes allotted on a volume for a file.

Answer 26

physical EOF

Question 27

In macOS, preference files for installed applications on a system.

Answer 27

plist files

Question 28

The part of a macOS file containing file metadata and application information, such as menus, dialog boxes, icons, executable code, and controls. Also contains resource map and header information, window locations, and icons

Answer 28

resource fork

Question 29

An early Linux file system.

Answer 29

Second Extended File System (Ext2)

Question 30

A block in the Linux file system that specifies and keeps track of the disk geometry and available space and manages the file system.

Answer 30

superblock

Question 31

Pointers to other files; they can point to items on other drives or other parts of the network and don’t affect the link count. See also hard link.

Answer 31

symbolic links

Question 32

A highly compressed data file containing one or more files or directories and their contents.

Answer 32

tarball

Question 33

A Linux file system that made improvements to Ext2, such as adding journaling as a built-in file recovery mechanism

Answer 33

Third Extended File System (Ext3)

Question 34

The inode pointers in the third layer or group of an OS

Answer 34

triple-indirect pointers

Question 35

A new feature in macOS that records log files for a macOS system.

Answer 35

unified logging

Question 36

An area of the macOS file system containing information from the MDB. See also Master Directory Block (MDB).

Answer 36

Volume Control Block (VCB)