1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
[[meta copyright="Copyright © 2008 Free Software Foundation, Inc."]]
[[meta license="""[[toggle id="license" text="GFDL 1.2+"]][[toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled
[[GNU_Free_Documentation_License|/fdl]]."]]"""]]
Name: Flávio Cruz
Email: flaviocruz at gmail dot com
Some [Hurd stuff](http://opensvn.csie.org/leic/hurd/)
And code: [cl-hurd](http://freehg.org/u/flavioc/cl-hurd/)
hg clone [http://freehg.org/u/flavioc/cl-hurd/](http://freehg.org/u/flavioc/cl-hurd/)
## Summer session
Creating an extensible translator library in lisp using the mig generated stubs.
### What's done
- The library for writing translators is mostly written.
- This library is intended to implement virtual filesystems. Examples are: translators were data is located in a local file (like zipfs, tarfs, rarfs, ...), single file translators (that do content filtering, output of a command, etc), network based filesystems (ftpfs, httpfs, ...), proxy filesystems (like hostmux, usermux, etc..)
- It's possible to specialize the basic translator library and implement new translator classes. This is done using CLOS.
- There is a tree-translator class that makes the managing of a node tree very easy, doing all the work for us, through a simple directory API and implementing the directory callbacks for us.
- There is a simple example (something like zipfs) translator that can expose the directories and file contents of a ZIP file.
- More translator examples include:
- /dev/null translator.
- /dev/zero translator.
- translator that creates a symlink node.
- tmpfs like translator.
- a translator that does proxying between clients and the underlying translator return all data in upper-case.
- a translator that watches for changes in a file describing the file system structure.
- Translator options (manipulated through fsysopts) have a simple and easy to use API.
- All the Mach port manipulation API is available.
- It's possible to send and receive messages. Simple example:
<pre>
(let* ((spec-mixed (make-message-spec :fields '(:string :integer :char :string :integer :real)))
(msg-mixed (make-message :spec spec-mixed))
(port (port-allocate :right-receive)))
(send-message msg-mixed :remote port :data (list "abc" 42 #\b "cba" 314 3.14))
(receive-message msg-mixed :source port) ; This returns T on success.
(get-message msg-mixed))) ; Returns '("abc" 42 #\b "cba" 314 3.14)
</pre>
- New message types (like :string, :integer) can be implemented, providing a powerful extension mechanism.
- Creation of symlinks and symlink path resolution.
- Creation of character/block devices, fifos and sockets.
- Patch that opens stdin + stdout to /dev/null.
- Project has been separated into 5 ASDF installable systems:
- hurd-common
- mach
- hurd
- hurd-translator
- tree-translator
### What needs to be done
- Using continuations for IO blocking operations. This can be done using cl-cont.
- Fix file-exec, fsys-getroot (block happens in trivfs based translators, when they do RPC's to me when I call fsys_getroot to them) and fetch-root (for passive translators).
- Use the socket stubs?
- Documentation
- More testing
- Integrate upstream
- I think it's a better idea to create a separate module/project for the project than integrating it in the Hurd tree.
- Another advantage is that savannah provides mercurial hosting.
### Project dependencies
- CLISP
- [CFFI](http://common-lisp.net/project/cffi/) (apt-get installable)
- [Flexi streams](http://www.weitz.de/flexi-streams/) (apt-get installable)
- [Trivial garbage](http://www.cliki.net/trivial-garbage) (not in debian repositories)
- [cl-zip](http://common-lisp.net/project/zip/) (only needed for the example translator)
## To do
### Documentation
- Manually Bootstrapping a Translator
### Translation
- Translate the Hurd website to Portuguese?
## Completed tasks
### Patches
- http://alioth.debian.org/tracker/index.php?group_id=30628&atid=410472
- libsvg patch accepted.
- Adapted glibc patch (http://www.schwinge.homeip.net/~thomas/tmp/glibc-patches/0009-2007-07-22-version-of-init-first.c_vs._GCC_4.1.patch.patch)
- http://opensvn.csie.org/leic/hurd/patches/glibc-init-first.patch
- Patch to remove some GNUMach IPC warnings and minor cleanup:
- http://opensvn.csie.org/leic/hurd/patches/gnumach-ipc-warnings.patch
- Website patches that correct some encountered typos:
- http://opensvn.csie.org/leic/hurd/patches/hurd-talk-typo.patch
### Documentation read
- GNU/Hurd User's Guide, an introduction to the important concepts and software of the GNU system, written for new users, AKA "GNUbies."
- Towards a New Strategy of OS Design, an architectural overview by Thomas Bushnell, BSG.
- The Hurd, a presentation by Marcus Brinkmann.
- The Hurd Hacking Guide.
- The GNU Mach Reference Manual
- The GNU Hurd Reference Manual
- The Unofficial GNU Mach IPC beginner's guide
- Mach IPC without MIG
- CFFI User's Manual
### Before selection
- Uptime program in C and Lisp using CFFI.
- Hello translator.
## Misc
### Lisp implementations that run on Hurd
- Clisp
- ECL
- ?
|
