05-14-2019, 03:48 AM
@Tim Curtis
Sorry for sporatic responses. (We're trying to empty all our kitchen cabinets before the contractor arrives tomorrow morning!)
AFAICT the following two approaches are equivalent
1) fresh r5.2 on uSD card. Plug it into an RPi. Boot without Ethernet. No AP appears. Plug in Ethernet and ssh in. Run
At this point without thinking I rebooted and unplugged Ethernet while reboot in progress but I believe result would have been same if I had simply unplugged Ethernet---r5.2 came up in AP mode. The symbolic link in /etc/systemd/system is no longer present.
2) fresh r5.2 on uSD card. Mount second partition on some other host (in my case a Linux laptop). Remove the link I pointed out.
Unmount partition and plug uSD card into an RPi. Boot without Ethernet. AP appears.
Either way, you are correct that the service was masked in the installation process. I don't yet know why.
Regards,
Kent
Sorry for sporatic responses. (We're trying to empty all our kitchen cabinets before the contractor arrives tomorrow morning!)
AFAICT the following two approaches are equivalent
1) fresh r5.2 on uSD card. Plug it into an RPi. Boot without Ethernet. No AP appears. Plug in Ethernet and ssh in. Run
Code:
sudo systemctl unmask hostapd
At this point without thinking I rebooted and unplugged Ethernet while reboot in progress but I believe result would have been same if I had simply unplugged Ethernet---r5.2 came up in AP mode. The symbolic link in /etc/systemd/system is no longer present.
2) fresh r5.2 on uSD card. Mount second partition on some other host (in my case a Linux laptop). Remove the link I pointed out.
Code:
kreed@T520:/media/kreed/rootfs/etc/systemd/system $ sudo rm hostapd.service
Unmount partition and plug uSD card into an RPi. Boot without Ethernet. AP appears.
Either way, you are correct that the service was masked in the installation process. I don't yet know why.
Regards,
Kent