PhysicsFS is a library to provide abstract access to various archives. It is intended for use in video games, and the design was somewhat inspired by Quake 3's file subsystem. The programmer defines a "write directory" on the physical filesystem. No file writing done through the PhysicsFS API can leave that write directory, for security. For example, an embedded scripting language cannot write outside of this path if it uses PhysFS for all of its I/O, which means that untrusted scripts can run more safely. Symbolic links can be disabled as well, for added safety. For file reading, the programmer lists directories and archives that form a "search path". Once the search path is defined, it becomes a single, transparent hierarchical filesystem. This makes for easy access to ZIP files in the same way as you access a file directly on the disk, and it makes it easy to ship a new archive that will override a previous archive on a per-file basis. Finally, PhysicsFS gives you platform-abstracted means to determine if CD-ROMs are available, the user's home directory, where in the real filesystem your program is running, etc.
OS | Architecture | Version |
---|---|---|
NetBSD 10.0 | aarch64 | physfs-3.0.2.tgz |
NetBSD 10.0 | aarch64 | physfs-3.0.2.tgz |
NetBSD 10.0 | aarch64eb | physfs-3.0.2.tgz |
NetBSD 10.0 | aarch64eb | physfs-3.0.2.tgz |
NetBSD 10.0 | alpha | physfs-3.0.2.tgz |
NetBSD 10.0 | alpha | physfs-3.0.2.tgz |
NetBSD 10.0 | earmv6hf | physfs-3.0.2.tgz |
NetBSD 10.0 | earmv6hf | physfs-3.0.2.tgz |
NetBSD 10.0 | earmv6hf | physfs-3.0.2.tgz |
NetBSD 10.0 | earmv7hf | physfs-3.0.2.tgz |
NetBSD 10.0 | earmv7hf | physfs-3.0.2.tgz |
NetBSD 10.0 | earmv7hf | physfs-3.0.2.tgz |
NetBSD 10.0 | i386 | physfs-3.0.2.tgz |
NetBSD 10.0 | i386 | physfs-3.0.2.tgz |
NetBSD 10.0 | m68k | physfs-3.0.2.tgz |
NetBSD 10.0 | m68k | physfs-3.0.2.tgz |
NetBSD 10.0 | m68k | physfs-3.0.2.tgz |
NetBSD 10.0 | mips64eb | physfs-3.0.2.tgz |
NetBSD 10.0 | mips64eb | physfs-3.0.2.tgz |
NetBSD 10.0 | powerpc | physfs-3.0.2.tgz |
NetBSD 10.0 | powerpc | physfs-3.0.2.tgz |
NetBSD 10.0 | powerpc | physfs-3.0.2.tgz |
NetBSD 10.0 | sh3el | physfs-3.0.2.tgz |
NetBSD 10.0 | sh3el | physfs-3.0.2.tgz |
NetBSD 10.0 | sparc64 | physfs-3.0.2.tgz |
NetBSD 10.0 | sparc64 | physfs-3.0.2.tgz |
NetBSD 10.0 | sparc | physfs-3.0.2.tgz |
NetBSD 10.0 | sparc | physfs-3.0.2.tgz |
NetBSD 10.0 | vax | physfs-3.0.2.tgz |
NetBSD 10.0 | vax | physfs-3.0.2.tgz |
NetBSD 10.0 | vax | physfs-3.0.2.tgz |
NetBSD 10.0 | x86_64 | physfs-3.0.2.tgz |
NetBSD 10.0 | x86_64 | physfs-3.0.2.tgz |
NetBSD 9.0 | aarch64 | physfs-3.0.2.tgz |
NetBSD 9.0 | aarch64 | physfs-3.0.2.tgz |
NetBSD 9.0 | alpha | physfs-3.0.2.tgz |
NetBSD 9.0 | alpha | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv4 | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv4 | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv4 | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv6hf | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv6hf | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv6hf | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv7hf | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv7hf | physfs-3.0.2.tgz |
NetBSD 9.0 | earmv7hf | physfs-3.0.2.tgz |
NetBSD 9.0 | i386 | physfs-3.0.2.tgz |
NetBSD 9.0 | i386 | physfs-3.0.2.tgz |
NetBSD 9.0 | m68k | physfs-3.0.2.tgz |
NetBSD 9.0 | powerpc | physfs-3.0.2.tgz |
NetBSD 9.0 | powerpc | physfs-3.0.2.tgz |
NetBSD 9.0 | powerpc | physfs-3.0.2.tgz |
NetBSD 9.0 | sparc64 | physfs-3.0.2.tgz |
NetBSD 9.0 | sparc64 | physfs-3.0.2.tgz |
NetBSD 9.0 | x86_64 | physfs-3.0.2.tgz |
NetBSD 9.0 | x86_64 | physfs-3.0.2.tgz |
NetBSD 9.3 | x86_64 | physfs-3.0.2.tgz |
Binary packages can be installed with the high-level tool pkgin (which can be installed with pkg_add) or pkg_add(1) (installed by default). The NetBSD packages collection is also designed to permit easy installation from source.
The pkg_admin audit command locates any installed package which has been mentioned in security advisories as having vulnerabilities.
Please note the vulnerabilities database might not be fully accurate, and not every bug is exploitable with every configuration.
Problem reports, updates or suggestions for this package should be reported with send-pr.