How to remove Cloud9 - files from BBB

[heidin...@googlemail.com]

Hello,

how can I remove the files from Cloud9 completely from my BBB. 

I have installed Debian on my BBB A6A 2GB and running out of space. I've already disabled Cloud9 and Bonescript with systemctl. Of course the files are still there. 

dpkg - l *cloud9* or apt-get remove cloud9 dosen't work.

The files are in the /opt/ folder. Can I remove them directly from there? 

Thanks!

Juergen

[William Hermans]

root@beaglebone:~# du -h /opt/cloud9/
...
58M     /opt/cloud9/

root@beaglebone:~# du -h /var/lib/cloud9/
...
53M     /var/lib/cloud9/

So this is a guess on my behalf but I'm betting a good bet. /opt/ is where the git was pulled to, and /var/lib is where it is run from. Opening cloud9 in the browser, and looking at the command prompt seems to confirm this.

So, if dpkg, and APT both have no clue about this, and you've disabled the service. I personally see no harm in using rm. I even ran "whereis cloud9" and nothing . . .

What all are you running that requires 1.7G space on the eMMC ?

--
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 beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Syn]

From: <heidin...@googlemail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Thursday, August 28, 2014 at 11:47 AM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: [beagleboard] How to remove Cloud9 - files from BBB

Hello,

how can I remove the files from Cloud9 completely from my BBB. 

I have installed Debian on my BBB A6A 2GB and running out of space. I've already disabled Cloud9 and Bonescript with systemctl. Of course the files are still there. 

dpkg - l *cloud9* or apt-get remove cloud9 dosen't work.

This only lists packages matching *cloud9* pattern. If you want to find which files were installed, use 

dpkg -L <package name found previously>

Also, you can use 

sudo apt-get purge <package name found previously>

Which is the same as remove, but also deletes the config files.

Regards,

John

The files are in the /opt/ folder. Can I remove them directly from there? 

Thanks!

Juergen

--

[m...@zepler.org]

On Thursday, 28 August 2014 21:01:17 UTC+1, William Hermans wrote:

What all are you running that requires 1.7G space on the eMMC ?

Erm... Debian?

I found the free space left on rootfs after an eMMC flash from BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img; apt-get update;  apt-get upgrade; apt-get clean was 132628 blocks, 92% free. Trying to install the application (node-RED) I want to run and its dependencies failed with ENOSPC

Deleting the tmp files from the failed npm installs leaves me 30256 blocks free. Unusable. The node.js version on the Angstrom image is too old to support all the packages I want to use.

Max

[John Syn]

From: <heidin...@googlemail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Thursday, August 28, 2014 at 11:47 AM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: [beagleboard] How to remove Cloud9 - files from BBB

man dpkg or dpkg —help will give you all the info you need.

Regards,

John

[William Hermans]

Max, the reason why I ask is that I am running Debian too, and have a rootfs that is 191M ( Megabytes ) in size. This includes a few standard debian tools such as openssh-server, and then Nodejs + express + socket.io. With a basic Nodejs server example app I'm working on.

--

[Robert Nelson]

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/

[William Hermans]

John, there is no package. It is downloaded from git, compiled, and installed by hand.

[William Hermans]

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,

Not sure why npm is a separate package, unless this is a super old version of node. When you build from source npm is built and installed along with Nodejs( latest source ive built )

[m...@zepler.org]

On Thursday, 28 August 2014 21:56:50 UTC+1, RobertCNelson wrote:

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

Now I'm getting really confused! I just followed the instructions on the 'latest images' page (http://beagleboard.org/latest-images). Do these apply only to rev C boards? It doesn't say. I did look for more recent images, but I find the information on elinux.org to be terse and opaque to the point of impenetrability. These are testing images, so presumably not stable? Why am I still referred to the 2014-05-14 image if this is known not to work?

For my project, In addition to the standard OS & I need a node.js >= 0.10.22, plus bonescript (but used as a package, not as a server) gcc, libraries etc plus apache, but not cloud9, X-windows, or anything to do with video or sound. I have a rev C on back order, but I'd like to hope the rev B can be salvaged for this project.

Max

[Robert Nelson]

