I can see multiple ways to approach this, maybe it would be best to start from the console image, and install everything needed, manually, then giving you all the instructions needed to duplicate ? Or i could just do another blog post if there is not enough call to make a completely different image to host.
Again, I do not know who else cares enough about their BBB images to want this. Personally, I do not need this myself technically( I do think its pretty cool ), but I can see where it would / could come in handy for many people at work, or school, etc. On Sat, Aug 23, 2014 at 6:54 PM, William Hermans <[email protected]> wrote: > Robert, ok, cool. I've created packages before, and one recently for > Nodejs. This is how my own 3.8.13-bone47 + barefs is so small with Nodejs + > express + socket.io. I would not be above doing the same for this cloud9, > and sharing the information in one way or another. > > I'm still very newb with git, and several aspects of "embedded" Linux, > Nodejs, etc. SO learning how to create a diff patch, etc . . . well let me > just say it is something i want to learn, but need the time. I will look at > all the relivent information you've given here, and see what I can come up > with on my own. Then I'll perhaps ask specific questions when / if I need > to. > > To this point: > > > *Otherwise, anytime you remove something auto installed by "beaglebone"* >> * it'll show one of above as "The following packages were automatically* >> * installed and are no longer required"* >> > > Yeah I get that, the "use autoremove" etc, but did not realize it was a > package created by you all. I see that it was now. I know that dpkg, and > perhaps apt too ( pretty sure aptitude could handle it as well ) can flag > packages as required for whatever, thus leaving the packages safe from > autoremove. However, I am still not 100% sure what cloud9 needs to run > properly. > > I do know that using APT as discussed previously *will* break cloud9. It's > still there looking all pretty, but the console does not work and the > premeade project files are all gone. > > Anyway, I'll work on this a little at a time as I think this is something > others will want too. I'm not sure if anyone else cares about what else is > running on the BBB, but i do . . .I'll have to toss together a NFS root > test "jig" for this so it may not be right away. > > > On Sat, Aug 23, 2014 at 5:51 PM, Robert Nelson <[email protected]> > wrote: > >> On Sat, Aug 23, 2014 at 6:39 PM, William Hermans <[email protected]> >> wrote: >> >> wicd handles eth0, so re add it to /etc/network/interfaces >> > >> > >> > Already had, but something, I'm assuming wicd was causing problems. >> Routing >> > was not being setup correctly. However, I was not 100% exactly what was >> > causing these issues as setting hwdaddr as suggested in the interfaces >> file >> > seemed like it could have been the cause as well. >> >> try: >> >> apt-get wicd* --purge >> >> > apt-get purge wpasupplicant && apt-get autoremove --purge >> > >> > Seemed to work just fine for me. But I do not need / use a wifi >> device.*YET* >> > >> > So, I suppose I do not get the purpose of these testing images if it is >> not >> > to let you, and the other maintainers know what we find wrong with >> them. I >> > have no problem making something work for myself usually, and would not >> even >> > have a problem creating patches. If I knew how. >> >> No you get the purpose, i just don't know how to fix the bone101, and >> the meta "beaglebone" package is one i don't really want to fix, this: >> >> >> The following packages were automatically installed and are no longer >> >> required: >> * >> >> The following packages will be REMOVED: >> >> I'd have to change the pkg to install from: >> >> beaglebone >> >> to: >> >> 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 xserver-xorg-video-modesetting >> >> Otherwise, anytime you remove something auto installed by "beaglebone" >> it'll show one of above as "The following packages were automatically >> installed and are no longer required" >> >> > Personally I would like to see a "minimal" console image without a lot >> of >> > bloat, that has this very awesome looking cloud9 version working. But if >> > that not your goal or the goal of beaglebone.org, then I suppose I >> could >> > just get something working for myself and continue on my merry way. >> Again, I >> > usually have no problems getting things I want done - done. >> >> That's the 'console' one here: >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-19 >> >> We've had requests from everything small -> to full.. Can't make them >> all, but i think the 'console' and 'lxde' is a happy medium. (console >> is 200Mb) >> >> To get cloud9 working on the 'console', you'd have to "sudo apt-get >> install nodejs nodejs-legacy npm" however the cloud9 bit hasn't been >> packaged so you still have to do this part by hand: >> >> >> https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org.sh#L238 >> >> > I will try to see if I can figure out your build script here, and see >> if I >> > can make it so those of us who use autoremove do not have to worry about >> > trashing our tools. >> >> 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.
