Thoughts from a passers-by:

Let the output formats (we need most!) dictate the requirements of the tool.
Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.
Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.
If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.
Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!

A writer needs a tool which concentrates his thought. A printing press expands thought.
What will the writer do if one gives the writer a printing press?

Why should the available book formats define the pen of the writer? 'Content rules format.'

I see a collection of printing presses. They can do a lot.
I read: They don't do the job 'software documentation'.
But what does this all have to do with solving the task 'software documentation'?
Nothing. One needs to specify what 'software documentation' is before choosing the tool.
To me it is:

  1. Hierarchy
    1. Headings
    2. Lists
  2. Descriptive text
  3. Non-descriptive text (quotes)
    1. Inline
    2. Multiline
  4. References
    1. Internal
    2. External
      1. Author, Title, Date, Location
      2. URI
  5. Images

Blocks of texts are organised in an hierarchy (a1).
Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).
A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).
A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.
I leave it to some higher power whether images (e) are required.
The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).

That's it.

'But I need to highlight some description text.' No, you don't.
If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:
o r s p a c e.
O R B O T H.

You haven't seen anything. Continue your walk.

Comment by Benjamin late Tuesday evening, March 31st, 2015

if you get the following error while trying to fetch sets;

ftp: Can't LOOKUP `': Temporary failure in name resolution

Please use the nyftp's IP address instead:

As reported by

Comment by Youri Sunday afternoon, March 22nd, 2015
Really looking forward to the future of this port! I'd love to build a fileserver with my C1 using NetBSD as the OS.
Comment by Bo terribly early Monday morning, March 9th, 2015
Thanks, Andrew. That worked.
Comment by Doug Thursday afternoon, March 5th, 2015

Instructions on how to build a FreeBSD image:

Instructions on how to build a Linux image:

Images can be published on when complete

How to customize and republish an image once a base image is available in VM Depot:

Comment by Ross in the wee hours of Saturday night, February 22nd, 2015
Halibut might be worth including in the mix of options to consider. The source tarball is 919K, it's written in portable ANSI C (apart from requiring at least a 32-bit platform), it has no dependencies, and the license is MIT. It can directly generate plain ASCII text, HTML, PDF, PostScript, Unix man pages (i.e. nroff input to work with the -mandoc macro package), and Unix info.
Comment by J. Lewis Wednesday evening, February 4th, 2015
You might want to check out installing pkgsrc and building your own packages - this article may help
Comment by Nick late Monday afternoon, January 5th, 2015

I have successfully installed NetBSD to my pi from the supplied images, but it is just the core system with no X server. I am a relative newby to Linux, let alone BSD and am slowly working my way around it, but I am struggling with pkg_add because I can't find a source file to match...

I downloaded rpi.img.gz from here:

I followed the instructions on this page, but fall down when trying to add packages

but when following the instructions here: and here:

I cannot find a matching distribution.

uname -a reports: NetBSD rpi 7.0_BETA NetBSD 7.0_BETA (RPI_201501031030Z) evbarm

but the closest I can get is

Should I be looking elsewhere for the repository?

Comment by Jonathan Sunday night, January 4th, 2015

The example code at has a bug. It skips the first file in the directory of files it's supposed to monitor.

I was able to fix this by changeing line 51 to while(cnt++ < 2 && (pdent = readdir(pdir)) != NULL)

Comment by Kevin early Thursday morning, January 1st, 2015

Some of the links in the "Additional Info" section refer to, whereas they should refer to

For example: /ports/sparc64/faq.html is a broken link.

But changing wiki to www works:

Links I've noticed that need correcting include: NetBSD/sparc64 FAQ Notes on System Models NetBSD/sparc64 History

Comment by Gareth mid-morning Wednesday, December 24th, 2014
Add a comment