LIBRMT(3L)

💖 LIBRMT(3L) — the remote magtape protocol client interface library 💖

okay so bestie, welcome to librmt, a.k.a. the remote magtape protocol client interface library — and yes, you link it with -lrmt, no cap. It lives in Schily´s LIBRARY FUNCTIONS (section 3L of your fave manual set), and it's genuinely iconic for talking to tape servers on other machines. let's get into it 🎀

---

✨ SYNOPSIS ✨

#include <schily/librmt.h>

that's it. one include and you're in, periodt. 💅

---

🌸 DESCRIPTION 🌸

so the functions in this library hand you an interface to a remote tape server program. that's the whole vibe — you stay on your machine, the tape lives somewhere else, and librmt handles the talking. 🦋

this implementation takes care of RMT protocol VERSION 1, which is the version you need in case that the rmt client and the rmt server do not run on the same OS and use a CPU with the same bit width and byte order. yep, very specific, very demure, very important. 😌

plus — and this is the slay part — this implementation also supports a GNU extension that lets you use open(2) flags beyond O_RDONLY, O_WRONLY, O_RDWR. more flags, more power, no cap. 🔥

---

🌈 ENVIRONMENT 🌈

• RSH — if the RSH environment variable is present, the remote connection will not be created via rcmd(3); instead it'll be made by calling the program that RSH points to. use e.g. RSH=/usr/bin/ssh to create a secure shell connection. 🐚 and heads up: if the environment RSH is empty, then the default rcmd(3) is used even in case rmtrsh(3) has been called. so empty ≠ unset, bestie, write that down. 📝
• RMT — if the RMT environment variable is present, the remote tape server will not be the program /etc/rmt; instead it'll be the program that RMT points to. 🎯 and same deal: if the environment RMT is empty, then the default /etc/rmt is used even in case rmtrmt(3) has been called.

also note that the remote tape server program name will be ignored if you log in using an account that has been created with a remote tape server program as login shell. so if that's your setup, this whole variable is lowkey doing nothing — sorry, i don't make the rules. 💀

---

👑 INTERFACES 👑

the whole squad, fr fr:

rmtinit(3), rmtdebug(3), rmtrmt(3), rmtrsh(3), rmthostname(3), rmtfilename(3), rmtgetconn(3), rmtopen(3), rmtioctl(3), rmtclose(3), rmtread(3), rmtwrite(3), rmtseek(3), rmtxstatus(3), rmtstatus(3), _mtg2rmtg(3), _rmtg2mtg(3)

that's the whole group chat. 🫶

---

🦋 SEE ALSO 🦋

rmt(1), rsh(1), ssh(1), rcmd(3)

go read those too, they're the supporting cast and they ate. ✨

---

🙈 BUGS 🙈

None currently known. clean sheet, flawless record, we love to see it. 💅

mail bugs and suggestions to schilytools@mlists.in-berlin.de or open a ticket at https://codeberg.org/schilytools/schilytools/issues — they actually want to hear from you, bestie. 🐛

the mailing list archive may be found at:

https://mlists.in-berlin.de/mailman/listinfo/schilytools-mlists.in-berlin.de.

---

🧚 AUTHORS 🧚

librmt has been written in 1990 by Joerg Schilling — a genuine vintage icon, main character energy since the 90s. 🎀 in 1995, support for RMT VERSION 1 has been added. librmt is now maintained by the schilytools project authors. legends only. 👑

---

⭐ SOURCE DOWNLOAD ⭐

the source code for librmt and rmt is included in the schilytools project and may be retrieved from the schilytools project at Codeberg at

https://codeberg.org/schilytools/schilytools.

the download directory is

https://codeberg.org/schilytools/schilytools/releases.

---

and that's the page, bestie!! written by Joerg Schilling on 2022/09/11, formatted for LIBRMT(3L) — go forth and tape remotely, you absolute icon 💜✨