tmi2/
tmi2/bin/
tmi2/etc/
tmi2/lib/
tmi2/lib/adm/
tmi2/lib/adm/daemons/languages/
tmi2/lib/adm/daemons/network/I3/
tmi2/lib/adm/daemons/virtual/template/
tmi2/lib/adm/obj/master/
tmi2/lib/adm/priv/
tmi2/lib/adm/shell/
tmi2/lib/adm/tmp/
tmi2/lib/cmds/
tmi2/lib/d/
tmi2/lib/d/Conf/
tmi2/lib/d/Conf/adm/
tmi2/lib/d/Conf/boards/
tmi2/lib/d/Conf/cmds/
tmi2/lib/d/Conf/data/
tmi2/lib/d/Conf/logs/
tmi2/lib/d/Conf/obj/
tmi2/lib/d/Conf/text/help/
tmi2/lib/d/Fooland/adm/
tmi2/lib/d/Fooland/data/
tmi2/lib/d/Fooland/data/attic/
tmi2/lib/d/Fooland/items/
tmi2/lib/d/TMI/
tmi2/lib/d/TMI/adm/
tmi2/lib/d/TMI/boards/
tmi2/lib/d/TMI/data/
tmi2/lib/d/TMI/rooms/
tmi2/lib/d/grid/
tmi2/lib/d/grid/adm/
tmi2/lib/d/grid/data/
tmi2/lib/d/std/
tmi2/lib/d/std/adm/
tmi2/lib/data/adm/
tmi2/lib/data/adm/daemons/
tmi2/lib/data/adm/daemons/doc_d/
tmi2/lib/data/adm/daemons/emoted/
tmi2/lib/data/adm/daemons/network/http/
tmi2/lib/data/adm/daemons/network/services/mail_q/
tmi2/lib/data/adm/daemons/network/smtp/
tmi2/lib/data/adm/daemons/news/archives/
tmi2/lib/data/attic/connection/
tmi2/lib/data/attic/user/
tmi2/lib/data/std/connection/b/
tmi2/lib/data/std/connection/l/
tmi2/lib/data/std/user/a/
tmi2/lib/data/std/user/b/
tmi2/lib/data/std/user/d/
tmi2/lib/data/std/user/f/
tmi2/lib/data/std/user/l/
tmi2/lib/data/std/user/x/
tmi2/lib/data/u/d/dm/working/doc_d/
tmi2/lib/data/u/l/leto/doc_d/
tmi2/lib/data/u/l/leto/smtp/
tmi2/lib/doc/
tmi2/lib/doc/driverdoc/applies/
tmi2/lib/doc/driverdoc/concepts/
tmi2/lib/doc/driverdoc/driver/
tmi2/lib/doc/driverdoc/efuns/arrays/
tmi2/lib/doc/driverdoc/efuns/buffers/
tmi2/lib/doc/driverdoc/efuns/compile/
tmi2/lib/doc/driverdoc/efuns/ed/
tmi2/lib/doc/driverdoc/efuns/floats/
tmi2/lib/doc/driverdoc/efuns/functions/
tmi2/lib/doc/driverdoc/efuns/general/
tmi2/lib/doc/driverdoc/efuns/numbers/
tmi2/lib/doc/driverdoc/efuns/parsing/
tmi2/lib/doc/driverdoc/lpc/constructs/
tmi2/lib/doc/driverdoc/lpc/preprocessor/
tmi2/lib/doc/driverdoc/lpc/types/
tmi2/lib/doc/driverdoc/platforms/
tmi2/lib/doc/mudlib/
tmi2/lib/ftp/
tmi2/lib/log/
tmi2/lib/obj/net/
tmi2/lib/obj/shells/
tmi2/lib/std/board/
tmi2/lib/std/body/
tmi2/lib/std/fun/
tmi2/lib/std/living/
tmi2/lib/std/object/
tmi2/lib/std/shop/
tmi2/lib/std/socket/
tmi2/lib/std/virtual/
tmi2/lib/student/
tmi2/lib/student/kalypso/
tmi2/lib/student/kalypso/armor/
tmi2/lib/student/kalypso/rooms/
tmi2/lib/student/kalypso/weapons/
tmi2/lib/u/l/leto/
tmi2/lib/u/l/leto/cmds/
tmi2/lib/www/errors/
tmi2/lib/www/gateways/
tmi2/lib/www/images/
tmi2/old/
tmi2/v21.7a10/
tmi2/v21.7a10/ChangeLog.old/
tmi2/v21.7a10/compat/simuls/
tmi2/v21.7a10/include/
tmi2/v21.7a10/testsuite/
tmi2/v21.7a10/testsuite/clone/
tmi2/v21.7a10/testsuite/command/
tmi2/v21.7a10/testsuite/data/
tmi2/v21.7a10/testsuite/etc/
tmi2/v21.7a10/testsuite/include/
tmi2/v21.7a10/testsuite/inherit/
tmi2/v21.7a10/testsuite/inherit/master/
tmi2/v21.7a10/testsuite/log/
tmi2/v21.7a10/testsuite/u/
tmi2/v21.7a10/tmp/
                    MTP - Mini Transmission Patchwork

