[openbeosstorage] Re: EntryList / entry_refs
- From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Tue, 26 Mar 2002 15:15:37 -0800
> On another note, I don't think we're going to be able to do much with
> some of the functions that take entry_refs until we get the new kernel.
> I have yet to figure out a way yet to turn an entry_ref into a file
> descriptor or a pathname with Posix.
I take it back. We're good to go. :-)
There was no way we were going to have a fully functional Posix-only BEntry
without an entry_ref_to_path() function, so I hacked out a way of making it
work.
There's now an external program in storage_kit/tools/ that links with the
R5 storage kit. It takes an entry_ref as command line parameters (a device
id, a directory inode #, and a leaf name) and prints out the full path for
the entry to stdout. Our Posix entry_ref_to_path() function invokes that
program and reads the pathname from a pipe. It's slow as could be, but
it'll suffice until we get the new kernel.
-Tyler
- Follow-Ups:
- [openbeosstorage] Quickie...
- From: Mike Lee
- References:
- [openbeosstorage] EntryList / entry_refs
- From: Tyler Dauwalder
Other related posts:
- » [openbeosstorage] EntryList / entry_refs
- » [openbeosstorage] Re: EntryList / entry_refs
- [openbeosstorage] Quickie...
- From: Mike Lee
- [openbeosstorage] EntryList / entry_refs
- From: Tyler Dauwalder