[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Fedora-legal-list] regarding ntop binary data file formats

Recently my co-maintainer made a update in rawhide for ntop package
from 3.3.8 to 3.3.9. It was without discussion with me. The update had
a dependency with GeoIP package which needs GeoLiteCity.dat and
GeoIPASNum.dat binary format files (they are compressed and optimized
form of big CSV files). GeoIP package can read this .dat files and
provide info. My questions is whether these .dat files can be included
into fedora ?

License for .dat files is at:

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=488717
Build id: http://koji.fedoraproject.org/koji/buildinfo?buildID=92821

Snippet from http://www.maxmind.com/app/geolitecity

GeoLite City is offered in binary format, a highly optimized database
that supports fast lookups using our Open Source API code. We
recommend using the binary files with APIs instead of importing the
CSV files into SQL because the binary format is more efficient and is
easy to set up and use.

    * Binary Format Installation Instructions
    * Download the latest GeoLite City Binary Format (28 MB when
uncompressed, last updated February 1st, 2009, next update March 9th,

CSV Format

Our CSV format enables you to load the database into a SQL database.
The GeoIP City and GeoLite City use the same locationIDs, so the GeoIP
City CSV files can be used as a drop in replacement for GeoLite City
CSV files without having to change the locationIDs. Note that queries
made against the CSV data imported into a SQL database can take up to
a few seconds. If performance is an issue, the binary format is much
faster, and can handle thousands of lookups per second.

    * Instructions on how to use our CSV databases with a SQL database.
    * Download the latest GeoLite City CSV Format (100 MB when uncompressed)


Rakesh Pandit

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]