Jupiter Broadcasting

The State of BSD | BSD Now 128

This week on BSDNow, we interview Nick Wolff about how FreeBSD is used across the State of Ohio & some of the specific technology used. That, plus the latest news is coming your way right now on BSDNow, the place to B…SD.

Thanks to:





Direct Download:

Video | HD Video | MP3 Audio | OGG Audio | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | iTunes Feed | Video Feed | HD Vid Feed | HD Torrent Feed

Become a supporter on Patreon:

– Show Notes: –

Headlines

Doc like an Egyptian: Managing project documentation with Sphinx

“While the main purpose of a wiki is to invite user contributions and to provide a low barrier to entry, very few people come to write documentation (however, every spambot on the planet will quickly find your wiki, which creates its own set of maintenance issues).

Wikis are designed for separate, one-ish page infobytes, such as how-tos. They really aren’t designed to provide navigation in a Table of Contents or to provide a flow of Chapters, though you can hack your pages to provide navigational elements to match the document’s flow. This gets more difficult as the document increases in size—our guides tend to be 300+ pages. It becomes a nightmare as you try to provide versioned copies of each of those pages so that the user is finding and reading the right page for their version of software.

While wiki translation extensions are available, how to configure them is not well documented, their use is slow and clunky, and translated pages only increase the number of available pages, getting you back to the problems in the previous bullet. This is a big deal for projects that have a global audience.

While output-generation wiki extensions are available (for example, to convert your wiki pages to HTML or PDF), how to configure them is not well documented, and they provide very little control for the layout of the generated format. This is a big deal for projects that need to make their documentation available in multiple formats.“

“While Sphinx is easy to learn, it does have its quirks. For example, it does not support stacked tags. This means, for example, you can not bold italic a phrase using tags—to achieve that requires a CSS workaround. And, while Sphinx does have extensive documentation, a lot of it assumes you already know what you are doing. When you don’t, it can be difficult to find an example that does what you are trying to achieve.

Sphinx is well suited for projects with an existing repository—say, on github—a build infrastructure, and contributors who are comfortable with using text editors and committing to the repo (or creating, say, git pull requests).“


Initial FreeBSD RISC-V Architecture Port Committed.


FreeBSD Bhyve hypervisor supporting Windows UEFI guests


FreeBSD TACACS+ GNS3 and Cisco 3700 Router


Interview – Nick Wolff – darkfiberiru@gmail.com / @darkfiberiru


News Roundup

Papers We Love Presents : Bryan Cantrill on Jails & Solaris Zones


FreeBSD Storage Summit


Tor Browser 5.5 for OpenBSD/amd64 -current is completed


“FreeBSD Mastery: Advanced ZFS” Table of Contents


Beastie Bits


Feedback/Questions