View Single Post
Old 04-17-2016, 05:17 AM   #5
stevepar
Junior Member
stevepar began at the beginning.
 
Posts: 5
Karma: 10
Join Date: Apr 2016
Device: Kindle Paperwhite
Thank you eschwartz

To be frank, I find the sticky just a tad too difficult to follow.

If I just run the code [sudo -v && wget -nv -O- https://github.com/eli-schwartz/cali...e-installer.sh | sudo sh -] I get the following output:

sudo -v && wget -nv -O- https://github.com/eli-schwartz/cali...e-installer.sh | sudo sh -
[sudo] password for steven:
2016-04-17 15:34:44 URL:https://raw.githubusercontent.com/el...e-installer.sh [2530/2530] -> "-" [1]
sh: 76: [[: not found
sh: 81: [[: not found
2016-04-17 15:34:46 URL:https://raw.githubusercontent.com/el...bre-upgrade.sh [2727/2727] -> "/usr/bin/calibre-upgrade.sh" [1]
sh: 88: [[: not found
Systemd not found, falling back on cron for scheduling.
Installing cron job...
no crontab for root

Later in the same post I see the script attached as a tarball. Looking at calibre-upgrade.sh.tar.gz I see it contains calibre-upgrade.sh as indicated in the post. Having looked in /usr/bin/ I can see the script has already been copied into that folder as an executable. Presumably, therefore, the calibre-upgrade.sh.tar.gz is just an optional method of adding the script to /usr/bin/.

Looking at the output generated by running [sudo -v && wget -nv -O- https://github.com/eli-schwartz/cali...e-installer.sh | sudo sh -] that would appear to indicate that as there is no crontab for root, the script won't automatically run unless I create a crontab for root, would that be fair to say?

Thanks for any further elucidation.
stevepar is offline   Reply With Quote