Just copy the host keys from the Plugbox installation to the ROM installation, right? Nope. Once the lights were working, I found I could control them as described in the PlugApps Dockstar LED Wiki Page. Then I re-inserted my USB drive and rebooted. Once the system was running from the ROM image, and I was logged in as root, I entered the following command: I chose the latter option (which reminded me why it was that I wanted to synchronize ssh host keys).
Dockstar led install#
The only way to install it in Plugbox, as far as I can tell, is to re-run the bootloader installation from Plugbox. I went looking, and did not find a pacman package that provides the fw_setenv utility. That tool, fw_setenv, is what we need to run in order to gain support for the LED. One such change was to install a utility that can be used to set boot parameters in the bootloader. I mentioned that the bootloader installer also made changes to the Linux installation on the ROM. In Part1, Step 4 I had downloaded and installed a new bootloader, which was written to /dev/mtd0. Without this, my ssh client will complain and prevent me from logging in to the ROM installation on the assumption that there was a spoofing attack going on. The second thing I wanted was to have the ssh host keys synchronized between the Plugbox Linux installation that I would be using day-to-day, and the ROM installation that I planned on keeping as a backup. Once Plugbox was installed, the light would simply turn off after the system had booted and remain off until the next time the system started up. The first of these was proper control over the little LED at the front. There were a couple of things I wanted to have working, just to make the installation complete.
The Dockstar doesn’t have a real-time-clock, which is why it needs an external time source. I placed openntpd ahead of sshd and crond:ĭAEMONS=(syslog-ng network netfs openntpd crond sshd) I prefer to use timezone designations rather than city names. I made sure that the following values were set as I like them: Comments aside, it looks something like this: server I chose not to use the “servers” (plural) configuration command.
Dockstar led plus#
Mine now contains “server” entries for three of my internal servers (all of which are also synchronized) plus one “server” line for us. (since I am located in the US). It is not strictly necessary, but it is a good idea to customize this file. In addition, it can sometimes be uncooperative in its operation. It is small and clean, but it lacks options and basic capabilities that I have come to expect. On the minus side, it is a stripped-down NTP client daemon written by the security fanatics who brought you OpenBSD. On the plus side, it is a stripped-down NTP client daemon written by the security fanatics who brought you OpenBSD.
Dockstar led movie#
It has been decorated with stickers, and given the name Pinback which is a reference to the movie Dark Star. Now that the Dockstar has been tamed, it’s time to teach it to do tricks. In Part 1, I went through the procedure I used to take control of a Seagate Freeagent Dockstar, most of which involved streamlining instructions from other sources.
0 kommentar(er)
