From: Roland Häder Date: Fri, 22 Feb 2013 11:32:53 +0000 (+0000) Subject: Initial import X-Git-Url: https://git.mxchange.org/?a=commitdiff_plain;h=a846540133ee3450e05da00ee4f11894a140a647;p=flightgear-website.git Initial import --- a846540133ee3450e05da00ee4f11894a140a647 diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000..ac3442d --- /dev/null +++ b/.gitattributes @@ -0,0 +1,56 @@ +* text=auto !eol +/.htaccess -text +/blacklist.txt -text +/eddh-eddl-lfpg.html -text +/eddh-ekch.html -text +/eddh-ekeb.html -text +/eddh-essa.html -text +/eddh-loww-lirf.html -text +/favicon.ico -text +/fgcom.html -text +/fgdata-bundle.html -text +/fgfs-scenery.html -text +/flights.html -text +guestbook/.htaccess -text +guestbook/LICENSE.txt -text +guestbook/arial.ttf -text +guestbook/captcha.png -text +guestbook/captcha.txt -text +guestbook/changelog.txt -text +guestbook/forbid.php -text +guestbook/index.php -text +guestbook/no-badbot.gif -text +guestbook/pixel.gif -text +guestbook/settings.php -text +guestbook/spider.jpg -text +/imprint.html -text +/index.html -text +/lemd-lfpg-eddl-eddh.html -text +/links.html -text +/lirf-leib-lemd.html -text +/pfs-scam.html -text +pub/.htaccess -text +pub/download-helper.zip -text +pub/fgfs-launcher.zip -text +pub/helper.zip -text +pub/rsyncd.conf -text +pub/screenshot-anonymizer-fvwm-crystal_1280x1024.svg -text +pub/svn-fgdata-bundle.sh -text +/robots.txt -text +/rsync.html -text +/tutorial-gimp-livery-drawing.html -text +tutorials/img/livery-paths/001-thumb.png -text +tutorials/img/livery-paths/001.png -text +tutorials/img/livery-paths/002-thumb.png -text +tutorials/img/livery-paths/002.png -text +tutorials/img/livery-paths/003-thumb.png -text +tutorials/img/livery-paths/003.png -text +tutorials/img/livery-paths/004-thumb.png -text +tutorials/img/livery-paths/004.png -text +tutorials/img/livery-paths/005-thumb.png -text +tutorials/img/livery-paths/005.png -text +tutorials/img/livery-paths/006-thumb.png -text +tutorials/img/livery-paths/006.png -text +tutorials/img/livery-paths/007-thumb.png -text +tutorials/img/livery-paths/007.png -text +/whitelist.txt -text diff --git a/.htaccess b/.htaccess new file mode 100644 index 0000000..adc6709 --- /dev/null +++ b/.htaccess @@ -0,0 +1,18 @@ +Options -Indexes +DirectoryIndex index.html + + + RewriteEngine on + + # Wir moegen keine Spione! ;-) + RewriteCond %{HTTP_USER_AGENT} !^Googlebot$ + RewriteRule ^(black|white)list.txt$ guestbook/index.php [L] + # Google von der Falle fernhalten + RewriteCond %{HTTP_USER_AGENT} ^Googlebot$ + RewriteRule ^(black|white)list.txt$ - [F] + + +# Wenn Zugriff verweigert zur Fehlerseite weiterleiten +ErrorDocument 403 http://flightgear.mxchange.org/guestbook/forbid.php + +Order Deny,Allow diff --git a/blacklist.txt b/blacklist.txt new file mode 100644 index 0000000..e69de29 diff --git a/eddh-eddl-lfpg.html b/eddh-eddl-lfpg.html new file mode 100644 index 0000000..f8545b0 --- /dev/null +++ b/eddh-eddl-lfpg.html @@ -0,0 +1,75 @@ + + + + Quix0r's FlightGear Webpage - From EDDH, over EDDL to LFPG + + + + +
A flight from EDDH, over EDDL to LFPG
+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · EDDH (Not needed to enter in AP!)
+ · DH257
+ · DW501
+ · DW460
+ · DENOL
+ · DL450 (reduce altitude to 2.000 feet in AP, speed 180kts, use airbrake [CTRL+B])
+ · DL019
+ · EDDL (Duesseldorf Airport, ADF 417) - First stop for refueling)
+ · DL237
+ · DL550
+ · PINUS
+ · LGE03
+ · BFS08
+ · ELVES
+ · TALUN
+ · DIDOR (start reducing altitude here)
+ · PG511
+ · PGS08
+ · PGS05
+ · PGS01
+ · LFPG (Paris Charles, final, ADF 343)
+
+ Notices: Between EDDH and EDDL we should not climb + higher than 10.000 feet. You should begin reducing the altitude to 1.000 feet + when you are approx. 4 to 6 minutes away with a maximum airspeed of 320 kts + away from your desired destination. +

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-03-29 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/eddh-ekch.html b/eddh-ekch.html new file mode 100644 index 0000000..962a669 --- /dev/null +++ b/eddh-ekch.html @@ -0,0 +1,61 @@ + + + +Quix0r's FlightGear Webpage - From EDDH to EKCH + + + + +
A flight from EDDH to EKCH and back
+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · EDDH (Not needed to enter in AP!)
+ · HAM (VOR; 113.10 MHz; 60 deg; 5,000ft)
+ · LUB (VOR; 110.60 MHz; 50 deg; 8,000ft)
+ · MIC (VOR; 112.20 MHz; 45 deg)
+ · CDA (VOR; 114.90 MHz; 0 deg)
+ · ??? (ILS; 109.30 MHz; 41.16 deg, NAV GS)
+ · EKCH (Copenhangen, Danmark)
+
+ Notices: You should not climb higher than 10.000ft. + You should begin reducing the altitude to 1.000 feet when you are approx. 4 + to 6 minutes away with a maximum airspeed of 320 kts away from your desired + destination. Reduce your speed to 180kts for a good landing with the Bravo. +

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-06-09 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/eddh-ekeb.html b/eddh-ekeb.html new file mode 100644 index 0000000..7f40fef --- /dev/null +++ b/eddh-ekeb.html @@ -0,0 +1,71 @@ + + + + Quix0r's FlightGear Webpage - From EDDH to EKEB and back + + + + +
A flight from EDDH to EKEB and back
+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · EDDH (Not needed to enter in AP!)
+ · DH101
+ · DH211
+ · HNT20
+ · LISBU
+ · SKR82
+ · VES30
+ · VES15
+ · EKEB (Esbjerg, Danmark)
+ · VES15
+ · VES30
+ · SKR82
+ · LISBU
+ · BOREP
+ · DH060
+ · ALF38
+ · R1276,DH010/EDDH (Choose R1276 first, if invalid use DH010)
+
+ Notices: You should not climb higher than 10.000ft. + You should begin reducing the altitude to 1.000 feet when you are approx. 4 + to 6 minutes away with a maximum airspeed of 320 kts away from your desired + destination. Reduce your speed to 180kts for a good landing with the Bravo. +

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-04-23 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/eddh-essa.html b/eddh-essa.html new file mode 100644 index 0000000..bcb9fb3 --- /dev/null +++ b/eddh-essa.html @@ -0,0 +1,77 @@ + + + + Quix0r's FlightGear Webpage - From EDDH to ESSA and back + + + + +
A flight from EDDH to ESSA and back
+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · EDDH (Not needed to enter in AP!)
+ · DH102
+ · DH033
+ · DH625
+ · TOSPA
+ · CH364
+ · BEDOS
+ · SA807
+ · SA801
+ · SA705
+ · ESSA (Sweden, near Stockholm)
+ · SA802
+ · TRS48
+ · VIBAR
+ · ROXEN
+ · BABSI
+ · ORSUN
+ · NEDIK (maybe invalid?)
+ · ALUBA
+ · DH657 (reduce altitude to 1.000ft and speed to 180kts with AP, then use airbrake [CTRL+B] to reduce speed to 180kts and update the AP again)
+ · DH030
+ · R1277 (just for lining up with the runway)
+ · EDDH (Not needed)
+
+ Notices: You should not climb higher than 10.000ft. + You should begin reducing the altitude to 1.000 feet when you are approx. 4 + to 6 minutes away with a maximum airspeed of 320 kts away from your desired + destination. Reduce your speed to 180kts for a good landing with the Bravo. +

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-04-09 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/eddh-loww-lirf.html b/eddh-loww-lirf.html new file mode 100644 index 0000000..6d0a01e --- /dev/null +++ b/eddh-loww-lirf.html @@ -0,0 +1,86 @@ + + + + Quix0r's FlightGear Webpage - From EDDH over LOWW to LIRF + + + + +
A flight from EDDH over LOWW to LIRF
+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · EDDH (Not needed to enter in AP!)
+ · DH231
+ · AGATI
+ · DV520
+ · RISOK
+ · DP444
+ · TALEG
+ · ABKIS (Lower altitude here)
+ · KADNO
+ · OKL36
+ · R1754 (LKPR: Ruzyne; no need to refuel)
+ · PG117
+ · TABEM
+ · TEMTA (Lower altitude here)
+ · OEZ13
+ · WGM87
+ · R1805/LOWW (Vienna, Austria; refuel here)
+ · WW144
+ · XANUT
+ · ILB23
+ · NIKOL (Marked on my paper)
+ · LEONN
+ · GITOD (Lower altitude here)
+ · BOL33 (200kts, 2.000ft)
+ · D7FNN
+ · R2635/LIRF (Roma, Italia)
+
+ Notices: You should not climb higher than 10.000ft. + You should begin reducing the altitude to 1.000 feet when you are approx. 4 + to 6 minutes away with a maximum airspeed of 320 kts away from your desired + destination. Reduce your speed to 180kts for a good landing with the Bravo. +

+ +

+ You may want to continue flying these routes:
+ · LIRF (Roma) over LEIB (Ibiza) to LEMD (Madrid)
+ · LEMD (Madrid) over LFPG (Paris) and EDDL (Düsseldorf) to EDDH (Hamburg).
+

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-04-23 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/favicon.ico b/favicon.ico new file mode 100644 index 0000000..52e77b7 Binary files /dev/null and b/favicon.ico differ diff --git a/fgcom.html b/fgcom.html new file mode 100644 index 0000000..c22a041 --- /dev/null +++ b/fgcom.html @@ -0,0 +1,115 @@ + + + + Quix0r's FlightGear Webpage - Compilation hints for FGCOM + + + + +
Compilation hints for FGCOM
+ +

