diff options
| -rw-r--r-- | community/weblogs/ArneBab/niches_for_the_hurd.mdwn | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn index 0bc07daa..523c0289 100644 --- a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn +++ b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn @@ -168,6 +168,19 @@ aren't possible. - Tinkering for fun - need documentation about the fun things which can be done. +- A more powerful alternative to FUSE filesystems: While FUSE is limited to standard +filesystem semantics, while Hurd translators can implement whatever they +want. +It is possible to change the behaviour in any aspect, including the way +file name lookup works. Admittedly the only specific use case I know is +the possibility to implement namespace-based translator selection with a +set of normal translators, without any changes to the Hurd itself. +It is also possible to extend the filesystem interfaces, adding new RPCs +and options as needed. This allows using the filesystem for +communication, yet implementing domain-specific interfaces where +standard filesystems are too unefficient or cumbersome. A sound server +would be one possible use case. + ### Need a few months of coding - A filesystem-based package manager. @@ -188,19 +201,6 @@ between computers). Maybe this should be placed in "need a lot of coding". you (translators written in scripting laguages can make this easier - they could also for example be taken to each computer on USB stick). -- A more powerful alternative to FUSE filesystems: While FUSE is limited to standard -filesystem semantics, while Hurd translators can implement whatever they -want. -It is possible to change the behaviour in any aspect, including the way -file name lookup works. Admittedly the only specific use case I know is -the possibility to implement namespace-based translator selection with a -set of normal translators, without any changes to the Hurd itself. -It is also possible to extend the filesystem interfaces, adding new RPCs -and options as needed. This allows using the filesystem for -communication, yet implementing domain-specific interfaces where -standard filesystems are too unefficient or cumbersome. A sound server -would be one possible use case. - - Namespace based translator selection (if you for example want to quickly check the contents of an iso image, just look at them via 'ls image.iso,,iso9660fs'). |