[openbeos] Re: FS question
- From: guillaume.maillard@xxxxxxxxxxx
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 16 Jan 2002 15:05:42 +0100
"Axel Dörfler"
<axeld@pinc-softwar To: openbeos@xxxxxxxxxxxxx
e.de> cc: (bcc: Guillaume
Maillard/DR-SUR/BE/PHILIPS)
Sent by: Subject: [openbeos] Re: FS
question
openbeos-bounce@fre
elists.org Classification:
01/16/02 02:56 PM
Please respond to
openbeos
> > Hi,
> >
> > Let's talk more 'technical'
> > Could somebody tell me: why use BeOS in general node_ref and
> > entry_ref? both of them hold device and inode numbers..
> > BUT these numbers are USELESS on the higher (or medium) level of
> > filesystem. these are usable for kernel methods. there are only
> > path/filename->inode tranlate.
> They are "useless" in the high-level API, that's right - that's why
> there are node_refs and entry_refs - you don't have to deal with inodes
> from user-land.
> Where exactly is your problem?
> Adios...
> Axel.
The problem is to make the StorageKit on other FS than BeFS ... FAT.. ReiserFS..
ie, how to solve the problem of node_refs and entry_refs
My problem is : how can I initialize eg.: a BDirectory with entry_ref?
get_ref_for_path can tranlate from filename/path to inode and device number
with stat(). it's easy. But I didn't find any reverse way to make an
lookup/mapping from dev.inode number to
path ( or fildescriptor is would be suitable)
Reagards,
G
Other related posts:
