How to remove Cloud9 - files from BBB

GoogleGroups
21

The eMMC is in a safe state at that point. The pmic doesn't seem to
always listen to use too shutdown.

Regards,

22

Robert,

So far so good!

I set a root password, created a regular user account, ran apt-get update & upgrade.

I’ve installed the following packages:
avahi-daemon nodejs nodejs-legacy nom ntp git man-db

I used dpkg-reconfigure tzdata to set my timezone information, configured git, and I should be good to go.

However, I don’t see a dtc command. Should this not be included in the initial image? It seems pretty fundamental to using the BBB!

Max

23

Nah, it's not essential to boot or flash the eMMC, thus it's not
installed on the console image.

sudo apt-get install device-tree-compiler

Regards,

24

Robert,

Thanks, I found the right package while waiting for my post to be moderated. A bit worried that I might not get the 1.4.0 version with the -@ switch, as the man pages don’t mention it, but the built-in help does. I see it came from a beagleboard repository. Looks like like I’m good to go now.

Thanks for all your help!

Max

25

If you are really need the space, start out with the “console” flasher:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-19

(200MB)

Then:

sudo apt-get update
sudo apt-get install nodejs nodejs-legacy npm

Regards,

–
Robert Nelson
http://www.rcn-ee.com/

sudo apt-get install nodejs nodejs-legacy npm seems to be currently broken. You, or at least I have been getting circular unresolved paackages. Deadending at…

root@arm:~# apt-get install nodejs nodejs-legacy npm
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
npm : Depends: node-gyp (>= 0.10.9) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@arm:~# apt-get install node-gyp
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
node-gyp : Depends: nodejs-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@arm:~# apt-get install nodejs-dev
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nodejs-dev : Depends: libv8-3.14-dev (>= 3.7) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

26

W: GPG error: http://debian.beagleboard.org wheezy-bbb Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY B2710B8359890110

27

Ok, so the only thing I can think that may have happened here is that I used backports to install systemd. Since this is the first time ive used backports, im not sure if there is anything I should have done after installing systemd, such as disabling the repo in sources.list ?

Anyway, I’ve reverted my rootfs to a prior state, and am going a different route now. Without backports or systemd installed.