> Not sure why npm is a separate package, unless this is a super old version
> of node. When you build from source npm is built and installed along with
> Nodejs( latest source ive built )

It's a debian thing.. Officially npm is "now" integrated into nodejs
download.. But in debian the nodejs package is built with npm disabled
and thus npm is packaged separately.

[William Hermans]

For what it is worth to anyone else reading this. npm is the only package manage to use on ARM platform devices. As other package managers, namely nvm do not seem to do architecture checking / segregation.

[William Hermans]

Sorry not nvm, that would be the nodejs version manager. I can not think of the other semi popular node package manager that seemed to enjoy downloading i386 source onto my BBB a few months back.

[John Syn]

From: William Hermans <yyr...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Thursday, August 28, 2014 at 1:57 PM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] How to remove Cloud9 - files from BBB

John, there is no package. It is downloaded from git, compiled, and installed by hand.

I only mentioned that because he was using dpkg -l *cloud9*

Regards,

John

[Robert Nelson]

On Thu, Aug 28, 2014 at 4:09 PM, <m...@zepler.org> wrote:
>
> On Thursday, 28 August 2014 21:56:50 UTC+1, RobertCNelson wrote:
>>
>> 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
>>
> Now I'm getting really confused! I just followed the instructions on the
> 'latest images' page (http://beagleboard.org/latest-images). Do these apply
> only to rev C boards? It doesn't say. I did look for more recent images, but
> I find the information on elinux.org to be terse and opaque to the point of
> impenetrability. These are testing images, so presumably not stable? Why am
> I still referred to the 2014-05-14 image if this is known not to work?

"testing" =/= "unstable"

They are just snapshots of a continuously evolving "image".. At some
point, we will cut a new release based off these and then fully test
and put it on http://beagleboard.org/latest-images

> For my project, In addition to the standard OS & I need a node.js >=
> 0.10.22, plus bonescript (but used as a package, not as a server) gcc,
> libraries etc plus apache, but not cloud9, X-windows, or anything to do with
> video or sound. I have a rev C on back order, but I'd like to hope the rev B
> can be salvaged for this project.

Okay, follow my previous instructs and add:

npm install -g bonescript --arch=armhf

[William Hermans]

Max, you're better off either starting with the console image Robert mentioned, or building your own from https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-RootFileSystem%28smallflash%29

Once you get the console image going, it is a simple matter of apt-get install <packages>

--

[m...@zepler.org]

Wiiliam,

I am just this moment following the procedure Robert suggests, using the 2014-08-19 console image. I'll dump a list of packages installed in the 2014-05-14 'full' image installation before I re-flash it so I can compare what is in and what is not. I'm not in a position to build anything just yet - no free disc space!

Max

[m...@zepler.org]

Robert,

Does this flasher not power down the Beaglebone when it's done? It's sitting there with all 4 user LEDS on at the moment

Max

[William Hermans]

Even using the console image Robert and I suggested, you'll gain back a lot more space on the eMMC.

Also note that Roberts instruction for building from scratch / source is done on a PC and not the BBB. But is more complex, and does pretty much require Linux on that machine. I only mention this in case you're thinking it has to be done on the BBB.

There is also another method for making your image smaller( without building from source ), but is complex and requires mix / matching files / directories from multiple sources. I'm still investigating this myself, so could not get into too much detail. Except that /var/modules is not fully populated in debian-7.5-bare-armhf-2014-07-07.tar.xz. So if you need specific modules . . .This could prove to be a minor pain in the butt at minimum. Systemd also lives in this directory.

[William Hermans]

Err, rather Systemd lives in /lib/

[Robert Nelson]

On Fri, Aug 29, 2014 at 3:16 PM, <m...@zepler.org> wrote:
> Robert,
>
> Does this flasher not power down the Beaglebone when it's done? It's sitting
> there with all 4 user LEDS on at the moment

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

[m...@zepler.org]

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

[Robert Nelson]

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

[m...@zepler.org]

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

[William Hermans]

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.

 

[William Hermans]

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

[William Hermans]

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.

On Mon, Sep 8, 2014 at 11:09 PM, William Hermans <yyr...@gmail.com> wrote:

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