redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2024-03-18T09:58:09Zhttps://gitlab.redox-os.org/redox-os/kernel/-/issues/140Add a system call to delete a namespace2024-03-18T09:58:09ZRon WilliamsAdd a system call to delete a namespaceThere does not seem to be a system call to remove a namespace after use. Contain creates namespaces and should delete them when when the user session completes.There does not seem to be a system call to remove a namespace after use. Contain creates namespaces and should delete them when when the user session completes.https://gitlab.redox-os.org/redox-os/ion/-/issues/1032unexplained attempt to open file2023-11-15T12:30:19ZRon Williamsunexplained attempt to open fileRunning `ls foo`, where foo does not exist, seems to result in an attempt to open a file named `ls foo`. I'm not sure if this is an attempt to execute or just an attempt to test the existence of the file `ls foo`. Either way, it doesn't ...Running `ls foo`, where foo does not exist, seems to result in an attempt to open a file named `ls foo`. I'm not sure if this is an attempt to execute or just an attempt to test the existence of the file `ls foo`. Either way, it doesn't seem like the right thing to do.https://gitlab.redox-os.org/redox-os/website/-/issues/195(Goal) Up-to-date translations2024-03-01T19:45:05ZRibbon(Goal) Up-to-date translationsThe official language of the website is English, the goal is to make all outdated translations in pair with the English pages, this issue will cover the progress.
Each translator will comment if the translation is in pair with English (...The official language of the website is English, the goal is to make all outdated translations in pair with the English pages, this issue will cover the progress.
Each translator will comment if the translation is in pair with English (up-to-date) and the language box will be marked.
- [x] Portuguese
- [ ] Mandarin
- [ ] Spanish
- [ ] Russian
- [ ] French
- [ ] German
- [ ] Italian
- [ ] Turkish
- [ ] Swedish
- [ ] Dutch
- [ ] Danish
- [ ] Norwegian
- [ ] Czech
- [ ] Esperanto
- [ ] Japanese
- [ ] Korean
- [ ] Hungarian
- [ ] Polish
- [ ] Ukrainian
- [ ] Arabichttps://gitlab.redox-os.org/redox-os/redox/-/issues/1416Add an option to ignore recipe errors2024-01-13T07:04:44ZRibbonAdd an option to ignore recipe errorsThis option will ignore a recipe error and build the next recipe of the Cookbook configuration (`make all` and `make rebuild` commands).
Currently the CI server only update the packages if all recipes compiled successfully, it's time co...This option will ignore a recipe error and build the next recipe of the Cookbook configuration (`make all` and `make rebuild` commands).
Currently the CI server only update the packages if all recipes compiled successfully, it's time consuming and could delay important updates on recipes.
This is equivalent to "delta updates" but for CI, only the successfully compiled programs will be updated on the package repository.
It could be implemented on the `.config` file and the Cookbook configuration.https://gitlab.redox-os.org/redox-os/redox/-/issues/1415Add a "ci.sh" bootstrap script for the CI server2023-11-08T17:24:04ZRibbonAdd a "ci.sh" bootstrap script for the CI serverThe current [bootstrap.sh](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/bootstrap.sh?ref_type=heads) script contains packages to build the Redox base system and recipes on the [demo](https://gitlab.redox-os.org/redox-os/redox...The current [bootstrap.sh](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/bootstrap.sh?ref_type=heads) script contains packages to build the Redox base system and recipes on the [demo](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/config/x86_64/demo.toml?ref_type=heads) Cookbook configuration.
As Redox receive more recipes they require more build tools to be installed on the CI server, but the current script don't accept "non-demo recipes" dependencies.
The solution is to create a specific script to configure the CI server, it will be a reduced version of the `bootstrap.sh` script with:
- The command to install the Ubuntu/Debian packages (to build all recipes from Cookbook)
- The commands to download the Redox build system
- The command to install the Rust toolchain
- The command to enable a source-based toolchain
- The commands to build all Cookbook configurations and recipes
This will reduce the maintenance effort of the CI server, the script name can be `ci.sh`https://gitlab.redox-os.org/redox-os/website/-/issues/194Replace the Hugo static site generator by a Rust-written alternative2023-12-17T11:45:42ZRibbonReplace the Hugo static site generator by a Rust-written alternativeCurrently our website and book use Hugo to work, Hugo is written in Go, AFAIK its garbage collector would reduce the website/book uptime and probably has more bugs.
## Current Rust candidates:
- [Cobalt](https://cobalt-org.github.io/)
...Currently our website and book use Hugo to work, Hugo is written in Go, AFAIK its garbage collector would reduce the website/book uptime and probably has more bugs.
## Current Rust candidates:
- [Cobalt](https://cobalt-org.github.io/)
- [Shokunin](https://shokunin.one/)
- [Zola](https://www.getzola.org/)
- [Mandy](https://github.com/angeldollface/mandy)https://gitlab.redox-os.org/redox-os/redox/-/issues/1414Favor specifying git dependencies in Cargo.toml over submodule usage.2023-11-05T07:17:26ZGabriel HanssonFavor specifying git dependencies in Cargo.toml over submodule usage.Pulling in submodules (dependencies) that populate repo roots add inconveniences such as:
* Extra setup steps with `git submodule update`.
* Editor and developer has difficulties in separating actual repo source dependency source code.
...Pulling in submodules (dependencies) that populate repo roots add inconveniences such as:
* Extra setup steps with `git submodule update`.
* Editor and developer has difficulties in separating actual repo source dependency source code.
* Usage of two "dependency managers", cargo and git. `cargo update` and `cargo clean` is seldom enough.
Just to name a few.
`cargo` has supports adding these dependencies in `Cargo.toml` using statements such as:
```toml
regex = { git = "https://github.com/rust-lang/regex.git", rev = "4c59b707"}
```
(Further reading: https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories.)
Would it be worth deprecating the usage of submodules to using this method instead? Workspace repositories could be used wherever it is common to work on multiple crates at the same time. I believe this change would allow for a simpler build process and a more enjoyable dev experience.
Anyway, sending this as an issue first given that such changes would touch almost every part of Redox. I'm more than willing to give this a try, but I would love to hear your thoughts first.https://gitlab.redox-os.org/redox-os/relibc/-/issues/185Add configuration instructions for Linux on the README2023-11-03T09:39:34ZRibbonAdd configuration instructions for Linux on the READMEWe need to document how to replace glibc with relibc on the build systems.
Goals:
- [ ] Add a Cargo example
- [ ] Add a Makefile example
- [ ] Add a CMake example
- [ ] Add a Meson exampleWe need to document how to replace glibc with relibc on the build systems.
Goals:
- [ ] Add a Cargo example
- [ ] Add a Makefile example
- [ ] Add a CMake example
- [ ] Add a Meson examplehttps://gitlab.redox-os.org/redox-os/kernel/-/issues/139Save kernel memory after panic2023-12-14T13:53:49ZRibbonSave kernel memory after panicOn Linux the [kdump](https://en.wikipedia.org/wiki/Kdump_(Linux)) method is used to save the kernel memory to a file after a panic (crash dump), by doing this the kernel memory snapshot can be analyzed later (debugging).
This method giv...On Linux the [kdump](https://en.wikipedia.org/wiki/Kdump_(Linux)) method is used to save the kernel memory to a file after a panic (crash dump), by doing this the kernel memory snapshot can be analyzed later (debugging).
This method gives more information than crash logs.https://gitlab.redox-os.org/redox-os/libredox/-/issues/1Tracking issue for libredox migration2024-03-22T19:08:48ZJacob Lorentzon4ldo2@protonmail.comTracking issue for libredox migrationredox_syscall is used in lots of places in userspace, and should, except for low-level userspace components, be replaced by libredox.
Such crates can be found both by searching for reverse-dependencies on crates.io, and directly checkin...redox_syscall is used in lots of places in userspace, and should, except for low-level userspace components, be replaced by libredox.
Such crates can be found both by searching for reverse-dependencies on crates.io, and directly checking redox repositories.
Libredox isn't 100% feature-complete yet, but this can be done incrementally.
# Recipes using redox_syscall directly
- [x] zerod - https://gitlab.redox-os.org/redox-os/zerod/-/merge_requests/5
- [x] userutils - https://gitlab.redox-os.org/redox-os/userutils/-/merge_requests/43
- [x] redoxfs - https://gitlab.redox-os.org/redox-os/redoxfs/-/merge_requests/71 (except unstable mremap)
- [x] ramfs - https://gitlab.redox-os.org/redox-os/ramfs/-/merge_requests/5
- [x] ptyd - https://gitlab.redox-os.org/redox-os/ptyd/-/merge_requests/8
- [x] randd - https://gitlab.redox-os.org/redox-os/randd/-/merge_requests/12
- [x] orbterm - https://gitlab.redox-os.org/redox-os/orbterm/-/merge_requests/21
- [x] orbital - https://gitlab.redox-os.org/redox-os/orbital/-/merge_requests/54 https://gitlab.redox-os.org/redox-os/orbital/-/merge_requests/55
- [ ] orbutils
- [x] nulld - https://gitlab.redox-os.org/redox-os/zerod/-/merge_requests/5
- [x] netutils - https://gitlab.redox-os.org/redox-os/netutils/-/merge_requests/46
- [x] netstack - https://gitlab.redox-os.org/redox-os/netstack/-/merge_requests/46
- [x] logd - https://gitlab.redox-os.org/redox-os/logd/-/merge_requests/4
- [x] ipcd - https://gitlab.redox-os.org/redox-os/ipcd/-/merge_requests/6
- [x] init - https://gitlab.redox-os.org/redox-os/init/-/merge_requests/10
- [ ] installer
- [x] extrautils - https://gitlab.redox-os.org/redox-os/extrautils/-/merge_requests/55
- [ ] contain
- [x] coreutils - https://gitlab.redox-os.org/redox-os/coreutils/-/merge_requests/209
- [x] audiod - https://gitlab.redox-os.org/redox-os/audiod/-/merge_requests/2
## Exceptions
- relibc - currently the very library providing the libredox symbols
- bootstrap - relibc isn't available when bootstrap runs
- escalated - uses relibc internals directly
- kernel - obviously allowed to use redox_syscall
- bootloader
- [x] drivers - https://gitlab.redox-os.org/redox-os/drivers/-/merge_requests/150 (except virttophys and iopl)
# Notable crates depending on redox_syscall
- [x] redox_users
- [x] redox_termios
- [x] redox_event
- [x] termion
- [x] redox_liner
- [x] tempfile - only uses error::ENOSYS
- [x] filetime - https://github.com/alexcrichton/filetime/pull/103 (not yet released, but Redox's fork works for now)
- [ ] parking_lot_core (although it currently shortcuts to the `#[cfg(unix)]` path which uses libc)
- [ ] winit - uses syscall and orbclient directly
- [x] orbclient
- [ ] datetime - used by `eza`, but looks unmaintained
- [ ] tokio-tar
- [ ] ...
- [x] redoxfs
- [ ] redoxer
- [x] redox-daemonJacob Lorentzon4ldo2@protonmail.comJacob Lorentzon4ldo2@protonmail.comhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1413HPET instability when running with qemu2023-10-30T14:50:46ZWill AngenentHPET instability when running with qemuWhen running the desktop build, compiled under ubuntu linux, with qemu 7.2.0 installed with brew, under MacOS 12.2, intel CPU, I get random crashes like these:
- [1.log](/uploads/29fadace825f9c6f9e526c1b2043bccc/1.log)
- [2.log](/upload...When running the desktop build, compiled under ubuntu linux, with qemu 7.2.0 installed with brew, under MacOS 12.2, intel CPU, I get random crashes like these:
- [1.log](/uploads/29fadace825f9c6f9e526c1b2043bccc/1.log)
- [2.log](/uploads/992d70d981db3a47eb5e9ce1a40c38d3/2.log)
- [3.log](/uploads/7d0a6b848b2758650bd1d53e8cbea666/3.log)
- [4.log](/uploads/8732e27ed04a27211f8b60c4e211efe9/4.log)
- [5.log](/uploads/1c5193aa6372b4c565fbbccfad04bfa5/5.log)
It appears that `period_fs` [here](https://gitlab.redox-os.org/redox-os/kernel/-/blob/master/src/arch/x86_64/time.rs#L19) is becoming zero.
When adding this debug print:
```
// Calculate divisor
if period_fs == 0 {
let capability2 = unsafe { hpet.base_address.read_u64(hpet::CAPABILITY_OFFSET) };
println!(
"hpet={:?} capability={:?} capability2={:?}",
hpet, capability, capability2
);
}
```
I managed to get this output:
```
capability=10164 capability2=42949675116306945
```
By the way:
42949675116306945 translates to 0x9896808086A201.
0x9896808086A201 >> 32 is 0x989680. In decimal, this is 10000000, the clock period.
The contents of hpet struct is the same in good & bad boots.https://gitlab.redox-os.org/redox-os/kernel/-/issues/138Support restartable sequences2023-10-29T20:37:56ZJacob Lorentzon4ldo2@protonmail.comSupport restartable sequencesRestartable sequences are available on Linux, and would allow better spinlock performance, and possibly make it easier to move parts of the futex API to userspace (because atomic hashmaps are hard without using spinlocks at least *somewh...Restartable sequences are available on Linux, and would allow better spinlock performance, and possibly make it easier to move parts of the futex API to userspace (because atomic hashmaps are hard without using spinlocks at least *somewhere*).
This would likely be achieved by userspace providing its TCB page to the kernel. Such a page may also store sigprocmask and possibly the pending mask/signal arguments, if most of signal handling is moved to userspace.https://gitlab.redox-os.org/redox-os/installer/-/issues/16pkgar support2023-10-29T15:20:35ZRibbonpkgar supportWhen the `REPO_BINARY` environment variable is enabled the installer don't download/install `pkgar` packages from the [CI server](https://static.redox-os.org/pkg/), even using the `pkgar` crate.When the `REPO_BINARY` environment variable is enabled the installer don't download/install `pkgar` packages from the [CI server](https://static.redox-os.org/pkg/), even using the `pkgar` crate.https://gitlab.redox-os.org/redox-os/redox/-/issues/1412Kernel and userspace separation policy2024-01-13T08:34:40ZRibbonKernel and userspace separation policyThis issue covers which components may be moved to userspace, or should continue stay in the kernel.
# Kernel
- CPU drivers - performance
- Memory manager - performance, and moving that to userspace is hard
- Context switch - core part...This issue covers which components may be moved to userspace, or should continue stay in the kernel.
# Kernel
- CPU drivers - performance
- Memory manager - performance, and moving that to userspace is hard
- Context switch - core part of the kernel
- Capability system - the kernel needs to implement at least the bare minimum to be able to isolate processes from each other
- Scheduler - performance
# Userspace currently
- cwd handling
- initfs
- fork and execv
- most drivers
- filesystem
- everything else
# Possible to move to userspace
- RTC driver
- path parsing (would require openat)
- the current namespace implementation (would also require openat)
- (part of) the file descriptor table (descriptors, not descriptions) - allows optimizing lseek, fcntl, POSIX pipes, etc.
- process management, including uid/gid/(not yet implemented:) supplementary groups
- application processor startup
- file descriptor allocation (where the lowest available number must be picked)
- virtual memory range allocationhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1411server-minimal can't be built from binaries2023-10-27T13:26:30ZRon Williamsserver-minimal can't be built from binaries`orbutils-background` package is not available as a static package, preventing server-minimal from being built from binaries.`orbutils-background` package is not available as a static package, preventing server-minimal from being built from binaries.https://gitlab.redox-os.org/redox-os/redox/-/issues/1410cd :: && mkdir myscheme2023-10-27T13:25:42ZPramod V Ucd :: && mkdir myscheme--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
I `cd ::`, which navigates to the apparent directory of schemes.
`ls` is very slow here.
The issue here occures rarely and...--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
I `cd ::`, which navigates to the apparent directory of schemes.
`ls` is very slow here.
The issue here occures rarely and randomly, about once in four tries.
Also, the main issue occurs when using the CLI from the host, not orbterm, in which case an entirely different issue occurs:
```
ion: prompt expansion failed: pipeline execution error: command error: Operation not permitted (os error 1)
```
In the external CLI, I `mkdir :myscheme`,`myscheme:`,`myscheme`,`:myscheme:`.
If the issue occurs, the entire system freezes. If the issue doesn't occur:
```
mkdir: thread 'main' panicked at src/uucore/src/lib/mods/error.rs:534:22:
Unexpected io error: Bad file number (os error 9)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```
(Even after `let RUST_BACKTRACE=1` within redox)
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
<!-- Redox OS Release: 0.0.0 -->
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Replace me
- `uname -a`:
```
Linux pvu-inspiron3511 6.5.8-4-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Oct 25 05:14:18 UTC 2023 x86_64 GNU/Linux
```
- `rustc -V`:
```
rustc 1.74.0-nightly (e3abbd499 2023-09-06)
```
- `git rev-parse HEAD`:
```
234dc596395f873f69b65e2bdea714f0bf9b0bc1
```
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
- `qemu -version`:
```
QEMU emulator version 8.1.2
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
```
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
0. Minimize the qemu window, and use the CLI where you started the qemu instance.
1. `cd ::` to the apparent directory of schemes.
2. `mkdir` `:myscheme`,`myscheme:`,`myscheme`,`:myscheme:`, one of them will randomly work.
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
In orbterm:
```
ion: prompt expansion failed: pipeline execution error: command error: Operation not permitted (os error 1)
```
In external CLI, if the issue doesn't work:
```
mkdir: thread 'main' panicked at src/uucore/src/lib/mods/error.rs:534:22:
Unexpected io error: Bad file number (os error 9)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```
(I *have* `let RUST_BACKTRACE=1`, still...)
When the issue occurs, the entire redox system freezes
[Full output of `script`](/uploads/ab955f78e21f63e0d5f84f95dece1765/redox.script-out.txt)
[`grep`ed contents with mkdir](/uploads/6542ee67e382667681b706fd44f8136d/mkdirscheme.log)
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
<!-- **Expected behavior**: -->
<!-- Replace me -->
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
<!-- **Actual behavior**: -->
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
Logs are attached.
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
<!-- **Proposed solution**: -->
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->
<!-- ## Optional references -->
<!-- If you have found issues or pull requests that are related to or blocking this issue, please link them below. See https://help.github.com/articles/autolinked-references-and-urls/ for more options. You can also link related code snippets by providing the permalink. See https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/ for more information. -->
<!-- Related to: -->
<!-- Blocked by: -->
<!-- ## Optional extras -->
<!-- If you have other relevant information not found in other sections, you can include it below. -->
<!-- **Code?** Awesome! You can also create a pull request with a reference to this issue. -->
<!-- **Files?** Attach your relevant files by dragging & dropping or pasting them below. -->
<!-- You also can preview your report before submitting it. Thanks for contributing to Redox! -->https://gitlab.redox-os.org/redox-os/redox/-/issues/1409Replace the Hugo static site generator by a Rust-written alternative2023-11-05T21:30:06ZRibbonReplace the Hugo static site generator by a Rust-written alternativeCurrently our website and book use Hugo to work, Hugo is written in Go, AFAIK its garbage collector would reduce the website/book uptime and probably has more bugs.
## Current Rust candidates:
- [Cobalt](https://cobalt-org.github.io/)
...Currently our website and book use Hugo to work, Hugo is written in Go, AFAIK its garbage collector would reduce the website/book uptime and probably has more bugs.
## Current Rust candidates:
- [Cobalt](https://cobalt-org.github.io/)
- [Shokunin](https://shokunin.one/)
- [Zola](https://www.getzola.org/)
- [Mandy](https://github.com/angeldollface/mandy)https://gitlab.redox-os.org/redox-os/redox/-/issues/1408Port cosmic-comp2024-01-13T07:57:18ZRibbonPort cosmic-comp[cosmic-comp](https://github.com/pop-os/cosmic-comp) is the most complete Rust-written Wayland compositor of the world, being Rust it become the most easy Wayland solution for us, because we already have upstream Redox support on many cr...[cosmic-comp](https://github.com/pop-os/cosmic-comp) is the most complete Rust-written Wayland compositor of the world, being Rust it become the most easy Wayland solution for us, because we already have upstream Redox support on many crates.https://gitlab.redox-os.org/redox-os/redox/-/issues/1407(Feature request) Automatic operating system detection on boot loader2023-10-25T17:39:39ZRibbon(Feature request) Automatic operating system detection on boot loaderDuring the Redox installation on HD/SSD the Redox boot loader will replace the active boot loader of any other OS, to improve our dual-boot support, we could automatically detect Windows, Linux and BSD installations on the disk and creat...During the Redox installation on HD/SSD the Redox boot loader will replace the active boot loader of any other OS, to improve our dual-boot support, we could automatically detect Windows, Linux and BSD installations on the disk and create menu entries for them, like GRUB does.
## UEFI case
UEFI boot loaders stay in a FAT32 partition, thus our boot loader can load other boot loaders (the most easy method, GRUB does this).
## BIOS case
Generally BIOS boot loaders are installed on the MBR partition table of the disk, probably our boot loader will need to manually load the OS kernels.https://gitlab.redox-os.org/redox-os/relibc/-/issues/184Tracking issue for missing functions to compile CPython 3.122023-10-22T23:45:53ZDarley BarretoTracking issue for missing functions to compile CPython 3.12- [ ] bindtextdomain
- [ ] bind_textdomain_codeset
- [ ] clock_nanosleep
- [ ] close_range
- [ ] confstr
- [ ] copy_file_range
- [ ] ctermid
- [ ] __ctype_b_loc
- [ ] __ctype_tolower_loc
- [ ] __ctype_toupper_loc
- [ ] dcgettext
- [ ] du...- [ ] bindtextdomain
- [ ] bind_textdomain_codeset
- [ ] clock_nanosleep
- [ ] close_range
- [ ] confstr
- [ ] copy_file_range
- [ ] ctermid
- [ ] __ctype_b_loc
- [ ] __ctype_tolower_loc
- [ ] __ctype_toupper_loc
- [ ] dcgettext
- [ ] dup3
- [ ] eventfd
- [ ] eventfd_read
- [ ] eventfd_write
- [ ] faccessat
- [ ] fchmodat
- [ ] fchownat
- [ ] fcntl64
- [ ] fdopendir
- [ ] fexecve
- [ ] fgetxattr
- [ ] flistxattr
- [ ] fopen64
- [ ] forkpty
- [ ] fremovexattr
- [ ] fsetxattr
- [ ] fstat64
- [ ] fstatat64
- [ ] fstatvfs64
- [ ] ftruncate64
- [ ] getloadavg
- [ ] getresgid
- [ ] getresuid
- [ ] getrlimit64
- [ ] getrusage
- [ ] getxattr
- [ ] initgroups
- [ ] lgetxattr
- [ ] __libc_current_sigrtmax
- [ ] __libc_current_sigrtmin
- [ ] __libc_start_main
- [ ] linkat
- [ ] listxattr
- [ ] llistxattr
- [ ] lockf64
- [ ] login_tty
- [ ] lremovexattr
- [ ] lseek64
- [ ] lsetxattr
- [ ] lstat64
- [ ] memfd_create
- [ ] mkdirat
- [ ] mkfifoat
- [ ] mknod
- [ ] mknodat
- [ ] mmap64
- [ ] nice
- [ ] nl_langinfo
- [ ] open64
- [ ] openat64
- [ ] openpty
- [ ] pause
- [ ] posix_fadvise64
- [ ] posix_fallocate64
- [ ] posix_spawn
- [ ] posix_spawnattr_destroy
- [ ] posix_spawnattr_init
- [ ] posix_spawnattr_setflags
- [ ] posix_spawnattr_setpgroup
- [ ] posix_spawnattr_setschedparam
- [ ] posix_spawnattr_setschedpolicy
- [ ] posix_spawnattr_setsigdefault
- [ ] posix_spawnattr_setsigmask
- [ ] posix_spawn_file_actions_addclose
- [ ] posix_spawn_file_actions_adddup2
- [ ] posix_spawn_file_actions_addopen
- [ ] posix_spawn_file_actions_destroy
- [ ] posix_spawn_file_actions_init
- [ ] posix_spawnp
- [ ] pread64
- [ ] preadv64v2
- [ ] pwrite64
- [ ] pwritev64v2
- [ ] readdir64
- [ ] readlinkat
- [ ] removexattr
- [ ] renameat
- [ ] __sched_cpualloc
- [ ] __sched_cpucount
- [ ] __sched_cpufree
- [ ] sched_getaffinity
- [ ] sched_getparam
- [ ] sched_get_priority_max
- [ ] sched_get_priority_min
- [ ] sched_getscheduler
- [ ] sched_rr_get_interval
- [ ] sched_setaffinity
- [ ] sched_setparam
- [ ] sched_setscheduler
- [ ] sem_clockwait
- [ ] sendfile64
- [ ] setegid
- [ ] seteuid
- [ ] setns
- [ ] setresgid
- [ ] setresuid
- [ ] setrlimit64
- [ ] setxattr
- [ ] sigwaitinfo
- [ ] splice
- [ ] stat64
- [ ] statvfs64
- [ ] symlinkat
- [ ] syscall
- [ ] __sysconf
- [ ] textdomain
- [ ] times
- [ ] truncate64
- [ ] __uflow
- [ ] unlinkat
- [ ] unshare
- [ ] utimensat
- [ ] wait3
- [ ] wait4
- [ ] waitid
- [ ] wcsftime
- [ ] wcsxfrm