+ I had some trouble compiling FGCOM + on my machine and which tag/branch/trunk I should compile. Here I would like to share my experiences with you and to + save you a lot time. +

+ +

+ First of all, I cannot give you support for FGCOM. I am not a C++ hacker, so please understand me. But I did fix some parts + in FGCOM where you might not know how to continue. I have a Debian Unstable (sqeeze/sid at the moment of creating this + document) with GCC 4.3.4 (works great for compiling FGFS, FGCOM!). So you might check first, which compiler you have. +

+ +

+ Then I have found out, you need some extra packages and my fix for a successfull compilation of FGCOM. But wait! Which one + now? The trunk is in bad shape (revision 226). So I took the branch fgcom3 here. But before you can begin, + you need to check-out the repository: +

+ +

+

svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/branches/fgcom3
+

+ +

+ The next thing is the extra packages. I need libgnet2, libgnet-dev, liboggz2_1, liboggz2-dev to get + installed before I can finish compilation. That wasn't very hard for now. :-) So let's head over to compilation: +

+ +

+

cd fgcom3
+$EDITOR Makefile
+

+ +

+ Insert any favorite text editor for $EDITOR. For my setup, I need to change the installation path and the LDFLAGS variable. + The shown values below are only new values +

+ +

+

[...]
+INSTALL_BIN:=/opt/bin
+INSTALL_DIR:=/opt/fgcom
+[...]
+LDFLAGS:=-L$(INSTALL_DIR)/lib
+[...]
+

+ +

+ The LDFLAGS line contains a space in the unmodified version which my linker doesn't like. So I need to hack that away. +

+ +

+ Now it is time to compile. Do a make in the fgcom3 directory. If you run in trouble, e.g. of missing or wrong spaces + between -L and /some/foo/path (maybe /opt/fgcom/lib?) then add or remove it like requested by the linker. Do a + make clean to cleanup everthing. Simply make won't give you what you want (you need cleanup). After + successfully building fgcom (no error line at the end) you should now see an executable file "fgcom" in the path + (do a ls -l). Well done! :-) Now, do a make install as a user with proper permission to write to the + installation paths) and you are nearly done. +

+ +

+ If you have changed installation paths, you maybe will get an error message complaining about missing library files. YICKS! + We forgot to tell the dynamic linker, where our libs are, they went to /opt/fgcom/lib which is an unknown lookup path to + the linker. +

+ +

+ We need to help the linker finding the libs by creating a new file for ldconfig, let's say fgcom.conf, so the new library + path /opt/fgcom/lib is known to the dynamic linker. Here you can find my version (very simple): +

+ +

+/opt/fgcom/lib
+

+ +

+ Place that file into /etc/ld.conf.d/ as root. Now re-run ldconfig and fgcom (placed in /opt/bin) should not + complain about missing libraries. Now, try the loop-back test as described here. +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2009-12-06 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/fgdata-bundle.html b/fgdata-bundle.html new file mode 100644 index 0000000..42f73d1 --- /dev/null +++ b/fgdata-bundle.html @@ -0,0 +1,114 @@ + + + +Quix0r's FlightGear Webpage - fgdata.bundle - How to get it and verify it + + + + +
fgdata.bundle - How to get it and verify it
+ +

+ There is a file called fgdata.bundle available on my server via BitTorrent + (see download link bewlow). This file can be downloaded with any regular download + tools and is mainly intended for people where the regular GIT download fails or + lasts so very long. The file is quite large so I need to add it to my robots.txt file to + prevent downloads by bots (the whole /pub directory is now blocked for all + bots). You can use git-bundle to extract it to your local hard drive (see + below for an example). +

+ +

+

+

+ +

+ How to use those hashes is mostly simplified with download tools + (frontends). So I would welcome you to head over to your program's + documentation. Comparing e.g. the SHA512 sum with your eyes is maybe not + such a good idea. If you still like to use tools such as md5sum, the command + to enter after download is simple: +

+ +

+

md5sum fgdata.bundle
+ (or use sha512 for a larger sum). +

+ +

+ The more recommended way is GnuPG because trust can come in play. I am not going to + tell you all from scratch here, please refer to the FAQ + section of GnuPG and make sure you are legally allowed to use such cryptographic programs in + your country. +

+ +

+ A simple step-by-step instruction: +

# Download the bundle file via BitTorrent:
+wget -c http://mxchange.org:23456/file?info_hash=%BF%FF%AB%0C%16%BF%8Eg%B8%A0%CFw%01%0A%5D%8F%3F%81%96y -O fgdata.bundle.torrent
+
+# Download the ASCII-armored signature file:
+wget -c http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.asc
+
+# Download the public key for my digitally signed downloads:
+wget -c http://mxchange.org/signed-downloads.asc
+
+# Import the public key (you need to create a local key-pair first: gpg --ken-key):
+gpg --import < signed-downloads.asc
+
+# Alternatively of the above two steps you can download it from a public key server:
+gpg --recv-keys --keyserver hkp://keys.gnupg.net A1B99B83
+
+# If you want to prevent GnuPG warning you, locally sign my public key:
+gpg --lsign-key A1B99B83
+
+# Alternatively and then you *REALLY* need to trust my key (have you verified my ID card for example?):
+gpg --sign-key A1B99B83
+
+# ... and upload your key (do only sign locally if you don't trust my key):
+gpg --send-keys --keyserver hkp://keys.gnupg.net xxx
+ If you want to trust my key and upload your signature (thank you) please + come to one of the key-signing parties I join (Chemnitzer Linuxtage 2011 is + maybe a possible candidate). +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2011-01-11 | + Last update: 2013-02-21 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/fgfs-scenery.html b/fgfs-scenery.html new file mode 100644 index 0000000..aa353a9 --- /dev/null +++ b/fgfs-scenery.html @@ -0,0 +1,99 @@ + + + +Quix0r's FlightGear Webpage - Which scenery I'm using + + + + +
Which scenery I'm using
+ +

+ On this page I want to give you informations about which scenery I'm + using. First of all, I always fly latest GIT/master for testing (stability) + it for the FGFS developers. Jester has help me with a lot compiler errors + and assertitions. Thanks a lot! +

+ +

+ So here is now the whole scenery I'm using: +

+ +

+

+

+ +

+ The TerraSync (not to mix with the terrasync program) is the latest scenery and models from the developers. You + should *NOT* download it into fgdata, instead you should download it in a separate folder. To do so, + follow this little tutorial: +

# Change into your $HOME directory:
+cd ~/
+# This will take very long ...
+svn co http://terrascenery.googlecode.com/svn/trunk/data/Scenery/ fgfs-scenery/
+# Expand your FG_SCENERY variable:
+export FG_SCENERY="${FG_SCENERY};${HOME}/fgfs-scenery/"
+# You may want to add that line into your ~/.bashrc file to expand it automatically everytime you login.
+
+ For Windozer users the above tutorial doesn't work, you need some different steps. First make sure you have TortoiseSVN and TortoiseGIT installed. If not, do so + or else you cannot continue. +

+ +

+ ·Change into e.g. c:\
+ ·Create a new folder called flightgear-scenery and change into that
+ ·Change into that folder and right-click on the free space
+ ·Now choose Subversion (or SVN) -> Checkout ...
+ ·Then enter this URL: http://terrascenery.googlecode.com/svn/trunk/data/Scenery/
+ ·Now just hit OK and the download should really long
+

+ +

+ If the process ends successfully, congratulations! If if ends with an error, try to update it (see below). Now we need to + tell FlightGear to use that directory as scenery path. To do so, you have two options:
+

+ +

+ ·(EXPERT) Extend the environment variable FG_SCENERY with ;c:/fgfs-scenery/
+ ·(BEGINNER) Add the path in FGRUN (and save it!)
+

+ +

+ Now try to fly e.g. at EDDL (Düsseldorf, Germany), if you see scenery and no water every where, it worked! If you + see water, double-check all paths. If it still doesn't work, you may have encountered a bug and anyway, you should + come to the forums or mailing list. +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2011-05-26 | + Last update: 2011-05-27 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/flights.html b/flights.html new file mode 100644 index 0000000..424f2ee --- /dev/null +++ b/flights.html @@ -0,0 +1,60 @@ + + + + Quix0r's FlightGear Webpage - Flights I have flew in FlightGear Flight Simulator + + + + +
Planed flights I have flewn with the Bravo
+ +

+ Here is a summerized list of flights I have flewn with FlightGear with the + help of fixed navigation points. You can get these with a program called + Atlas. If you like we can meet up in IRC (irc.flightgear.org) and + fly it wing by wing. :) +

+ +

