My Tailscale dashboard shows that the version of Tailscale on my Comet is out of date and needs to be updated. When I click the update button, it complains that an executable couldn’t be found in the usual location. How do you update Tailscale on the Comet?
Hi, please run command tailscale update in Toolbox > Terminal.
The tailscale version won't save after a firmware update. So we need to run this command again after next update in RM1 firmware.
Thank you! That worked perfectly!
needed to restart tailscale by issuing the following: /etc/init.d/S99tailscale restart
I wonder if it would be possible to have a script stored someplace on the device that can be run after firmware updates with the output dumped into the log, that could allow power users to preserve tweaks they made outside of the UI.
/userdata isn’t erased with firmware updates.
If there could be an autorun.sh stored there that would be run on firmware updates that would be a great kludge for power users. Bonus points if there’s an autorun_reboot.sh and autorun_upgrade.sh.
Have to look/play more but I believe with the overlay, you can add your own stuff just about anywhere, as long as it doesn’t edit a file that exists, as those are replaced on firmware updates..
Your reboot script can then do what you want, including edit the ‘OEM’ files.
Or.. What my original thought was.. Power users would just run their script from /userdata after a firmware update, redoing all the changes they want made.
In fact, everything is much simpler.
There is a script /etc/init.d/S99custom in the system.
If you look into it, we will see the following (only important part is shown here):
start() {
for i in /etc/kvmd/user/scripts/S??* ;do
That is, it searches for user scripts in this folder - /etc/kvmd/user/scripts/ (needs to be created manually), which must match the following mask S??*.
So everything is simple, we make a script, call it S20tailscale-update.sh (for example), put it here - /etc/kvmd/user/scripts/, and everything works and survives updates.
This is how I managed to add support for the Wi-Fi USB adapter that I posted about here on this forum.
And the most important thing in your case is that this script is launched just before Tailscale is initialized.
That’s great, and exactly the sort of use case I was thinking of - a script that needs to be run before you can get basic connectivity working. Thanks!
Cool.
I’m sure I would have found that eventually. Haven’t played too much with that aspect, still trying to figure out my EDID issues, if it even is the issue..