diff options
| -rw-r--r-- | contributing.mdwn | 2 | ||||
| -rw-r--r-- | faq/foo_max.mdwn | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index 6fdc2d41..9ecdbdce 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -177,7 +177,7 @@ This is the list of tasks that we *want* to address soon, starting with the most * Extensively test (e.g. running testsuites of glibc, perl, curl, rust-mio) and fix the lwip-based TCP/IP stack, to be sure we don't get regressions by switching to it. * Fix swapping with `rumpdisk`. * Fix the [GPLv2 vs GPLv3 licence incompatibility between ext2fs and libparted](https://bugs.debian.org/838244): - * For /hurd/ext2fs, use a different libstoreio that does not include the parted module. + * For /hurd/ext2fs, use a different libstore that does not include the parted module. * For /hurd/ext2fs.static in the bootstrap chain (e.g. to access wd0s1), add a storeio translator before it, and have ext2fs open it, use `file_get_storage_info` and access the underlying device. That wouldn't need any code modification if we were using an initial ramfs exposing that storeio on /dev/wd0s1. * Prevent duplicate instances of `rumpdisk` from competing for the disk PCI cards (e.g. when a second one gets started from a chroot), otherwise mayhem happens. * Fix the memory consumption of `rumpdisk`. diff --git a/faq/foo_max.mdwn b/faq/foo_max.mdwn index 14015b9b..5f736680 100644 --- a/faq/foo_max.mdwn +++ b/faq/foo_max.mdwn @@ -39,7 +39,7 @@ since Posix 2008 `realpath(path, NULL)` and `getcwd(NULL, 0)` allocate the path dynamically. In general, using `FOO_MAX` in source code (with a large value) leads to code -that is not acually checking against overflows. `PATH_MAX` being 4096 is +that is not actually checking against overflows. `PATH_MAX` being 4096 is actually "wrong" on Linux: $ printf '#include <limits.h>\nPATH_MAX' | cpp -P |