+ · EDDH (Hamburg) to ESSA (Stockholm-Arlanda Airport)
+ · EDDH (Hamburg) to EKEB (Esbjerg)
+ · EDDH (Hamburg) over EDDL (Duesseldorf) to LFPG (Paris Charles)
+ · From EDDH (Hamburg) over LOWW (Vienna) to LIRF (Roma)
+ · Continued flight from LIRF (Vienna) over LEIB (Ibiza) to LEMD (Madrid)
+ · Continued flight from LEMD (Madrid) over LFPG (Paris) and EDDL (Düsseldorf) to EDDH (Hamburg)
+ · EDDH (Hamburg) to EKCH (Copenhagen) with VOR navigation
+
+ Notices: A detailed list of my flight plans is now + available! :) Just click on the links above to get to them. I used a program + called Atlas to figure the route out. +

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-03-29 | + Last update: 2011-01-11 | + Author: Roland Häder
+ FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/guestbook/.htaccess b/guestbook/.htaccess new file mode 100644 index 0000000..96d6fb4 --- /dev/null +++ b/guestbook/.htaccess @@ -0,0 +1,4 @@ +Order allow,deny +Allow from all + +ErrorDocument 404 http://www.mxchange.org/guestbook/index.php diff --git a/guestbook/LICENSE.txt b/guestbook/LICENSE.txt new file mode 100644 index 0000000..7a45bfe --- /dev/null +++ b/guestbook/LICENSE.txt @@ -0,0 +1,470 @@ + MOZILLA PUBLIC LICENSE + Version 1.1 + + --------------- + +1. Definitions. + + 1.0.1. "Commercial Use" means distribution or otherwise making the + Covered Code available to a third party. + + 1.1. "Contributor" means each entity that creates or contributes to + the creation of Modifications. + + 1.2. "Contributor Version" means the combination of the Original + Code, prior Modifications used by a Contributor, and the Modifications + made by that particular Contributor. + + 1.3. "Covered Code" means the Original Code or Modifications or the + combination of the Original Code and Modifications, in each case + including portions thereof. + + 1.4. "Electronic Distribution Mechanism" means a mechanism generally + accepted in the software development community for the electronic + transfer of data. + + 1.5. "Executable" means Covered Code in any form other than Source + Code. + + 1.6. "Initial Developer" means the individual or entity identified + as the Initial Developer in the Source Code notice required by Exhibit + A. + + 1.7. "Larger Work" means a work which combines Covered Code or + portions thereof with code not governed by the terms of this License. + + 1.8. "License" means this document. + + 1.8.1. "Licensable" means having the right to grant, to the maximum + extent possible, whether at the time of the initial grant or + subsequently acquired, any and all of the rights conveyed herein. + + 1.9. "Modifications" means any addition to or deletion from the + substance or structure of either the Original Code or any previous + Modifications. When Covered Code is released as a series of files, a + Modification is: + A. Any addition to or deletion from the contents of a file + containing Original Code or previous Modifications. + + B. Any new file that contains any part of the Original Code or + previous Modifications. + + 1.10. "Original Code" means Source Code of computer software code + which is described in the Source Code notice required by Exhibit A as + Original Code, and which, at the time of its release under this + License is not already Covered Code governed by this License. + + 1.10.1. "Patent Claims" means any patent claim(s), now owned or + hereafter acquired, including without limitation, method, process, + and apparatus claims, in any patent Licensable by grantor. + + 1.11. "Source Code" means the preferred form of the Covered Code for + making modifications to it, including all modules it contains, plus + any associated interface definition files, scripts used to control + compilation and installation of an Executable, or source code + differential comparisons against either the Original Code or another + well known, available Covered Code of the Contributor's choice. The + Source Code can be in a compressed or archival form, provided the + appropriate decompression or de-archiving software is widely available + for no charge. + + 1.12. "You" (or "Your") means an individual or a legal entity + exercising rights under, and complying with all of the terms of, this + License or a future version of this License issued under Section 6.1. + For legal entities, "You" includes any entity which controls, is + controlled by, or is under common control with You. For purposes of + this definition, "control" means (a) the power, direct or indirect, + to cause the direction or management of such entity, whether by + contract or otherwise, or (b) ownership of more than fifty percent + (50%) of the outstanding shares or beneficial ownership of such + entity. + +2. Source Code License. + + 2.1. The Initial Developer Grant. + The Initial Developer hereby grants You a world-wide, royalty-free, + non-exclusive license, subject to third party intellectual property + claims: + (a) under intellectual property rights (other than patent or + trademark) Licensable by Initial Developer to use, reproduce, + modify, display, perform, sublicense and distribute the Original + Code (or portions thereof) with or without Modifications, and/or + as part of a Larger Work; and + + (b) under Patents Claims infringed by the making, using or + selling of Original Code, to make, have made, use, practice, + sell, and offer for sale, and/or otherwise dispose of the + Original Code (or portions thereof). + + (c) the licenses granted in this Section 2.1(a) and (b) are + effective on the date Initial Developer first distributes + Original Code under the terms of this License. + + (d) Notwithstanding Section 2.1(b) above, no patent license is + granted: 1) for code that You delete from the Original Code; 2) + separate from the Original Code; or 3) for infringements caused + by: i) the modification of the Original Code or ii) the + combination of the Original Code with other software or devices. + + 2.2. Contributor Grant. + Subject to third party intellectual property claims, each Contributor + hereby grants You a world-wide, royalty-free, non-exclusive license + + (a) under intellectual property rights (other than patent or + trademark) Licensable by Contributor, to use, reproduce, modify, + display, perform, sublicense and distribute the Modifications + created by such Contributor (or portions thereof) either on an + unmodified basis, with other Modifications, as Covered Code + and/or as part of a Larger Work; and + + (b) under Patent Claims infringed by the making, using, or + selling of Modifications made by that Contributor either alone + and/or in combination with its Contributor Version (or portions + of such combination), to make, use, sell, offer for sale, have + made, and/or otherwise dispose of: 1) Modifications made by that + Contributor (or portions thereof); and 2) the combination of + Modifications made by that Contributor with its Contributor + Version (or portions of such combination). + + (c) the licenses granted in Sections 2.2(a) and 2.2(b) are + effective on the date Contributor first makes Commercial Use of + the Covered Code. + + (d) Notwithstanding Section 2.2(b) above, no patent license is + granted: 1) for any code that Contributor has deleted from the + Contributor Version; 2) separate from the Contributor Version; + 3) for infringements caused by: i) third party modifications of + Contributor Version or ii) the combination of Modifications made + by that Contributor with other software (except as part of the + Contributor Version) or other devices; or 4) under Patent Claims + infringed by Covered Code in the absence of Modifications made by + that Contributor. + +3. Distribution Obligations. + + 3.1. Application of License. + The Modifications which You create or to which You contribute are + governed by the terms of this License, including without limitation + Section 2.2. The Source Code version of Covered Code may be + distributed only under the terms of this License or a future version + of this License released under Section 6.1, and You must include a + copy of this License with every copy of the Source Code You + distribute. You may not offer or impose any terms on any Source Code + version that alters or restricts the applicable version of this + License or the recipients' rights hereunder. However, You may include + an additional document offering the additional rights described in + Section 3.5. + + 3.2. Availability of Source Code. + Any Modification which You create or to which You contribute must be + made available in Source Code form under the terms of this License + either on the same media as an Executable version or via an accepted + Electronic Distribution Mechanism to anyone to whom you made an + Executable version available; and if made available via Electronic + Distribution Mechanism, must remain available for at least twelve (12) + months after the date it initially became available, or at least six + (6) months after a subsequent version of that particular Modification + has been made available to such recipients. You are responsible for + ensuring that the Source Code version remains available even if the + Electronic Distribution Mechanism is maintained by a third party. + + 3.3. Description of Modifications. + You must cause all Covered Code to which You contribute to contain a + file documenting the changes You made to create that Covered Code and + the date of any change. You must include a prominent statement that + the Modification is derived, directly or indirectly, from Original + Code provided by the Initial Developer and including the name of the + Initial Developer in (a) the Source Code, and (b) in any notice in an + Executable version or related documentation in which You describe the + origin or ownership of the Covered Code. + + 3.4. Intellectual Property Matters + (a) Third Party Claims. + If Contributor has knowledge that a license under a third party's + intellectual property rights is required to exercise the rights + granted by such Contributor under Sections 2.1 or 2.2, + Contributor must include a text file with the Source Code + distribution titled "LEGAL" which describes the claim and the + party making the claim in sufficient detail that a recipient will + know whom to contact. If Contributor obtains such knowledge after + the Modification is made available as described in Section 3.2, + Contributor shall promptly modify the LEGAL file in all copies + Contributor makes available thereafter and shall take other steps + (such as notifying appropriate mailing lists or newsgroups) + reasonably calculated to inform those who received the Covered + Code that new knowledge has been obtained. + + (b) Contributor APIs. + If Contributor's Modifications include an application programming + interface and Contributor has knowledge of patent licenses which + are reasonably necessary to implement that API, Contributor must + also include this information in the LEGAL file. + + (c) Representations. + Contributor represents that, except as disclosed pursuant to + Section 3.4(a) above, Contributor believes that Contributor's + Modifications are Contributor's original creation(s) and/or + Contributor has sufficient rights to grant the rights conveyed by + this License. + + 3.5. Required Notices. + You must duplicate the notice in Exhibit A in each file of the Source + Code. If it is not possible to put such notice in a particular Source + Code file due to its structure, then You must include such notice in a + location (such as a relevant directory) where a user would be likely + to look for such a notice. If You created one or more Modification(s) + You may add your name as a Contributor to the notice described in + Exhibit A. You must also duplicate this License in any documentation + for the Source Code where You describe recipients' rights or ownership + rights relating to Covered Code. You may choose to offer, and to + charge a fee for, warranty, support, indemnity or liability + obligations to one or more recipients of Covered Code. However, You + may do so only on Your own behalf, and not on behalf of the Initial + Developer or any Contributor. You must make it absolutely clear than + any such warranty, support, indemnity or liability obligation is + offered by You alone, and You hereby agree to indemnify the Initial + Developer and every Contributor for any liability incurred by the + Initial Developer or such Contributor as a result of warranty, + support, indemnity or liability terms You offer. + + 3.6. Distribution of Executable Versions. + You may distribute Covered Code in Executable form only if the + requirements of Section 3.1-3.5 have been met for that Covered Code, + and if You include a notice stating that the Source Code version of + the Covered Code is available under the terms of this License, + including a description of how and where You have fulfilled the + obligations of Section 3.2. The notice must be conspicuously included + in any notice in an Executable version, related documentation or + collateral in which You describe recipients' rights relating to the + Covered Code. You may distribute the Executable version of Covered + Code or ownership rights under a license of Your choice, which may + contain terms different from this License, provided that You are in + compliance with the terms of this License and that the license for the + Executable version does not attempt to limit or alter the recipient's + rights in the Source Code version from the rights set forth in this + License. If You distribute the Executable version under a different + license You must make it absolutely clear that any terms which differ + from this License are offered by You alone, not by the Initial + Developer or any Contributor. You hereby agree to indemnify the + Initial Developer and every Contributor for any liability incurred by + the Initial Developer or such Contributor as a result of any such + terms You offer. + + 3.7. Larger Works. + You may create a Larger Work by combining Covered Code with other code + not governed by the terms of this License and distribute the Larger + Work as a single product. In such a case, You must make sure the + requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. + + If it is impossible for You to comply with any of the terms of this + License with respect to some or all of the Covered Code due to + statute, judicial order, or regulation then You must: (a) comply with + the terms of this License to the maximum extent possible; and (b) + describe the limitations and the code they affect. Such description + must be included in the LEGAL file described in Section 3.4 and must + be included with all distributions of the Source Code. Except to the + extent prohibited by statute or regulation, such description must be + sufficiently detailed for a recipient of ordinary skill to be able to + understand it. + +5. Application of this License. + + This License applies to code to which the Initial Developer has + attached the notice in Exhibit A and to related Covered Code. + +6. Versions of the License. + + 6.1. New Versions. + Netscape Communications Corporation ("Netscape") may publish revised + and/or new versions of the License from time to time. Each version + will be given a distinguishing version number. + + 6.2. Effect of New Versions. + Once Covered Code has been published under a particular version of the + License, You may always continue to use it under the terms of that + version. You may also choose to use such Covered Code under the terms + of any subsequent version of the License published by Netscape. No one + other than Netscape has the right to modify the terms applicable to + Covered Code created under this License. + + 6.3. Derivative Works. + If You create or use a modified version of this License (which you may + only do in order to apply it to code which is not already Covered Code + governed by this License), You must (a) rename Your license so that + the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", + "MPL", "NPL" or any confusingly similar phrase do not appear in your + license (except to note that your license differs from this License) + and (b) otherwise make it clear that Your version of the license + contains terms which differ from the Mozilla Public License and + Netscape Public License. (Filling in the name of the Initial + Developer, Original Code or Contributor in the notice described in + Exhibit A shall not of themselves be deemed to be modifications of + this License.) + +7. DISCLAIMER OF WARRANTY. + + COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, + WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF + DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. + THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE + IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE + COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF + ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. + + 8.1. This License and the rights granted hereunder will terminate + automatically if You fail to comply with terms herein and fail to cure + such breach within 30 days of becoming aware of the breach. All + sublicenses to the Covered Code which are properly granted shall + survive any termination of this License. Provisions which, by their + nature, must remain in effect beyond the termination of this License + shall survive. + + 8.2. If You initiate litigation by asserting a patent infringement + claim (excluding declatory judgment actions) against Initial Developer + or a Contributor (the Initial Developer or Contributor against whom + You file such action is referred to as "Participant") alleging that: + + (a) such Participant's Contributor Version directly or indirectly + infringes any patent, then any and all rights granted by such + Participant to You under Sections 2.1 and/or 2.2 of this License + shall, upon 60 days notice from Participant terminate prospectively, + unless if within 60 days after receipt of notice You either: (i) + agree in writing to pay Participant a mutually agreeable reasonable + royalty for Your past and future use of Modifications made by such + Participant, or (ii) withdraw Your litigation claim with respect to + the Contributor Version against such Participant. If within 60 days + of notice, a reasonable royalty and payment arrangement are not + mutually agreed upon in writing by the parties or the litigation claim + is not withdrawn, the rights granted by Participant to You under + Sections 2.1 and/or 2.2 automatically terminate at the expiration of + the 60 day notice period specified above. + + (b) any software, hardware, or device, other than such Participant's + Contributor Version, directly or indirectly infringes any patent, then + any rights granted to You by such Participant under Sections 2.1(b) + and 2.2(b) are revoked effective as of the date You first made, used, + sold, distributed, or had made, Modifications made by that + Participant. + + 8.3. If You assert a patent infringement claim against Participant + alleging that such Participant's Contributor Version directly or + indirectly infringes any patent where such claim is resolved (such as + by license or settlement) prior to the initiation of patent + infringement litigation, then the reasonable value of the licenses + granted by such Participant under Sections 2.1 or 2.2 shall be taken + into account in determining the amount or value of any payment or + license. + + 8.4. In the event of termination under Sections 8.1 or 8.2 above, + all end user license agreements (excluding distributors and resellers) + which have been validly granted by You or any distributor hereunder + prior to termination shall survive termination. + +9. LIMITATION OF LIABILITY. + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT + (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL + DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, + OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR + ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY + CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, + WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER + COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN + INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF + LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY + RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW + PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE + EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO + THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. + +10. U.S. GOVERNMENT END USERS. + + The Covered Code is a "commercial item," as that term is defined in + 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer + software" and "commercial computer software documentation," as such + terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 + C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), + all U.S. Government End Users acquire Covered Code with only those + rights set forth herein. + +11. MISCELLANEOUS. + + This License represents the complete agreement concerning subject + matter hereof. If any provision of this License is held to be + unenforceable, such provision shall be reformed only to the extent + necessary to make it enforceable. This License shall be governed by + California law provisions (except to the extent applicable law, if + any, provides otherwise), excluding its conflict-of-law provisions. + With respect to disputes in which at least one party is a citizen of, + or an entity chartered or registered to do business in the United + States of America, any litigation relating to this License shall be + subject to the jurisdiction of the Federal Courts of the Northern + District of California, with venue lying in Santa Clara County, + California, with the losing party responsible for costs, including + without limitation, court costs and reasonable attorneys' fees and + expenses. The application of the United Nations Convention on + Contracts for the International Sale of Goods is expressly excluded. + Any law or regulation which provides that the language of a contract + shall be construed against the drafter shall not apply to this + License. + +12. RESPONSIBILITY FOR CLAIMS. + + As between Initial Developer and the Contributors, each party is + responsible for claims and damages arising, directly or indirectly, + out of its utilization of rights under this License and You agree to + work with Initial Developer and Contributors to distribute such + responsibility on an equitable basis. Nothing herein is intended or + shall be deemed to constitute any admission of liability. + +13. MULTIPLE-LICENSED CODE. + + Initial Developer may designate portions of the Covered Code as + "Multiple-Licensed". "Multiple-Licensed" means that the Initial + Developer permits you to utilize portions of the Covered Code under + Your choice of the NPL or the alternative licenses, if any, specified + by the Initial Developer in the file described in Exhibit A. + +EXHIBIT A -Mozilla Public License. + + ``The contents of this file are subject to the Mozilla Public License + Version 1.1 (the "License"); you may not use this file except in + compliance with the License. You may obtain a copy of the License at + http://www.mozilla.org/MPL/ + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the + License for the specific language governing rights and limitations + under the License. + + The Original Code is ______________________________________. + + The Initial Developer of the Original Code is ________________________. + Portions created by ______________________ are Copyright (C) ______ + _______________________. All Rights Reserved. + + Contributor(s): ______________________________________. + + Alternatively, the contents of this file may be used under the terms + of the _____ license (the "[___] License"), in which case the + provisions of [______] License are applicable instead of those + above. If you wish to allow use of your version of this file only + under the terms of the [____] License and not to allow others to use + your version of this file under the MPL, indicate your decision by + deleting the provisions above and replace them with the notice and + other provisions required by the [___] License. If you do not delete + the provisions above, a recipient may use your version of this file + under either the MPL or the [___] License." + + [NOTE: The text of this Exhibit A may differ slightly from the text of + the notices in the Source Code files of the Original Code. You should + use the text of this Exhibit A rather than the text found in the + Original Code Source Code for Your Modifications.] + diff --git a/guestbook/arial.ttf b/guestbook/arial.ttf new file mode 100644 index 0000000..ff0815c Binary files /dev/null and b/guestbook/arial.ttf differ diff --git a/guestbook/captcha.png b/guestbook/captcha.png new file mode 100644 index 0000000..b22655a Binary files /dev/null and b/guestbook/captcha.png differ diff --git a/guestbook/captcha.txt b/guestbook/captcha.txt new file mode 100644 index 0000000..c07b38c --- /dev/null +++ b/guestbook/captcha.txt @@ -0,0 +1 @@ +152368 \ No newline at end of file diff --git a/guestbook/changelog.txt b/guestbook/changelog.txt new file mode 100644 index 0000000..8585de9 --- /dev/null +++ b/guestbook/changelog.txt @@ -0,0 +1,39 @@ +Spider-Trap 0.92 + +Found a bug? +Please report the bug at our site http://www.spider-trap.de/forum/Bug+Report-2:0.html! +Thanks a lot! + +Version 0.92 - 14.01.2006 +- fixed ";" in settings +- no mail on add a spider +- new changelog +- upgrade the documentation +- Captcha Function + + +Version 0.91 - 13.01.2006 +- added whitelist for goog bots +- lock on txt and htaccess files +- bug - only blacklist updated +- use own word in settings for remove the ban +- redirection to directory path after ban +- new function to get the ip of the user +- new Banners added + +Version 0.90 - 06.01.2005 +- first released version + +Versions below 0.90 were developer version + +The contents of this file are subject to the Mozilla Public License +Version 1.1 (the "License"); you may not use this file except in +compliance with the License. You may obtain a copy of the License at +http://www.mozilla.org/MPL/ + +Software distributed under the License is distributed on an "AS IS" +basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the +License for the specific language governing rights and limitations +under the License. + +(c) 2005-2006 Thomas Zeithaml diff --git a/guestbook/forbid.php b/guestbook/forbid.php new file mode 100644 index 0000000..f88851f --- /dev/null +++ b/guestbook/forbid.php @@ -0,0 +1,135 @@ + +* @copyright (c) 2005-2006 Spider-Trap Team +* +* The contents of this file are subject to the Mozilla Public License +* Version 1.1 (the "License"); you may not use this file except in +* compliance with the License. You may obtain a copy of the License at +* http://www.mozilla.org/MPL/ +* +* Software distributed under the License is distributed on an "AS IS" +* basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the +* License for the specific language governing rights and limitations +* under the License. +*/ +require 'settings.php'; +include trap_core_path."core.inc.php"; + +function ts_gfx($ts_random) { +$rcode = hexdec(md5($_SERVER['HTTP_USER_AGENT'] . $_SERVER['SERVER_SOFTWARE'] . $_SERVER['HTTP_ACCEPT_CHARSET'] . sitekey . $ts_random . datekey . filemtime("settings.php"))); +$code = substr($rcode, 2, 6); + +setCaptchaId($code); + +$circles=5; +$width=100; +$height=40; +$font=5; + +$fontwidth = ImageFontWidth($font) * strlen($code); +$fontheight = ImageFontHeight($font); + +$max_lines = $fontheight / 4; +if (random_lines == true) +{ + $lines = rand(1, $max_lines); +} + else +{ + $lines=2; +} +if ($lines > $max_lines) $lines = $max_lines; + +$im = @imagecreate ($width,$height); +$background_color = imagecolorallocate ($im, rand(0,100),rand(0,100),rand(0,100)); +$text_color = imagecolorallocate ($im, rand(200,255),rand(200,255),rand(200,255)); // Random Text + +$r=0.01;$g=0.51;$b=0.87; +for ($i=1;$i<=$circles;$i++) { + $value=rand(200, 255); + $randomcolor = imagecolorallocate ($im , $value*$r, $value*$g,$value*$b); + imagefilledellipse($im,rand(0,$width-10),rand(0,$height-3), + rand(20,70),rand(20,70),$randomcolor); +} + +imagerectangle($im,0,0,$width-1,$height-1,$text_color); + +$w_pos = rand(5, abs($width - $fontwidth)); +$h_pos = rand(5, abs($height - 1 - $fontheight)); +imagestring ($im, $font, $w_pos, $h_pos, $code, $text_color); + +$y2 = 0; $y = 0; +for ($i=0;$i<$lines;$i++) { + while(abs($y2 - $y) < 2) + { + $y=rand($h_pos, ($h_pos + $fontheight)); + } + $y2 = $y; + $randomcolor=imagecolorallocate($im, 0,0, rand(100, 255)); + imageline($im, 0, $y, $width, $y, $randomcolor); +} + +header ("Content-type: image/jpeg"); +imagejpeg ($im,'',80); +ImageDestroy($im); +die(); +} +$ts_random=rand(); +$pos= strpos($_SERVER['REQUEST_URI'], '?'); +$basename = basename(substr($_SERVER['REQUEST_URI'], 0, $pos)); +if($basename==basename(__FILE__)) +ts_gfx($_GET['ts_random']); + +$value = getCaptchaId(); +if($_POST['unbanme'] == $value ){ + remove_blacklist(getip(), $_SERVER["HTTP_USER_AGENT"]); + header("Location: ../"); + exit; +} else { +?> + + + +403 - Zugriff verboten + +

