Not a FreeBSD manual

Just a ongoing reference

My favorite hobby is my #homelab. It’s where I continuously improve my Unix administration and networking skills. It took me basically all weekend but I have my home lab completely isolated and virtualized on an 8th gen i7 Dell OptiPlex 7060 with 32GB of RAM. I also have a 14TB Iron Wolf HD

The hardest part was setting up the virtual network. I’d never done that kind of thing manually. I’d just used whatever default network that #libvirt created for me. This was hard and did require googling and reading #manpages. The problem with the wizard that creates networks is there’s no option for both DNAT and SNAT.

I learned a lot and got it working perfectly despite the garbage #verizon CR1000A router and its notorious bug. Yeah, you can’t add static routes. So I’m in a double NAT situation. Turns out this is okay because it effectively isolates the homelab. All I had to do was add static routing on my laptop and desktop.

Nobody else will be able to access my homelab unless they know its network and gateway addresses, much less how to configure a static route. It’s basic but works.

On a recent system update, I was alerted to the fact that I had modified a config file(/etc/groff/man.local). Did I want to merge them? Discard them? Fuck if I knew. 😆

.\" man.local - Added 202203 kbowen
.\" Add a searchable string before each section header
.rn SH SH-orig
.de SH
.SH-orig \(sc \\$*

Looking at the diff, I had no recollection of adding these lines. Fortunately for me, my past self was considerate enough to indicate their purpose. Unfortunately for me, my past self failed to credit the source for their inspiration. Bad dog!

I'd really like to read the article where I cribbed this from today.
Better a half-assed comment then no comment at all, I guess. But, still. Do better.

#NoteToSelf #man #manpages #groff #comments

Hello everyone, I made some updates to ManpageViewer, fixed some bugs, implemented interface improvements, now it's easier to read the manpages, and the search system has also been improved. As you can see, I also adopted another name. I also expanded the scope, with the creation of "Custom Manpages," I can add the manpages of a specific software.

https://man.nergahak.co.za/

#man #manpages #FreeBSD #MINIX #NetBSD #OpenBSD #UNIX #pkgsrc #DataBase

Nergahak Manpages DataBase

Nergahak Manpages DataBase

lolcat tricks and fun

In case you have ever wondered what it would look like to have all of your favourite console output piped through lolcat(6) 🏳️‍🌈, here is a nice example

required (one of *sh is enough)

  • Open Source OS
  • sh
  • csh
  • ksh
  • zsh
  • bash
  • fish
  • syntax skills on piping I/O
  • love of colours
  • typing skills
  • sense of humour

typing
man lolcat

...will get you the standard sh output delimited by the man command itself. This means that I used a simple trick to get all of my output piped through lolcat

ssh -Xv -p65534 -l userid |lolcat

This command syntax gets all of my commands in that ssh session piped through lolcat, creating an awsome rainbow colour galore

notes

  • ssh secure session piped through lolcat gets you a slower output, compliments of the inner workings of lolcat. Feel free to optimize the program and release the patches if the lowerspeed irks you.
  • test the speed by doing
  • ls -lR ~ and compare that in a standard ssh sessios without full lolcat pipe
  • I used the -X switch because I also start X programs from this shell (which I run in Xorg {it also works in wayland})
  • I use the -v switch because I love log messages of ssh
  • you can also animate your piped lolcat output with
  • lolcat -a
  • I watch the output on a large TV also, because lolcat(6) 🏳️‍🌈 is that awsome

sources:

lolcat --help

man lolcat(6) 🏳️‍🌈

https://github.com/busyloop/lolcat

man man(1)

#programming #rainbow #sh #csh #ksh #zsh #bash #fish #lolcat #man #manpages #OpenSource #Linux #BSD #POSIX #TV

Does computer #history interest you, or maybe you're just curious where well-known and well-used tools come from? I've just updated the History of #Unix #Manpages, https://manpages.bsd.lv/history.html, with the content you didn't know you wanted til this very moment. Learn about how the "man" program came to be, and just why are manpages styled like that? It includes snippets from Cynthia "Cindy" Livingston, who wrote the manpage language "mdoc"; John Eaton, who wrote the first GPL man tool; Doug McIlroy, who helped to divide manpages into sections; and more. Did you know that serving manpages online was part of one of the original http daemons? Or that an xman existed before X11R6, in X10? Enjoy!
History of Unix Manpages

Manpages: Struktur, Syntax und Verwendung

Eine kurze Einleitung in die Linux Manpages, sowie Tipps und Tricks, die ich auf dem Weg aufgegriffen habe.

#Linux #Administration #Manpages #Befehle #Shell #Linux

https://gnulinux.ch/manpages-struktur-syntax-und-verwendung

Manpages: Struktur, Syntax und Verwendung

Eine kurze Einleitung in die Linux Manpages, sowie Tipps und Tricks, die ich auf dem Weg aufgegriffen habe.

GNU/Linux.ch
🤣 Oh, joy! Yet another groundbreaking revelation: people like *examples* in man pages. Who could have guessed? 🚀 Thank goodness someone finally added the most *basic* #examples to #tcpdump and #dig... because, you know, reading is hard. 📚🔍
https://jvns.ca/blog/2026/03/10/examples-for-the-tcpdump-and-dig-man-pages/ #manpages #programming #humor #HackerNews #ngated
Examples for the tcpdump and dig man pages

Examples for the tcpdump and dig man pages

Julia Evans
Examples for the tcpdump and dig man pages

Examples for the tcpdump and dig man pages

Julia Evans