> > *After giving him a configured BBG (he'd have been dead in the water with > the image that came in the BBG eMMC, which really breaks the ideal for a > newbie idea) and showing him how to install the Windows drivers and connect > to the BBG with Chrome web browser, it clearly was a great starting point > for him.* >
Anything of this nature still has a learning curve. Personally, I think things of this nature are a waste of time. Not because they're not handy, or cool. But instead you have to spend a time investment to learn anything. So you may as well learn the "underlying basics" so you're better prepared in the future to deal with more complex problems. So a very quick example . . . Not knowing what Node-RED really is, I'd have to spend a considerable amount of time learning this new "software technology", when I could instead just write my own code and be done with it. Now sure, because I'm an experienced developer, who *now* has a decent bit of javascript / Nodejs experience, this may be easier for me. However, I had to learn all of this, just like anyone else, and in fact I'm by far not a Nodejs "expert". And in fact, I knew very little of Nodejs 3 years ago when we got our first BBB's . . . On Fri, Feb 5, 2016 at 11:54 AM, Wally Bkg <[email protected]> wrote: > I agree that if you plan to have your Beaglebone connected directly to the > Internet the current default setups are woefully inadequate, I'm > comfortable with my IOT stuff behind a solid firewall on a trusted subnet, > but having just setup a friend with a BBG Cloud9 BoneScript and Node-Red > and the USB "gadget", it is a pretty setup to explain and demo. > > Knowing better tools made me ignore it all starting with my Rev A6 BBW, > but when a friend very experienced in electronics, but total newbie at > programming, asked me about Arduino vs. Raspberry Pi vs. Beaglebone -- he > was aware of them all but unsure where to start, I had to play with the > newbie stuff a bit myself before actually recommending anything. > > After giving him a configured BBG (he'd have been dead in the water with > the image that came in the BBG eMMC, which really breaks the ideal for a > newbie idea) and showing him how to install the Windows drivers and connect > to the BBG with Chrome web browser, it clearly was a great starting point > for him. > > > On Friday, February 5, 2016 at 12:27:59 PM UTC-6, William Hermans wrote: >> >> >>> >>> * I very much appreciate the reply. I was accessing Cloud9 through eth0 >>> not usb0 so root access from the network was possible. Were I only >>> accessing the BeagleBone over the usb network I wouldn't have been >>> concerned. However I remotely connected over port 3000 and saw a command >>> line running with root.I tried chasing down the problem but found the >>> Cloud9 IDE just too convoluted to figure out. I tried but failed to change >>> the default user and password in the configuration file referred to in my >>> earlier post. At that point I simply killed Cloud9, and just used Byobu >>> (tmux) terminals to work with node.js.* >> >> >> You're not alone with finding cloud9 too convoluted to even bother >> messing with. Personally, I have years experience with Debian( think over >> 20 ), and am a very experienced programmer in a few different languages. So >> I'm not exactly computer illiterate, and can usually solve most problems >> rather quickly. Not so with the current default base Debian image with >> cloud9 etc. >> >> I actually found it much easier to build my own Debian images from >> scratch, based on Roberts kernel build guide, compiling Nodejs personally, >> and installing it via a package, than using the cloud9 images with >> bonescript, and all that fluff. >> >> I just use a very basic custom image that is less than 200M in size, with >> Nodejs + Express + NPM installed, and then ssh in to write code on a NFS >> share <--- This is so I can edit code for the BBB on a local system running >> Windows, in my editor of choice. VIM, and all that is kind of neat, but is >> not exactly my sort of "thing" . . . >> >> >> On Fri, Feb 5, 2016 at 9:44 AM, Paul Wolfson <[email protected]> wrote: >> >>> I very much appreciate the reply. I was accessing Cloud9 through eth0 >>> not usb0 so root access from the network was possible. Were I only >>> accessing the BeagleBone over the usb network I wouldn't have been >>> concerned. However I remotely connected over port 3000 and saw a command >>> line running with root. >>> >>> I tried chasing down the problem but found the Cloud9 IDE just too >>> convoluted to figure out. I tried but failed to change the default user >>> and password in the configuration file referred to in my earlier post. At >>> that point I simply killed Cloud9, and just used Byobu (tmux) terminals to >>> work with node.js. >>> >>> In the latest build Debian r43 build Cloud9 is not installed by default >>> so it's all good. Robert's little connmanctl tutorial post yesterday made >>> networking much easier than messing with /etc/network/interfaces. >>> >>> ------------------------------------------------- >>> Paul Wolfson, Ph.D., TX LPI, #A17473 >>> Editor, TALI "The Texas Investigator" >>> Dallas Legal Technology >>> 3402 Oak Grove Avenue, Suite 300-A >>> Dallas, Texas 75204-2353 >>> >>> >>> *214-257-0984 (Tel)214-838-7220 (Fax)Send me an email.* >>> ------------------------------------------------- >>> The contents of this email are confidential to the sender and the >>> ordinary user of the email address to which it was addressed, and may also >>> be privileged. If you are not the addressee of the email, you may not >>> copy, forward, disclose or otherwise use it or any part of it in any form >>> whatsoever. If you have received this email in error, please advise the >>> sender at 214-257-0984. Thank you. >>> ------------------------------------------------- >>> >>> On Fri, Feb 5, 2016 at 11:21 AM, Wally Bkg <[email protected]> wrote: >>> >>>> I'm not very experienced with Cloud9 or BoneScript, but as I understand >>>> it, at present BoneScript is only usable for code running as root because >>>> of device driver permissions. Also BoneScript PWM is not working in the >>>> "latest" versions. >>>> >>>> While this is not optimal, adding user permissions into the mix would >>>> likely overwhelm people coming from Arduino. Raspberry Pi currently has >>>> basically the same setup where only root users can use on board hardware, >>>> unless its changed with a new Raspbian release recently. >>>> >>>> Are you accessing Cloud9 via the USB "gadget" or Ethernet (Wired or >>>> WiFi)? I might make a difference. >>>> >>>> >>>> >>>> On Thursday, January 7, 2016 at 3:42:01 PM UTC-6, Paul Wolfson wrote: >>>>> >>>>> I've been using my BBB for some time with Ubuntu 3.8.13-bone30 but >>>>> upgraded to Debian 4.1.12-ti-r29 because of OS stability problems. The >>>>> Cloud9 IDE is back. I opened it and saw a command shell prompt running as >>>>> root@beaglebone. >>>>> >>>>> Does anyone know off the top of their head where the default user is >>>>> set? >>>>> >>>>> I saw this, >>>>> http://stackoverflow.com/questions/28822695/change-the-username-and-add-a-password-for-cloud9-in-the-beaglebone-black >>>>> but >>>>> after changing >>>>> .describe("auth", "Basic Auth username:password") >>>>> to >>>>> .describe("auth", "debian:temppwd") >>>>> >>>>> and rebooting, the Cloud9 bash prompt is still "root@beaglebone:~# ." >>>>> >>>>> [if this is a double post, I apologize] >>>>> >>>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
