Bryan Drewery пре 21 година
родитељ
комит
cebca06a7a
2 измењених фајлова са 23 додато и 12 уклоњено
  1. 19 3
      doc/INSTALL
  2. 4 9
      doc/UPGRADING

+ 19 - 3
doc/INSTALL

@@ -31,10 +31,26 @@ After the compile process is finished, the binaries will be placed in wraith.OS.
 
 Step 3: Making bots
 
-simply do ./binary -C
-You may need to 'export EDITOR=pico' or to whatever editor you prefer.
+Simply do ./binary -C
+You may need to 'export EDITOR=pico' or 'setenv EDITOR pico' to whatever editor you prefer first (probably defaults to vi).
 Make sure you check all settings presented.
 
-If you were updating an old bot on the shell:
+At the bottom list bots like:
+bot1 ip host
+bot2 . +host (for ipv6 host)
+bot3 . . ipv6ip
+bot4 . .
+--
+Then save and exit.
+The binary will auto move to binpath/binname.
+
+Then on the hub do for every bot you added:
+.newleaf bot *!ident@host *!ident@ip
+
+Then just run the binary!
+All bots within the binary will be spawned with it's own PID.
+
+
+UPDATING BOTS:
 ./old_binary -U new_binary
 If you want bots to auto restart use '-u' instead

+ 4 - 9
doc/UPGRADING

@@ -1,12 +1,7 @@
 
-Get the new src.
-Copy your pack/* to the new pack/
-./build all
-untar the package that is created
-Set a hub +U
-Then on that hub, copy all the binaries for the new version to it's dir..
+Set a hub +u
+Download new binaries to hub shell.
+Then, copy all the binaries (untarred) for the new version to it's dir..
 whatever os you are in, copy the appropiate new hub binary to 'newhub', then on the hub, type .update newhub
-Sit back and cry as all the bots die probably.. nah j/k
-
-This will all be improved over time, and you won't need to redo your entire net ever...
+Sit back and relay while your net is updated :)