AXGETPUT(1)

okay bestie, pull up a chair 🫶 you're reading axgetput(1) from the Linux Programmer's Manual — section 1, the user-commands one, obviously 💅 this is the page that moves your files around over AX.25 packet radio. let's get into it ✨

🌸 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 💫

okay so first up: the flags, because that's literally the whole game here 👑

• -b blocksize — sets the blocksize (that's the frame length) of the transmitted data. it defaults to 256 bytes, and that number matches typical AX.25 network confurations best. like, it's tuned for it. 💅
• -i — compute the CRC checksum only. just the checksum. nothing else. periodt.
• -s — says "bestie, my input is coming from a stream". 🦋 this one is available only if STDIN is a pipe — no pipe, no -s, sorry. the filename argument may be omitted if -s is given, and the length of the file need not to be known, so you can just stream and vibe.
• -v — print version and exit. a lil hello and then she's gone 👋
• -h, ? — print usage and exit. when you're lost, ask for help — that's main character energy.

---

so here's the tea 🍵 axgetput is the actual name of the program. you execute it as like bget or bput, while axgetput is the common program to which bget and bput are linked to. and axgetput autodetermines which operation mode the user desires — it just knows. iykyk 🔥

it also sets the pty to be 8bit clean (which is what enables binary mode for the file transfer, slay), and it requires that the user is logged in through axspawn(8). no axspawn, no transfer, no cap.

🎀 I. #BIN Protocol 🎀

bget is for downloading a file on this system — from the unix login shell, via his ax25 session, over to his packet-radio terminal program. the download "protocol" is the #BIN standard, the one everybody knows from packet radio mailboxes. iconic.

bput does it the other way round: with this comand, the user may upload a file to this computer. ⬆️

and the #BIN protocol gives you a CRC consistency check after the file is transfered, so you know it landed intact. the transfer of the file modification time is also part of the #BIN protocol. timestamps stay cute ✨

💜 II. YAPP Protocol 💜

yget or yput is reserverd for the yapp protocol — which is not supported in this version. 😭 reserved but not served. it's giving "coming soon" energy.

💜 II. DIDADIT Protocol 💜

(yes, it says II twice, we don't make the rules 🙈)

rget or rput is reserverd for the didadit protocol — which is also not supported in this version. same vibe, different name. 💀

Anyone like to implement yapp and didadit protcols? 👀 that's a genuine open invitation from the original page, bestie. the door is open. the crown is on the table. 👑

🫶 AUTHOR 🫶

Thomas Osterried DL9SAU <thomas@x-berg.in-berlin.de> Ralf Baechle DL5RB <ralf@linux-mips.org>

---

and that's the whole page, bestie 💖 it's a Linux one, dated 21 January 2007, and it lives at AXGETPUT(1). go forth and transfer those files — you've got this 🌈💅