[openbeosstorage] Re: Kernel Interface Design
- From: "Tyler Dauwalder" <tyler@xxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Mon, 18 Feb 2002 06:32:31 +0000
>...before we get too heavily invested in this unified open(), read(), etc.
>architecture, I'm going to talk to the kernel folks. If you look at the
>kernel team page ( http://open-beos.sourceforge.net/tms/kernel.html :-),
>one of their todo's under "vfs redo" is to "remove multiple streams".
>That may mean a more R5 vfs add-on style interface.
Okay, I heard back from the kernel guys. They said Travis@NewOS
is planning on scrapping the unified open() and read() concept and
going to something more R5ish, so I guess that's what we should
anticipate.
-Tyler
- Follow-Ups:
- [openbeosstorage] Re: Kernel Interface Design
- From: Keith Poole
Other related posts:
- » [openbeosstorage] Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- » [openbeosstorage] Re: Kernel Interface Design
- [openbeosstorage] Re: Kernel Interface Design
- From: Keith Poole