1FILE-HIERARCHY(7) file-hierarchy FILE-HIERARCHY(7)
2
3
4
6 file-hierarchy - File system hierarchy overview
7
9 Operating systems using the systemd(1) system and service manager are
10 organized based on a file system hierarchy inspired by UNIX, more
11 specifically the hierarchy described in the File System Hierarchy[1]
12 specification and hier(7), with various extensions, partially
13 documented in the XDG Base Directory Specification[2] and XDG User
14 Directories[3]. This manual page describes a more generalized, though
15 minimal and modernized subset of these specifications that defines more
16 strictly the suggestions and restrictions systemd makes on the file
17 system hierarchy.
18
19 Many of the paths described here can be queried with the systemd-
20 path(1) tool.
21
23 /
24 The file system root. Usually writable, but this is not required.
25 Possibly a temporary file system ("tmpfs"). Not shared with other
26 hosts (unless read-only).
27
28 /boot/
29 The boot partition used for bringing up the system. On EFI systems,
30 this is possibly the EFI System Partition (ESP), also see systemd-
31 gpt-auto-generator(8). This directory is usually strictly local to
32 the host, and should be considered read-only, except when a new
33 kernel or boot loader is installed. This directory only exists on
34 systems that run on physical or emulated hardware that requires
35 boot loaders.
36
37 /efi/
38 If the boot partition /boot/ is maintained separately from the EFI
39 System Partition (ESP), the latter is mounted here. Tools that need
40 to operate on the EFI system partition should look for it at this
41 mount point first, and fall back to /boot/ — if the former doesn't
42 qualify (for example if it is not a mount point or does not have
43 the correct file system type MSDOS_SUPER_MAGIC).
44
45 /etc/
46 System-specific configuration. This directory may or may not be
47 read-only. Frequently, this directory is pre-populated with
48 vendor-supplied configuration files, but applications should not
49 make assumptions about this directory being fully populated or
50 populated at all, and should fall back to defaults if configuration
51 is missing.
52
53 /home/
54 The location for normal user's home directories. Possibly shared
55 with other systems, and never read-only. This directory should only
56 be used for normal users, never for system users. This directory
57 and possibly the directories contained within it might only become
58 available or writable in late boot or even only after user
59 authentication. This directory might be placed on
60 limited-functionality network file systems, hence applications
61 should not assume the full set of file API is available on this
62 directory. Applications should generally not reference this
63 directory directly, but via the per-user $HOME environment
64 variable, or via the home directory field of the user database.
65
66 /root/
67 The home directory of the root user. The root user's home directory
68 is located outside of /home/ in order to make sure the root user
69 may log in even without /home/ being available and mounted.
70
71 /srv/
72 The place to store general server payload, managed by the
73 administrator. No restrictions are made how this directory is
74 organized internally. Generally writable, and possibly shared among
75 systems. This directory might become available or writable only
76 very late during boot.
77
78 /tmp/
79 The place for small temporary files. This directory is usually
80 mounted as a "tmpfs" instance, and should hence not be used for
81 larger files. (Use /var/tmp/ for larger files.) This directory is
82 usually flushed at boot-up. Also, files that are not accessed
83 within a certain time may be automatically deleted.
84
85 If applications find the environment variable $TMPDIR set, they
86 should use the directory specified in it instead of /tmp/ (see
87 environ(7) and IEEE Std 1003.1[4] for details).
88
89 Since /tmp/ is accessible to other users of the system, it is
90 essential that files and subdirectories under this directory are
91 only created with mkstemp(3), mkdtemp(3), and similar calls. For
92 more details, see Using /tmp/ and /var/tmp/ Safely[5].
93
95 /run/
96 A "tmpfs" file system for system packages to place runtime data in.
97 This directory is flushed on boot, and generally writable for
98 privileged programs only. Always writable.
99
100 /run/log/
101 Runtime system logs. System components may place private logs in
102 this directory. Always writable, even when /var/log/ might not be
103 accessible yet.
104
105 /run/user/
106 Contains per-user runtime directories, each usually individually
107 mounted "tmpfs" instances. Always writable, flushed at each reboot
108 and when the user logs out. User code should not reference this
109 directory directly, but via the $XDG_RUNTIME_DIR environment
110 variable, as documented in the XDG Base Directory Specification[2].
111
113 /usr/
114 Vendor-supplied operating system resources. Usually read-only, but
115 this is not required. Possibly shared between multiple hosts. This
116 directory should not be modified by the administrator, except when
117 installing or removing vendor-supplied packages.
118
119 /usr/bin/
120 Binaries and executables for user commands that shall appear in the
121 $PATH search path. It is recommended not to place binaries in this
122 directory that are not useful for invocation from a shell (such as
123 daemon binaries); these should be placed in a subdirectory of
124 /usr/lib/ instead.
125
126 /usr/include/
127 C and C++ API header files of system libraries.
128
129 /usr/lib/
130 Static, private vendor data that is compatible with all
131 architectures (though not necessarily architecture-independent).
132 Note that this includes internal executables or other binaries that
133 are not regularly invoked from a shell. Such binaries may be for
134 any architecture supported by the system. Do not place public
135 libraries in this directory, use $libdir (see below), instead.
136
137 /usr/lib/arch-id/
138 Location for placing dynamic libraries into, also called $libdir.
139 The architecture identifier to use is defined on Multiarch
140 Architecture Specifiers (Tuples)[6] list. Legacy locations of
141 $libdir are /usr/lib/, /usr/lib64/. This directory should not be
142 used for package-specific data, unless this data is
143 architecture-dependent, too. To query $libdir for the primary
144 architecture of the system, invoke:
145
146 # systemd-path system-library-arch
147
148 /usr/share/
149 Resources shared between multiple packages, such as documentation,
150 man pages, time zone information, fonts and other resources.
151 Usually, the precise location and format of files stored below this
152 directory is subject to specifications that ensure
153 interoperability.
154
155 /usr/share/doc/
156 Documentation for the operating system or system packages.
157
158 /usr/share/factory/etc/
159 Repository for vendor-supplied default configuration files. This
160 directory should be populated with pristine vendor versions of all
161 configuration files that may be placed in /etc/. This is useful to
162 compare the local configuration of a system with vendor defaults
163 and to populate the local configuration with defaults.
164
165 /usr/share/factory/var/
166 Similar to /usr/share/factory/etc/, but for vendor versions of
167 files in the variable, persistent data directory /var/.
168
170 /var/
171 Persistent, variable system data. Must be writable. This directory
172 might be pre-populated with vendor-supplied data, but applications
173 should be able to reconstruct necessary files and directories in
174 this subhierarchy should they be missing, as the system might start
175 up without this directory being populated. Persistency is
176 recommended, but optional, to support ephemeral systems. This
177 directory might become available or writable only very late during
178 boot. Components that are required to operate during early boot
179 hence shall not unconditionally rely on this directory.
180
181 /var/cache/
182 Persistent system cache data. System components may place
183 non-essential data in this directory. Flushing this directory
184 should have no effect on operation of programs, except for
185 increased runtimes necessary to rebuild these caches.
186
187 /var/lib/
188 Persistent system data. System components may place private data in
189 this directory.
190
191 /var/log/
192 Persistent system logs. System components may place private logs in
193 this directory, though it is recommended to do most logging via the
194 syslog(3) and sd_journal_print(3) calls.
195
196 /var/spool/
197 Persistent system spool data, such as printer or mail queues.
198
199 /var/tmp/
200 The place for larger and persistent temporary files. In contrast to
201 /tmp/, this directory is usually mounted from a persistent physical
202 file system and can thus accept larger files. (Use /tmp/ for small
203 ephemeral files.) This directory is generally not flushed at
204 boot-up, but time-based cleanup of files that have not been
205 accessed for a certain time is applied.
206
207 If applications find the environment variable $TMPDIR set, they
208 should use the directory specified in it instead of /var/tmp/ (see
209 environ(7) for details).
210
211 The same security restrictions as with /tmp/ apply: mkstemp(3),
212 mkdtemp(3), and similar calls should be used. For further details
213 about this directory, see Using /tmp/ and /var/tmp/ Safely[5].
214
216 /dev/
217 The root directory for device nodes. Usually, this directory is
218 mounted as a "devtmpfs" instance, but might be of a different type
219 in sandboxed/containerized setups. This directory is managed
220 jointly by the kernel and systemd-udevd(8), and should not be
221 written to by other components. A number of special purpose virtual
222 file systems might be mounted below this directory.
223
224 /dev/shm/
225 Place for POSIX shared memory segments, as created via shm_open(3).
226 This directory is flushed on boot, and is a "tmpfs" file system.
227 Since all users have write access to this directory, special care
228 should be taken to avoid name clashes and vulnerabilities. For
229 normal users, shared memory segments in this directory are usually
230 deleted when the user logs out. Usually, it is a better idea to use
231 memory mapped files in /run/ (for system programs) or
232 $XDG_RUNTIME_DIR (for user programs) instead of POSIX shared memory
233 segments, since these directories are not world-writable and hence
234 not vulnerable to security-sensitive name clashes.
235
236 /proc/
237 A virtual kernel file system exposing the process list and other
238 functionality. This file system is mostly an API to interface with
239 the kernel and not a place where normal files may be stored. For
240 details, see proc(5). A number of special purpose virtual file
241 systems might be mounted below this directory.
242
243 /proc/sys/
244 A hierarchy below /proc/ that exposes a number of kernel tunables.
245 The primary way to configure the settings in this API file tree is
246 via sysctl.d(5) files. In sandboxed/containerized setups, this
247 directory is generally mounted read-only.
248
249 /sys/
250 A virtual kernel file system exposing discovered devices and other
251 functionality. This file system is mostly an API to interface with
252 the kernel and not a place where normal files may be stored. In
253 sandboxed/containerized setups, this directory is generally mounted
254 read-only. A number of special purpose virtual file systems might
255 be mounted below this directory.
256
258 /bin/, /sbin/, /usr/sbin/
259 These compatibility symlinks point to /usr/bin/, ensuring that
260 scripts and binaries referencing these legacy paths correctly find
261 their binaries.
262
263 /lib/
264 This compatibility symlink points to /usr/lib/, ensuring that
265 programs referencing this legacy path correctly find their
266 resources.
267
268 /lib64/
269 On some architecture ABIs, this compatibility symlink points to
270 $libdir, ensuring that binaries referencing this legacy path
271 correctly find their dynamic loader. This symlink only exists on
272 architectures whose ABI places the dynamic loader in this path.
273
274 /var/run/
275 This compatibility symlink points to /run/, ensuring that programs
276 referencing this legacy path correctly find their runtime data.
277
279 User applications may want to place files and directories in the user's
280 home directory. They should follow the following basic structure. Note
281 that some of these directories are also standardized (though more
282 weakly) by the XDG Base Directory Specification[2]. Additional
283 locations for high-level user resources are defined by
284 xdg-user-dirs[3].
285
286 ~/.cache/
287 Persistent user cache data. User programs may place non-essential
288 data in this directory. Flushing this directory should have no
289 effect on operation of programs, except for increased runtimes
290 necessary to rebuild these caches. If an application finds
291 $XDG_CACHE_HOME set, it should use the directory specified in it
292 instead of this directory.
293
294 ~/.config/
295 Application configuration and state. When a new user is created,
296 this directory will be empty or not exist at all. Applications
297 should fall back to defaults should their configuration or state in
298 this directory be missing. If an application finds $XDG_CONFIG_HOME
299 set, it should use the directory specified in it instead of this
300 directory.
301
302 ~/.local/bin/
303 Executables that shall appear in the user's $PATH search path. It
304 is recommended not to place executables in this directory that are
305 not useful for invocation from a shell; these should be placed in a
306 subdirectory of ~/.local/lib/ instead. Care should be taken when
307 placing architecture-dependent binaries in this place, which might
308 be problematic if the home directory is shared between multiple
309 hosts with different architectures.
310
311 ~/.local/lib/
312 Static, private vendor data that is compatible with all
313 architectures.
314
315 ~/.local/lib/arch-id/
316 Location for placing public dynamic libraries. The architecture
317 identifier to use is defined on Multiarch Architecture Specifiers
318 (Tuples)[6] list.
319
320 ~/.local/share/
321 Resources shared between multiple packages, such as fonts or
322 artwork. Usually, the precise location and format of files stored
323 below this directory is subject to specifications that ensure
324 interoperability. If an application finds $XDG_DATA_HOME set, it
325 should use the directory specified in it instead of this directory.
326
328 Unprivileged processes generally lack write access to most of the
329 hierarchy.
330
331 The exceptions for normal users are /tmp/, /var/tmp/, /dev/shm/, as
332 well as the home directory $HOME (usually found below /home/) and the
333 runtime directory $XDG_RUNTIME_DIR (found below /run/user/) of the
334 user, which are all writable.
335
336 For unprivileged system processes, only /tmp/, /var/tmp/ and /dev/shm/
337 are writable. If an unprivileged system process needs a private
338 writable directory in /var/ or /run/, it is recommended to either
339 create it before dropping privileges in the daemon code, to create it
340 via tmpfiles.d(5) fragments during boot, or via the StateDirectory= and
341 RuntimeDirectory= directives of service units (see systemd.unit(5) for
342 details).
343
344 /tmp/, /var/tmp/ and /dev/shm/ should be mounted nosuid and nodev,
345 which means that set-user-id mode and character or block special
346 devices are not interpreted on those file systems. In general it is not
347 possible to mount them noexec, because various programs use those
348 directories for dynamically generated or optimized code, and with that
349 flag those use cases would break. Using this flag is OK on
350 special-purpose installations or systems where all software that may be
351 installed is known and doesn't require such functionality. See the
352 discussion of nosuid/nodev/noexec in mount(8) and PROT_EXEC in mmap(2).
353
355 Unix file systems support different types of file nodes, including
356 regular files, directories, symlinks, character and block device nodes,
357 sockets and FIFOs.
358
359 It is strongly recommended that /dev/ is the only location below which
360 device nodes shall be placed. Similarly, /run/ shall be the only
361 location to place sockets and FIFOs. Regular files, directories and
362 symlinks may be used in all directories.
363
365 Developers of system packages should follow strict rules when placing
366 their files in the file system. The following table lists recommended
367 locations for specific types of files supplied by the vendor.
368
369 Table 1. System package vendor files locations
370 ┌──────────────────────────┬────────────────────────────┐
371 │Directory │ Purpose │
372 ├──────────────────────────┼────────────────────────────┤
373 │/usr/bin/ │ Package executables that │
374 │ │ shall appear in the $PATH │
375 │ │ executable search path, │
376 │ │ compiled for any of the │
377 │ │ supported architectures │
378 │ │ compatible with the │
379 │ │ operating system. It is │
380 │ │ not recommended to place │
381 │ │ internal binaries or │
382 │ │ binaries that are not │
383 │ │ commonly invoked from the │
384 │ │ shell in this directory, │
385 │ │ such as daemon binaries. │
386 │ │ As this directory is │
387 │ │ shared with most other │
388 │ │ packages of the system, │
389 │ │ special care should be │
390 │ │ taken to pick unique names │
391 │ │ for files placed here, │
392 │ │ that are unlikely to clash │
393 │ │ with other package's │
394 │ │ files. │
395 ├──────────────────────────┼────────────────────────────┤
396 │/usr/lib/arch-id/ │ Public shared libraries of │
397 │ │ the package. As above, be │
398 │ │ careful with using too │
399 │ │ generic names, and pick │
400 │ │ unique names for your │
401 │ │ libraries to place here to │
402 │ │ avoid name clashes. │
403 ├──────────────────────────┼────────────────────────────┤
404 │/usr/lib/package/ │ Private static vendor │
405 │ │ resources of the package, │
406 │ │ including private binaries │
407 │ │ and libraries, or any │
408 │ │ other kind of read-only │
409 │ │ vendor data. │
410 ├──────────────────────────┼────────────────────────────┤
411 │/usr/lib/arch-id/package/ │ Private other vendor │
412 │ │ resources of the package │
413 │ │ that are │
414 │ │ architecture-specific and │
415 │ │ cannot be shared between │
416 │ │ architectures. Note that │
417 │ │ this generally does not │
418 │ │ include private │
419 │ │ executables since binaries │
420 │ │ of a specific architecture │
421 │ │ may be freely invoked from │
422 │ │ any other supported system │
423 │ │ architecture. │
424 ├──────────────────────────┼────────────────────────────┤
425 │/usr/include/package/ │ Public C/C++ APIs of │
426 │ │ public shared libraries of │
427 │ │ the package. │
428 └──────────────────────────┴────────────────────────────┘
429
430 Additional static vendor files may be installed in the /usr/share/
431 hierarchy to the locations defined by the various relevant
432 specifications.
433
434 The following directories shall be used by the package for local
435 configuration and files created during runtime:
436
437 Table 2. System package variable files locations
438 ┌────────────────────┬────────────────────────────┐
439 │Directory │ Purpose │
440 ├────────────────────┼────────────────────────────┤
441 │/etc/package/ │ System-specific │
442 │ │ configuration for the │
443 │ │ package. It is recommended │
444 │ │ to default to safe │
445 │ │ fallbacks if this │
446 │ │ configuration is missing, │
447 │ │ if this is possible. │
448 │ │ Alternatively, a │
449 │ │ tmpfiles.d(5) fragment may │
450 │ │ be used to copy or symlink │
451 │ │ the necessary files and │
452 │ │ directories from │
453 │ │ /usr/share/factory/ during │
454 │ │ boot, via the "L" or "C" │
455 │ │ directives. │
456 ├────────────────────┼────────────────────────────┤
457 │/run/package/ │ Runtime data for the │
458 │ │ package. Packages must be │
459 │ │ able to create the │
460 │ │ necessary subdirectories │
461 │ │ in this tree on their own, │
462 │ │ since the directory is │
463 │ │ flushed automatically on │
464 │ │ boot. Alternatively, a │
465 │ │ tmpfiles.d(5) fragment may │
466 │ │ be used to create the │
467 │ │ necessary directories │
468 │ │ during boot, or the │
469 │ │ RuntimeDirectory= │
470 │ │ directive of service units │
471 │ │ may be used to create them │
472 │ │ at service startup (see │
473 │ │ systemd.unit(5) for │
474 │ │ details). │
475 ├────────────────────┼────────────────────────────┤
476 │/run/log/package/ │ Runtime log data for the │
477 │ │ package. As above, the │
478 │ │ package needs to make sure │
479 │ │ to create this directory │
480 │ │ if necessary, as it will │
481 │ │ be flushed on every boot. │
482 ├────────────────────┼────────────────────────────┤
483 │/var/cache/package/ │ Persistent cache data of │
484 │ │ the package. If this │
485 │ │ directory is flushed, the │
486 │ │ application should work │
487 │ │ correctly on next │
488 │ │ invocation, though │
489 │ │ possibly slowed down due │
490 │ │ to the need to rebuild any │
491 │ │ local cache files. The │
492 │ │ application must be │
493 │ │ capable of recreating this │
494 │ │ directory should it be │
495 │ │ missing and necessary. To │
496 │ │ create an empty directory, │
497 │ │ a tmpfiles.d(5) fragment │
498 │ │ or the CacheDirectory= │
499 │ │ directive of service units │
500 │ │ (see systemd.unit(5)) may │
501 │ │ be used. │
502 ├────────────────────┼────────────────────────────┤
503 │/var/lib/package/ │ Persistent private data of │
504 │ │ the package. This is the │
505 │ │ primary place to put │
506 │ │ persistent data that does │
507 │ │ not fall into the other │
508 │ │ categories listed. │
509 │ │ Packages should be able to │
510 │ │ create the necessary │
511 │ │ subdirectories in this │
512 │ │ tree on their own, since │
513 │ │ the directory might be │
514 │ │ missing on boot. To create │
515 │ │ an empty directory, a │
516 │ │ tmpfiles.d(5) fragment or │
517 │ │ the StateDirectory= │
518 │ │ directive of service units │
519 │ │ (see systemd.unit(5)) may │
520 │ │ be used. │
521 ├────────────────────┼────────────────────────────┤
522 │/var/log/package/ │ Persistent log data of the │
523 │ │ package. As above, the │
524 │ │ package should make sure │
525 │ │ to create this directory │
526 │ │ if necessary, possibly │
527 │ │ using tmpfiles.d(5) or │
528 │ │ LogsDirectory= (see │
529 │ │ systemd.unit(5)), as it │
530 │ │ might be missing. │
531 ├────────────────────┼────────────────────────────┤
532 │/var/spool/package/ │ Persistent spool/queue │
533 │ │ data of the package. As │
534 │ │ above, the package should │
535 │ │ make sure to create this │
536 │ │ directory if necessary, as │
537 │ │ it might be missing. │
538 └────────────────────┴────────────────────────────┘
539
541 Programs running in user context should follow strict rules when
542 placing their own files in the user's home directory. The following
543 table lists recommended locations in the home directory for specific
544 types of files supplied by the vendor if the application is installed
545 in the home directory. (User applications installed system-wide are
546 covered by the rules outlined above for vendor files.)
547
548 Table 3. Vendor package file locations under the home directory of the
549 user
550 ┌──────────────────────────────┬────────────────────────────┐
551 │Directory │ Purpose │
552 ├──────────────────────────────┼────────────────────────────┤
553 │~/.local/bin/ │ Package executables that │
554 │ │ shall appear in the $PATH │
555 │ │ executable search path. It │
556 │ │ is not recommended to │
557 │ │ place internal executables │
558 │ │ or executables that are │
559 │ │ not commonly invoked from │
560 │ │ the shell in this │
561 │ │ directory, such as daemon │
562 │ │ executables. As this │
563 │ │ directory is shared with │
564 │ │ most other packages of the │
565 │ │ user, special care should │
566 │ │ be taken to pick unique │
567 │ │ names for files placed │
568 │ │ here, that are unlikely to │
569 │ │ clash with other package's │
570 │ │ files. │
571 ├──────────────────────────────┼────────────────────────────┤
572 │~/.local/lib/arch-id/ │ Public shared libraries of │
573 │ │ the package. As above, be │
574 │ │ careful with using overly │
575 │ │ generic names, and pick │
576 │ │ unique names for your │
577 │ │ libraries to place here to │
578 │ │ avoid name clashes. │
579 ├──────────────────────────────┼────────────────────────────┤
580 │~/.local/lib/package/ │ Private, static vendor │
581 │ │ resources of the package, │
582 │ │ compatible with any │
583 │ │ architecture, or any other │
584 │ │ kind of read-only vendor │
585 │ │ data. │
586 ├──────────────────────────────┼────────────────────────────┤
587 │~/.local/lib/arch-id/package/ │ Private other vendor │
588 │ │ resources of the package │
589 │ │ that are │
590 │ │ architecture-specific and │
591 │ │ cannot be shared between │
592 │ │ architectures. │
593 └──────────────────────────────┴────────────────────────────┘
594
595 Additional static vendor files may be installed in the ~/.local/share/
596 hierarchy, mirroring the subdirectories specified in the section
597 "Vendor-supplied operating system resources" above.
598
599 The following directories shall be used by the package for per-user
600 local configuration and files created during runtime:
601
602 Table 4. User package variable file locations
603 ┌──────────────────────────┬────────────────────────────┐
604 │Directory │ Purpose │
605 ├──────────────────────────┼────────────────────────────┤
606 │~/.config/package/ │ User-specific │
607 │ │ configuration and state │
608 │ │ for the package. It is │
609 │ │ required to default to │
610 │ │ safe fallbacks if this │
611 │ │ configuration is missing. │
612 ├──────────────────────────┼────────────────────────────┤
613 │$XDG_RUNTIME_DIR/package/ │ User runtime data for the │
614 │ │ package. │
615 ├──────────────────────────┼────────────────────────────┤
616 │~/.cache/package/ │ Persistent cache data of │
617 │ │ the package. If this │
618 │ │ directory is flushed, the │
619 │ │ application should work │
620 │ │ correctly on next │
621 │ │ invocation, though │
622 │ │ possibly slowed down due │
623 │ │ to the need to rebuild any │
624 │ │ local cache files. The │
625 │ │ application must be │
626 │ │ capable of recreating this │
627 │ │ directory should it be │
628 │ │ missing and necessary. │
629 └──────────────────────────┴────────────────────────────┘
630
632 systemd(1), hier(7), systemd-path(1), systemd-gpt-auto-generator(8),
633 sysctl.d(5), tmpfiles.d(5), pkg-config(1), systemd.unit(5)
634
636 1. File System Hierarchy
637 http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html
638
639 2. XDG Base Directory Specification
640 http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
641
642 3. XDG User Directories
643 https://www.freedesktop.org/wiki/Software/xdg-user-dirs/
644
645 4. IEEE Std 1003.1
646 http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03
647
648 5. Using /tmp/ and /var/tmp/ Safely
649 https://systemd.io/TEMPORARY_DIRECTORIES
650
651 6. Multiarch Architecture Specifiers (Tuples)
652 https://wiki.debian.org/Multiarch/Tuples
653
654
655
656systemd 249 FILE-HIERARCHY(7)