Closed ajfisher closed 9 years ago
NB Installing minicom instead of picocom
Does that work with inotool? They had a dependency of picocom on their docs was all...
On Sun Nov 23 2014 at 19:29:16 Alec Clews notifications@github.com wrote:
NB Installing minicom instead of picocom
— Reply to this email directly or view it on GitHub https://github.com/alecthegeek/CCHS_Raspian_for_IoT/issues/12#issuecomment-64110605 .
from reading docs they seem "equivalent", i.e. serial terminal emulation. Should be able to use putty as well I assume :-)
I'll test
All done,
Still needs more tesing
These were the mods I noted as I was building out a clean install for the LCA SimpleBot:
In
https://github.com/alecthegeek/CCHS_Raspian_for_IoT/blob/master/runme2nd#L229-L233
You're doing a global install of johnny-five etc. This has some known issues in terms of version management in moving node modules and it also makes it much harder to run the examples (as they aren't in a project folder). You get a warning about this in the script output:
I'd remove these as they can all be installed in user space very easily. If you keep them then
https://github.com/alecthegeek/CCHS_Raspian_for_IoT/blob/master/runme2nd#L233
Needs to go to raspi-io which is the package.
Once we deploy the LCA SB code it will be as simple as a git clone && node install so that should be cool for that side and pull in all the other package deps anyway.
Some other things I installed: