wishlist:david
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
wishlist:david [2017/04/09 12:28] dcvmoole another new todo item |
wishlist:david [2017/10/11 18:13] (current) dcvmoole networking project is merged |
||
|---|---|---|---|
| Line 204: | Line 204: | ||
| * complication: a proper implementation will require a non-trivial extension to the PM/VFS protocol | * complication: a proper implementation will require a non-trivial extension to the PM/VFS protocol | ||
| * subsequent project: also implement paccept(2); this will require storing more call state in VFS | * subsequent project: also implement paccept(2); this will require storing more call state in VFS | ||
| - | |||
| - | === Move the BSD socket API into VFS === | ||
| - | |||
| - | * status: **PULL REQUEST FILED** | ||
| - | * reason: libc should not need to test or track socket types, it violates the light-libc minix philosophy | ||
| - | * reason: the individual writes to implement sendto (etc) probably violate posix signal atomicity | ||
| - | * benefit: this allows for proper socket call support in trace(1) | ||
| - | * complication: this will break everything, require INET's retirement and a substantial UDS rewrite | ||
| - | * note: this is probably best done along with many other network stack related changes | ||
| === Implement job control === | === Implement job control === | ||
| Line 230: | Line 221: | ||
| * complication: different file system will require different small exceptions | * complication: different file system will require different small exceptions | ||
| * complication: no neat way to model orphan management in the edge (directory) layer | * complication: no neat way to model orphan management in the edge (directory) layer | ||
| + | |||
| + | === Move the BSD socket API into VFS === | ||
| + | |||
| + | * status: **MERGED** | ||
| + | * reason: libc should not need to test or track socket types, it violates the light-libc minix philosophy | ||
| + | * reason: the individual writes to implement sendto (etc) probably violate posix signal atomicity | ||
| + | * benefit: this allows for proper socket call support in trace(1) | ||
| + | * complication: this will break everything, require INET's retirement and a substantial UDS rewrite | ||
| + | * note: this is probably best done along with many other network stack related changes | ||
| === Look into setuid/seteuid behavior === | === Look into setuid/seteuid behavior === | ||
wishlist/david.1491733728.txt.gz · Last modified: 2017/04/09 12:28 by dcvmoole
