diff options
Diffstat (limited to 'community')
| -rw-r--r-- | community/gsoc/project_ideas.mdwn | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn index 0dc5f152..c4b665b7 100644 --- a/community/gsoc/project_ideas.mdwn +++ b/community/gsoc/project_ideas.mdwn @@ -145,7 +145,7 @@ virtualization using so-called logical partitions. (Similar to Linux-vserver, OpenVZ etc.) While subhurd allow creating a complete second system instance, with an own set -of Hurd servers and UNIX daemons and all, there are also situations where it is +of Hurd servers and [[UNIX]] daemons and all, there are also situations where it is desirable to have a smaller subenvironment, living withing the main system and using most of its facilities -- similar to a chroot environment. A simple way to create such a subenvironment with a single command would be very helpful. @@ -279,7 +279,7 @@ ongoing. ## Fix File Locking -Over the years, UNIX has aquired a host of different file locking mechanisms. +Over the years, [[UNIX]] has aquired a host of different file locking mechanisms. Some of them work on the Hurd, while others are buggy or only partially implemented. This breaks many applications. @@ -745,7 +745,7 @@ alltogether, the current Hurd implementation is based on variant of the original CMU [[microkernel/Mach]]. Unfortunately, Mach was created about two decades ago, and is in turn based on -even older BSD code. Parts of the BSD kernel -- file systems, UNIX mechanisms +even older BSD code. Parts of the BSD kernel -- file systems, [[UNIX]] [[mechanism]]s like processes and signals, etc. -- were ripped out (to be implemented in [[userspace_servers|hurd/translator]] instead); while other mechanisms were added to allow implementing stuff in userspace. @@ -821,7 +821,7 @@ shell script that uses xmlfs to extract some interesting information from an ## Allow Using `unionfs` Early at Boot -In UNIX systems, traditionally most software is installed in a common directory +In [[UNIX]] systems, traditionally most software is installed in a common directory hierachy, where files from various packages live beside each other, grouped by function: user-invokable executables in `/bin`, system-wide configuration files in `/etc`, architecture specific static files in `/lib`, variable data in @@ -897,7 +897,7 @@ to do a detailed analysis of the problem. ## Lexical `..` Resolution -For historical reasons, UNIX filesystems have a real (hard) `..` link from each +For historical reasons, [[UNIX]] filesystems have a real (hard) `..` link from each directory pointing to its parent. However, this is problematic, because the meaning of "parent" really depends on context. If you have a symlink for example, you can reach a certain node in the filesystem by a different path. If @@ -926,7 +926,7 @@ suggestions welcome... :-) ) ## Secure `chroot` implementation -As the Hurd attempts to be (almost) fully UNIX-compatible, it also implements a +As the Hurd attempts to be (almost) fully [[UNIX]]-compatible, it also implements a `chroot()` system call. However, the current implementation is not really good, as it allows easily escaping the `chroot`, for example by use of [[passive_translators|hurd/translator]]. |