Zugriff auf diese Website können Sie hier freischalten + +

+Falsche Eingabe - Sperre nicht aufgehoben !"; +} +?> +

Diese Seite dient zum Schutz vor sogenannten "bösen" Spambots. Oft ist es der Fall, dass man persönliche Daten wie z.B. die Bankverbindung + auf einer Webseite angibt. Damit diese Daten nicht in den Suchmaschinen auftauchen + hat man sich auf einen Standard geeinigt, wie man Websiten vor der Indexierung ausschließen kann.*
+ +
+ Sie sind einem Link gefolgt der für diesen Spambot gedacht war und haben dadurch eine Sperre Ihrer IP-Adresse ausgelöst.
+

Um + diese Sperre aufzuheben, müssen Sie in das folgende Formular den unten + angezeigten Wert eintragen und danach abschicken - dann haben Sie sofort + wieder Zugriff auf diese Website. +

+ /> +

+ + + +
+ + + +

 

+

* Dazu legt man eine Datei mit Namen robots.txt in das Root Verzeichnis des Webspaces und hinterlegt darin, welche Seiten indexiert werden dürfen und welche nicht. Suchmaschinen wie MSN, Yahoo oder Google halten sich an diese Regeln. Spambots aber lesen Internetseiten aus ohne dabei auf diese Richtlinien zu achten. Um dies zu unterbinden und damit die Webseiten zu schützen, werden diese Spambots ausgesperrt. Mehr Informationen über Webcrawler gibt es z.B: bei http://www.robotstxt.org/wc/robots.html

+

+powered by Spider-trap.de + + + \ No newline at end of file diff --git a/guestbook/index.php b/guestbook/index.php new file mode 100644 index 0000000..4a29ce7 --- /dev/null +++ b/guestbook/index.php @@ -0,0 +1,23 @@ + +* @copyright (c) 2005-2006 Spider-Trap Team +* +* The contents of this file are subject to the Mozilla Public License +* Version 1.1 (the "License"); you may not use this file except in +* compliance with the License. You may obtain a copy of the License at +* http://www.mozilla.org/MPL/ +* +* Software distributed under the License is distributed on an "AS IS" +* basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the +* License for the specific language governing rights and limitations +* under the License. +*/ +include "settings.php"; +include trap_core_path."core.inc.php"; +add_blacklist($_SERVER['REMOTE_ADDR'], $_SERVER['REQUEST_METHOD'], $_SERVER['REQUEST_URI'], $_SERVER['SERVER_PROTOCOL'], $_SERVER['HTTP_REFERRER'], $_SERVER['HTTP_USER_AGENT']); +header('Location: forbid.php'); +exit; +?> diff --git a/guestbook/no-badbot.gif b/guestbook/no-badbot.gif new file mode 100644 index 0000000..3a7eb3f Binary files /dev/null and b/guestbook/no-badbot.gif differ diff --git a/guestbook/pixel.gif b/guestbook/pixel.gif new file mode 100644 index 0000000..2d2380b Binary files /dev/null and b/guestbook/pixel.gif differ diff --git a/guestbook/settings.php b/guestbook/settings.php new file mode 100644 index 0000000..fcbaedc --- /dev/null +++ b/guestbook/settings.php @@ -0,0 +1,53 @@ + +* @copyright (c) 2005-2006 Spider-Trap Team +* +* The contents of this file are subject to the Mozilla Public License +* Version 1.1 (the "License"); you may not use this file except in +* compliance with the License. You may obtain a copy of the License at +* http://www.mozilla.org/MPL/ +* +* Software distributed under the License is distributed on an "AS IS" +* basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the +* License for the specific language governing rights and limitations +* under the License. +*/ +// Schreibrechte CHMOD 777 +error_reporting(0); +$htaccess_file = dirname(dirname(__FILE__))."/.htaccess"; +if (!is_writeable($htaccess_file)) die("Cannot write ".$htaccess_file." !"); +$blacklist_file = dirname(dirname(__FILE__))."/blacklist.txt"; +if (!is_writeable($blacklist_file)) die("Cannot write ".$blacklist_file." !"); +$whitelist_file = dirname(dirname(__FILE__))."/whitelist.txt"; +if (!is_writeable($whitelist_file)) die("Cannot write ".$whitelist_file." !"); + +$alert_email = "webmaster@mxchange.org"; // Email für Benachrichtigungen + +$mail_on_add = true; // Email senden wenn neue Sperre +$mail_on_remove = true; // Email senden wenn Sperre für jemand aufgehoben wurde ? + +$trap_path = "guestbook/"; // path of the trap - must end with a "/" + +$sleep_min = 30; $sleep_max = 300; + +$captcha_file = dirname(dirname(__FILE__))."/".$trap_path."captcha.txt"; +if (!is_writeable($captcha_file)) die("Cannot write ".$captcha_file." !"); + +// Bitte randomizen Sie diesen String etwas selber! ;-) +define('sitekey', "spider-trap_gp2eg1f23.g24ih13]f.i31g]042ih9gi4p]goieghopekgfp1elf"); + +// Hier koennen Sie auch das deutsche Datumsformat nehmen, Uhrzeit nicht, da diese zu haeufig wechselt +// und somit die Codegenerierung nicht identische Codes liefert +define('datekey', date("d-m-Y", time())); + +// Sollen die Linienanzahl per Zufall gewaehlt werden? Ja = true, Nein, fixierte Anzahl = false +define('random_lines', true); + +// Wo sind die "Core-Dateien" abgelegt? (mit abschliessendem Slash!) +define('trap_core_path', "/usr/share/php/spider-trap/"); + +// +?> diff --git a/guestbook/spider.jpg b/guestbook/spider.jpg new file mode 100644 index 0000000..e20325c Binary files /dev/null and b/guestbook/spider.jpg differ diff --git a/imprint.html b/imprint.html new file mode 100644 index 0000000..9cc20dd --- /dev/null +++ b/imprint.html @@ -0,0 +1,51 @@ + + + +Quix0r's FlightGear Webpage - Imprint / Impressum + + + + +

+ + + + + + + +
Imprint / Impressum
+ +
+ Kein Support, keine Beratung per Telefon
+
+ Alle Inhalte, die sich ausserhalb dieses Angebotes (also ausserhalb von http://flightgear.mxchange.org) befinden sind keine Werke von mir. Ich habe keinen Einfluß auf die Gestaltung + von externen Seiten und distanziere mich von diesen und deren Inhalten. Auch trotz sorfätiger Überprüfung der aufgenommenen Links, kann ich dennoch keine + Garantie für diese Seiten abgeben. Ich übernehme weiterhin keine Gewähr für die Erreichbarkeit der verlinkten Seiten und für die Korrektheit und + rechtliche Unbedenklichkeit der von den jeweiligen Anbietern hinterlegten Inhalten.
+
+

+ +

+ Please further note: flightgear.org and many (all?) sub domains and including the forums use Google Analytics to track + your surf behavior. If you don't want that and still want to visit their pages, use Ghostery for your browser and + activate the blocking feature. It may slow down your surf experience a little but should remain useable. +

+ +

+ + Created: 2008-04-23 | + Last update: 2011-06-08 | + Author: Roland Häder
+ Links collection | + Back to index +
+

+ + + diff --git a/index.html b/index.html new file mode 100644 index 0000000..c86fab0 --- /dev/null +++ b/index.html @@ -0,0 +1,173 @@ + + + +Quix0r's FlightGear Webpage - A simple FlightGear Helping Page + + + + +
A simple page for simple help
+ +

+ The main purpose of this webpage is to help people having a fully featured + FlightGear + installation. It is mainly based on my own experiences I have made with this + great piece of software and at home while playing with my Saitek X52 Pro joystick. +

+ +

+ First of all, you need to download the latest version of FlightGear + from a mirror. At the moment of writing this page it was 2.0 in + main program and scenery. Use this link for instance. +

+ +

+ If you have done so you can only fly a bit around in the area of San + Francisco (KSFO plus some more). That is indeed not very much. So you need + to get some scenery and more "shared models". Also you will see a + lot warning messages or failures. We fix them all step-by-step. +

+ +

+ So first let us fix the warnings (a bit, not all) and failures while the + program is starting up. Most happens because of missing scenery and objects + like buildings in the scenery. Download SharedModels.tgz and (if you + have a dial-in connection) GlobalObjects.tgz from this webpage. + You don't need to download every single building! Just grab the big tar balls. +

+ +

+ On Linux systems you will find tools like tar and gzip for + uncompression and extraction of the data. But wait! You need to know where you + shall put them. +

+ +

+ The GlobalObjects.tgz archive contains a lot directories like eXXXnYYY + plus a lot sub directories with small files in. First change the directory to FG_ROOT + (on my Debian system it is /usr/shared/games/FlightGear/ and change again + into Scenery/Objects/. The final command will looks like this:
+
+

cd /usr/share/games/FlightGear/Scenery/Objects/
+wget http://flightgear.mxchange.org/pub/scenemodels/GlobalObjects.tgz
+tar xzf GlobalObjects.tgz # (this will take looooong ...)
+rm -f GlobalObjects.tgz # (to save disk space)

+ Or try my copy. + You can use the tab key for autocompletition if you prefer not to enter all + single characters in the cd command. +

+ +

That part was simple, wasn't it? :)

+ +

+ Now we need to get the SharedModels.tgz file but its content + should be stored in a different folder. Here are again the needed + commands to get it, extract and fix a small bug in it:
+
+

cd ../../
+wget http://flightgear.mxchange.org/pub/scenemodels/SharedModels.tgz
+tar xzf SharedModels.tgz # (will take again a bit longer)
+rm -f SharedModels.tgz # (again for saving disk space)
+

+ +

+ Alternative download: (from my server)
+ · SharedModels.tgz
+ · GlobalObjects.tgz +

+ +

+ Well done! You can now still fly around in the basic area of San Fransico + Beach but with some more objects and details. :) Enjoy it before we continue + with the last steps. +

+ +

+ If you have a lot (!!!) disk space left you may want to download more scenery + (or the whole world?) on your drive. But you can also save it by using an + external rsync server. I have discontinued to provide + it due to low disk space on my server (only 40 GByte). But still you can + donwload all packages. +

+ +

+ If you want to use an external rsync server (you + need TerraSync to do so) please use my launch-helper which available here. It is written in Bash (Born Again + Shell) and starts TerraSync for you to connect to a public rsync server. It also helps you with playing in + multi-player mode and many more! +

+ +

+ If you want to download all the scenery then find a free weekend and continue below + this paragraph. Everyone else is done here or might download some aircrafts as well. +

+ +

+ Hint for mass-downloaders: You don't need the data from + AirportOverlays and RawData if you just want to fly around! You need them if + you want to build scenery only. And don't mess around with the Models-Airspace.tar.gz + and Scenery-Airspace.tar.gz located here. In the Scenery-Airspace.tar.gz you will find a + folder called Objects. Don't mix that with the one in + Scenery. If you do so you need to re-install your scenery again. +

+ +

+ Continue here with full scenery download: wget can be a good + friend if you know how to use it and if you clean up the download after usage. + So this next script is based on it. +

+ +

+ You can find my download helper here. + Here are the needed commands to get full scenery on your drive:
+
+

cd /usr/share/games/FlightGear/Scenery/
+wget http://flightgear.mxchange.org/pub/download-helper.zip
+unzip download-helper.zip
+sh extract.sh
+

+ +

+ Clean up of downloaded archives is being done by extract.sh. If you like you + can remove download-helper.zip, extract.sh, listing + and okay. They belong to my script and not to FlightGear. +

+ +

+ If the download fails just try to restart it with sh extract.sh + after some minutes. The both servers are very busy these days... :-/ +

+ +

+ Happy gaming! +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-03-28 | + Last update: 2011-05-26 | + Author: Roland Häder
+ Links collection | + FGCOM Tutorial | + fgdata.bundle Tutorial | + My used scenery | + How to rsync a scenery | + My flights in FGFS | + Imprint (needed in Germany) +
+

+ + + diff --git a/lemd-lfpg-eddl-eddh.html b/lemd-lfpg-eddl-eddh.html new file mode 100644 index 0000000..11421f3 --- /dev/null +++ b/lemd-lfpg-eddl-eddh.html @@ -0,0 +1,89 @@ + + + + Quix0r's FlightGear Webpage - Continued flight from LEMD over LFPG and EDDL to EDDH + + + + +
A continued flight from LEMD over LFPG and EDDL to EDDH
+ +

+ This is a continued flight enroute of LIRF over LEIB to LEMD. +

+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · LEMD (Madrid, Spain)
+ · UCEDA
+ · NOLSA
+ · ORTEZ
+ · TIRET
+ · RBT06 (Lower altitude here)
+ · RGS17
+ · PGD08
+ · LFPG (Not needed to enter in AP, set NAV1 to 110.1 MHz, 85.32 degrees)
+ · PG086
+ · DIDOR
+ · NEBUL
+ · BBE38
+ · MODRU (Lower altitude here)
+ · DL550
+ · DL013
+ · DL003
+ · R2934 (Set NAV1 to 111.5 MHz, 52.7 degrees)
+ · EDDL (Not needed to enter in AP)
+ · DL050
+ · BAM58
+ · DL430
+ · DGW01
+ · OSTAK
+ · VISKI
+ · VERED
+ · DH235 (Lower altitude here)
+ · DH258 (Altitude should be 3.000 ft)
+ · DH010
+ · R1276 (Set NAV1 to 110.5 MHz, 230.2 degrees
+ · EDDH (Not needed to enter in AP)
+
+ Notices: You should not climb higher than 10.000ft. + You should begin reducing the altitude to 1.000 feet when you are approx. 4 + to 6 minutes away with a maximum airspeed of 320 kts away from your desired + destination. Reduce your speed to 180kts for a good landing with the Bravo. +

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-04-26 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/links.html b/links.html new file mode 100644 index 0000000..beb672d --- /dev/null +++ b/links.html @@ -0,0 +1,51 @@ + + + + Quix0r's FlightGear Webpage - Some nice links I have collected + + + + +
Some nice links I have collected
+ +

+ Here is a list of nice FlightGear-related links I have found in the Internet. +

+ +

+ · Anders' nice multi-player carrier patch. This one is now included in CVS
+ · Stewart's Hangar
+ · Lighter-than-air simulation in JSBSim and FlightGear
+ · Helijah's Hangar
+ · buster's FlightGear Site
+ · jomo's FlightGear Site
+ · My announcement for my MP server mpserver08 @ the forums.
+ · My announcement for my launcher script.
+ · Another link I need to addd...
+

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2009-03-18 | + Last update: 2011-04-08 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/lirf-leib-lemd.html b/lirf-leib-lemd.html new file mode 100644 index 0000000..d50f655 --- /dev/null +++ b/lirf-leib-lemd.html @@ -0,0 +1,81 @@ + + + + Quix0r's FlightGear Webpage - Continued flight from LIRF over LEIB to LEMD + + + + +
A continued flight from LIRF over LEIB to LEMD
+ +

+ This is a continued flight enroute of EDDH over LOWW to LIRF. +

+ +

+ You can use this flight plan for the auto-pilot in your favorite airplane + (never in real!). You should be directed straight on the runway for save + landing... and don't forget to pull out the gear! ;-) +

+ +

+ · LIRF (Roma, Italia)
+ · VALMA
+ · MADKA
+ · POULP
+ · VELON
+ · BALEN
+ · JOA26
+ · SSJ53 (Lower altitude here)
+ · IBA36
+ · R2306/LEIB (Ibiza, Spain))
+ · IBA27
+ · NINOT
+ · VLC18
+ · MINGU
+ · PALIO (Lower altitude here)
+ · MAA63
+ · MAA04
+ · R2256/LEMD (Madrid, Spain)
+
+ Notices: You should not climb higher than 10.000ft. + You should begin reducing the altitude to 1.000 feet when you are approx. 4 + to 6 minutes away with a maximum airspeed of 320 kts away from your desired + destination. Reduce your speed to 180kts for a good landing with the Bravo. +

+ +

+ You may want to continue flying these routes:
+ · LEMD (Madrid) over LFPG (Paris) and EDDL (Düsseldorf) to EDDH (Hamburg).
+

+ +

+ And never use these flight plans in reality! +

+ +

+ Meet you in FGFS. :) +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-04-23 | + Last update: 2011-01-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/pfs-scam.html b/pfs-scam.html new file mode 100644 index 0000000..a3607e1 --- /dev/null +++ b/pfs-scam.html @@ -0,0 +1,117 @@ + + + + Quix0r's FlightGear Webpage - What you should know before you order PFS + + + + +
What you should know before you order PFS
+ +

+ The PFS (Pro Flight Simulator) is a fork of FlightGear with main focus on making quick money (more to scam on innocent people + but more about that later). Right now, I don't feel comfortable to put a link to these scammer + folks. So just search and *DON'T* buy it. So I start with their webpage (the source + code file is a different topic). +

+ +

+ The header is on nearly every page the same and looks "professionally" made. The index page + (where you enter a website) looks like every other MLM product advertising page I have seen so far. I also + spare out to link to them for the same reason I will not link to PFS). On that page you can already find + many lies if you know FlightGear for a longer time: +

+ +

+

+

+ +

+ Source code references +

+ +

+ TaxiDraw:
+ SourceForge Project Website +

git clone git://mapserver.flightgear.org/taxidraw
+

+ +

+ Kelpie Flight Planner:
+ SourceForge Project Website +

+ +

+ And please remember one thing: I don't call myself as a truther or so. I just summon up this + page to put some simple facts about the PFS scam together. +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2011-06-08 | + Last update: 2011-06-16 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/pub/.htaccess b/pub/.htaccess new file mode 100644 index 0000000..0a9ef2d --- /dev/null +++ b/pub/.htaccess @@ -0,0 +1,3 @@ +Options +Indexes + +Order Deny,Allow diff --git a/pub/download-helper.zip b/pub/download-helper.zip new file mode 100644 index 0000000..8844fc6 Binary files /dev/null and b/pub/download-helper.zip differ diff --git a/pub/fgfs-launcher.zip b/pub/fgfs-launcher.zip new file mode 100644 index 0000000..79294d6 Binary files /dev/null and b/pub/fgfs-launcher.zip differ diff --git a/pub/helper.zip b/pub/helper.zip new file mode 100644 index 0000000..e8b4549 Binary files /dev/null and b/pub/helper.zip differ diff --git a/pub/rsyncd.conf b/pub/rsyncd.conf new file mode 100644 index 0000000..a9568f0 --- /dev/null +++ b/pub/rsyncd.conf @@ -0,0 +1,102 @@ +# sample rsyncd.conf configuration file + +# GLOBAL OPTIONS + +#motd file=/etc/motd +# log file=/var/log/rsyncd.log +# for pid file, dont' use /var/run/rsync.pid unless you're not going to run +# rsync out of the init.d script. The /var/run/rsyncd.pid below is OK. +pid file=/var/run/rsyncd.pid +syslog facility=daemon +#socket options= +address=0.0.0.0 +lock file = /var/lock/rsyncd + +# MODULE OPTIONS +[Airports] + + comment = Flight Gear Archive - Airports + path = /some/path/fgdata/Scenery/Airports/ + use chroot = no +# max connections=10 + lock file = /var/lock/rsyncd +# the default for read only is yes... + read only = yes + list = yes + uid = nobody + gid = nogroup +# exclude = +# exclude from = +# include = +# include from = +# auth users = +# secrets file = /etc/rsyncd.secrets + strict modes = yes +# hosts allow = +# hosts deny = + ignore errors = no + ignore nonreadable = yes + transfer logging = yes + log format = %t: host %h (%a) %o %f (%l bytes). Total %b bytes. + timeout = 600 + refuse options = dry-run + dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz + +# MODULE OPTIONS +[Terrain] + + comment = Flight Gear Archive - Terrain + path = /some/path/fgdata/Scenery/Terrain/ + use chroot = no +# max connections=10 + lock file = /var/lock/rsyncd +# the default for read only is yes... + read only = yes + list = yes + uid = nobody + gid = nogroup +# exclude = +# exclude from = +# include = +# include from = +# auth users = +# secrets file = /etc/rsyncd.secrets + strict modes = yes +# hosts allow = +# hosts deny = + ignore errors = no + ignore nonreadable = yes + transfer logging = yes + log format = %t: host %h (%a) %o %f (%l bytes). Total %b bytes. + timeout = 600 + refuse options = dry-run + dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz + +[Objects] + + comment = Flight Gear Archive - Objects + path = /some/path/fgdata/Scenery/Objects/ + use chroot = no +# max connections=10 + lock file = /var/lock/rsyncd +# the default for read only is yes... + read only = yes + list = yes + uid = nobody + gid = nogroup +# exclude = +# exclude from = +# include = +# include from = +# auth users = +# secrets file = /etc/rsyncd.secrets + strict modes = yes +# hosts allow = +# hosts deny = + ignore errors = no + ignore nonreadable = yes + transfer logging = yes + log format = %t: host %h (%a) %o %f (%l bytes). Total %b bytes. + timeout = 600 + refuse options = dry-run + dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz diff --git a/pub/screenshot-anonymizer-fvwm-crystal_1280x1024.svg b/pub/screenshot-anonymizer-fvwm-crystal_1280x1024.svg new file mode 100644 index 0000000..f5071b4 --- /dev/null +++ b/pub/screenshot-anonymizer-fvwm-crystal_1280x1024.svg @@ -0,0 +1,115 @@ + + + + + + diff --git a/pub/svn-fgdata-bundle.sh b/pub/svn-fgdata-bundle.sh new file mode 100644 index 0000000..b40e1cd --- /dev/null +++ b/pub/svn-fgdata-bundle.sh @@ -0,0 +1,23 @@ +#!/bin/sh + +GIT_DIR="/home/quix0r/fgdata/" +BASE_FILE="/var/www/foo/pub/fgfs/fgdata.bundle" +USER="bar" +GROUP="www-data" + +cd "${GIT_DIR}" +nice --adjustment=19 rm -fv ${BASE_FILE}* +nice --adjustment=19 git pull || exit 1 +nice --adjustment=19 git-bundle create ${BASE_FILE} HEAD || exit 1 +echo "$0: Creating MD5 checksum ..." +nice --adjustment=19 md5sum ${BASE_FILE} > "${BASE_FILE}.md5" || exit 1 +echo "$0: Creating SHA1 checksum ..." +nice --adjustment=19 sha1sum ${BASE_FILE} > "${BASE_FILE}.sha1" || exit 1 +echo "$0: Creating SHA256 checksum ..." +nice --adjustment=19 sha256sum ${BASE_FILE} > "${BASE_FILE}.sha256" || exit 1 +echo "$0: Creating SHA512 checksum ..." +nice --adjustment=19 sha512sum ${BASE_FILE} > "${BASE_FILE}.sha512" || exit 1 +echo "$0: Doing chmod/chown ..." +chown "${USER}.${GROUP}" ${BASE_FILE}* || exit 1 +chmod a+r ${BASE_FILE}* || exit 1 +echo "$0: All done." diff --git a/robots.txt b/robots.txt new file mode 100644 index 0000000..ab6fe6b --- /dev/null +++ b/robots.txt @@ -0,0 +1,383 @@ +User-agent: grub-client +Disallow: / + +User-agent: grub +Disallow: / + +User-agent: looksmart +Disallow: / + +User-agent: WebZip +Disallow: / + +User-agent: larbin +Disallow: / + +User-agent: b2w/0.1 +Disallow: / + +User-agent: psbot +Disallow: / + +User-agent: Python-urllib +Disallow: / + +User-agent: NetMechanic +Disallow: / + +User-agent: URL_Spider_Pro +Disallow: / + +User-agent: CherryPicker +Disallow: / + +User-agent: EmailCollector +Disallow: / + +User-agent: EmailSiphon +Disallow: / + +User-agent: WebBandit +Disallow: / + +User-agent: EmailWolf +Disallow: / + +User-agent: ExtractorPro +Disallow: / + +User-agent: CopyRightCheck +Disallow: / + +User-agent: Crescent +Disallow: / + +User-agent: SiteSnagger +Disallow: / + +User-agent: ProWebWalker +Disallow: / + +User-agent: CheeseBot +Disallow: / + +User-agent: LNSpiderguy +Disallow: / + +User-agent: ia_archiver +Disallow: / + +User-agent: ia_archiver/1.6 +Disallow: / + +User-agent: Teleport +Disallow: / + +User-agent: TeleportPro +Disallow: / + +User-agent: MIIxpc +Disallow: / + +User-agent: Telesoft +Disallow: / + +User-agent: Website Quester +Disallow: / + +User-agent: moget/2.1 +Disallow: / + +User-agent: WebZip/4.0 +Disallow: / + +User-agent: WebStripper +Disallow: / + +User-agent: WebSauger +Disallow: / + +User-agent: WebCopier +Disallow: / + +User-agent: NetAnts +Disallow: / + +User-agent: Mister PiX +Disallow: / + +User-agent: WebAuto +Disallow: / + +User-agent: TheNomad +Disallow: / + +User-agent: WWW-Collector-E +Disallow: / + +User-agent: RMA +Disallow: / + +User-agent: libWeb/clsHTTP +Disallow: / + +User-agent: asterias +Disallow: / + +User-agent: httplib +Disallow: / + +User-agent: turingos +Disallow: / + +User-agent: spanner +Disallow: / + +User-agent: InfoNaviRobot +Disallow: / + +User-agent: Harvest/1.5 +Disallow: / + +User-agent: Bullseye/1.0 +Disallow: / + +User-agent: Mozilla/4.0 (compatible; BullsEye; Windows 95) +Disallow: / + +User-agent: Crescent Internet ToolPak HTTP OLE Control v.1.0 +Disallow: / + +User-agent: CherryPickerSE/1.0 +Disallow: / + +User-agent: CherryPickerElite/1.0 +Disallow: / + +User-agent: WebBandit/3.50 +Disallow: / + +User-agent: NICErsPRO +Disallow: / + +User-agent: Microsoft URL Control - 5.01.4511 +Disallow: / + +User-agent: DittoSpyder +Disallow: / + +User-agent: Foobot +Disallow: / + +User-agent: WebmasterWorldForumBot +Disallow: / + +User-agent: SpankBot +Disallow: / + +User-agent: BotALot +Disallow: / + +User-agent: lwp-trivial/1.34 +Disallow: / + +User-agent: lwp-trivial +Disallow: / + +User-agent: BunnySlippers +Disallow: / + +User-agent: Microsoft URL Control - 6.00.8169 +Disallow: / + +User-agent: URLy Warning +Disallow: / + +User-agent: LinkWalker +Disallow: / + +User-agent: cosmos +Disallow: / + +User-agent: moget +Disallow: / + +User-agent: hloader +Disallow: / + +User-agent: humanlinks +Disallow: / + +User-agent: LinkextractorPro +Disallow: / + +User-agent: Offline Explorer +Disallow: / + +User-agent: Mata Hari +Disallow: / + +User-agent: LexiBot +Disallow: / + +User-agent: Web Image Collector +Disallow: / + +User-agent: The Intraformant +Disallow: / + +User-agent: True_Robot/1.0 +Disallow: / + +User-agent: True_Robot +Disallow: / + +User-agent: BlowFish/1.0 +Disallow: / + +User-agent: JennyBot +Disallow: / + +User-agent: MIIxpc/4.2 +Disallow: / + +User-agent: BuiltBotTough +Disallow: / + +User-agent: ProPowerBot/2.14 +Disallow: / + +User-agent: BackDoorBot/1.0 +Disallow: / + +User-agent: toCrawl/UrlDispatcher +Disallow: / + +User-agent: WebEnhancer +Disallow: / + +User-agent: suzuran +Disallow: / + +User-agent: VCI WebViewer VCI WebViewer Win32 +Disallow: / + +User-agent: VCI +Disallow: / + +User-agent: Szukacz/1.4 +Disallow: / + +User-agent: QueryN Metasearch +Disallow: / + +User-agent: Openfind data gathere +Disallow: / + +User-agent: Openfind +Disallow: / + +User-agent: Xenu's Link Sleuth 1.1c +Disallow: / + +User-agent: Xenu's +Disallow: / + +User-agent: Zeus +Disallow: / + +User-agent: RepoMonkey Bait & Tackle/v1.01 +Disallow: / + +User-agent: RepoMonkey +Disallow: / + +User-agent: Microsoft URL Control +Disallow: / + +User-agent: Openbot +Disallow: / + +User-agent: URL Control +Disallow: / + +User-agent: Zeus Link Scout +Disallow: / + +User-agent: Zeus 32297 Webster Pro V2.9 Win32 +Disallow: / + +User-agent: Webster Pro +Disallow: / + +User-agent: EroCrawler +Disallow: / + +User-agent: LinkScan/8.1a Unix +Disallow: / + +User-agent: Keyword Density/0.9 +Disallow: / + +User-agent: Kenjin Spider +Disallow: / + +User-agent: Iron33/1.0.2 +Disallow: / + +User-agent: Bookmark search tool +Disallow: / + +User-agent: GetRight/4.2 +Disallow: / + +User-agent: FairAd Client +Disallow: / + +User-agent: Gaisbot +Disallow: / + +User-agent: Aqua_Products +Disallow: / + +User-agent: Radiation Retriever 1.1 +Disallow: / + +User-agent: Flaming AttackBot +Disallow: / + +User-agent: Oracle Ultra Search +Disallow: / + +User-agent: MSIECrawler +Disallow: / + +User-agent: PerMan +Disallow: / + +User-agent: searchpreview +Disallow: / + +User-agent: * +Disallow: /guestbook + +User-agent: Googlebot +Disallow: /guestbook + +User-agent: * +Disallow: /blacklist.txt + +User-agent: Googlebot +Disallow: /blacklist.txt + +User-agent: * +Disallow: /whitelist.txt + +User-agent: Googlebot +Disallow: /whitelist.txt + +User-agent: * +Disallow: /pub + +User-agent: Googlebot +Disallow: /pub diff --git a/rsync.html b/rsync.html new file mode 100644 index 0000000..a6d0744 --- /dev/null +++ b/rsync.html @@ -0,0 +1,92 @@ + + + + Quix0r's FlightGear Webpage - How to use rsync to get the scenery from a rsync server + + + + +
How to get the scenery from a rsync server
+ +

+ Here you will learn how to mirror (in this case) the FlightGear scenery from my server to your local hard + drive. But you can easily adapt this on other rsync servers because the + procedure is nearly the same. +

+ +

+ First of all you need a lot free hard disk space before you + can start. 4 gigs left might be to much but should not hurt. :) So let us start + with the sync procedure, shall we? +

+ +

+ Get a console window (unter Linux a terminal box) ready and find a place where + you want to have your scenery downloaded to. In my example I asume that you + want to create a new directory for your scenery. Then create the sub + directories Airports, Terrain and + Objects and start the rsync process in both directories. +

+ +

+ To fast for you? Okay! Here are my commands I have entered: +

+ +

+

cd
+mkdir fgfs-scenery
+cd fgfs-scenery
+mkdir Terrain # The first letter must be capitalized...
+mkdir Objects # ... and don't miss the s here.
+mkdir Airports # ... and the s again!
+rsync -a rsync://flightgear.mxchange.org/Terrain/ ./Terrain/
+rsync -a rsync://flightgear.mxchange.org/Objects/ ./Objects/
+rsync -a rsync://flightgear.mxchange.org/Airports/ ./Airports/
+cd
+

+ +

+ Discontinued service: Due to low disk space on my server I + had to discontinue my rsync server. You can still download the whole scenery + from my server. +

+ +

+ That should take a long time so you may want to setup a small script + containing these commands and while download is running you may want + to take out your dog for a walk. :-) +

+ +

+ After this there is only one step left: Use the new path + ~/fgfs-scenery/ as the new scenery path for FlightGear. + To do so simply call fgfs with the parameter --fg-scenery=~/fgfs-scenery/. +

+ +

+ Happy gaming! +

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2008-03-29 | + Last update: 2011-02-05 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/tutorial-gimp-livery-drawing.html b/tutorial-gimp-livery-drawing.html new file mode 100644 index 0000000..3828685 --- /dev/null +++ b/tutorial-gimp-livery-drawing.html @@ -0,0 +1,202 @@ + + + + Quix0r's FlightGear Webpage - Tutorial: How to get paths for livery drawing in GIMP + + + + +
Tutorial: How to get paths for livery drawing in GIMP
+ +

+ Problem: +

+ +

+ Most airplane constructors (for FlightGear, not the real ones!) provide a + so-called "paint kit" which provides the designer an already + effective way to draw his/her livery (in GIMP, of course). So if you want to + draw a livery for your favorite (real or fantasy) airplane, you still + encounter these ugly looking white stripes on the borders. They are being + added by GIMP in the process of removing the alpha channel from the image + (maybe Skyop asked you to do so? ;-) ). Now you need to get rid of them, + because they make your model (this also applies on building, towers, hangars + and all other "ground-level" constructions with textures) look + unprofessional and not good. +

+ +

+ Steps to do: +

+ +

+ I take skyop's CRJ1000 paintkit from git as an example. It is called + CRJ1000-paintkit.xcf. I do this tutorial slowy, so for + experienced GTK/GIMP/Linux/Computer-in-general users it might be a bit + boring. Just head on faster if you feel you already know that step. +

+ +

+ First, startup GIMP. On my desktop it looks like in the picture below.
+ GIMP has fully started
+ Image #1: GIMP has fully started up on a FVWM-Crystal desktop +

+ +

+ Load the paint kit (it must be provided or else ask the airplane constructor + kindly to provide one for GIMP) into GIMP. Again where you saved that file, + I leave that completely up to you. :-) So look for it (btw.: noticed the + file selection boxes have a "bookmarking" feature called + "Places"? Just in case you want to shortcut a lot clicks into one + single ...)
+ GTK selection box with the paint kit file already marked
+ Image #2: GTK selection box with the paint kit file already marked +

+ +

+ If you have done so, the image got loaded into your computer's RAM and + displayed as similar below (maybe you have a different solution so GIMP will + change the zoom factor to match the image into your screen so it may + NOT look exacly the same).
+ GIMP has loaded the CRJ1000-paintkit.xcf file and displayed it
+ Image #3: GIMP has loaded the CRJ1000-paintkit.xcf file and displayed it +

+ +

+ Now make the layer called [DEL] UV map active by simply + clicking on it and click the little magic wand in the toolbox. Need a + screenshot? Just one more step please: Click in the large white area of + that image (maybe between the two fuselage halves?). The result of these + three steps is shown below.
+ Magically selected parts of the airplane
+ Image #4: Magically selected parts of the airplane +

+ +

+ Next choose Select from the image window's menu + and click Invert/ or hit CTRL+I. The (animated) + selection will now change slightly so I go to next step. Choose + Select again, but now Shrink. + You should get a similar box as show below. The invertion step is very + import so don't leave it out. If you miss it you will get a wrong path + as the final result.
+ Open Shrink Selection box and inverted selection
+ Image #5: Open Shrink Selection box and inverted selection +

+ +

+ Now enter 3 to 5 or more as selection shrink value (you have find that out + for yourself because it depends on the image and alpha channel) and hit the + OK button. The selection is now shrinked and may look like + mine below. I choosed 3 as shrink value.
+ Shrinked selection with 3 as value
+ Image #6: Shrinked selection with 3 as value +

+ +

+ Now you could start drawing your livery into the layer by + adding a new transparent layer, but you should save your + selection (path! hint, hint!) for later usage (on the same paint kit, of + course). To do so, choose Select again and hit + To Path (here it was the last entry in the menu). + GIMP now starts to convert the selection into a path, but after it is done, + nothing seems to happen to your image, right? Wrong! You added a path to + your image. To make that visible, just bring up the path dialog (which can + be accessed through Windows, + Dockable Dialogs. If you want to shortcut that, hit + the last menu entry Layers, Channels, Paths, Undo which + gives you a similar window like the one in lower right corner of my + screenshots. Now just hit that 3rd item in that window and you get a similar + view like following screenshot.
+ Paths dialog box selected with the previously generated path
+ Image #7: Paths dialog box selected with the previously generated path +

+ +

+ Now you may wish to rename it and export it on your hard drive. To do the + first step, double-click the current name Selection and type what + ever you want to call it. You may want to choose All airplane parts + or something descriptive. After that, right click the path and hit + Export Path ... (that one with the little disk). + Select the desired folder where you want to store it (preferable near the + CRJ1000-paintkit.xcf file) and e.g. name it + CRJ1000-paintkit-paths.svg so you can easily look it up for + later purposes. I leave this step out, screenshotting it, you will get a + similar selection box as above. +

+ +

+ Now you can start drawing liveries for your favorite airplane and reuse (or + first create) your exported paths for easy drawing! If you have imported + your path, you need to convert it into a selection and keep it invisible. + I think you already know, where to do that or didn't you take a longer + look on the path's context menu, do you? :-) +

+ +

+ Thank you for participating my tutorial! If you have + feedback to tell me, contact me at my email address, ICQ, Jabber or in IRC + channel (Quix0r). +

+ +

+ By the way: I used a converted, as path exported selection + to blacken my personal things on my screenshots. The path can be found here. +

+ +

+ Used software: +

+

+ +

+ PS: My manually mirrored download archive for FlightGear can be found + here. So take a look around. :) +

+ +

+ + Created: 2011-06-11 | + Last update: 2011-06-11 | + Author: Roland Häder
+ My flights in FGFS | + FGCOM Tutorial | + fgdata.bundle Tutorial | + How to rsync a scenery | + Links collection | + Imprint (needed in Germany) | + Back to index +
+

+ + + diff --git a/tutorials/img/livery-paths/001-thumb.png b/tutorials/img/livery-paths/001-thumb.png new file mode 100644 index 0000000..013c62b Binary files /dev/null and b/tutorials/img/livery-paths/001-thumb.png differ diff --git a/tutorials/img/livery-paths/001.png b/tutorials/img/livery-paths/001.png new file mode 100644 index 0000000..99939b7 Binary files /dev/null and b/tutorials/img/livery-paths/001.png differ diff --git a/tutorials/img/livery-paths/002-thumb.png b/tutorials/img/livery-paths/002-thumb.png new file mode 100644 index 0000000..76249e0 Binary files /dev/null and b/tutorials/img/livery-paths/002-thumb.png differ diff --git a/tutorials/img/livery-paths/002.png b/tutorials/img/livery-paths/002.png new file mode 100644 index 0000000..fa7d248 Binary files /dev/null and b/tutorials/img/livery-paths/002.png differ diff --git a/tutorials/img/livery-paths/003-thumb.png b/tutorials/img/livery-paths/003-thumb.png new file mode 100644 index 0000000..61d2d75 Binary files /dev/null and b/tutorials/img/livery-paths/003-thumb.png differ diff --git a/tutorials/img/livery-paths/003.png b/tutorials/img/livery-paths/003.png new file mode 100644 index 0000000..e57fdad Binary files /dev/null and b/tutorials/img/livery-paths/003.png differ diff --git a/tutorials/img/livery-paths/004-thumb.png b/tutorials/img/livery-paths/004-thumb.png new file mode 100644 index 0000000..ed80e41 Binary files /dev/null and b/tutorials/img/livery-paths/004-thumb.png differ diff --git a/tutorials/img/livery-paths/004.png b/tutorials/img/livery-paths/004.png new file mode 100644 index 0000000..1a827e1 Binary files /dev/null and b/tutorials/img/livery-paths/004.png differ diff --git a/tutorials/img/livery-paths/005-thumb.png b/tutorials/img/livery-paths/005-thumb.png new file mode 100644 index 0000000..36607c7 Binary files /dev/null and b/tutorials/img/livery-paths/005-thumb.png differ diff --git a/tutorials/img/livery-paths/005.png b/tutorials/img/livery-paths/005.png new file mode 100644 index 0000000..578f250 Binary files /dev/null and b/tutorials/img/livery-paths/005.png differ diff --git a/tutorials/img/livery-paths/006-thumb.png b/tutorials/img/livery-paths/006-thumb.png new file mode 100644 index 0000000..69172cd Binary files /dev/null and b/tutorials/img/livery-paths/006-thumb.png differ diff --git a/tutorials/img/livery-paths/006.png b/tutorials/img/livery-paths/006.png new file mode 100644 index 0000000..c403bc9 Binary files /dev/null and b/tutorials/img/livery-paths/006.png differ diff --git a/tutorials/img/livery-paths/007-thumb.png b/tutorials/img/livery-paths/007-thumb.png new file mode 100644 index 0000000..21f4f12 Binary files /dev/null and b/tutorials/img/livery-paths/007-thumb.png differ diff --git a/tutorials/img/livery-paths/007.png b/tutorials/img/livery-paths/007.png new file mode 100644 index 0000000..5850d9d Binary files /dev/null and b/tutorials/img/livery-paths/007.png differ diff --git a/whitelist.txt b/whitelist.txt new file mode 100644 index 0000000..e69de29