Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

axgetput(1) [debian man page]

AXGETPUT(1)						     Linux Programmer's Manual						       AXGETPUT(1)

NAME
axgetput - upload or download files via AX.25 / axspawn Linux login session. SYNOPSIS
axgetput [-b blocksize] [-i] [-v] [-h] [?] filename axgetput [-b blocksize] [-i] -s [-v] [-h] [?] [filename] DESCRIPTION
-b blocksize Set the blocksize (frame length) of transmitted data. Defaults to 256 bytes which matches typical AX.25 network confurations best. -i Compute CRC checksum only. .B -s Indicates input from a stream. This option is available only if STDIN is a pipe. The filename argument may be omitted if -s is given. The length of the file need not to be known. -v print version and exit. -h, ? print usage and exit. axgetput is the actual name of the program. You execute for e.g. bget or bput while axgetput is the common program to which bget and bput are linked to. axgetput autodetermines which operation mode the user desires. axgetput sets the pty to be 8bit clean (thus enables binary mode for the file transfer). It requires that the user is logged in through axspawn(8). I. #BIN Protocol bget is used for downloading a file on this system from the unix login shell via his ax25 session to his packet-radio terminal program. The download "protocol" is the "#BIN" standard known from packet radio mailboxes. bput does it the other way round: with this comand, the user may upload a file to this computer. The #BIN protocol provides a CRC consistency check after the file is transfered. The transfer of the file modification time is part of the #BIN protocol. II. YAPP Protocol yget or yput is reserverd for the yapp protocol, which is not supported in this version. II. DIDADIT Protocol rget or rput is reserverd for the didadit protocol, which is not supported in this version. Anyone like to implement yapp and didadit protcols? AUTHOR
Thomas Osterried DL9SAU <thomas@x-berg.in-berlin.de> Ralf Baechle DL5RB <ralf@linux-mips.org> Linux 21 January 2007 AXGETPUT(1)

Check Out this Related Man Page

AXSPAWN.CONF(5) 					     Linux Programmer's Manual						   AXSPAWN.CONF(5)

NAME
axspawn.conf - Control the operation of axspawn. DESCRIPTION
The axspawn.conf file controls the operation of the axspawn(8) program. The operation of the config file can best be seen in an example: # this is /etc/ax25/axspawn.conf # # allow automatic creation of user accounts create yes # allow empty password field (so user may login via telnet, too) [default no] create_empty_password no #create_empty_password yes # create with system utility useradd(8)? [default no] #create_with_useradd no create_with_useradd yes # # pwcheck method: password or call or group. [default: password] #pwcheck call #pwcheck group pwcheck password # # guest user if above is 'no' or everything else # fails. Disable with "no" guest guest # # group id or name for autoaccount group hams # # first user id to use first_uid 400 # # maximum user id max_uid 2000 # # where to add the home directory for the new user home /home/hams # # secure homedirectories (g-rwx) #secure_home yes # # user's shell shell /bin/bash # # bind user id to callsign for outgoing connects. associate yes The "associate" option has to be used with great care. If a user logs on it removes any existing callsign from the translation table for this userid and replaces it with the callsign and SSID of the user. This will happen with multiple connects (same callsign, different SSIDs), too. Unless you want your users to be able to call out from your machine disable "associate". FILES
/etc/ax25/axspawn.conf SEE ALSO
axspawn(8). Linux 2 August 1996 AXSPAWN.CONF(5)
Man Page