Comments on: Chapter 2: Raspberry Pi Software

By: Idan

Idan — Fri, 23 Mar 2018 20:16:42 +0000

On windows, after installing bonjour print services, ping raspberrypi.local worked

But on the linux (virtual machine) it didn’t. What package/tool should I install and run on it ?

By: Idan

Idan — Fri, 23 Mar 2018 18:00:23 +0000

page 29:
pi@raspberrypi:~ $ systemctl status avahi-daemon
gives the following output and gets stuck ( I have to stop to continue typing)

● avahi-daemon.service – Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2018-03-23 17:48:09 UTC; 1min 9s ago
Main PID: 367 (avahi-daemon)
Status: “avahi-daemon 0.6.32 starting up.”
CGroup: /system.slice/avahi-daemon.service
├─367 avahi-daemon: running [raspberrypi.local]
└─369 avahi-daemon: chroot helper

Mar 23 17:48:09 raspberrypi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Mar 23 17:48:09 raspberrypi avahi-daemon[367]: Network interface enumeration completed.
Mar 23 17:48:09 raspberrypi avahi-daemon[367]: Server startup complete. Host name is raspberrypi.local. Local
Mar 23 17:48:09 raspberrypi avahi-daemon[367]: Service “raspberrypi” (/services/multiple.service) successfull
Mar 23 17:48:12 raspberrypi avahi-daemon[367]: Joining mDNS multicast group on interface eth0.IPv6 with addre
Mar 23 17:48:12 raspberrypi avahi-daemon[367]: New relevant interface eth0.IPv6 for mDNS.
Mar 23 17:48:12 raspberrypi avahi-daemon[367]: Registering new address record for fe80::5511:d56a:ccaa:f71f o
Mar 23 17:48:16 raspberrypi avahi-daemon[367]: Joining mDNS multicast group on interface eth0.IPv4 with addre
Mar 23 17:48:16 raspberrypi avahi-daemon[367]: New relevant interface eth0.IPv4 for mDNS.
Mar 23 17:48:16 raspberrypi avahi-daemon[367]: Registering new address record for 192.168.3.102 on eth0.IPv4.
~
~
~
Therefore , trying to ssh with the domain name / ping raspberrypi.local from the linux machine says the it couldn’t find this host name

what can I do?

By: Michael

Michael — Sat, 29 Jul 2017 19:45:31 +0000

There is no need to boot into the desktop. The link given by Dan (https://www.raspberrypi.org/blog/a-security-update-for-raspbian-pixel/) explains that placing a file called ‘ssh’ in the /boot/ directory of the SD card will enable ssh on first boot:

“The boot partition on a Pi should be accessible from any machine with an SD card reader, on Windows, Mac, or Linux. If you want to enable SSH, all you need to do is to put a file called ssh in the /boot/ directory. The contents of the file don’t matter: it can contain any text you like, or even nothing at all. When the Pi boots, it looks for this file; if it finds it, it enables SSH and then deletes the file.”

By: Eric

Eric — Fri, 05 May 2017 21:51:49 +0000

A fresh Raspian install does NOT have SSH enabled. I had to boot into the desktop and then go to configuration and turn on SSH. Once I did this, Putty was able to connect. From reading this chapter it seemed like you just plug in the network cable, run putty, put in the IP address with Port 22 and Bob’s your uncle. Ain’t so.

By: Dan

Dan — Tue, 31 Jan 2017 02:32:05 +0000

New versions of Raspian have SSH disabled by default. You have to add a file called “SSH” to the /boot/ directory to enable it at boot. The file is deleted on first boot.

https://www.raspberrypi.org/blog/a-security-update-for-raspbian-pixel/

By: admin

admin — Fri, 30 Dec 2016 19:52:36 +0000

Thanks, that is very useful information

By: cv007

cv007 — Fri, 30 Dec 2016 00:23:42 +0000

Section- ‘What time is it?’
I have a headless RPI3 with the onboard wifi, and was sidetracked for an hour or so while reading this book because I could not get the time synced up with the default ntp.service (I installed ntpdate which works ok, but I think). I stumbled upon the following page after much searching-
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=141454

I added the following line to /etc/rc.local as described-
/sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p udp –dport 123 -j TOS –set-tos 0x00
rebooted, and now ntp works ok (ntpq -p will show whether ntp is working- lots of 0’s means its not working 🙂 )

I commented out the added line to rc.local and tested again to double check- without this line I cannot get ntp to communicate with the time servers. The thread linked above was started over 6 months ago so it appears it still can be a problem for some (I have the latest Jessie Lite installed).

By: ronbonne

ronbonne — Sun, 04 Dec 2016 23:37:28 +0000

On RPi 3 the red power LED cannot be controlled in the way described in the book (pages 50-53). Apparently they changed the functionality. So the “heartbeat” proposed on page 53 will not work on RPi 3. It should work on RPi 2. The activity LED (LED0) is still available for control.

By: sorlac

sorlac — Wed, 19 Oct 2016 02:24:51 +0000

On page 53, the procedure written to make the heartbeat appear on the power LED does not work.The power LED is solid after reboot. The 2 lines added were still at the end of config.txt after the reboot.

By: Johann Fischer

Johann Fischer — Tue, 20 Sep 2016 21:11:00 +0000

Hello, on page 49, I would think that the command to update the firmware w/o the kernel would be: sudo SKIP_KERNEL=1 rpi-update, wouldn’t it?