MTP is a small program made just for one purpose: to avoid editing files
in LPmuds by using ed. With MTP it's quite easy to create files in LPmud
(e.g. by using the roommaker), transfer them to one's own machine, modify
them with the favourite editor and send them back for installation. Especially
in connection with SCCS I hope MTP to become a small but useful tool.

Nevertheless, MTP is just a patchwork. I expect it to have infinite bugs. It's
up to you to help me find them and get them out. Any bug report is deeply
appreciated and best sent to rg@irb.informatik.uni-dortmund.de

WARNING
-------

     mtp MUST be used EXCLUSIVELY for LPC files for LPmud. This is due to 
     the fact that disk space is *VERY* limited. Expect to face *SERIOUS*
     consequences if this rule is not obeyed. By the way a log file catches
     everything you do.

ADDITIONAL FEATURES
-------------------

     Read the CHANGES-file carefully to understand the access permission
     rights.


NAME
     mtp - mini transmission patchwork

SYNOPSIS
     mtp [-or] [-g<MUDname>] file1 file2 ...

DESCRIPTION
     In standard mode mtp tries to read the specified files and transfer them
     to the player's home directory in the local MUD. The attempt fails, if

     - the source file cannot be accessed
     - the connection to the MTPserver cannot be made up
     - the user doesn't exist or is not a wizard
     - the password used is wrong
     - the destination file already exists
     - the destination file cannot be accessed

     mtp accepts the UNIX wildcards in standard mode, in reception mode
     the full file name without path has to be sustained.

OPTIONS
     -o : Overwrite mode. Archwizards have to add -o, if they write to
          foreign directories.
     -r : Reception mode. The file is transferred from the MUD to the local
          machine.
     -g : Specifies the Game, you want to join, specified in $HOME/.mtprc.

EXAMPLES

     mtp room.c

     will transfer the local file 'room.c' to /players/user/room.c in the MUD

     mtp -o /doc/README

     will transfer the README-file (must be in the current directory) to
     the MUD and place it in /doc. Just Archwizards have permission to do so.

     mtp -r /obj/living.c

     will transfer the file /obj/living.c to the current directory

     mtp obj/staff.c will transfer the file obj/staff.c
     to /players/xxx/obj/staff.c


FILES
     MTPLOG
	Logs the file transfer

     ...mudlib/players/people/<player>.o  :
	File used to determine level and password (encrypted) of player

     $HOME/.mtprc
	Specifies the games to play. The "default" line specifies the game
	that is taken, when you don't specify a game. The other lines should
	be self explanatory. (Remember every game must be in one line.)

     mtplock
        Directories containing a file called mtplock CANNOT be read by MTP
        using the -r-option.

	An example might be the must useful here:

default TubMud
game TubMud    host para.cs.tu-berlin.de port 7682 wizard data password Lalala
game Nightfall host 134.2.72.157         port 4243 wizard data password no_way

BUGS

Please help me wipe them out ! EMail to

     rg@irb.informatik.uni-dortmund.de (Mentar)

or visit me in TUBMUD

     130.149.19.77 7680