Enter the query into the form above.
API method:
GET /api/symbols?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Return #t if user namespaces can be created by unprivileged users.
Run THUNK in a new container process and return its PID. ROOT specifies the root directory for the container. MOUNTS is a list of <file-system> objects that specify file systems to mount inside the container. NAMESPACES is a list of symbols that correspond to the possible Linux namespaces: mnt, ipc, uts, user, and net. When LOCK-MOUNTS? is true, arrange so that none of MOUNTS can be unmounted or remounted individually from within THUNK.
When LOOPBACK-NETWORK? is true and 'net is amount NAMESPACES, set up the loopback device ("lo") and a minimal /etc/hosts.
When WRITABLE-ROOT? is false, remount the container's root as read-only before calling THUNK. Call POPULATE-FILE-SYSTEM before the root is (potentially) made read-only.
HOST-UIDS specifies the number of host user identifiers to map into the user namespace. GUEST-UID and GUEST-GID specify the first UID (respectively GID) that host UIDs (respectively GIDs) map to in the namespace.
Like 'container-excursion', but return the return value of THUNK.
Run THUNK in a new container process and return its exit status; call PROCESS-SPAWNED-HOOK with the PID of the new process that has been spawned. MOUNTS is a list of <file-system> objects that specify file systems to mount inside the container. NAMESPACES is a list of symbols corresponding to the identifiers for Linux namespaces: mnt, ipc, uts, pid, user, and net. By default, all namespaces are used.
HOST-UIDS is the number of host user identifiers to map into the container's user namespace, if there is one. By default, only a single uid/gid, that of the current user, is mapped into the container. The host user that creates the container is the root user (uid/gid 0) within the container. Only root can map more than a single uid/gid.
GUEST-UID and GUEST-GID specify the first UID (respectively GID) that host UIDs (respectively GIDs) map to in the namespace.
RELAYED-SIGNALS is the list of signals that are "relayed" to the container process when caught by its parent.
When LOOPBACK-NETWORK? is true and 'net is amount NAMESPACES, set up the loopback device ("lo") and a minimal /etc/hosts.
When WRITABLE-ROOT? is false, remount the container's root as read-only before calling THUNK. Call POPULATE-FILE-SYSTEM before the root is (potentially) made read-only.
When CHILD-IS-PID1? is true, and if NAMESPACES contains 'pid', then the child process runs directly as PID 1. As such, it is responsible for (1) installing signal handlers and (2) reaping terminated processes by calling 'waitpid'. When CHILD-IS-PID1? is false, a new intermediate process is created instead that takes this responsibility.
Note that if THUNK needs to load any additional Guile modules, the relevant module files must be present in one of the mappings in MOUNTS and the Guile load path must be adjusted as needed.
Write an initial RAM disk (initrd) to OUTPUT. The initrd starts the script at INIT, running GUILE. It contains all the items referred to by REFERENCES-GRAPHS.
Write a cpio archive containing DIRECTORY to file OUTPUT, with reset timestamps in the archive. When COMPRESS? is true, compress it using GZIP. On success, return OUTPUT.
Return the list of modules that FILE depends on. The returned list contains module names, not actual file names.
Create a new directory OUTPUT and ensure that the directory OUTPUT/lib/modules/VERSION can be used as a source of Linux kernel modules for the first kmod in PATH now to eventually load. Take modules to put into OUTPUT from INPUTS.
Right now that means it creates modules.*.bin which modprobe will use to find loadable modules.
Lookup module NAME under DIRECTORY, and return its absolute file name. NAME can be a file name with or without '.ko', or it can be a module name. Raise an error if it could not be found.
Module names can differ from file names in interesting ways; for instance, module names usually (always?) use underscores as the inter-word separator, whereas file names often, but not always, use hyphens. Examples: "usb-storage.ko", "serpent_generic.ko".
Return the list of names of currently loaded Linux modules.
Write a database that maps "module names" as they appear in the relevant ELF section of '.ko[.gz|.xz|.zst]' files, to actual file names. This format is Guix-specific. It aims to deal with inconsistent naming, in particular hyphens vs. underscores.
Return the list of PCI devices of the system (<pci-device> records).
Read the 'pci.ids' database at FILE (get it from the pciutils package or from <https://pci-ids.ucw.cz/>) and return a lookup procedure that takes a PCI vendor ID and a device ID (two integers) and returns the vendor name and device name as two values.
Return the list of modules that match ALIAS according to KNOWN-ALIASES. ALIAS is a string like "scsi:t-0x00" as returned by 'device-module-aliases'.
Return the list of alias/module pairs read from ALIAS-FILE. Each alias is actually a pattern.