On Fri, Oct 11, 2002 at 01:57:17PM -0700, Andy Ross wrote:
> Simon Fowler wrote:
> > Performing well under Linux with ReiserFS is a good advertisement
> > for Linux and ReiserFS, but not so good for FlightGear if that's
> > /all/ we perform well under.
> 
> I think you have perhaps misinterpreted.  My point was that a
> blunderingly simple file-per-airport scheme was adequate on all
> filesystems, not that it required fancy stuff.  The reiserfs note was
> a fun bit of trivia about how OS authors try to accomodate stuff like
> this.  If we work everywhere, but are blazingly fast (or take up far
> less space) under linux/reiserfs, I'd again consider that a feature
> and not a bug.
> 
Actually, I was thinking of the behaviour I've seen with large
directories on ext2/3 . . . And also how mutt handles my maildirs
with several thousand files. That's not really an issue here,
though, so consider it random paranoia ;-)

> > I rather like the idea of the airport files being /part/ of the
> > scenery. It certainly seems to be where they'd belong, logically
> > speaking. [...] there've been several reports of runways and their
> > navaids being completely out of sync with the scenery, and this
> > seems like a good way to fix them.
> 
> Right.  The only complication is that there's an existing use case
> that requires doing fast lookup of airports by ID.  My idea was to
> distribute files with the scenery and drop them in a single global
> directory.  Trivially simple to implement and maintain -- users who
> discover airport or navaid bugs can just fix the file and post it to
> the mailing list; they don't need any coding experience at all.
> 
What about simply putting all the airport files in the scenery, and
having a script that searched through the scenery directories for
all the *-apt.xml files and built/updated a set of indexes from
them? That keeps the files in the right place, and gives the indices
needed to get fast lookups based on whatever criteria are needed.

Although none of this deals with the problem of making sure the
scenery and the airports are consistent . . . That would rely on
having consistent data when the scenery is generated, which is a
very different matter. Unless we're all building our own scenery, of
course . . .

/me needs to acquire an eight-way alphaserver to play around with
this scenery generation thing . . . ;-)

Simon

-- 
PGP public key Id 0x144A991C, or http://himi.org/stuff/himi.asc
(crappy) Homepage: http://himi.org
doe #237 (see http://www.lemuria.org/DeCSS) 
My DeCSS mirror: ftp://himi.org/pub/mirrors/css/ 

Attachment: msg09166/pgp00000.pgp
Description: PGP signature

Reply via email to