FreeLists / openbeos / [openbeos] Re: kernel mime_table module

["Mikael Jansson (mailing lists)" <lists@xxxxxxxxxxxxxxxxx>]

"Alexander G. M. Smith" <agmsmith@xxxxxxxxxx>:
>
> Ingo Weinhold wrote on Sun, 09 Jan 2005 18:24:08 +0100:
> > As François proposed, storing an entry_ref with the FD should help. 
> > Otherwise, as I wrote, getting any file name at all might not be 
> > possible 
> > without iterating through the whole volume.
> 
> I think we have fast enough hardware that we can afford the space and 
> time
> costs of having a back pointer in each inode to the parent directory.  
> Or
> if you want to be ambitious, multiple parents (for hard links and 
> other
> aliases).  Then you can find the file name and get the MIME type from 
> the
> extension.
> 
> By the way, in AGMSRAMFileSystem, I simplified it by storing the file 
> name
> in the inode - it's a file property, not a directory property.  After 
> much
> thought, the loss of the ability to have different file names for the 
> same
> file is the loss of a misfeature that only causes user pain.  If you 
> want
> another name for a file, use a symbolic link.
> 
Also, having different file names for a specific file needs hard links 
anyway, correct?
If so, that's another argument against, as BeOS doesn't suport hard 
links.

--
Mikael Jansson
http://mikael.jansson.be