New 0.5 draft of the SemPiTernal HOWTO

[Frank]

Comments below - not finished, but didn’t have time to read all (on the road).  Sorry for the format:
——————————————————————————————
idiosyncracies - idiosyncrasies 

rectagular - rectangular

presoldered - pre-soldered

kitbuilders - kit builders

Regarding the download (done as normal user) and the root commands using the download, does something need to be said about where the file is stored (in uses’s directory)?  If you use `sudo` instead of “as root” the file location will not be an issue.

For root commands, instead of sudo bash, maybe just preface sudo before each command - this is how most Pi/Distro’s I’ve seen do it

duting - during

Under On - only “On”

Note that my Pi 3’s (latest & fastest) take 60+ seconds to boot & be pingable.  Then about another 10-20 seconds to be available via SSH (depending on wired or wireless)

For adding group changes, why not use `usermod`.  Users editing config files are more prone to messing them up, than letting the utilities make the changes.

tunnelling - tunneling

avaolable - available

Is “Wait for Network at Boot” really required?  On my Gentoo Pi's with dhcpcd, it will background wait indefinitely (maybe my Gentoo configuration setting) , and will grab an IP when a cable is connected.

Regarding updating and installing pieces - do all SBC’s use Debian based “apt”?

“The Pi 3 Raspbian implementors” was actually the Pi 3 hardware designer/manufacturer (Raspberry Pi Foundation) - they created the default mapping of BT vs. Serial.  This is not Raspbian’s fault or decision.

“/boot” is not mounted by default.  To check for overlays, they may have to mount “/boot”

“force_turbo=1” forces the Pi to run at maximum clock speed all the time.  This generates heat & increased power consumption.  If constant/max clock speed is desired (for NTP constancy?), keep this.  If power/heat are a concern, remove this.

an HAT - a hat

I’m not following the “blink” table.  It’s not jumping out at me or making sense…

For cloning a GIT repository, I’ve used “- -  depth=1” to get what I think is just the top, latest version?  If my understanding is correct, this will be quicker for people on slow connections.  If I’m wrong about what this does in GIT, please correct my understanding.  Is there a down side to using depth=1?

You’re using Reference Clock 20 & 22.  NTPSec docs state Reference Clock 20 has been removed (redundant to GPSd).  Please tell me 20 (NMEA) is still there!  That’s been a concern of mine since reading the NTPSec docs.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20160505/7e7861b5/attachment.html>