$ npm ls -gp --depth=0 | awk -F/ '/node_modules/ && !/\/npm$/ {print $NF}' | xargs npm -g rm| #!/usr/bin/env bash | |
| npm ls -gp | awk -F/ '/node_modules/ && !/node_modules.*node_modules/ {print $NF}' | xargs npm -g rm |
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
Add to ~/.profile
export PATH=~/.npm-global/bin:$PATH
source ~/.profile
| ============= FOR LINUX ============= | |
| Taken from: | |
| https://github.com/sindresorhus/guides/blob/master/npm-global-without-sudo.md | |
| 1. Create new global folder : mkdir GlobalNodeModule | |
| 2. Create .npm-packages file inside : mkdir GlobalNodeModule/.npm-packages | |
| 3. Edit npmrc to point to your new global folder: | |
| prefix=/path/to your/folder/.npm-packages # space in folder name is a non-issue | |
Our goal here is to have one USB stick to rule them all. Objectives:
- We want a full system - not a live CD
- We want to boot this system on a Macbook Pro (requires UEFI)
- We want to boot this system on a Acer C720 Chromebook (requires Legacy BIOS support)
- We want the system "functional"
The last bullet is subject to interpretation, but I'm defining functional as:
- X Windows works (with LXDE)
There are multiple ways to get a full disk encrypted arch linux system on raspberry. In this tutorial, we will install a 64-bit arch linux armv8 system, using dropbear as ssh server for remote pre-boot unlocking of the root filesystem. However, it will still be possible to unlock and use the pi as usual, with a keyboard and monitor. We will also create an unencrypted partition in the installation process, usable as a rescue system.
Differences to the 32-bit arch linux arm version:
- probably better performance
- can run 64-bit software
- comes without the proprietary video-driver blobs
Some computers don't work out of the box. For example, my laptop needs the kernel parameter pci=nommconf to be able to use the wifi.
- Copy the Arch Linux ISO into a USB drive:
This guide created mostly as a summarizing note of installation process rather than guide itself, so it may lack descriptions and may not be applicable in some specific cases. Mostly based on [Arch Wiki][arch-wiki] and four years of Arch daily usage, some concepts and solutions taken from [this][bullet-proof] incredible guide. It is highly recommended and sometimes important to carefully read and understand it; all it's assumptions also applicable in this guide, such as risk of data loss understanding.
Firstly, define some environment variables - to avoid mistyping and save some time:
Again: follow this guide only if you are fully understand what are you going to do. I am not responsible for any losses and software or hardware damage.