Haiku/haiku
Haiku/haiku
1
0
Fork 0
mirror of https://review.haiku-os.org/haiku synced 2024-11-23 07:18:40 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc/user: mention libnetwork and a bit of the filesystem hierarchy

Browse Source 
Based on the feedback from Maya Posch in https://mayaposch.wordpress.com/2024/01/20/porting-nymphcast-to-the-haiku-operating-system/
Thanks for noting that the information was missing!

Change-Id: I4a9f709b17cb3a4a771f167b5af0fc83843ec5ad
Reviewed-on: https://review.haiku-os.org/c/haiku/+/7406
Reviewed-by: Niels Sascha Reedijk <niels.reedijk@gmail.com>
Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
This commit is contained in:
PulkoMandy 2024-02-17 16:49:03 +01:00 committed by Adrien Destugues
parent d72ca12e19
commit 2a2e7ad562
2 changed files with 52 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/user/posix/_libroot.dox
View File

@ -1,5 +1,5 @@
/*
* Copyright 2019 Haiku, Inc. All rights reserved.
* Copyright 2019-2024 Haiku, Inc. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@ -15,7 +15,9 @@ Haiku implements a standard library containing the standard functions from C
available in libroot, which is linked in by default.
For convenience and POSIX compatibility, empty "m" and "pthread" libraries are
also provided, but the math and thread functions are also defined in libroot.
also provided, but the math and thread functions are also defined in libroot. However, this is
currently not the case for "rt" and "trace" (both also part of the standard libraries required
in POSIX).
The C library also contains a number of GNU and BSD extensions to the C and
POSIX standards. The BSD extensions are enabled by default unless a specific
@ -30,4 +32,8 @@ _GNU_SOURCE.
The GNU and BSD extensions are in a separate library, so the -lbsd linker flag
may be needed to use them.
On the other hand, network socket functions (socket, connect, bind, accept, ...) are provided in
a separate library, libnetwork.so. To use these functions you will need to use the -lnetwork
linker command line switch (instead of the POSIX specified -lxnet).
*/

44
docs/user/storage/storageintro.dox Normal file
View File

@ -0,0 +1,44 @@
/*!
\page storage_intro Introduction to the storage kit
\section Filesystem hierarchy
The filesystems are organized in a hierarchy starting at the root directory (which has the path
'/'). Unlike on typical UNIX systems, the root filsystem is not a mass storage filesystem that
the OS was booted from. Instead, it is a virtual filesystem that can only contain directories,
symbolic links, and mountpoints.
All the other filesystems are mounted as subdirectories of the root filesystem or further down
in the file hierarchy.
The booted filesystem (what would be the rootfs in a typical UNIX) is mounted in '/boot'. For
convenience, several links are created in the rootfs to well-known directories ('/bin', '/var',
etc). These point into the corresponding directories in /boot/system, which are managed by
packagefs.
The packagefs is a read-only union filesystem that makes available the content of various software
packages (installed as .hpkg files) to constitute the entire /boot/system directory. The files can
be accessed either as a complete filesystem hierarchy directly in /boot/system, or by referencing
specific packages exposed in /boot/system/package-links (each directory is a view of the packagefs,
containing only the files for a given package and all its dependencies). In theory, this allows
packages to be exposed in the package-links directory even while they are not actually "activated"
in the main system hierarchy. It also allows to access a version of a file provided by a specific
package, in the case that two packages provide identically named files.
While packagefs is mostly read-only, some directories (called "shine-through") are actually
exposing the content of the underlying filesystem. This includes for example the "config" directory
(for configuration files) and the "non-packaged" directory, where a mirror of the standard
filesystem hierarchy is available for non packaged software. This can be used to install software
locally that is not available yet in HPKG form (for example, as a destination for "make install").
For a complete list of directories and how to access them in a way that is safe to future
filesystem reorganizations, see \link find_directory, \link find_path, and \link BPathFinder.
*/
/*!
\addtgroup storage
See \link storage_intro for general concepts and filesystem hierarchy description.
*/