One more thing noted: *root@beaglebone:~# apt-get remove xserver-xorg-core* > *Reading package lists... Done* > *Building dependency tree* > *Reading state information... Done* > *The following packages were automatically installed and are no longer > required:* > * am335x-pru-package gyp javascript-common libjs-node-uuid libsoc2 > libv8-3.14-dev libv8-3.14.5 node-abbrev node-ansi* > * node-archy node-async node-block-stream node-combined-stream > node-cookie-jar node-delayed-stream node-forever-agent* > * node-form-data node-fstream node-fstream-ignore > node-github-url-from-git node-glob node-graceful-fs node-gyp* > * node-inherits node-ini node-json-stringify-safe node-lockfile > node-lru-cache node-mime node-minimatch node-mkdirp* > * node-mute-stream node-node-uuid node-nopt node-normalize-package-data > node-npmlog node-once node-osenv node-qs* > * node-read node-read-package-json node-request node-retry node-rimraf > node-semver node-sha node-sigmund node-slide* > * node-tar node-tunnel-agent node-which nodejs nodejs-dev nodejs-legacy > npm wwwconfig-common xinput-calibrator* > *Use 'apt-get autoremove' to remove them.* > *The following packages will be REMOVED:* > * beaglebone xserver-xorg xserver-xorg-core xserver-xorg-input-all > xserver-xorg-input-evdev* > * xserver-xorg-input-synaptics xserver-xorg-input-wacom > xserver-xorg-video-fbdev xserver-xorg-video-modesetting* > *0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded.* > *After this operation, 4127 kB disk space will be freed.* > *Do you want to continue [Y/n]? n* > *Abort.* >
Since when is X11 a requirement for *ANY* Nodejs package ? I'd have a assume these packages were somehow installed from within X that made such a requirement ? Either way, this is bad mojo. On Fri, Aug 22, 2014 at 9:04 PM, William Hermans <[email protected]> wrote: > Jason, Ok cloud9 seems to be functional, and I have to say this is pretty > awesome. Where can I find documentation on how you have this setup ? > > Ok moving on to the other things for this image. First, there is no > uEnv.txt file *period*. We have bbb-uEnv.txt, and nfs-uEnv.txt. Neither one > of these will work, because I have the original uboot from an A5A. So, I > follow Roberts build from source instructions, so I know how to deal with > this. Someone else may not, but this is a testing image after all - I guess. > > I'm still poking around, but I disabled HDMI in uEnv.txt, and the image > now seems to be more responsive. networking interfaces still seems flaky, > but im in the process of purging wicd wpasupplicant etc. > > > On Fri, Aug 22, 2014 at 10:12 AM, William Hermans <[email protected]> > wrote: > >> I did check port 3333, as that is what I had set for my own cloud9 build >> that never realty worked. But the port I used was based off the >> instructiond on the cloud9 git as far as i remember. >> >> I'll definitely look into hacking in that cloud9 build, and it seems I'll >> be building from scratch somewhat anyway. As my hackfest yielded less than >> optimal results. The barefs the way I set it up was 108M, and with >> openssh-server around 144M >> >> >> On Fri, Aug 22, 2014 at 10:01 AM, Jason Kridner <[email protected]> >> wrote: >> >>> >>> >>> On Friday, August 22, 2014, Robert Nelson <[email protected]> >>> wrote: >>> >>>> On Fri, Aug 22, 2014 at 9:56 AM, William Hermans <[email protected]> >>>> wrote: >>>> >> You mean, you needed to wait for the device to boot and the server to >>>> >> start? >>>> > >>>> > >>>> > No, I mean I got "invalid login" when trying to login via ssh. >>>> Period. >>>> > Perhaps it could have been the key generation Robert mentioned above. >>>> As I >>>> > had to make an adjustment to the interfaces file( from the host ). >>>> When I >>>> > rebooted, it worked. >>>> > >>>> > >>>> >> Browsing to http://<IP>:3000 didn't work for you? >>>> > >>>> > >>>> > NO port 80, and 8080 only. I did not try port 3000 as the error i >>>> pasted >>>> > above indicated that Nodejs was somehow listening on port 80. >>>> >>>> Port 80: is bonescript (nodejs) >>> >>> Port 3000: is cloud9 (nodejs) >>> >>> >>> I think it might be worth me seeing if bonescript could be more tightly >>> integrated with cloud9 as an option such that cloud9 could move to port 80. >>> not sure what those guys use for HTML content preprocessing. >>> >>> >>>> Port 8080: is apache2 >>>> >>>> Regards, >>>> >>>> -- >>>> Robert Nelson >>>> http://www.rcn-ee.com/ >>>> >>>> -- >>>> 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.
