cyclades-devices(5)

💖 cyclades-devices — the vibe check ✨

okay bestie, so this is the cyclades-devices(5) manual page and it's lowkey the blueprint for getting your Cyclades terminal server talking to your Unix box. it's giving matchmaker energy. let's go 💅

---

🌸 NAME 🌸

cyclades-devices — the tables that drive cyclades-serial-client. periodt. no cap, that's literally its whole job.

---

🦋 DESCRIPTION 🦋

so the cyclades-devices file is where all the mapping lives between your Unix device files (the /dev/* girlies) and the addresses of the serial ports on your Cyclades Terminal Servers. one entry per serial port, and the format is exactly this:

device:rastype:rasname:physport:type:options

📝 quick note bestie: a # character at the beginning of a line means it's a comment. the file will not be reading it, she's just there for the vibes.

and now the entry fields, one by one, i'm obsessed with them:

• devname — the full pathname of the file that gets associated with the serial port. it must start with a /dev/ prefix, non-negotiable. you've got two naming schemes to pick from here:
  • devname doesn't exist, and it'll get linked to a free pseudo-tty. this is the default behavior of cyclades-ser-cli. ✨
  • devname is the name of a valid slave pseudo-tty. in this case you have to assign the -t 1 option in the options field. (heads up though: this option is not supported by this release 😭)
• rastype — the Terminal Server type:
  • prts, for Cyclades Pr302X/TS Terminal Servers.
  • path, for Cyclades PathRAS Terminal Server.
• rasname — the Host Name or IP Address of the Terminal Server where the serial port resides. that's her address, she lives there 💖
• physport — the Number of physical port in the Terminal Server. and here's the lil twist: if physport is assigned to zero, then rasname gets treated as the IP address associated with this port, in an IP-based addressing scheme. sneaky but iconic.
• type — the Server type that will be contacted to handle the serial port:
  • rtelnet, for Remote Telnet Server
  • socket, for Socket Server
• options — per-port specific options, passed along to the cyclades-ser-cli program. extra little treat for each port. 🎀

---

🎀 EXAMPLES 🎀

1. a Device on a PR3020/TS Terminal Server pr3k Port 1, accessed through the /dev/ctty01 device file name, using telnet protocol (remote telnet server)

/dev/ctty01:prts:pr3k:1:rtelnet:

2. the same device, but with an IP address pr3k_port1 associated to the serial port (IP-based port addressing)

/dev/ctty01:prts:pr3k_port1:0:rtelnet:

3. a Device on a PathRAS Terminal Server pr3k Port 2, accessed through the /dev/ctty02 device file name, using socket protocol (socket server)

/dev/ctty02:path:pr3k:2:socket:

look at her go. three entries, three completely different flexes. ate 💅🔥

---

🌈 FILES 🌈

• /etc/cyclades-devices — this file. that's it, that's the whole list. the main character herself. 👑

---

⭐ SEE ALSO ⭐

• cyclades-serial-client(1)
• cyclades-ser-cli(1)

go read those too bestie, they're the whole support system for this one. 🫶

---

and that's a wrap on cyclades-devices(5) — yes the footer says cyclades-devices(5) again because the universe loves a full circle moment, mwah 💜✨