On Sun, Jan 30, 2005 at 02:16:03AM -0500, Michael Jennings wrote:
> On Monday, 24 January 2005, at 13:19:33 (+0100),
> Jan Nordholz wrote:
> 
> > I recently found out that having one's config dir on a NFS share is
> > a bad idea. Enlightenment names its background-thumbnail-files after
> > inode, mtime and _device_, which is a little pointless when the
> > device number is in the anonymous range (that is, majors 0,
> > 144-146):
> 
> E runs on more than just Linux.  You cannot assume anything about
> device numbers.
> 
> Michael
Hi Michael.

You're right, I forgot about the L in lanana.org. That makes the
suggested patch useless, but the problem persists, which is not limited
to a single OS. And as the assigned device number of a NFS mount is
volatile by nature, and trying to determine the respective mount type
at runtime (in order to decide whether E could trust the device number
or not) would be too time-consuming for the job, wouldn't it be
better to abandon the device number as identification altogether,
replacing it by (for example) the lower 16 bits of the filesize?
Perhaps not the best choice, as background images tend to be equally
dimensioned, so a series of uncompressed images will all be equal
in size... but I'd prefer too little cache-rebuilds over too many,
especially as the old data isn't wiped out in that process.

Just making suggestions and trying to be helpful (if you come to
a decision involving some changes, I'd volunteer to write the
appropriate patch)...

Jan

-- 
Jan Nordholz
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to