New pages

Jump to navigation Jump to search
New pages
Hide registered users | Hide bots | Show redirects
(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)
  • 18:06, 16 February 2023Create a secure connection between nodes (hist | edit) ‎[1,957 bytes]EA3CV (talk | contribs) (Created page with "In order to avoid possible impersonation, it is necessary that connections between neighbouring nodes are made with authentication. The steps to follow are 1. Register node 2. Assign password to the node 3. Set node type Although it is not necessary for both nodes to have authentication enabled, it is desirable. <b>The following is an example of how it is implemented at one endpoint</b> <b>Scenario</b> Node-A: <b>XX0XX-2</b> Node-B: <b>ZZ8ZZ-...")
  • 09:24, 16 February 2023List of nodes for mobile use (hist | edit) ‎[1,096 bytes]EA3CV (talk | contribs) (Created page with "Displays a list of connected nodes reporting: Type of NODE And the duration of the connection This command has been created to be used from a mobile app. It is possible to use it from a terminal or from console. The script is called <b>mnode.pl</b> Using the sysop user, it has to be copied to: /spider/local_cmd To run it use <b>mnode</b> or <b>mn</b> The output would look something like this example: <pre> List of connected Nodes: Callsign Type Con...")
  • 08:57, 16 February 2023List of users for mobile use (hist | edit) ‎[1,411 bytes]EA3CV (talk | contribs) (Created page with "Shows a list of users connected to the node reporting: If the user is registered with an <b>R</b> Type of USER which can be either <b>EXT</b> or <b>LOCL</b> And the duration of the session. This command has been created to be used from a mobile app. It is possible to use it from a terminal or from console. The script is called <b>muser.pl</b> Using the sysop user, it has to be copied to: /spider/local_cmd To run it use <b>muser</b> or <b>mu</b> The output woul...")
  • 14:57, 15 February 2023Restoring the user DB (Mojo branch) (hist | edit) ‎[337 bytes]EA3CV (talk | contribs) (Created page with "From the command line as <b>sysop</b> user: Stopped service <pre> sudo service dxspider stop </pre> Change to the directory that contains the user backup: <b>user_json</b> <pre> cd /spider/local_data </pre> Run regeneration of <b>users.v3j</b> <pre> perl user_json </pre> Start cluster service <pre> sudo service dxspider start </pre>")
  • 18:24, 14 February 2023RBN.mojo (hist | edit) ‎[15,596 bytes]EA3CV (talk | contribs) (Created page with "IF YOU ARE ON THE MASTER BRANCH, STOP (I REPEAT) STOP READING THIS DOCUMENT AND READ UPGRADE.mojo FIRST. If you are not on an existing 'mojo' branch, or you have a build less than 260, please stop reading as well and read UPGRADE.mojo (in the section about installing packages), as you need to install some extra packages before restarting the new version of the code. If in doubt try installing the packages again as this will either confirm that all is already done or wi...")
  • 18:10, 14 February 2023UPDATE.mojo (hist | edit) ‎[8,534 bytes]EA3CV (talk | contribs) (Created page with "There are the notes for upgrading to the mojo branch. PLEASE NOTE THERE HAVE BEEN CHANGES FOR all MOJO BRANCH USERS. See APPENDIX(i) at the end of this document. The BIG TICKET ITEM in this branch is that (potentially) '''long lived''' commands such as sh/dx and commands that poll external internet resources now don't halt the flow of data through the node. I am also using a modern, event driven, web socket "manager" called Mojolicious which is considerably more efficie...")
  • 16:16, 14 February 2023Configure Node with more than one local IP (Mojo branch) (hist | edit) ‎[1,708 bytes]EA3CV (talk | contribs) (Created page with "Add the variable '''@main::localhost_names''' to allow other IP addresses to be treated in the same way as localhost in '''Configure node with Dynamic IP (Mojo branch)'''. You must include ALL the normal localhost names + any other interface names that you might want to include: <pre> set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.1.30 172.16.0.20) </pre> using the qw() construction is easier than: <pre> set/var @main::localhost_names ('127.0.0.1', '::1', '19...")
  • 16:11, 14 February 2023Configure node with Dynamic IP (Mojo branch) (hist | edit) ‎[1,046 bytes]EA3CV (talk | contribs) (Created page with "Introduce aliasing for localhost in DX Spots and outgoing PC92 A records on login. There are two variables which can be set with the alias to use: <pre> $main::localhost_alias_ipv4 $main::localhost_alias_ipv6 </pre> These can be set in the '''/spider/scripts/startup''' <pre> set/var $main::localhost_alias_ipv4 = "your_IP" </pre> but this is only necessary if the node has more than one interface, virtual hosts or Dynamic IP. You can check what your IP is with the foll...")
  • 18:45, 9 February 2023Node configuration for user access (hist | edit) ‎[4,789 bytes]EA3CV (talk | contribs) (This is a beta version to be reviewed) originally created as "NODE CONFIGURATION FOR USER ACCESS"
  • 08:22, 1 February 2023CVS (hist | edit) ‎[7,024 bytes]G0vgs (talk | contribs) (Created page with "==CVS== ===CVS from a Linux platform=== CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your DXSpider installation to the latest sources by using a few simple commands. A graphical interface to CVS for Windows is explained in the next section. Please be aware that if you update your system using CVS, it is possible that you could be running code that is very beta and not fully test...")
  • 08:21, 1 February 2023Security (hist | edit) ‎[2,558 bytes]G0vgs (talk | contribs) (Created page with "==Security== From version 1.49 DXSpider has some additional security features. These are not by any means meant to be exhaustive, however they do afford some security against piracy. These two new features can be used independently of each other or in concert to tighten the security. ===Registration=== The basic principle of registration is simple. If a user is not registered by the sysop, then they have read-only access to the cluster. The only thing they can act...")
  • 08:21, 1 February 2023Web based statistics (hist | edit) ‎[2,957 bytes]G0vgs (talk | contribs) (Created page with "==Web based statistics== ===Generic installation=== From version 1.50, you can use the freeware software MRTG to produce really nice graphical statistics on your web site. For an example try http://www.gb7mbc.net/mrtg/stats.html. The following should help you get it all working. First you need to download the latest version of MRTG from http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need the following files.. libpng-1.0.14.tar.gz zlib-1.1.4.tar....")
  • 08:20, 1 February 2023Java Web applet (hist | edit) ‎[2,607 bytes]G0vgs (talk | contribs) (Created page with "==Java Web applet== In the spider tree will be a directory spider-web. This is a neat little java web applet that can be run from a website. The applet must run on the same machine as the cluster. The included README file is shown below. I should comment here that the applet is precompiled, that is, ready to go. It was compiled using JDK1.3.1. If your version is earlier than this then it may not work. Should that be the case you need to recompile or update your J...")
  • 08:19, 1 February 2023Information, files and useful programs (hist | edit) ‎[10,260 bytes]G0vgs (talk | contribs) (Created page with "==Information, files and useful programs== ===MOTD=== One of the more important things a cluster sysop needs to do is to get information to his users. The simplest way to do this is to have a banner that is sent to the user on login. This is know as a "message of the day" or "motd". To set this up, simply create a file in /spider/data called motd and edit it to say whatever you want. It is purely a text file and will be sent automatically to anyone logging in to th...")
  • 08:19, 1 February 2023Databases (hist | edit) ‎[2,902 bytes]G0vgs (talk | contribs) (Created page with "==Databases== Spider allows the creation of local or remote databases. It supports chained databases, allowing several different databases to be scanned with one simple command. Importing of databases is limited at present to the standard AK1A databases such as OBLAST and the DB0SDX QSL database but will expand with time. ===Creating databases=== Creating a database could not be more simple. All the commands are sent from the cluster prompt as the sysop user. To c...")
  • 08:16, 1 February 2023Scripts (hist | edit) ‎[2,451 bytes]G0vgs (talk | contribs) (Created page with "==Scripts== From 1.48 onwards it will become increasingly possible to control DXSpider's operation with scripts of various kinds. The directory /spider/scripts is where it all happens and is used for several things. Firstly it contains a file called startup that can be used to call in any changes to the cluster from the default settings on startup. This script is executed immediately after all initialisation of the node is done but before any connections are possible...")
  • 08:15, 1 February 2023Other filters (hist | edit) ‎[2,764 bytes]G0vgs (talk | contribs) (Created page with "==Other Filters== ==Filtering Mail== In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The original looks something like this .... # the list of regexes for messages that we won't store having # received them (bear in mind that we must receive them fully before # we can bin them) The format of each line is as follows # type source pattern # P/B/F T/F/O/S...")
  • 08:14, 1 February 2023Routing and Filtering (hist | edit) ‎[18,500 bytes]G0vgs (talk | contribs) (Created page with "==Introduction== From DXSpider version 1.48, major changes were introduced to the way node connections are treated. This is part of an ongoing process to remove problems with loops and to enable talk and other functions to propagate across the whole of the worldwide cluster network. In fact, in a Spider network, it would be useful, perhaps even necessary to have loops. This would give real resilience to the network, meaning that if a link dropped, the information flo...")
  • 08:14, 1 February 2023DXSpider Administration Manual (hist | edit) ‎[2,960 bytes]G0vgs (talk | contribs) (Created page with "#Authors and Contributors #Routing and Filtering ##Introduction ##Route filters ##The node_default filter ##General route filtering ##General filter rules ##Types of filter ##Routing_and_Filtering...")
  • 08:08, 29 January 2023DXSpider Configuration Manual (hist | edit) ‎[57 bytes]G0vgs (talk | contribs) (Created page with "This is a placeholder for the new configuration manual...")
  • 15:45, 27 January 2023Ubuntu 22.04 (hist | edit) ‎[6,412 bytes]EI6IZ (talk | contribs) (Created page with "=== Installing dxspider 'mojo' branch on Ubuntu 22.04 === ==== Prerequisites ==== A stock install of Ubuntu server edition, install the standard version, not the light version. The default settings are fine and no extra packages are required at install time. as part of the standard install you will be asked to create a user account on the system, choose strong passwords. This is the account that you will use to manage the Ubuntu server and will have sudo privileges....")
  • 09:51, 27 January 2023DXSpider Installation Manual (New) (hist | edit) ‎[181 bytes]G0vgs (talk | contribs) (Created page with "This page is a work in progress and will be the new Installation Manual")
  • 19:02, 24 January 2023Translations (hist | edit) ‎[66,633 bytes]G0vgs (talk | contribs) (Created page with " The DXSpider Benutzer-Handbuch v1.51 Ian Maude, G0VGS, (g0vgs@gb7mbc.net) February 2003 revision 0.2 uebersetzt im April 2003 (dj2ang/dh0sp), korrekturgelesen und aktualisiert auf April 2003, rev. 0.5 im Juli 2003 (dl3sbb) aktualisiert auf Stand Juni 2004 - Rev. 1.0 im Juli 2004 (dl3sbb) Eine umfassendes Handbuch fuer Benutzer des "DXSpider" DXCluster Programmes ------------------------------------------------------------------------------- Inhaltsuebersicht 1. E...")
  • 18:59, 24 January 2023Windows (hist | edit) ‎[452 bytes]G0vgs (talk | contribs) (Created page with "==Windows== ===What does "EINPROGRESS" or "EWOULDBLOCK" not exported by Errno.pm mean?=== These are messages put out by starting cluster.pl under Windows with certain releases of Activestate perl. The messages are warnings and can be safely ignored. They happen because Unix systems have these error condition names as synonyms for another error. Windows does not have them and so it complains about it on startup. The warnings are entirely benign.")
  • 18:58, 24 January 2023Administration (hist | edit) ‎[6,622 bytes]G0vgs (talk | contribs) (Created page with "==Administration== ===How can I get Spider to restart automatically if it crashes?=== Put this line into /etc/inittab .. DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7 Run telinit q as root. Spider will restart so be aware. However, any time you reboot, cluster.pl will start in tty7 and if it crashes, it should restart ok. ===How can I monitor traffic to and from a node or user?=== There are 2 ways to achieve this. You can...")
  • 18:58, 24 January 2023Installation (hist | edit) ‎[1,639 bytes]G0vgs (talk | contribs) (Created page with "==Installation== ===Where do I get DXSpider=== All things Spider can be found at http://www.dxcluster.org and the actual program and patches can be found in the download area. Linux users can download a tarball ([http://www.dxcluster.org/download/CVSlatest.tgz CVSlatest.tgz]) and Windows users can download a zip file ([http://www.dxcluster.org/download/CVSlatest.zip CVSlatest.zip]) ===How do I use the patches=== Patching is done in the standard linux way ... zcat...")
  • 18:52, 24 January 2023DXSpider Command Reference (hist | edit) ‎[55,911 bytes]G0vgs (talk | contribs) (Created page with "==ACCEPT== *accept - Set a filter to accept something There are 2 types of filter, accept and reject. See HELP FILTERING for more info. ===accept/announce=== *accept/announce [0-9] <pattern> Set an 'accept' filter line for announce Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters w...")
  • 18:49, 24 January 2023DXSpider FAQ (hist | edit) ‎[2,393 bytes]G0vgs (talk | contribs) (Created page with "#Installation ##Where do I get DXSpider? ##How do I use the patches? ##If I use a tarball to overwrite my installation, what happens to my configuration? ##Installation#I am running RedHat 5.2 and I am getting strange errors, what is wrong?|I am running RedHat 5.2 and I am getting st...")
  • 18:49, 24 January 2023Contacts (hist | edit) ‎[431 bytes]G0vgs (talk | contribs) (Created page with "==Contacts== This Primer is a work in progress. Additional features and filters are added from time to time by Dirk Koopman, G1TLH, the developer behind DXSpider. So periodic revisions will be made to this document. If you have any questions, comments, or suggestions relative to this primer on spot filtering, please contact, Jim Samuels, W3BG jimsam@comcast.net or Dave Hawes, N3RD (W3FRC Cluster SYSOP) dave.n3rd@comcast.net")
  • 18:48, 24 January 2023Some Practice Examples (hist | edit) ‎[2,720 bytes]G0vgs (talk | contribs) (Created page with "=Some Practice Examples= The proceeding sections have discussed the basics of DXSpider filters. The following are some examples utilizing basic filters and some not so basic combination filters. Let's say you don't want to see any of those 6m, 2m, or 220 spots. reject/spot 0 on uhf As a good stand alone contest filter ... accept/spot on contesthf/<mode> where mode is either CW, SSB, or RTTY '''Note:''' since a slot number is not included slot 1 is assumed. It's...")
  • 18:48, 24 January 2023Clear filters (hist | edit) ‎[651 bytes]G0vgs (talk | contribs) (Created page with "=Clear filters= A clear filter line will delete the slot number specified or all slots and consequently all filters that have been created by a user. Syntax: clear/spots [0-9] or clear/spots all Example ... This will clear any or both accept and reject spot filters in slot 2. clear/spots 2 This will clear each and every user spot filter - it will clear out all filters in all slots. clear/spots all '''Note''' - if you just want to replace a spot filter, ent...")
  • 18:47, 24 January 2023Accept filters (hist | edit) ‎[7,405 bytes]G0vgs (talk | contribs) (Created page with "=Accept filters= An accept filter line means that if a spot matches pass it on to the user, send it down the line to the next rule or to the user, and trash, dump, all other spots that do not match to the next filter line. Syntax: accept/spots [0-9] <pattern> Any of the following patterns may be used in this line ... freq <range> on <range> info <string> call <prefixes> call_dxcc <numbers> call_itu <numbers> call_zone <numbers> call_state <state2-letter abb...")
  • 18:47, 24 January 2023Reject filters (hist | edit) ‎[9,921 bytes]G0vgs (talk | contribs) (Created page with "=Reject filters= A reject filter line means that if a spot matches, send it to the trash, dump it, do not send it down the line to the next rule or to the user, but pass-on all other spots that do not match. Syntax: reject/spots [0-9] <pattern> Any of the following patterns may be used in this line ... freq <range> on <range> info <string> call <prefixes> call_dxcc <numbers> call_itu <numbers> call_zone <numbers> call_state <state 2-letter abbreviations> b...")
  • 18:46, 24 January 2023Types of spot filters used in DXSpider (hist | edit) ‎[6,159 bytes]G0vgs (talk | contribs) (Created page with "==Types of spot filters used in DXSpider== Basic filter types are "accept", "reject", and "clear" where the following applies ... *Reject filters - any spots that match will be dumped, all others passed on. *Accept filters - any spots that match are passed on, all others are dumped. *Clear filters - the filter slot(s) referenced will be cleared from the filter repository For the most part we will use only reject and accept filters. These are the main filter types. Ba...")
  • 18:46, 24 January 2023Configuring spot filters (hist | edit) ‎[1,868 bytes]G0vgs (talk | contribs) (Created page with "==What is a spot filter== A spot filter is one rule (a one line spot filter) or multiple rules (multiple line spot filters) that a user can setup within DXSpider to control which specific spot(s) are received at the shack console. These configurable filters/rules reside on the DXSpider node and are stored along with the user's other information. Filters can be likened to a car wash . . . . . like cars, information goes in one end dirty, gets washed and comes out the oth...")
  • 18:46, 24 January 2023Foreword (hist | edit) ‎[609 bytes]G0vgs (talk | contribs) (Created page with "While attempting to learn how DXSpider filters work, I found that I had to glean bits and pieces of information from the DXSpider User Manual and Administrators Guide as well as various posted messages, help files and the program and data-base files themselves. Therefore, this is by no means an original work. I have used and in some cases copied from some of these sources. What I have tried to accomplish is to gather this scattered information, put it in one spot (please...")
  • 18:45, 24 January 2023Introduction (hist | edit) ‎[152 bytes]G0vgs (talk | contribs) (Created page with "The original PacketCluster software written in the mid-80s by Dick Newell, AK1A. DXSpider is a modern replacement and is written by Dirk Koopman, G1TLH.")
  • 18:44, 24 January 2023DXSpider Filtering Manual (hist | edit) ‎[2,973 bytes]G0vgs (talk | contribs) (Created page with "The original PacketCluster software written in the mid-80s by Dick Newell, AK1A. DXSpider is a modern replacement and is written by Dirk Koopman, G1TLH.")
  • 18:42, 24 January 2023The crontab file (hist | edit) ‎[910 bytes]G0vgs (talk | contribs) (Created page with "==General Information== The following relates to all versions of DXSpider and is not platform related. ===The crontab file=== Login as 'sysop' and create a file in /spider/local_cmd called crontab. Edit it with your favourite editor and add a line like this (I have included a comment) # check every 10 minutes to see if gb7xxx is connected and if not # start a connect job going 0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx') The callsi...")
  • 18:41, 24 January 2023Installing the software (hist | edit) ‎[7,271 bytes]G0vgs (talk | contribs) (Created page with "==Installing the software== At this point you will need to create 2 additional directories under "C:\Spider." Make directories "C:\spider\local" and "C:\spider\local_cmd". If "C:\spider" is missing, go back and figure out why, because it shouldn't be. Now create your own local copy of the DXVars.pm file by:- copy c:\spider\perl\DXVars.pm.issue c:\spider\local\DXVars.pm Now you'll need to edit this file using a text editor like Notepad. If nothing else, you can si...")
  • 18:41, 24 January 2023Microsoft Windows Installation (hist | edit) ‎[5,762 bytes]G0vgs (talk | contribs) (Created page with "==Microsoft Windows Installation== ===Introduction=== IMPORTANT: What you'll be left with once you've followed these instructions is (hopefully) a working DX Spider v1.55 system that is capable of accepting or originating "internet" connections, plus inbound and outbound AX.25 and TCP/IP radio connections. Whatever, this document is intended to get you started with DX Spider in a Microsoft Windows (TM) environment. It's not intended to teach you anything other than h...")
  • 18:40, 24 January 2023Configuration (hist | edit) ‎[16,069 bytes]G0vgs (talk | contribs) (Created page with "==Configuration== ===Allowing ax25 connects from users=== This is dealt with in the previous section ===Setting up telnet connects (from 1.47 onwards)=== From version 1.47 you can choose to allow the perl cluster.pl program to allow connections directly (i.e. not via the /spider/src/client interface program). If you are using Windows then this is the only method available of allowing incoming telnet connections. to make the change happen... Having done that, you ne...")
  • 18:40, 24 January 2023Setting up the AX25 Utilities (hist | edit) ‎[13,224 bytes]G0vgs (talk | contribs) (Created page with "==Setting up the AX25 Utilities== The aim of this section is not to fully cover the installation and configuration of all the possible ax25 modules. I will attempt to cover a simple installation and configure 2 serial ports as if they had TNC's on them. I will also show what additional configuration the DXSpider program requires. Please bear in mind that I am basing this section on a RedHat 7.1 distribution, if you are using SuSe or any other distibution then your mi...")
  • 18:39, 24 January 2023Running more than one instance of DXSpider (hist | edit) ‎[2,132 bytes]G0vgs (talk | contribs) (Created page with "Sometimes you may need to run more than one instance of DXSpider on the same machine. The information below should help you achieve that. Although you don't need to create a new user it makes some things slightly easier. So. * create a new user (say sysop2) * login (or su or sudo bash) to root * cd ~sysop2 * mkdir spider * cd /spider * cp -a * ~sysop2/spider * cd ~sysop2 * chown -R sysop2:sysop2 spider * vi /etc/inittab * copy the line: sp:2345:respawn:su -c "perl...")
  • 18:39, 24 January 2023Centos6 (hist | edit) ‎[9,293 bytes]G0vgs (talk | contribs) (Created page with "== Introduction == Centos is a community rebuild of Redhat enterprise linux (RHEL) and the instructions given here will also work for other modern redhat based linux distributions such as RHEL,Scientific Linux, Fedora Linux Centos is an excellent choice of linux distribution to run DXSpider on.  RHEL (& by extension Centos) is supported for ten years from it's release date, the Centos 6.x series will be supported until 2020. Installing Dxspider on centos version 6...")
  • 18:38, 24 January 2023Linux quick installation guide (hist | edit) ‎[1,691 bytes]G0vgs (talk | contribs) (Created page with "==Linux quick installation guide== This section is designed for experienced Spider sysops who want to install Spider from scratch. It is simply a check list of things that need to be done without any explanations. The name in brackets at the end of each line is the user that should be doing that process. *Login as root *Get the additional CPAN modules and install them (root) *Create the "sysop" user and set a password (root) *Put the Spider tarball in sysop and...")
  • 18:38, 24 January 2023Linux Installation (hist | edit) ‎[5,800 bytes]G0vgs (talk | contribs) (Created page with "==Introduction== This section describes the installation of the mojo branch of DXSpider on a Debian based Distribution such as Ubuntu. ==Preparation== I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it. I am assuming version 1.50 for this section but of course you would use the latest version. Login as root and create a user to run the cluster under. UNDER NO CIRCUMSTANCES USE ROOT AS THIS USER!....")
  • 18:38, 24 January 2023Authors and Contributors (hist | edit) ‎[733 bytes]G0vgs (talk | contribs) (Created page with "DXSpider was written from scratch and almost entirely by Dirk Koopman, G1TLH. The documentation was written, amended and appended to by G1TLH, G0VGS, G0RDI, N7XY, K1XX and EI6IZ. This wiki, based on the documentation distributed with DXSpider, was created, is hosted by and largely maintained by G0VGS. The filtering primer was written by WB3G and N3RD The Slogan page is maintained by HA5DI If you would like to help update and improve the DXSpider wiki project, please...")
  • 18:37, 24 January 2023DXSpider Installation Manual (hist | edit) ‎[3,010 bytes]G0vgs (talk | contribs) (Created page with "#Authors and Contributors *Installation under the Linux operating system #Linux Installation ##Introduction ##Preparation ##Installing the software ##Setting callsigns etc ##The client program ##Linux_Installation#Starting up for the first time|Starting up f...")
  • 18:36, 24 January 2023Hints, tips and common questions (hist | edit) ‎[1,655 bytes]G0vgs (talk | contribs) (Created page with "==Hints, tips and common questions== '''Q. These commands seem very long! Can I shorten them? ''' Of course you can and the usual abbreviations work. If you are unsure, try it. '''Q. I am not sure if this command is correct. Can I cause any harm if I try it?''' Do not be afraid to try a command to see if it will work, at the worst you will get an error message. If you require any help on a command, just type help followed by the command you want help on. Loo...")
(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)