Matthew,
Not at all :) good question.
This hostname capability is provided by avahi. And it is already installed in the basic rootfs.
In your local network environment the host name is broadcasted by avahi. Your MacOS boxes would see it as nameofhost.local (it is debian.local if you have not changed hostname after installation).
So go ahead and ping it, or ssh in.
or
See if you get response in either cases.
Quote
Quick one as I am being thick.
Not at all :) good question.
This hostname capability is provided by avahi. And it is already installed in the basic rootfs.
Quote
Updated 25 Aug 2019:
Basic Debian buster Kirkwood rootfs for most Kirwood plugs:
- tarball size: 209M
- install size: 536M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-tools, and mtd-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root
In your local network environment the host name is broadcasted by avahi. Your MacOS boxes would see it as nameofhost.local (it is debian.local if you have not changed hostname after installation).
So go ahead and ping it, or ssh in.
ping nameofhost.local
or
ssh root@nameofhost.local
See if you get response in either cases.