<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">The only things that are a issue when
radically changing platforms (eg Windows <-> linux or
bigendian <-> littleedian) may be binary compatibility
issues with the databases.<br>
<br>
But the standard way to copy an instance of a node is simply to
zip up the old node's /spider/* and unzip it to your new machine
in the correct place (which in your case means making sure you are
logged in to the sysop user and you have done a successful "mkdir
spider; sudo ln -s ~/spider /" <br>
<br>
After that I would do this:<br>
<br>
1. On the windows machine do a "export_users" to create an
absolutely up to date "user_asc" file - this is optional as there
will already be one that is no more than 7 days old and it won't
have changed significantly<br>
2. Recursively copy the contents of c:\spider\* to /spider/* on
the RPi as the sysop user. Probably the best way is to zip up the
entire directory and then (remembering to cd to the correct place)
unzipping it on the RPi. <br>
3. cd /spider/data<br>
4. rm dupefile qsl.v1 usdb.v1 users.v3<br>
5. perl user_asc<br>
6. /spider/perl/create_qsl.pl<br>
7. cd /tmp; wget -qN <a class="moz-txt-link-freetext" href="ftp://ftp.w1nr.net/usdbraw.gz">ftp://ftp.w1nr.net/usdbraw.gz</a>;
/spider/perl/create_usdb.pl usdbraw.gz<br>
<br>
At this point you will have recreated your user file, qsl info
file (that is queried by sh/dxqsl <callsign>) and the usdb
file. <br>
<br>
8. Before you start this instance of the node, please review the
callsigns in /spider/local/DXVars.pm because you don't want both
the windows node and this one to clash. Change the SSID of $mycall
and $myalias so that you can run both in parallel. Once you have
done this run: /spider/perl/update_sysop.pl. You can do this on
either machine but you will need to stop any running node first.<br>
<br>
At this point you can start the node.<br>
<br>
If all you want to do is recreate the databases, then stop the RPi
instance (if it's running) and then do actions 4->8 in the list
above.<br>
<br>
<b>NOTE</b>: (and this applies to all RPi nodes) The RPi uses a SD
Card as storage which is fine for experimentation, but utterly
useless if you intend to run the node for years (never mind more
than a few months). Apart from the fact that the SD card is slow -<u><b>
it is going to wear out</b></u>. <br>
<br>
If you want to run an RPi as a main node then get a usb connected
hard disk (a 2.5" 5400 rpm disk is fine) and use that instead. You
will have a much less eventful experience.<br>
<br>
Dirk G1TLH<br>
<br>
On 03/03/18 00:53, Anthony (N2KI) via Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAK4NQ92Xs3nEkeymrpz-1stpXhF7en_O7hPiLF2Jm0rhh87U2w@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">I am playing
with a Pi and DX Spider. How would I transfer the current
registered users on my windows system DX Spider node to my Pi
node?</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Thanks!</div>
<div>
<div class="gmail_signature" data-smartmail="gmail_signature"> <br>
Regards,<br>
<br>
Anthony (N2KI)<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
</body>
</html>