Author Topic: Linux woes - share RPi image?  (Read 5968 times)

labusr

  • NewMember
  • *
  • Posts: 34
Linux woes - share RPi image?
« on: March 18, 2014, 11:22:02 PM »
I haven't had much luck with trying to get node.js part of the Raspberry Pi home automation demo working.  Would anyone be willing to share their Raspberry Pi image of a working demo perhaps?

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Linux woes - share RPi image?
« Reply #1 on: March 19, 2014, 07:15:16 AM »
I might share mine but need some time to slim it down, change some settings, password etc.
Will have to see where I can dump it, not sure if google drive will host such a large file.
Stay tuned.

labusr

  • NewMember
  • *
  • Posts: 34
Re: Linux woes - share RPi image?
« Reply #2 on: March 19, 2014, 10:28:24 AM »
I might share mine but need some time to slim it down, change some settings, password etc.
Will have to see where I can dump it, not sure if google drive will host such a large file.
Stay tuned.

Thanks Felix, I've been knocking my head against the wall with Linux.  I'd really appreciate it!

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Linux woes - share RPi image?
« Reply #3 on: March 22, 2014, 09:02:51 PM »
Ok finally I got some time to get around to do this.
I shared a 4GB image in my google drive: https://drive.google.com/file/d/0B89HtwH5i2d0ODdMQVdQY25hSTg/edit?usp=sharing
All user:passwords should be pi:raspberry
This is DHCP and it runs the GarageMote example

labusr

  • NewMember
  • *
  • Posts: 34
Re: Linux woes - share RPi image?
« Reply #4 on: March 22, 2014, 09:07:53 PM »
THANK YOU SO MUCH!  Really.

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Linux woes - share RPi image?
« Reply #5 on: March 22, 2014, 09:34:54 PM »
You're welcome. I must warn that I have had trouble restoring an image to other types of SD cards because of slightly different sizes. So if you try a 4GB card and it won't fit, then the only other way is to try a 8GB card. Sorry but I don't know how to get around this.

charlieroot

  • NewMember
  • *
  • Posts: 13
Re: Linux woes - share RPi image?
« Reply #6 on: November 02, 2014, 10:36:37 PM »

Was anyone able to boot this image? I wrote it to the same 8gb card I've been using already but it wouldn't boot for me.


Big Country

  • NewMember
  • *
  • Posts: 2
Re: Linux woes - share RPi image?
« Reply #7 on: November 16, 2014, 02:49:24 PM »
I was unable to get the file from Google drive to work on:

1. raspi B+ w/16Gb card
nor
2. raspi B w/8Gb card

Two separate computers downloading/unzipping/writing to card
 :(

Following the instructions on the gateway-setup page, I can get all the way to the end with no problems except...
When running:
Code: [Select]
node chat.js &
It throws an error within Chat.js 
Code: [Select]
io.configure(function () {    
^ typeerror: object #<server> has no method 'configure'


From what I've read around the web, io.configure isn't supported anymore, but I've been unable to get the sample code fixes to work for this problem.

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Linux woes - share RPi image?
« Reply #8 on: November 16, 2014, 06:18:38 PM »
At some point I will do a complete reinstall with the latest sources that I can get. But typically that takes 2-3 shots before I can do it cleanly from start to end, and it's very time consuming, especially with documentation. For now I don't have another solution. There were other threads in the forum where people talked about getting node to work and shared their issues/solutions. From what I can recall it is mostly a wrong path somewhere or missing step/configuration.

charlieroot

  • NewMember
  • *
  • Posts: 13
Re: Linux woes - share RPi image?
« Reply #9 on: November 16, 2014, 06:30:23 PM »

I seemed to get lots of node/socket.io/serialport errors during install.

I used this package and it solved my issues...

sudo wget http://node-arm.herokuapp.com/node_latest_armhf.deb
sudo dpkg -i node_latest_armhf.deb

After I got that package installed (installing socket.io and serialport via npm worked flawlessly now), I still had the same io.configure problem you have Big Country. You can comment out those lines to get it working.

If you still need further help, let me know. I'll even image up my SD if you like.


ColinR

  • Full Member
  • ***
  • Posts: 176
Re: Linux woes - share RPi image?
« Reply #10 on: November 18, 2014, 06:27:48 PM »
Out of curiosity, why node? It seems like with most available code being in python, people would be using it server side with standard stuff like apache, wsgi, even flask. There are so many ways to implement a REST API without node.

Colin
CuPID Controls :: Open Source browser-based sensor and device control
Interfaceinnovations.org/cupidcontrols.html
cupidcontrols.com

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Linux woes - share RPi image?
« Reply #11 on: November 18, 2014, 09:52:35 PM »
I guess preference, some experience, and the features. Plus .. it's javascript (heart) :)

ColinR

  • Full Member
  • ***
  • Posts: 176
Re: Linux woes - share RPi image?
« Reply #12 on: November 19, 2014, 01:36:41 AM »
I love javascript as much as the next guy (and I write plenty of it), but everybody knows it belongs on the client! Except you node nuts. :)

I'll pollute your airwaves with some RPi gateway based on python shortly.

C
CuPID Controls :: Open Source browser-based sensor and device control
Interfaceinnovations.org/cupidcontrols.html
cupidcontrols.com

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Linux woes - share RPi image?
« Reply #13 on: November 19, 2014, 07:43:03 AM »
I started with python in my early days of Moteino and RaspberryPi. Eventually moved to node. I don't think there's anything wrong with server javascript.
If you coded in COBOL then we could have a debate but other than that it's like anything else - use whatever works and makes you productive. And if code amount is less, that's a plus.
I stumble upon debates between Eagle and Kicad and people have very strong opinions. I'm like ... MEH. It really doesn't matter, what makes you productive is more important.

ColinR

  • Full Member
  • ***
  • Posts: 176
Re: Linux woes - share RPi image?
« Reply #14 on: November 19, 2014, 02:36:35 PM »
I don't think that there's anything wrong with it, and I certainly agree that you should use what works best for you. Shoot, if it's good enough for LinkedIn, it's good enough for something. I'll leave the debate about apps that are ideal and not for node to others. That said, you won't catch me using JS server-side (or python client-side).

I think the analogy with an EDA like Eagle vs. KiCAD is not a great one, however. When you are done using your circuit editor, you get a set of files that are exactly the same regardless of where they came from, and the end product is a PCB which can't tell you which editor designed it. So the productivity thing is just your personal preference.

When designing an ecosystem for development, you're creating something for others to use. I think it's hard to ignore that the vast majority of the libraries for the Pi (and linux embedded systems in general) are written in Python these days. On top of that you'll find much more familiarity (and support) within the community for the standard LAMP stack. As I've said before, pushing boundaries of existing technology is where innovation is born. For me, it's just recognizing a time and place to do so.

C
CuPID Controls :: Open Source browser-based sensor and device control
Interfaceinnovations.org/cupidcontrols.html
cupidcontrols.com