RSPORTS(5)
π RSPORTS(5) π
okay bestie, so this is rsports(5), straight out of the Linux Programmer's Manual β yes the manual, section 5, the file-formats girlies. pull up a chair, grab a boba, we're doing config files today π§β¨
πΈ NAME πΈ
rsports β the Rose port configuration file. that's it, that's the whole thing. she's a config file, she's iconic, she holds port lore π
π¦ DESCRIPTION π¦
so like. rsports is an ASCII file (plain text, no drama, no weird binary nonsense) and it holds all the info about every single Rose port you're gonna be using. all of them. the whole roster π
here's the tea: when you run a Rose utility β think call and friends β it takes an optional argument that's the port name. and that port name? it's literally a pointer. a reference. it says "hey, go find the line inside rsports that has this exact same name." matching names, matching energies, it's giving soulmates fr fr π«Ά
and the info on that line? it's enough to bind the command to a particular Rose interface. how does the binding happen, you ask? not me about to explain β by matching the address on the line in rsports with the address of the port set by ifconfig or rsattach. so those two addresses gotta line up. no match, no bind, no cap π€
π¬ comments, bestie π¬
the rsports file can have comments! and a comment starts with a # β but only in the first column. first column only. don't be putting your # in the middle of nowhere and expecting it to work, she's picky like that π
other than comments, you get port descriptions, and the format is this, with every field separated by white space:
name address description
π the fields, explained π
nameβ this is the unique Rose port identifier. unique, okay?? she does not share her name with anyone else, that's the whole point πaddressβ the address of the Rose interface you're binding to. this is the one that has to match up with whatifconfigorrsattachset. the moment of truth β¨descriptionβ a free format description of this interface. and the way that this field just extends all the way to the end of the line?? obsessed. it may contain spaces. go off, write a whole paragraph, she doesn't care π
fr fr reminder:nameandaddressare white-space-delimited, butdescriptioneats the rest of the line. so don't be surprised when your third field swallows everything after it π«
π FILES π
/etc/ax25/rsports
that's where she lives. that's her address (ironic, given the whole file is about addresses, iykyk) π π
π SEE ALSO π
go read those too, they're all part of the same friend group π«Ά
and that's the whole vibe check, bestie πβ¨ this page is from the Linux manual, dated 27 August 1996 (yes, 1996, she's a vintage queen and she ATE), and you just read RSPORTS(5). go configure your ports, you absolute main character ππππ¦πΈ
π¦ where this page comes from
- alpine 3.24: ax25-tools-doc 1.1.0-r0 Β· GPL-2.0-or-later
- debian bookworm: libax25 0.0.12-rc5+git20190411+b17ff36-4+b1 Β· LGPL-2.1-or-later
- debian trixie: libax25 0.0.12-rc5+git20230513+5581005-1 Β· LGPL-2.1-or-later
- fedora 43: ax25-tools-docs 1.0.4-14.fc43 Β· GPL-2.0-or-later
- fedora 44: ax25-tools-docs 1.0.4-17.fc44 Β· GPL-2.0-or-later
- nixos 26.05: libax25 0.0.12-rc5
- nixpkgs unstable: libax25 0.0.12-rc5
- ubuntu jammy: libax25 0.0.12-rc5+git20190411+b17ff36-4 Β· LGPL-2.1-or-later
- ubuntu noble: libax25 0.0.12-rc5+git20230513+5581005-1 Β· LGPL-2.1-or-later
- ubuntu questing: libax25 0.0.12-rc5+git20230513+5581005-1
- ubuntu resolute: libax25 0.0.12-rc5+git20230513+5581005-1build1 Β· LGPL-2.1-or-later
- ubuntu stonking: libax25 0.0.12-rc5+git20230513+5581005-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms