diff options
| author | Joshua Branson <jbranso@dismail.de> | 2026-04-05 12:41:56 -0400 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2026-04-16 00:24:35 +0200 |
| commit | 03da3f057b78da1968f67d2e77c892cb3a04e7ce (patch) | |
| tree | d37359d9619d4d4d35b493761d7e5a72e9ce5f36 | |
| parent | b85fada9d95c11c312946e8027b897de411fdfed (diff) | |
fix a typo: extfs -> ext2fs
Message-ID: <20260405164201.3490-8-jbranso@dismail.de>
| -rw-r--r-- | open_issues/resource_management_problems.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/open_issues/resource_management_problems.mdwn b/open_issues/resource_management_problems.mdwn index d1a29a00..6c3a5d3e 100644 --- a/open_issues/resource_management_problems.mdwn +++ b/open_issues/resource_management_problems.mdwn @@ -24,7 +24,7 @@ discardable, for example. This is the fundamental failing of the Mach/Hurd architecture. The Hurd operates via many server to client relationships, in which servers request resources on behalf of their clients. For example at -any given time, `extfs` could have many different clients (emacs, vim, +any given time, `ext2fs` could have many different clients (emacs, vim, git etc.) requesting data, creating files, deleting files, re-naming files, etc. Suppose one rogue client out of 50 is continually requesting increasingly more memory, which is exhasting the machine's |