|
19 | 19 | \texttt{ext4} (Linux specific), \texttt{XFS} (used on Linux but coming from SGI |
20 | 20 | IRIX), \texttt{JFS} (used on Linux but came from IBM AIX), \texttt{ufs} (BSD |
21 | 21 | systems), \texttt{FAT32} (Win), \texttt{ZFS} (Solaris born, then ported to other |
22 | | -systems), etc. The filesystem can be either used on local or remote storage, |
23 | | -and in case of a remote storage network filesystem protocols like \texttt{NFS} or |
24 | | -\texttt{AFS} are used. Note that these network filesystems do not define the |
25 | | -filesystem structure itself, they only provide for accessing existing |
26 | | -filesystems remotely. Each filesystem also has its limits, a largest file size |
27 | | -or the maximum size of the filesystem itself, for example. |
| 22 | +systems), \texttt{APFS} (macOS and iOS since 2017), etc. A filesystem can be |
| 23 | +either used on local or remote storage, and in case of a remote storage network |
| 24 | +filesystem protocols like \texttt{NFS} or \texttt{AFS} are used to access the |
| 25 | +data. Note that these network filesystems do not define the filesystem |
| 26 | +structure itself, they only provide for accessing existing filesystems remotely. |
| 27 | +Each filesystem also has its limits, a largest file size or the maximum size of |
| 28 | +the filesystem itself, for example. |
28 | 29 | \item Unix does not have A, B, C, D\dots disks as Windows and other systems. |
29 | 30 | All filesystems are mounted to a single directory hierarchy on any Unix system, |
30 | 31 | as shown on the slide where you can see the root filesystem and three other |
|
0 commit comments