Mirrors/junest
1
0
Fork 0
mirror of https://github.com/fsquillace/junest.git synced 2026-01-23 02:34:30 +00:00
Code Issues Projects Releases Wiki Activity

Fix checks for updating Arch Linux keyrings

Browse source
This commit is contained in:
Filippo Squillace 2017-09-18 14:56:16 +02:00
parent f60bbb5c2a
commit d858d577c8
2 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -46,13 +46,13 @@ The main advantages on using JuNest are:
JuNest follows the [Arch Linux philosophy](https://wiki.archlinux.org/index.php/The_Arch_Way).
How different JuNest is from Docker and Vagrant?
How different is JuNest from Docker and Vagrant?
------------------------------------------------
Although JuNest sounds similar to a virtualisation/Linux container -like system,
JuNest differentiate a lot between Docker and Vagrant.
In fact, the purpose of JuNest is **not** to
build a complete isolated environment but, conversely, is the ability to run
programs as they are running natively from the host OS. Almost everything is shared
programs as they were running natively from the host OS. Almost everything is shared
between host OS and the JuNest sandbox (kernel, process subtree, network, mounting, etc)
and only the root filesystem gets isolated
(as the programs installed in JuNest need to reside elsewhere).

6
lib/checks/check.sh
View file

@ -32,7 +32,11 @@ info "Validating JuNest located in ${JUNEST_HOME}..."
info "Initial JuNest setup..."
echo "Server = ${DEFAULT_MIRROR}" >> /etc/pacman.d/mirrorlist
pacman --noconfirm -Syyu
pacman --noconfirm -Syy
pacman --noconfirm -S archlinux-keyring
pacman-key --init
pacman-key --populate archlinux
pacman --noconfirm -Su
pacman --noconfirm -S grep coreutils
pacman --noconfirm -S $(pacman -Sg base-devel | cut -d ' ' -f 2 | grep -v sudo)