You are not logged in.
Holy Crap!!!! I have been at this for days!!! It worked!!!
But I want to take away some learning from this. But I am mostly confused still. Please let me ask some questions before I close the ticket.
1) Is the fact that I installed "Linux Homebrew" and that it runs on my machine gonna be a problem? Should I uninstall it, so I don't get /home-based packages happening and stuff in the "normal" places happening? I mean, is that more of an Apple" way of managing stuff?
( I downloaded and installed it in order to get this to work, originally)
2) I see many "legitimate" sites that suggest the action you are wa3) Hrning against. And I am not AT ALL questioning the logic. Rather, I am trying to get to grips with what I should expect to do as "best practice". And I know it is likely that I should already *know* this....but I don't.
And so I want to get to a place where can see when the "legitimate" sites are doing dumb stuff. Right now, I will take your advice to heart. But I guess with that, I have to figure out plan "B"..which arrives at my 3rd and final question:
3) How can I avoid this in the future? That is where, specifically, did I go wrong? And how can I avoid it in the future?
Thanks.
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
Is it just a matter of the sudo -i and the exit bit? Is that where I screwed up?
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
Should I just give up desktop computing and find another hobby?
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
How can I avoid this in the future?
Both nodejs and npm are available from the official Debian repositories.
Use https://www.debian.org/distrib/packages#search_packages or the system tools to search the repositories.
A simple `apt-get install nodejs npm` would have installed those without ever running the script at all.
Remember: if you can't `apt-get` it, it's probably not worth having
Offline
Is it just a matter of the sudo -i and the exit bit? Is that where I screwed up?
Well, the "bash -" bit was run after a pipe and `sudo` wouldn't apply on the other side of the redirection so yes, a full root shell must be used.
Or:
curl -sL https://deb.nodesource.com/setup_5.x | sudo bash -
As I say, really bad idea though
Offline
A simple `apt-get install nodejs npm` would have installed those without ever running the script at all.
Remember: if you can't `apt-get` it, it's probably not worth having
OMG!!!!
The time, energy, etc. I put into this going about it the wrong way is big, by my standards. This was an expensive lesson.
One wonders, why did I not think to look there before? And why did none of the sites that suggest the download, simply suggest it in this way? [ rhetorical question ]
But I thank you for helping me with this. Someday, when I get big......oh, nevermind.
Thanks.
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
@ perchslayer
Couple of tips before installing anything...
Check the Debian repos to see if you what you want can be got there ( Menu -> Help -> Debian -> Package Search )
Look up the apt commands (`man apt-get` etc). You can see what the outcome of apt-get will be by using the "-s" ( =simulate) switch.
[damo@debian ~]$ sudo apt-get install -s nodejs npm
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
gyp libc-ares-dev libc-ares2 libjs-node-uuid libjs-underscore libssl-dev libssl-doc libv8-3.14-dev
libv8-3.14.5 node-abbrev node-ansi node-ansi-color-table 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-underscore node-which nodejs-dev
I have to admit I didn't check the repos earlier - I just assumed you were having to install it from somewhere else
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Thank you again. This is really good stuff. From now on, that is my plan. But by now, gosh, I have plenty of "stuff", but I just need to know how to use it.
BTW, this new text editor called Atom is really nice for those of us like myself that don't have the keyboard chops down for VIM or Emacs. And it has some nice slick advantages over Geany too. And it installs on BL without a hiccup or hitch.
So if you hear of anyone like me who needs to "get in the game" and get started, you might let them know. Just thought I would mention.
https://atom.io/docs/v0.194.0/getting-s … lling-atom
Peace and out.
Roland Shield
n00b 2.x
ass.clown@perchslayer.com | "...'ere I am, J.H."
Offline
Right, the script needs to be run as root, which is not very wise at all.
Use:
sudo -i apt-get purge bunsen-os-release curl -sL https://deb.nodesource.com/setup_5.x | bash - apt-get install nodejs apt-get install bunsen-os-release exit
Generally speaking, you should *never* download and run random scripts as root.
Thanks alot, that worked for me. I even was able to install Angular/latest, but only if I choose
... curl -sL https://deb.nodesource.com/setup_6.x | bash - ...
I was curious, what it means:
sudo -i
but I was able to return (from root) to regular account after several? "exit" in terminal.
Offline
As a fellow node.js developer on Bunsenlabs, what I do on a fresh install is using NVS. No need to start anything as sudo, install work wonderfully, and you have the added bonus of being able to switch node.js version at will.
Offline
D219 suggestion looks great, I use a similar thing vor python.. but I want to intall npm.
$ sudo apt-get install npm
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package npm
HALP
Offline
Do it this way:
sudo apt-get install nodejs-legacy
sudo ln -s /usr/bin/nodejs /usr/sbin/node
Then , if you want the latest node (for security audits) do:
sudo npm install npm@latest -g
Offline
Do it this way:
sudo apt-get install nodejs-legacy sudo ln -s /usr/bin/nodejs /usr/sbin/node
Then , if you want the latest node (for security audits) do:
sudo npm install npm@latest -g
done that, the last line gives me:
sudo: npm: command not found
--
Also, if I may ask: Why the nodejs-legacy, but not the nodejs package?
Offline
Maybe this would work better:
https://nodejs.org/en/download/package- … tributions
Offline
If you intend to do node.js development in the long run, you may want to use a version manager. This will allow you to switch node.js versions easily when working on different projects, and upgrade as new stable versions of node are released.
@D219 mentioned NVS, another option widely used in the industry and maintained is nvm. Also, simple to install, as long as you're ok to `curl something | bash`
Thinkpad X1Carbon 3rd Gen | BunsenLabs Deuterium
Thinkpad X250 | BunsenLabs Deuterium
Thinkpad X1Carbon 1st Edition | CrunchBang Waldorf r20121015
Thinkpad X240 | Wally <-- don't buy that & Eee-PC 1000H | CrunchBang Statler r20110207 Openbox
Offline
Moderator, moving to GUI & Applications
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline