diff --git a/AUTHORS b/AUTHORS new file mode 100644 index 0000000..ec2057b --- /dev/null +++ b/AUTHORS @@ -0,0 +1,58 @@ + + + Developers and Contributors + _________________________________________________________________ + + Here we attempt to list most of the Xastir developers and contributors + who have devoted large amounts of time to making Xastir one of the best + APRS(tm) clients ever. Unfortunately we can't devote much time to + keeping this list current or adding new contributors. + + Xastir was originally written by Frank Giannandrea, KC2GJS (was KC0DGE). + + APRS(tm) is a Trademark of Bob Bruninga + + Developers and Contributors (in alphabetical order): + + DK7IN Rolf Bleher + HI8GN Jose R Marte A + IK0YUP Alessandro Frigeri + K2DLS Dan Srebnick + KA6HLD Jerry Dunmire + KA9KIM Mike Sims + KB3EGH Derrick Brashear + KB3EHW Reuven Gevaryahu (our resident docs guy!) + KC2ELS Jack Twilley + KD5AMB Mark Grennan + KD6VPE Jim Sevilla + KD6ZWR Chris Bell + KE4NFJ Gerald Stueve (K4INT) + KG4IJB Charles Byam + KM5VY Tom Russo + N0VH Jim Chandler + N2YGK Alan Crosswell + N3NYN Michael G Petry + N7IPB Ken Koster + N7TAP Olivier Calle + N8YSZ Dan Brown + PE1DNN Henk de Groot + VE3UNW Richard Hagemyer + VE6LFM Lloyd Miller + WE7U Curt Mills + + SmartBeaconing(tm) was invented by Tony Arnerich (KD7TA) and Steve + Bragg (KA9MVA) for the HamHUD project. They offer the algorithm to + other authors as long as proper credit is given and the term + SmartBeaconing(tm) is used to describe it. So be it. Thanks Tony + and Steve! + + Thanks go to all the people who have made individual contributions to + the Xastir project by sending bug-reports, patches, or who have + otherwise supported the project. There are too many to list. + + If you think that you are missing from this list contact the Xastir + Development Team at . + _________________________________________________________________ + + Copyright (C) 2000-2018 The Xastir Group + diff --git a/COPYING b/COPYING new file mode 100644 index 0000000..60549be --- /dev/null +++ b/COPYING @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/README.GIT b/README.GIT new file mode 100644 index 0000000..f42e3ff --- /dev/null +++ b/README.GIT @@ -0,0 +1,303 @@ +Git Instructions: +----------------- + + For those who think git might be a bit too complicated to deal with, + here are (I think) the minimal commands. See the "SUDO" section in + README.sudo for ideas to make updating Xastir even simpler. + + +USERS: +------ + + Initial Copy (Git Clone): + ------------------------- + + 0) Make sure git is installed on your system. + + 1) Run + git config --global user.name "Your Name" user.email "Your@email.address" + + The above is not strictly necessary, but if you ever try to make changes + to Xastir and get them integrated with the project it is important. + + NOTE: If you already have a different git global config, you can create + a local config for a particular repo by going into that repo and doing: + git config --local user.name "Your Name" user.email "Your@email.address" + + Check the config by: + git config --local -l + git config --global -l + git config -l # Doesn't differentiate between global and local though! + + 2) Go to to access the project page. + There you will find the URL of the git repository, just to the + right of a button that says "HTTPS". Copy this URL to your clipboard. + + (At the time of this writing, the URL was + ) + + 3) Open a shell, navigate to a directory where you want to store + the Xastir source code, and enter this command: + + git clone https://github.com/Xastir/Xastir.git + + This will create a clone of the Xastir git repository in an + "Xastir" subdirectory of the current directory. + + All done! You now have the latest development sources on your computer. + Not only that, you have a complete copy of the entire project history + and access to all prior releases. + + + Updating Your Copy: + ------------------- + + cd Xastir + git pull # Update your local repo (May be dangerous for developers) + ./bootstrap.sh + mkdir -p build # Build in a separate directory + cd build + ../configure + (make clean;make -j3 2>&1) | tee make.log + sudo make install # "make install-strip" can be used after the first + # time: It removes debugging info from executable + sudo chmod 4555 /usr/local/bin/xastir # Only needed if using kernel AX.25 + xastir & # Start it up! + + Note that you'll need autoconf 2.53 or newer and automake 1.6.3 or newer + in order to run the "./bootstrap.sh" script. + + -or- + + Bypass all of the commands above and just type: + cd Xastir + ./update-xastir + + +DEVELOPERS: +----------- + + Initial Checkout: + ----------------- + + HTTPS Method: + git clone https://github.com/Xastir/Xastir + + -or- + + SSH Method. Add keys to GitHub and then: + + git clone git@github.com:Xastir/Xastir + + Note that using the SSH method means that you won't have to answer the + popups for user/password each time you do anything with the remote repo, + although you will have to enter a passphrase if you added a passphrase to + your SSH key. The SSH method is highly recommended for active developers! + + + Normal Development Flow: + ------------------------ + + A pull before committing can be dangerous, if there are substantial + conflicts between your work and others (not very likely with Xastir, but + definitely likely in bigger projects). It is much better to do a fetch + (which pulls down changes from the remote but DOESN'T merge them into your + tracking branch), then look at what changed upstream, and then either a + merge, rebase, stash/pop, or something else depending on the level of + conflict you see. See README.GIT. + + Doing a pull before starting your own work is reasonable, but if someone + pushes while you're working (again, not very likely with Xastir), you can + still wind up with really ugly history, with weird merge commits and + undesired branching. + + On the other hand, if you replace "git pull" with "git pull --rebase" in + that recipe, with the caveat that sometimes you might have to be more + careful and that you need to understand what you're doing, a lot of the + danger of the simple git pull can be avoided. + + We will often be working on a branch for development, then merging that + branch with the trunk when that feature or bug-fix is ready for prime-time. + + Commit your work to your LOCAL repo: + + - First add all desired changes to the staging area: + git add ... + + - Then commit your staged changes to your local repo + + git commit + + Push your local repo changes up to GitHub when you are ready to + publish them: + + git push + + + Important: Git Commit Message Format + ------------------------------------ + + Git commit messages need to be in a certain format to make the best use + of the "git log" commands. In particular the first line needs to be 50 + chars or less, then a BLANK LINE, then a detailed commit message. See + this link for more info: + + http://chris.beams.io/posts/git-commit/ + + + Checking Out A Branch: + ---------------------- + + All branches associated with the Xastir project are contained in the clone + you made earlier. You can switch your current working directory to + one of those branches easily: + + cd Xastir + git fetch (this updates your local repo copy from github, but doesn't + merge changes into your working tree) + git checkout (this switches all the files in your working + tree to match those in the branch) + git merge (This makes sure that all the changes that + may have happened upstream on that branch + get into your copy) + + You do not have to do this in a new directory --- so long as + you haven't changed any files in the source tree, git checkout + automatically swaps out all files it knows about with versions from the + branch. + + If you really want to keep more than one branch's code around to work on, + you can do that if you have git version 2.5 or later with the following + commands: + + cd Xastir + git worktree add + + This will create a new directory tree called with the named + branch checked out into it. + + In early 2018, there is only one active branch, the master branch, + and we will be performing releases by creating release branches. + + There are many more git commands and options. Many of them are more of + use to the developers. Some of those are listed below. The above should + be enough for most people to keep their copies in sync with the latest git + development sources. + + + If Using Multiple GitHub Accounts: + ---------------------------------- + + You may have trouble getting your commits attributed to the correct GitHub + login. GitHub uses the username/email in your git config settings for + attribution. If it is wrong, you may have to do some of the below in order + to set a LOCAL username and email for the one repository. + + The user.name and user.email are pulled from the global git config, but a + local git config inside each repo will override those settings. + + Go to root of checked-out repo and set local user.name and user.email for + this repo: + + git config user.name + git config user.email + git config -l # Shows both local and global settings, hard to tell which is which + git config --global # Shows global settings + git config --local -l # Shows local repo configs, so should show new settings + + Another method (but more error-prone) of editing local/global git config is: + + git config edit # Edit local config + git config --global edit # Edit global config + + If new commits still aren't using the right email, make sure you have not + set GIT_COMMITTER_EMAIL or GIT_AUTHOR_EMAIL environment variables. + + + More Info: + ---------- + + Make sure you know how git works. Read https://git-scm.com/book/en/v2 + + If you are very familiar with CVS, get used to working differently, because + git is different. + + Read and understand http://chris.beams.io/posts/git-commit/ + + Read http://justinhileman.info/article/changing-history/ + + Read http://think-like-a-git.net/ + + Read "Visual Git Cheat Sheet" at http://ndpsoftware.com/git-cheatsheet.html + + Branching and merging in git is very simple, and is documented very well + by all those links. We will not repeat it here. + + If you use SSH, set up your SSH keys on GitHub and do the "git clone" using + the SSH path. This will save you having to put in your password each time + you use the remote repository, although if you added a passphrase to your + SSH key you'll have to enter that each time. + + Useful Git Commands: + -------------------- + + Set up global user/email + git config --global user.name "Your Name" + git config --global user.email "user@domain.com" + + Set up user/email for a local repository + cd /path/repository + git config user.name "Your Name" + git config user.email "user@domain.com" + + Configure Git's editor: + git config --global core.editor /path/to/editor + + Colorizing Git output (set once and forget): + git config --global color.ui auto + + Clone a repo: + git clone http://github.com/Xastir/Xastir + git clone https://github.com/Xastir/Xastir + git clone git@github.com:Xastir/Xastir + + Status of local repo: + git status + + Diff for a file: + git diff + + See all branches, local and remote: + git branch -a + + Visual Git viewer: + gitk (tcl/tk and generic X11 viewer, comes with git) + or + gitg (gnome git viewer) + + Add files to the staging area: + git add + + Commit changes to LOCAL repo: + git commit # If have files in staging area already + git commit # Ignores staging area + + Push local changes to remote repository: + git push + + Update local repo from remote repo + git fetch + + Update local repo and merge remote/local changes in local repo (May be + dangerous for developers with modified code in their working tree): + git pull + + Rebase local changes against latest master branch + git fetch + git rebase master + + +------------------------------------------------------------------------ +Copyright (C) 2000-2018 The Xastir Group + + diff --git a/README.qt b/README.qt new file mode 100644 index 0000000..d508730 --- /dev/null +++ b/README.qt @@ -0,0 +1,177 @@ +LATEST STATUS: +-------------- +The File->Exit and Interface->Interface Control portions work. No other +menu options have been implemented. It will connect to a server and display +raw packets as they come in, but there are no maps, symbols, etc. There's +not any packet decoding either. The networking is both IPv4 and IPv6 +compatible. It compiles/runs fine and should be very cross-platform at +this stage (must be compiled on each one though). + + +INITIAL PREPARATION: +-------------------- +Qt4 development tools are required for compiling -or- GUI design. For SuSE +Linux they are in the "libqt4-devel" RPM package. This includes "qmake", +"uic", and "designer" (Qt4 Designer). + +You'll also need the gcc-c++ compiler installed. For SuSE Linux that's in +the "gcc-c++" package. + +You can do manual builds or builds from within Qt Creator. In general I +describe manual builds here. + + +MANUAL BUILD: +------------- + cd Xastir/src/qt + ./build.sh + + +RUN THE EXECUTABLE: +------------------- + cd build + ./xastir_qt & + + +GENERAL QT4 NOTES: +------------------ +*) Do an out-of-source build to keep the source code directory pristine. + Perform all configure/compile commands from inside a "build" directory: + + mkdir -p build + cd build + +*) Use QT 4 Designer to create the graphical elements. Each + dialog/window gets written out to a separate *.ui file. + + designer & + Open->mainwindow.ui + +*) Manual compile of ".ui" files: Use the "uic" compiler to compile + .ui files to .h files: Note: The "qmake" command below does this + automatically! + + uic -o *.h *.ui + +*) moc -o mydialog.moc mydialog.h + +*) Use "qmake -project" to create the initial .pro file for the + os-independent build system. + +*) Include the .h files in the .cpp files for your C++ program. + +*) Use "qmake" to build the project. + +*) "make" + +Examples: (Generic, not for the Xastir project: + uic -o ui_mydialog.h mydialog.ui + moc -o mydialog.moc mydialog.h + qmake -project + qmake + make + + +Once the project branch has been checked-out, these steps issued +from the command-line should compile it: + + cd Xastir/src/qt + mkdir -p build + cd build + qmake ../xastir-qt.pro + make + + +Remember also that the *best* way to do multiple builds of an +autoconfiscated code (and a qmake-ified code) is do do out-of-source +builds, not in-source builds. Doing so keeps the source tree +unpolluted with build droppings. Thus, + + mkdir ~/builds/xastir-qt -p + cd ~/builds/xastir-qt + qmake ~/src/xastir/qt/xastir-qt.pro + make + +will build the qt stuff, and + + mkdir ~/builds/xastir-motif -p + cd ~/builds/xastir-motif + ~/src/xastir/configure + make + +will build the normal build, and neither will interfere with the +other. + + +libqt4-devel rpm provides these binaries (as well as include files +and others). Those with '*' are the ones we currently use: +* /usr/bin/designer + /usr/bin/lconvert + /usr/bin/linguist + /usr/bin/lrelease + /usr/bin/lupdate +* /usr/bin/moc + /usr/bin/pixeltool + /usr/bin/qdbuscpp2xml + /usr/bin/qdbusxml2cpp + /usr/bin/qdoc3 + /usr/bin/qhelpconverter + /usr/bin/qhelpgenerator +* /usr/bin/qmake + /usr/bin/qt3to4 + /usr/bin/qttracereplay + /usr/bin/qvfb + /usr/bin/rcc +* /usr/bin/uic + /usr/bin/uic3 + + +SPECIFIC NOTES: +--------------- + + +Here's what Qt Creator does when you do a Build->Clean All: +----------------------------------------------------------- +Starting: /usr/bin/make clean -w +make: Entering directory `/home/src/we7u/xastir/xastir-qt' +rm -f moc_xastir.cpp +rm -f ui_mainwindow.h +rm -f main.o mainwindow.o moc_xastir.o +rm -f *~ core *.core +make: Leaving directory `/home/src/we7u/xastir/xastir-qt' +Exited with code 0. + + +Here's a Qt Creator Build->Build All command: +--------------------------------------------- +Configuration unchanged, skipping QMake step. +Starting: /usr/bin/make -w +make: Entering directory `/home/src/we7u/xastir/xastir-qt' +/usr/bin/uic mainwindow.ui -o ui_mainwindow.h +g++ -c -m64 -pipe -g -Wall -W -D_REENTRANT -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include -I. -I. -o main.o main.cpp +g++ -c -m64 -pipe -g -Wall -W -D_REENTRANT -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include -I. -I. -o mainwindow.o mainwindow.cpp +/usr/bin/moc -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include -I. -I. xastir.h -o moc_xastir.cpp +g++ -c -m64 -pipe -g -Wall -W -D_REENTRANT -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include -I. -I. -o moc_xastir.o moc_xastir.cpp +g++ -m64 -o xastir-qt main.o mainwindow.o moc_xastir.o -L/usr/lib64 -lQtGui -L/usr/lib64 -L/usr/X11R6/lib64 -lQtNetwork -lQtCore -lpthread +make: Leaving directory `/home/src/we7u/xastir/xastir-qt' +Exited with code 0. + + +Here's a Qt Creator Build->Run qmake (I must have something misconfigured in my project): +----------------------------------------------------------------------------------------- +Starting: /usr/bin/qmake /home/src/we7u/xastir/xastir-qt/xastir-qt.pro -spec linux-g++-64 -r CONFIG+=debug QMLJSDEBUGGER_PATH=/usr/share/qtcreator/qml/qmljsdebugger +Exited with code 0. + + + + +LINUX: +------ +For Linux: Had to run "qmake;make" on a 32-bit system because all the files +had been created on a 64-bit system. On a 64-bit system just run "make". + + diff --git a/callpass.1 b/callpass.1 new file mode 100644 index 0000000..7e362d2 --- /dev/null +++ b/callpass.1 @@ -0,0 +1,29 @@ +.TH callpass 1 2009-12-22 "The Xastir Group" + +.SH NAME +callpass \- generate Pass-code associated with your callsign for authentication via xastir to APRS(tm) network. + +.SH SYNOPSIS +.B callpass +.I + +.SH DESCRIPTION +Generate passcode for use in xastir authentication to APRS network for traffic delivery to cooperating systems. +.SH EXAMPLES + +callpass nocall + outputs 'Passcode for nocall is 12960' + +.SH NOTES +There is no error or consistency check for callsign. This utility will generate a passcode for any string. +.SH SEE ALSO +xastir help file +.br +.PP +.B APRS[tm] +is a Trademark of Bob Bruninga, his home page is at "http://www.aprs.org/aprs.html" + +.SH COPYING +Copyright (C) 1999,2000 Frank Giannandrea KC2GJS +.br +Copyright (C) 2000-2018 The Xastir Group diff --git a/callpass/AUTHORS b/callpass/AUTHORS new file mode 100644 index 0000000..e69de29 diff --git a/callpass/COPYING b/callpass/COPYING new file mode 100644 index 0000000..94a9ed0 --- /dev/null +++ b/callpass/COPYING @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + To protect your rights, we need to prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. You must make sure that they, too, receive +or can get the source code. And you must show them these terms so they +know their rights. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM +IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF +SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU General Public License does not permit incorporating your program +into proprietary programs. If your program is a subroutine library, you +may consider it more useful to permit linking proprietary applications with +the library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. But first, please read +. diff --git a/callpass/ChangeLog b/callpass/ChangeLog new file mode 100644 index 0000000..e69de29 diff --git a/callpass/INSTALL b/callpass/INSTALL new file mode 100644 index 0000000..007e939 --- /dev/null +++ b/callpass/INSTALL @@ -0,0 +1,370 @@ +Installation Instructions +************************* + +Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation, +Inc. + + Copying and distribution of this file, with or without modification, +are permitted in any medium without royalty provided the copyright +notice and this notice are preserved. This file is offered as-is, +without warranty of any kind. + +Basic Installation +================== + + Briefly, the shell commands `./configure; make; make install' should +configure, build, and install this package. The following +more-detailed instructions are generic; see the `README' file for +instructions specific to this package. Some packages provide this +`INSTALL' file but do not implement all of the features documented +below. The lack of an optional feature in a given package is not +necessarily a bug. More recommendations for GNU packages can be found +in *note Makefile Conventions: (standards)Makefile Conventions. + + The `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation. It uses +those values to create a `Makefile' in each directory of the package. +It may also create one or more `.h' files containing system-dependent +definitions. Finally, it creates a shell script `config.status' that +you can run in the future to recreate the current configuration, and a +file `config.log' containing compiler output (useful mainly for +debugging `configure'). + + It can also use an optional file (typically called `config.cache' +and enabled with `--cache-file=config.cache' or simply `-C') that saves +the results of its tests to speed up reconfiguring. Caching is +disabled by default to prevent problems with accidental use of stale +cache files. + + If you need to do unusual things to compile the package, please try +to figure out how `configure' could check whether to do them, and mail +diffs or instructions to the address given in the `README' so they can +be considered for the next release. If you are using the cache, and at +some point `config.cache' contains results you don't want to keep, you +may remove or edit it. + + The file `configure.ac' (or `configure.in') is used to create +`configure' by a program called `autoconf'. You need `configure.ac' if +you want to change it or regenerate `configure' using a newer version +of `autoconf'. + + The simplest way to compile this package is: + + 1. `cd' to the directory containing the package's source code and type + `./configure' to configure the package for your system. + + Running `configure' might take a while. While running, it prints + some messages telling which features it is checking for. + + 2. Type `make' to compile the package. + + 3. Optionally, type `make check' to run any self-tests that come with + the package, generally using the just-built uninstalled binaries. + + 4. Type `make install' to install the programs and any data files and + documentation. When installing into a prefix owned by root, it is + recommended that the package be configured and built as a regular + user, and only the `make install' phase executed with root + privileges. + + 5. Optionally, type `make installcheck' to repeat any self-tests, but + this time using the binaries in their final installed location. + This target does not install anything. Running this target as a + regular user, particularly if the prior `make install' required + root privileges, verifies that the installation completed + correctly. + + 6. You can remove the program binaries and object files from the + source code directory by typing `make clean'. To also remove the + files that `configure' created (so you can compile the package for + a different kind of computer), type `make distclean'. There is + also a `make maintainer-clean' target, but that is intended mainly + for the package's developers. If you use it, you may have to get + all sorts of other programs in order to regenerate files that came + with the distribution. + + 7. Often, you can also type `make uninstall' to remove the installed + files again. In practice, not all packages have tested that + uninstallation works correctly, even though it is required by the + GNU Coding Standards. + + 8. Some packages, particularly those that use Automake, provide `make + distcheck', which can by used by developers to test that all other + targets like `make install' and `make uninstall' work correctly. + This target is generally not run by end users. + +Compilers and Options +===================== + + Some systems require unusual options for compilation or linking that +the `configure' script does not know about. Run `./configure --help' +for details on some of the pertinent environment variables. + + You can give `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: + + ./configure CC=c99 CFLAGS=-g LIBS=-lposix + + *Note Defining Variables::, for more details. + +Compiling For Multiple Architectures +==================================== + + You can compile the package for more than one kind of computer at the +same time, by placing the object files for each architecture in their +own directory. To do this, you can use GNU `make'. `cd' to the +directory where you want the object files and executables to go and run +the `configure' script. `configure' automatically checks for the +source code in the directory that `configure' is in and in `..'. This +is known as a "VPATH" build. + + With a non-GNU `make', it is safer to compile the package for one +architecture at a time in the source code directory. After you have +installed the package for one architecture, use `make distclean' before +reconfiguring for another architecture. + + On MacOS X 10.5 and later systems, you can create libraries and +executables that work on multiple system types--known as "fat" or +"universal" binaries--by specifying multiple `-arch' options to the +compiler but only a single `-arch' option to the preprocessor. Like +this: + + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CPP="gcc -E" CXXCPP="g++ -E" + + This is not guaranteed to produce working output in all cases, you +may have to build one architecture at a time and combine the results +using the `lipo' tool if you have problems. + +Installation Names +================== + + By default, `make install' installs the package's commands under +`/usr/local/bin', include files under `/usr/local/include', etc. You +can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PREFIX', where PREFIX must be an +absolute file name. + + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +pass the option `--exec-prefix=PREFIX' to `configure', the package uses +PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. + + In addition, if you use an unusual directory layout you can give +options like `--bindir=DIR' to specify different values for particular +kinds of files. Run `configure --help' for a list of the directories +you can set and what kinds of files go in them. In general, the +default for these options is expressed in terms of `${prefix}', so that +specifying just `--prefix' will affect all of the other directory +specifications that were not explicitly provided. + + The most portable way to affect installation locations is to pass the +correct locations to `configure'; however, many packages provide one or +both of the following shortcuts of passing variable assignments to the +`make install' command line to change installation locations without +having to reconfigure or recompile. + + The first method involves providing an override variable for each +affected directory. For example, `make install +prefix=/alternate/directory' will choose an alternate location for all +directory configuration variables that were expressed in terms of +`${prefix}'. Any directories that were specified during `configure', +but not in terms of `${prefix}', must each be overridden at install +time for the entire installation to be relocated. The approach of +makefile variable overrides for each directory variable is required by +the GNU Coding Standards, and ideally causes no recompilation. +However, some platforms have known limitations with the semantics of +shared libraries that end up requiring recompilation when using this +method, particularly noticeable in packages that use GNU Libtool. + + The second method involves providing the `DESTDIR' variable. For +example, `make install DESTDIR=/alternate/directory' will prepend +`/alternate/directory' before all installation names. The approach of +`DESTDIR' overrides is not required by the GNU Coding Standards, and +does not work on platforms that have drive letters. On the other hand, +it does better at avoiding recompilation issues, and works well even +when some directory options were not specified in terms of `${prefix}' +at `configure' time. + +Optional Features +================= + + If the package supports it, you can cause programs to be installed +with an extra prefix or suffix on their names by giving `configure' the +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. + + Some packages pay attention to `--enable-FEATURE' options to +`configure', where FEATURE indicates an optional part of the package. +They may also pay attention to `--with-PACKAGE' options, where PACKAGE +is something like `gnu-as' or `x' (for the X Window System). The +`README' should mention any `--enable-' and `--with-' options that the +package recognizes. + + For packages that use the X Window System, `configure' can usually +find the X include and library files automatically, but if it doesn't, +you can use the `configure' options `--x-includes=DIR' and +`--x-libraries=DIR' to specify their locations. + + Some packages offer the ability to configure how verbose the +execution of `make' will be. For these packages, running `./configure +--enable-silent-rules' sets the default to minimal output, which can be +overridden with `make V=1'; while running `./configure +--disable-silent-rules' sets the default to verbose, which can be +overridden with `make V=0'. + +Particular systems +================== + + On HP-UX, the default C compiler is not ANSI C compatible. If GNU +CC is not installed, it is recommended to use the following options in +order to use an ANSI C compiler: + + ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" + +and if that doesn't work, install pre-built binaries of GCC for HP-UX. + + HP-UX `make' updates targets which have the same time stamps as +their prerequisites, which makes it generally unusable when shipped +generated files such as `configure' are involved. Use GNU `make' +instead. + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot +parse its `' header file. The option `-nodtk' can be used as +a workaround. If GNU CC is not installed, it is therefore recommended +to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" + + On Solaris, don't put `/usr/ucb' early in your `PATH'. This +directory contains several dysfunctional programs; working variants of +these programs are available in `/usr/bin'. So, if you need `/usr/ucb' +in your `PATH', put it _after_ `/usr/bin'. + + On Haiku, software installed for all users goes in `/boot/common', +not `/usr/local'. It is recommended to use the following options: + + ./configure --prefix=/boot/common + +Specifying the System Type +========================== + + There may be some features `configure' cannot figure out +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine type, give it the +`--build=TYPE' option. TYPE can either be a short name for the system +type, such as `sun4', or a canonical name which has the form: + + CPU-COMPANY-SYSTEM + +where SYSTEM can have one of these forms: + + OS + KERNEL-OS + + See the file `config.sub' for the possible values of each field. If +`config.sub' isn't included in this package, then this package doesn't +need to know the machine type. + + If you are _building_ compiler tools for cross-compiling, you should +use the option `--target=TYPE' to select the type of system they will +produce code for. + + If you want to _use_ a cross compiler, that generates code for a +platform different from the build platform, you should specify the +"host" platform (i.e., that on which the generated programs will +eventually be run) with `--host=TYPE'. + +Sharing Defaults +================ + + If you want to set default values for `configure' scripts to share, +you can create a site shell script called `config.site' that gives +default values for variables like `CC', `cache_file', and `prefix'. +`configure' looks for `PREFIX/share/config.site' if it exists, then +`PREFIX/etc/config.site' if it exists. Or, you can set the +`CONFIG_SITE' environment variable to the location of the site script. +A warning: not all `configure' scripts look for a site script. + +Defining Variables +================== + + Variables not defined in a site shell script can be set in the +environment passed to `configure'. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the `configure' command line, using `VAR=value'. For example: + + ./configure CC=/usr/local2/bin/gcc + +causes the specified `gcc' to be used as the C compiler (unless it is +overridden in the site shell script). + +Unfortunately, this technique does not work for `CONFIG_SHELL' due to +an Autoconf limitation. Until the limitation is lifted, you can use +this workaround: + + CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash + +`configure' Invocation +====================== + + `configure' recognizes the following options to control how it +operates. + +`--help' +`-h' + Print a summary of all of the options to `configure', and exit. + +`--help=short' +`--help=recursive' + Print a summary of the options unique to this package's + `configure', and exit. The `short' variant lists options used + only in the top level, while the `recursive' variant lists options + also present in any nested packages. + +`--version' +`-V' + Print the version of Autoconf used to generate the `configure' + script, and exit. + +`--cache-file=FILE' + Enable the cache: use and save the results of the tests in FILE, + traditionally `config.cache'. FILE defaults to `/dev/null' to + disable caching. + +`--config-cache' +`-C' + Alias for `--cache-file=config.cache'. + +`--quiet' +`--silent' +`-q' + Do not print messages saying which checks are being made. To + suppress all normal output, redirect it to `/dev/null' (any error + messages will still be shown). + +`--srcdir=DIR' + Look for the package's source code in directory DIR. Usually + `configure' can determine that directory automatically. + +`--prefix=DIR' + Use DIR as the installation prefix. *note Installation Names:: + for more details, including other options available for fine-tuning + the installation locations. + +`--no-create' +`-n' + Run the configure checks, but stop before creating any output + files. + +`configure' also accepts some other, not widely useful, options. Run +`configure --help' for more details. diff --git a/callpass/Makefile.am b/callpass/Makefile.am new file mode 100644 index 0000000..910678a --- /dev/null +++ b/callpass/Makefile.am @@ -0,0 +1,39 @@ + +# Copyright (C) 2000-2018 The Xastir Group + + +bin_PROGRAMS = callpass + +callpass_SOURCES = callpass.c + +callpass_LINK=$(CC) $(AM_CFLAGS) $(CFLAGS) $(LDFLAGS) -o $@ + +EXTRA_DIST = config.guess config.sub install-sh \ + missing placeholder \ + bootstrap.sh INSTALL callpass.1 \ + COPYING + +MAINTAINERCLEANFILES = configure aclocal.m4 Makefile.in Makefile \ + config.guess config.sub install-sh missing mkinstalldirs \ + xastir.spec xastir-min.spec + +docdir=${prefix}/share/doc/xastir +doc_DATA=ChangeLog \ + COPYING INSTALL + +# It'd be nice to remove the directory and contents at +# "${pkgdatadir}/doc" then install a symlink called "doc" there pointing +# to "${prefix}/share/doc/xastir/". The new location for the +# documentation is FHS compliant. + +install-exec-hook: + -rm -rf $(DESTDIR)${pkgdatadir}/doc + +install-data-hook: + +#mandir=${prefix}/share/man +#man_MANS=callpass.1 + +ChangeLog:: + + diff --git a/callpass/NEWS b/callpass/NEWS new file mode 100644 index 0000000..e69de29 diff --git a/callpass/README b/callpass/README new file mode 100644 index 0000000..e69de29 diff --git a/callpass/bootstrap.sh b/callpass/bootstrap.sh new file mode 100755 index 0000000..1b4be89 --- /dev/null +++ b/callpass/bootstrap.sh @@ -0,0 +1,29 @@ +#!/bin/sh +# +# +# Copyright (C) 2000-2018 The Xastir Group +# +# +# This simple routine will run autostuff in the appropriate +# order to generate the needed configure/makefiles +# + +echo " 5) Removing autom4te.cache directory..." +rm -rf autom4te.cache + +echo " 4) Running aclocal..." +aclocal + +echo " 3) Running autoheader..." +autoheader + +echo " 2) Running autoconf..." +autoconf + +# Cygwin needs these parameters to be separate. +echo " 1) Running automake..." +automake -a -c + +echo "Bootstrap complete." + + diff --git a/callpass/callpass.c b/callpass/callpass.c new file mode 100644 index 0000000..b3bbf58 --- /dev/null +++ b/callpass/callpass.c @@ -0,0 +1,80 @@ +/* + * + * XASTIR, Amateur Station Tracking and Information Reporting + * Copyright (C) 1999,2000 Frank Giannandrea + * Copyright (C) 2000-2018 The Xastir Group + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License + * as published by the Free Software Foundation; either version 2 + * of the License, or (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. + * + * Look at the README for more information on the program. + */ + +#include +#include +#include + +#define kKey 0x73e2 // This is the seed for the key +#define true 1 + + + +static short doHash(char *theCall) { + char rootCall[10]; // need to copy call to remove ssid from parse + char *p1 = rootCall; + short hash; + short i,len; + char *ptr = rootCall; + + while ((*theCall != '-') && (*theCall != '\0')) *p1++ = toupper((int)(*theCall++)); + *p1 = '\0'; + + hash = kKey; // Initialize with the key value + i = 0; + len = (short)strlen(rootCall); + + while (i1) { + + strncpy(temp,argv[1],100); + + temp[99] = '\0'; // Forced termination + + if (strlen(temp)>0) + printf("Passcode for %s is %d\n",temp,doHash(temp)); + + } else + printf("Usage:callpass \n"); + + return(0); +} + diff --git a/callpass/configure.ac b/callpass/configure.ac new file mode 100644 index 0000000..126a9e3 --- /dev/null +++ b/callpass/configure.ac @@ -0,0 +1,188 @@ +# Process this file with autoconf to produce a configure script. +# +# +# Copyright (C) 2000-2018 The Xastir Group + + +######################################################################### +# SET VERSION HERE! +# +# Note that the most standard OSS method of doing numbering is: +# Major.Minor.PatchLevel +# +# If we are only doing patches, change the PATCHLEVEL number. +# If we add new features, change the MINOR number. +# If we feel we've added enough new features or rewritten enough +# code to warrant it, change the MAJOR number. +# +# Also: We adopted the convention of using odd numbers for development +# or development releases, even numbers for STABLE releases. +# +# +# AC_INIT(): +# It should look something like this: ([xastir], [2.0.8], [xastir@xastir.org]) +# The revision number must contain at least one '.' and two digits. +AC_INIT([xastir], [2.1.1], [xastir@xastir.org]) +AM_INIT_AUTOMAKE +######################################################################### + + +AC_PREREQ(2.53) + +AC_CONFIG_SRCDIR([callpass.c]) +#AM_CONFIG_HEADER(config.h) +AC_CONFIG_HEADERS(config.h) +AM_INIT_AUTOMAKE([subdir-objects]) + + +echo "" +echo "Configuring AC_PACKAGE_NAME AC_PACKAGE_VERSION" +echo "" + +# Take out the dots in order to create the TOCALL +AC_DEFINE_UNQUOTED(XASTIR_TOCALL, "`echo AC_PACKAGE_VERSION | sed -e 's/^/APX/' -e 's/\.//g'`", [Defines the version tocall]) + +# Check for host type +AC_CANONICAL_HOST + +# Define _GNU_SOURCE if appropriate +# doesn't work with older (heh) autoconfs +AC_GNU_SOURCE + +# Checks for programs. +AC_PROG_CC +AC_PROG_CPP +AC_PROG_INSTALL +AC_PROG_LN_S +AC_PROG_MAKE_SET +AC_PROG_AWK +AC_PROG_RANLIB +#AC_PROG_YACC + +AM_PROG_CC_C_O + +# add compiler flags +XASTIR_COMPILER_FLAGS + +# Check for binaries + +# JMT - XXX - what is this and why is it relevant? +#AC_DEFINE(_REENTRANT, 1, [Use reentrant code if available.]) +AC_DEFINE_UNQUOTED(STIPPLE, 1, [Legacy stuff, use crowbar and lets keep going]) + +# Checks for libraries. +# +# +# Find the X11 include and library directories. +# + +CPPFLAGS="$CPPFLAGS $X_CFLAGS" +LDFLAGS="$LDFLAGS $X_LIBS" +LIBS="$LIBS $X_PRE_LIBS -lX11 $X_EXTRA_LIBS" + + +# Check for endian +AC_C_BIGENDIAN + + + +# Our old stuff. Doesn't work in all cases. +# Checks for header files. +#AC_CHECK_HEADERS([Xm/Xm.h],MOTIF_INC="yes", AC_MSG_ERROR(*** Cannot find Motif include files: Please install one of Motif/OpenMotif/Lesstif development packages. ***)) + +AC_SUBST(LDFLAGS) +AC_SUBST(LIBS) + + +# +AC_FUNC_ALLOCA +AC_HEADER_DIRENT +AC_HEADER_STDC +AC_HEADER_SYS_WAIT + + +# Remove duplicate entries. Thanks to Paul Lutt, ke7xt, for this! +# +# Don't get rid of dupes on the LIBS line. We may need the same +# "-Llibdir" called out several times, immediately prior to each +# "-llibrary" that needs it. +# +changequote(,) +CFLAGS=`echo "$CFLAGS" | awk '{for(i=1;i<=NF;++i) {if (arg[$i]++ == 0) s = s " " $i} print s}'` +CPPFLAGS=`echo "$CPPFLAGS" | awk '{for(i=1;i<=NF;++i) {if (arg[$i]++ == 0) s = s " " $i} print s}'` +LDFLAGS=`echo "$LDFLAGS" | awk '{for(i=1;i<=NF;++i) {if (arg[$i]++ == 0) s = s " " $i} print s}'` +#LIBS=`echo "$LIBS" | awk '{for(i=1;i<=NF;++i) {if (arg[$i]++ == 0) s = s " " $i} print s}'` +changequote([,]) + + +# +# Remove "-g" CFLAGS/CPPFLAGS entries. Note: This is a _bad_ idea +# as debuggers won't have a symbol table to work from! +# +#changequote(,) +#CFLAGS=`echo "$CFLAGS" | awk '{for(i=1;i<=NF;++i) {if ($i != "-g") s = s " " $i} print s}'` +#CPPFLAGS=`echo "$CPPFLAGS" | awk '{for(i=1;i<=NF;++i) {if ($i != "-g") s = s " " $i} print s}'` +#changequote([,]) + + +# +# Remove extraneous spaces from output variables (asthetic) +# + +CC=`echo $CC | sed -e 's/ */ /g'` +CFLAGS=`echo $CFLAGS | sed -e 's/ */ /g'` +CPPFLAGS=`echo $CPPFLAGS | sed -e 's/ */ /g'` +CXXFLAGS=`echo $CXXFLAGS | sed -e 's/ */ /g'` +LDFLAGS=`echo $LDFLAGS | sed -e 's/ */ /g'` +TESTED_LIBS=`echo $LIBS | sed -e 's/ */ /g'` +LIBS=`echo $LIBS | sed -e 's/ */ /g'` + + + +tmp_path="$ac_default_prefix" +tmp_bin_path="$ac_default_prefix" +if test "x$prefix" != xNONE; then + tmp_path="$prefix" + tmp_bin_path="$prefix" +fi +if test "x$exec_prefix" != xNONE; then + tmp_bin_path="$exec_prefix" +fi +AC_DEFINE_UNQUOTED(XASTIR_PATH, "`echo $tmp_path`", [Path to installed Xastir files.]) +AC_DEFINE_UNQUOTED(XASTIR_BIN_PATH, "`echo $tmp_bin_path`", [Path to installed Xastir binaries.]) + + + +AC_DEFINE_UNQUOTED(XASTIR_INSTALLED_LIBS, "`echo $ILIBS`", [Defines the installed libs]) + + +AC_SUBST(LDFLAGS) +AC_SUBST(LIBS) +#AC_SUBST(CPPFLAGS) +AC_SUBST(X_CFLAGS) +#AC_SUBST(LDFLAGS) +#AC_SUBST(X_PRE_LIBS) +#AC_SUBST(X_LIBS) +#AC_SUBST(X_EXTRA_LIBS) + +AC_CONFIG_FILES([Makefile]) + +AC_OUTPUT + +# Please leave these in as they're very useful for debug when we +# port to new platforms! Leave them commented out unless doing +# debugging on the configure scripts. +# +#echo "" +#echo " LIBS: $LIBS" +#echo " LDFLAGS: $LDFLAGS" +#echo " CFLAGS: $CFLAGS" +#echo " CPPFLAGS: $CPPFLAGS" +#echo " X_LIBS: $X_LIBS" +#echo " X_PRE_LIBS: $X_PRE_LIBS" +#echo "X_EXTRA_LIBS: $X_EXTRA_LIBS" + + +echo "Type 'make' to build (Use 'gmake' instead on some systems)." + + diff --git a/config/tnc-startup.aea b/config/tnc-startup.aea new file mode 100644 index 0000000..f6f15f1 --- /dev/null +++ b/config/tnc-startup.aea @@ -0,0 +1,46 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for AEA TNC's. +# lines that begin with a pound sign are comments. +# +# This has not been tweaked yet to be specific to AEA's. +# Please modify it and send the patches to the mailing lists. +# Thanks. +# +HID on +#CWID off +EXP on +ECHO off +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYAlias WIDE1-1 +# +B E 0 +DIGI on +FLow off +FUll off +HEA off +#LFadd off +#LFSup ON +#AUTOLF off +#MCOM off +MFILTER 0 +MON ON +# +# Important! Only monitor PID 0xf0 packets: +MPROTO OFF +# +#MResp OFF +MRPt on +MSTamp off +MXMit off +NEWmode off +#PACLen 128 +PASSALL off +#SCR 0 +# B E 0 must be set to 0 or both APRS and your TNC will send BCNS +# Which will alternate in everyones L and A lists and fill up +# their logs. Do NOT set B E to anything other than 0 while APRS +# is running. + diff --git a/config/tnc-startup.d700 b/config/tnc-startup.d700 new file mode 100644 index 0000000..c67e853 --- /dev/null +++ b/config/tnc-startup.d700 @@ -0,0 +1,68 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# TNC Init file for KENWOOD D700. Also reported to work with the +# Alinco DR-135TP radio (with the EJ-41U TNC which also uses a Tasco +# TNC just like the Kenwoods). Perhaps works with the Alinco DR-635 +# radio (with the EJ-50U TNC) too. +# +# NOTE: TXD on a D700A is fixed at 500ms (1/2 second) in "APRS" +# mode. In "packet" mode we can change the txd to other values. +# +# +#Don't send CONTROL-C before this line +##META +TC 1 +##Pause for one second +##META +##META +#Put the TNC in packet mode since this is where we want to end up +# Change the 1 to 0 to go to normal radio mode +##META +TNC 2 +# Pause for two seconds +##META +##META +##META +##META +# Enable 4800 baud GPS +# Change to 2 for 9600 baud GPS +# Disable both the META line and the GU line for no change +##META +GU 1 +# Pause for two seconds +##META +##META +##META +##META +#Turn off Terminal Control +##META +TC 0 +# Pause for two seconds just in case +##META +##META +##META +##META +HID off +#CWID off +AWlen 8 +BBSMsgs ON +B E 0 +LOC E 0 +Echo off +FLow off +AUTOLF off +MCOM off +MON ON +MRPt on +PACLen 128 +PASSALL off +HBAUD 1200 +TXDELAY 25 +HEADERLN off +# Delete following lines if without GPS +GBAUD 4800 +GPSTEXT $GPRMC +LTMH OFF +LTM 10 +# diff --git a/config/tnc-startup.d72_d710 b/config/tnc-startup.d72_d710 new file mode 100644 index 0000000..5bb7d13 --- /dev/null +++ b/config/tnc-startup.d72_d710 @@ -0,0 +1,46 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# TNC Init file for KENWOOD TM-D710 or TH-D72 radios. +# Contributed by Kai Günter, LA3QMA. +# +# If using a GPS you must change GBAUD, GPSTEXT, LTMH. +# +# +#Don't send CONTROL-C before this line +##META +#TC 1 +##Pause for one second +##META +##META +#Put the TNC in packet mode since this is where we want to end up +# Change the 1 to 0 to go to normal radio mode +##META +TN 2,0 +# Pause for two seconds +##META +##META +##META +##META +HID off +AWlen 8 +BBSMsgs ON +B E 0 +LOC E 0 +Echo off +FLow off +AUTOLF off +MCOM off +MON ON +MRPt on +PACLen 128 +PASSALL off +HBAUD 1200 +TXDELAY 25 +HEADERLN off +# Delete following lines if without GPS +#GBAUD 4800 +#GPSTEXT $GPRMC +#LTMH OFF +# +# diff --git a/config/tnc-startup.kam b/config/tnc-startup.kam new file mode 100644 index 0000000..85f0286 --- /dev/null +++ b/config/tnc-startup.kam @@ -0,0 +1,42 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for a Kantronics KAM TNC. +# lines that begin with a pound sign are comments. +# Edit this file for your tnc! +# +# Important! Only uncomment if really needed as a fill-in digi: +#myalias WIDE1-1 +# +INTF TERM +#One KAM user reports this command does not exist on his KAM +#txu on +xflow off +MONITOR ON +MSTAMP OFF +HEADERLN OFF +#One KAM user reports this command does not exist on his KAM +#SCREENLN 0 +AUTOLF OFF +LFADD OFF +CD SOFT +MCOM OFF/OFF +MCON OFF +FILT OFF +AUTOCR 0 +BEACON EVERY 0 +BT % +BUDL OFF/OFF +CMS DISC +CONL OFF +CT APRS Network no connected messages supported! +ECHO OFF +FLOW OFF +HID OFF/OFF +#CWID EVERY 0 +MSTAMP OFF +PASSALL OFF +# +# Important! Monitor only PID 0xf0 packets: +PID OFF + diff --git a/config/tnc-startup.kpc2 b/config/tnc-startup.kpc2 new file mode 100644 index 0000000..60464d8 --- /dev/null +++ b/config/tnc-startup.kpc2 @@ -0,0 +1,29 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for Kantronics TNC. +# lines that begin with a pound sign are comments. +# +# +HID off +#CWID every 0 +B E 0 +DIGI on +ECho off +FLow off +FUll off +HEA off +LFadd off +AUTOLF off +MCOM off +MON ON +MResp OFF +MRPt on +MSTamp off +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYAlias WIDE1-1 +# +NEWmode off +SCR 0 +# diff --git a/config/tnc-startup.kpc3 b/config/tnc-startup.kpc3 new file mode 100644 index 0000000..400e7a4 --- /dev/null +++ b/config/tnc-startup.kpc3 @@ -0,0 +1,75 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for Kantronics TNC. +# lines that begin with a pound sign are comments. +# +# This configuration sets up Control-E mode for a KPC-3+ (GPS +# connected to the 2nd serial port). When Xastir is actively +# getting GPS fixes, the TNC beacons only what Xastir sends to it. +# When Xastir stops getting GPS data from the TNC, the TNC will +# revert to dumb-tracker mode and start sending NMEA strings out all +# by itself at a 20-minute rate. If the GPS get disconnected or +# turned off, the dumb-tracker mode will cease to send out beacons. +# This last function is done by the "CLEAR" parameter for the BLT +# commands. +# +# Some people prefer to turn off the GPS but still have the TNC +# beacon their last good GPS position when in dumb-tracker mode. +# To do this, remove the "CLEAR" parameters from the BLT command +# lines. +# + +int terminal + +# Clear out the LT buffers so we don't have old data in there: +LT 1 +LT 2 +LT 3 +LT 4 +# Clear out the buffer regularly to prevent stale data: +BLT 1 00:20:00 CLEAR +BLT 2 00:20:00 CLEAR +BLT 3 00:00:00 +BLT 4 00:00:00 +# Set up the NMEA strings to capture: +GPSHEAD 1 $GPRMC +GPSHEAD 2 $GPGGA +# +GPSPORT 4800 NORMAL CHECKSUM +LGETCHAR $05 +# +HID off +#CWID every 0 +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYAlias WIDE1-1 +# +B E 0 +DIGI on +ECho off +FILT off +FLow off +FUll off +HEA off +LFadd off +LFSup ON +AUTOLF off +MCOM off +MON ON +MResp OFF +MRPt on +MSTamp off +MXMit off +NEWmode off +#PACLen 128 +PASSALL off +# +# Important! Monitor only PID 0xf0 packets: +PID off +# +SCR 0 +# B E 0 must be set to 0 or both APRS and your TNC will send BCNS +# Which will alternate in everyones L and A lists and fill up +# their logs. Do NOT set B E to anything other than 0 while APRS +# is running. diff --git a/config/tnc-startup.null b/config/tnc-startup.null new file mode 100644 index 0000000..e69de29 diff --git a/config/tnc-startup.paccomm b/config/tnc-startup.paccomm new file mode 100644 index 0000000..e36d654 --- /dev/null +++ b/config/tnc-startup.paccomm @@ -0,0 +1,49 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for a Pac-Comm TNC with v5.x firmware. +# Adapted from Kantronics startup file by Kurt Freiberger, WB5BBW + +# lines that begin with a pound sign are comments. + +HID off +#CWID every 0 +MON 0 +ECHO off +#MYCall WB5BBW +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYAlias WIDE1-1 +# +# +# +#MY1Alias LOCAL +#MY2Alias REGION +#MY3Alias WORLD +# +# B E 0 must be set to 0 or both APRS and your TNC will send BCNS +# Which will alternate in everyones L and A lists and fill up +# their logs. Do NOT set B E to anything other than 0 while APRS +# is running. +B E 0 +# This enables DIGI On and DIGI-SWAP,DIGI-NOT-OWN, DIGI-ONCE enabled. +DIGI 7 +FLow off +FUll off +HEA off +LFadd off +AUTOLF off +MCOM off +MFILT $00 +MRPt on +MSTamp off +NEWmode off +PASSALL off +SCR 0 +MON 1 +# +# Important! Monitor only PID 0xf0 packets: +PIDCHECK on +# +# End of tnc-startup.pac +# diff --git a/config/tnc-startup.pico b/config/tnc-startup.pico new file mode 100644 index 0000000..5f56625 --- /dev/null +++ b/config/tnc-startup.pico @@ -0,0 +1,85 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for a dual-port Paccomm PicoPacket TNC. +# lines that begin with a pound sign are comments. + +ECHO off +AUTOLF on +BEACON EVERY 0 +# +# Clear the GPS buffers +LTEXT % +L1TEXT % +L2TEXT % +L3TEXT % +# +# Set up the NMEA strings we wish to capture: +#GPSTEXT % +GPSTEXT $GPRMC +# +#LG1TEXT % +LG1TEXT $GPGGA +# +LG2TEXT % +#LG2TEXT $GPVTG +# +LG3TEXT % +#LG3TEXT $PGRME +# +# Digipeat,callsign substitution, +# no digi of own packets, and digi-once +DIGIPEAT 7 +ELOC 0 +FLOW off +FULLDUP off +GPS off +HEADERLI off +HID off +#CWID every 0 +INTERVAL 0 +LFADD off +LGETCHAR $05 +LOC E 0 +# +MALL ON +MCOM off +MCON on +MFILTER 0 +MONITOR 3 +MRPT on +MSTAMP off +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYALIAS WIDE1-1 +# +#MY1ALIAS SAR +#MY2ALIAS ESAR +#MY3ALIAS ESAR2 +NEWMODE off +NOMODE on +#PACLEN 128 +# +# Only used in KISS mode? +PERSIST 128 +# +PASSALL off +# +# Important! Monitor only PID 0xf0 packets: +PIDCHECK on +# +PMS off +SCREENLN 0 +# +# Only used in KISS mode? +SLOTTIME 15 +# +TXDELAY 30 +XFLOW off +# +# +# BEACON EVERY 0 must be set to 0 or both Xastir and your TNC will send +# beacons which will alternate in everyones lists and fill up their +# logs. Do NOT set BEACON EVERY to anything other than 0 while Xastir +# is running. + diff --git a/config/tnc-startup.sys b/config/tnc-startup.sys new file mode 100644 index 0000000..376442f --- /dev/null +++ b/config/tnc-startup.sys @@ -0,0 +1,55 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for Kantronics TNC. +# lines that begin with a pound sign are comments. + +int terminal + +ECHO off +HID off +#CWID off +#CWID every 0 +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYAlias WIDE1-1 +# +B E 0 +DIGI on +EXP on +Filt off +FLow off +FUll off +HEA off +LFadd off +LFSup on +AUTOLF off +MCOM off +MFILT off +MON on +MResp off +MRPt on +MSTamp off +MXMit off +NEWmode off +#PACLen 128 +PASSALL off +# +# +# Important! Monitor only PID 0xf0 packets: +# *Kantronics* +PID off +# *TAPR2* +MNOAX25 off +# *Paccomm* +PIDCHECK on +# *AEA* +MPROTO OFF +# End of monitor only PID 0xf0 packets section +# +# +SCR 0 +# B E 0 must be set to 0 or both APRS and your TNC will send BCNS +# Which will alternate in everyones L and A lists and fill up +# their logs. Do NOT set B E to anything other than 0 while APRS +# is running. diff --git a/config/tnc-startup.thd7 b/config/tnc-startup.thd7 new file mode 100644 index 0000000..5883939 --- /dev/null +++ b/config/tnc-startup.thd7 @@ -0,0 +1,78 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# TNC Init file for KENWOOD TH-D7 +# +#-------------------------------------------------- +# Note: Terminal Control commands are send without +# CONTROL-C before the lines. +#-------------------------------------------------- +# +#-------------------------------------------------- +# Turn on Terminal Control +# +# This will make the TH-D7 drop out of Packet mode. +# Once out of Packet mode, the TH-D7 will forget +# all old TNC settings and even KISS mode, so we +# can start from a clean situation. +#-------------------------------------------------- +# +##META +TC 1 +# Pause one second +##META +##META +# +#-------------------------------------------------- +# Turn off Terminal Control +# +# This will make the TH-D7 switch to Packet mode. +#-------------------------------------------------- +# +##META +TC 0 +# Pause for two seconds just in case +##META +##META +##META +##META +# +#-------------------------------------------------- +# Initialize the TNC +# +# This will setup the TH-D7 TNC for use with APRS. +#-------------------------------------------------- +# +HID off +#CWID off +AWlen 8 +BBSMsgs ON +B E 0 +LOC E 0 +Echo off +FLow off +AUTOLF off +MCOM off +MON ON +MRPt on +PACLen 128 +PASSALL off +# +# Enable this line ONLY if you're running 9600 baud packet. It +# changes the on-the-air speed from the default 1200 baud. +#HBAUD 9600 +# +TXDELAY 25 +# +#-------------------------------------------------- +# Initialize the GPS +# +# Enable the commands if running with GPS. +# If running without GPS, leave them disabled. +#-------------------------------------------------- +# +#GBAUD 4800 +#GPSTEXT $GPRMC +#LTMH OFF +#LTM 10 +# diff --git a/config/tnc-startup.tnc2 b/config/tnc-startup.tnc2 new file mode 100644 index 0000000..a7034d0 --- /dev/null +++ b/config/tnc-startup.tnc2 @@ -0,0 +1,47 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for a TAPR TNC2 style of TNC. This +# includes many TNC's from TAPR, Paccomm, MFJ, AEA, etc that were +# based on the original TAPR-2 design. + +# lines that begin with a pound sign are comments. + +HID off +#CWID every 0 +MON 0 +ECHO off +#MYCall WB5BBW +# +# Important! Only uncomment if really needed as a fill-in digi: +#MYAlias WIDE1-1 +# +#MY1Alias WIDE +#MY2Alias REGION +#MY3Alias WORLD +# B E 0 must be set to 0 or both APRS and your TNC will send BCNS +# Which will alternate in everyones L and A lists and fill up +# their logs. Do NOT set B E to anything other than 0 while APRS +# is running. +B E 0 +# This enables DIGI On and DIGI-SWAP,DIGI-NOT-OWN, DIGI-ONCE enabled. +DIGI 7 +FLow off +FUll off +HEA off +LFadd off +AUTOLF off +MCOM off +MFILT $00 +MRPt on +MSTamp off +NEWmode off +PASSALL off +SCR 0 +MON 1 +# +# Important! Monitor only PID 0xf0 packets: +PIDCHECK on +# +# End of tnc-startup.tnc2 +# diff --git a/config/tnc-startup.tnc2-ui b/config/tnc-startup.tnc2-ui new file mode 100644 index 0000000..7c8d785 --- /dev/null +++ b/config/tnc-startup.tnc2-ui @@ -0,0 +1,18 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for the TNC2-UI TNC. +# lines that begin with a pound sign are comments. + +HID off +#CWID off +MONITOR OFF +ECHO OFF +LF OFF +BEACON 0 +LTIME 0 +HEADER OFF +MCOM OFF +AXLF OFF +MONITOR ON + diff --git a/config/tnc-stop.d700 b/config/tnc-stop.d700 new file mode 100644 index 0000000..23a6a4a --- /dev/null +++ b/config/tnc-stop.d700 @@ -0,0 +1,47 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +#TNC STOP FILE +# Undo any settings make in tnc-startup.sys +# Edit this file for your tnc! +UNPROTO CQ +AUTOLF ON +ECHO ON +#Don't send CONTROL-C before this line +##META +TC 1 +##Pause for one second +##META +##META +# Turn off AUX port +##META +GU 0 +##META +#Put the TNC in internal mode since this is where we want to end up +# Change the 1 to 0 to go to normal radio mode +##META +TNC 1 +# Pause for two seconds +##META +##META +##META +##META +# Enable 4800 baud GPS +# Change to 2 for 9600 baud GPS +# Disable both the META line and the GU line for no change +##META +GU 1 +# Pause for two seconds +##META +##META +##META +##META +#Turn off Terminal Control +##META +TC 0 +# Pause for two seconds just in case +##META +##META +##META +##META +# diff --git a/config/tnc-stop.d72_d710 b/config/tnc-stop.d72_d710 new file mode 100644 index 0000000..ce14e12 --- /dev/null +++ b/config/tnc-stop.d72_d710 @@ -0,0 +1,38 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# TNC STOP FILE for Kenwood TM-D710 or TH-D72 radios. +# Contributed by Kai Günter, LA3QMA. +# +# Undo any settings make in tnc-startup.sys +# Edit this file for your tnc! +# +# +UNPROTO CQ +AUTOLF ON +ECHO ON +#Don't send CONTROL-C before this line +##META +TC 1 +##Pause for one second +##META +##META +##META +#Put the TNC in internal mode since this is where we want to end up +# Change the 1 to 0 to go to normal radio mode +##META +TN 0,0 +# Pause for two seconds +##META +##META +##META +##META +#Turn off Terminal Control +##META +TC 0 +# Pause for two seconds just in case +##META +##META +##META +##META +# diff --git a/config/tnc-stop.sys b/config/tnc-stop.sys new file mode 100644 index 0000000..b1ce488 --- /dev/null +++ b/config/tnc-stop.sys @@ -0,0 +1,8 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +#TNC STOP FILE +# Undo any settings make in tnc-startup.sys +# Edit this file for your tnc! +UNPROTO CQ +AUTOLF ON diff --git a/config/tnc-stop.thd7 b/config/tnc-stop.thd7 new file mode 100644 index 0000000..c42a2e7 --- /dev/null +++ b/config/tnc-stop.thd7 @@ -0,0 +1,38 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# TNC Stop file for KENWOOD TH-D7 +# +#-------------------------------------------------- +# Note: Terminal Control commands are send without +# CONTROL-C before the lines. +#-------------------------------------------------- +# +#-------------------------------------------------- +# Turn on Terminal Control +# +# This will make the TH-D7 drop out of Packet mode. +# Once out of Packet mode, the TH-D7 will forget +# all TNC settings. No need to restore anything. +#-------------------------------------------------- +# +##META +TC 1 +# Pause one second +##META +##META +# +#-------------------------------------------------- +# Resume standalone APRS use. +# +# GPS en Beacon settings are not changed. Once back +# in APRS mode, the GPS and Beacon are resumed as +# they were. +#-------------------------------------------------- +# +##META +TNC 1 +# Pause one second +##META +##META +# diff --git a/config/tnc-stop.tnc2-ui b/config/tnc-stop.tnc2-ui new file mode 100644 index 0000000..ac25f35 --- /dev/null +++ b/config/tnc-stop.tnc2-ui @@ -0,0 +1,11 @@ +# +# Copyright (C) 2000-2018 The Xastir Group +# +# This is the TNC Startup file for the TNC2-UI TNC. +# lines that begin with a pound sign are comments. + +MONITOR OFF +LF ON +ECHO ON +MONITOR ON +