Determine first what interfaces are available:
Add to /etc/rc.conf:
# Do not wait for lease; useful if no network is within reach, so boot will not hang
# select the appropriate interface (-i) for your wifi card. (i.e. -i wpi0)
wpa_supplicant_flags="-B -i wpi0 -c /etc/wpa_supplicant.conf"
Can anyone explain if all files (including the subdirectory overlays/ ) need to be copied?
"Copy all files except 'kernel*.img' into /boot and reboot"
Or would a subset be sufficient?
Thanks very much
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:
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.).
'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.
if you get the following error while trying to fetch sets;
ftp: Can't LOOKUP `nyftp.NetBSD.org:http': Temporary failure in name resolution
Please use the nyftp's IP address instead: 220.127.116.11
As reported by http://stackoverflow.com/questions/27690637/installing-netbsd-sets-via-http-on-raspberry-pi-fails
Instructions on how to build a FreeBSD image: http://azure.microsoft.com/blog/2014/05/22/running-freebsd-in-azure/
Instructions on how to build a Linux image: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-tutorial/
Images can be published on http://vmdepot.msopentech.com when complete
How to customize and republish an image once a base image is available in VM Depot: https://vmdepot.msopentech.com/tutorial/freeBSD.html