Hi, On Mon, Mar 12, 2007 at 12:27:09AM +0100, Thomas Schwinge wrote:
> http://savannah.gnu.org/task/?5469 -- Rewrite pfinet > > The libchannel project should be done before, or at least in parallel, > I'd say. [...] > http://savannah.gnu.org/task/?5485 -- Design and implement a sound > system > > Both libchannel and the device driver update should be done before, or > at least in parallel, I'd say. LIbchannel isn't really necessary for either of these projects. Aside from the fact that I still don't see any use in a generic libchannel at all, there is nothing wrong with implementing these things independently, and later moving them to libchannel if someone really feels like implementing it. Libchannel is only an optimization. Answering any attempt of implementing sound or improved networking or whatever with "write libchannel first" doesn't make any sense. Sound support doesn't really depend on a new driver framework either. It requires sound drivers in Mach of course, but that doesn't mean all the other drivers need to be updated for that. Another interesting task: Improve subhurds. (Allow running as root, more debug possibilities, sharing of services etc.) -antrik- _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
