Clone/future-install-scripts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
93b3298147
future-install-scripts/pacstrap.in

94 lines
2.3 KiB
Plaintext
Raw Normal View History

initial commit
2012-06-18 03:17:10 +08:00
#!/bin/bash
#
# Assumptions:
# 1) User has partitioned, formatted, and mounted partitions on /mnt
# 2) Network is functional
# 3) Arguments passed to the script are valid pacman targets
# 4) A valid mirror appears in /etc/pacman.d/mirrorlist
#
add proper help/usage for tools
2012-06-18 05:52:39 +08:00
shopt -s extglob
Create a project Makefile * the Makefile uses m4 to build the common lib into the scripts * it includes install, uninstall and clean targets * the dist target creates a source tar from a tag Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-06-18 17:07:37 +08:00
m4_include(common)
initial commit
2012-06-18 03:17:10 +08:00
pacstrap: store cache on target system by default However, add a '-c' switch to use the host cache instead. The default is useful for when installing a system from an install media (which has possibly constrained storage), but the '-c' switch is useful when e.g. creating build-chroots. I considered doing this the other way around ('-c' being the default). However, I think it makes sense to default to the expected behavior for install both because a new user is less likely to know that they need to add a switch, and because the errormessage they'd get when they run out of space/memory is nonsensical and would cause lots of annoying questions. [dave: use proper array addition, nuke readlink, use arithmetic flag] Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-23 01:14:09 +08:00
newroot=/mnt
reverse default and set values for hostcache option
2012-07-14 21:33:46 +08:00
hostcache=0
initial commit
2012-06-18 03:17:10 +08:00
add proper help/usage for tools
2012-06-18 05:52:39 +08:00
usage() {
cat <<EOF
enforce user-specified root directory Remove the -r option, forcing the user to explicitly pass a root directory. This removes some confusion wherein we set defaults, but wouldn't allow all the defaults to be accepted. This also adds some mild documentation to the help output for genfstab and pacstrap.
2012-07-15 22:04:49 +08:00
usage: ${0##*/} [options] root [packages...]
add proper help/usage for tools
2012-06-18 05:52:39 +08:00
Options:
pacstrap: store cache on target system by default However, add a '-c' switch to use the host cache instead. The default is useful for when installing a system from an install media (which has possibly constrained storage), but the '-c' switch is useful when e.g. creating build-chroots. I considered doing this the other way around ('-c' being the default). However, I think it makes sense to default to the expected behavior for install both because a new user is less likely to know that they need to add a switch, and because the errormessage they'd get when they run out of space/memory is nonsensical and would cause lots of annoying questions. [dave: use proper array addition, nuke readlink, use arithmetic flag] Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-23 01:14:09 +08:00
-c Use the package cache on the host, rather than the target
enforce user-specified root directory Remove the -r option, forcing the user to explicitly pass a root directory. This removes some confusion wherein we set defaults, but wouldn't allow all the defaults to be accepted. This also adds some mild documentation to the help output for genfstab and pacstrap.
2012-07-15 22:04:49 +08:00
-d Allow installation to a non-mountpoint directory
pacstrap installs packages to the specified new root directory. If no packages
are given, pacstrap defaults to the "base" group.
add proper help/usage for tools
2012-06-18 05:52:39 +08:00
EOF
}
if [[ -z $1 || $1 = @(-h|--help) ]]; then
usage
exit $(( $# ? 0 : 1 ))
fi
pacstrap/arch-chroot: require root privileges to run Suggested by Pierre. This makes sense since somewhere along the line, pacman or mount are going to complain.
2012-06-19 20:12:20 +08:00
(( EUID == 0 )) || die 'This script must be run with root privileges'
enforce user-specified root directory Remove the -r option, forcing the user to explicitly pass a root directory. This removes some confusion wherein we set defaults, but wouldn't allow all the defaults to be accepted. This also adds some mild documentation to the help output for genfstab and pacstrap.
2012-07-15 22:04:49 +08:00
while getopts ':cd' flag; do
initial commit
2012-06-18 03:17:10 +08:00
case $flag in
pacstrap: add -d option to allow install to non-mount
2012-06-18 11:45:46 +08:00
d)
directory=1
;;
pacstrap: store cache on target system by default However, add a '-c' switch to use the host cache instead. The default is useful for when installing a system from an install media (which has possibly constrained storage), but the '-c' switch is useful when e.g. creating build-chroots. I considered doing this the other way around ('-c' being the default). However, I think it makes sense to default to the expected behavior for install both because a new user is less likely to know that they need to add a switch, and because the errormessage they'd get when they run out of space/memory is nonsensical and would cause lots of annoying questions. [dave: use proper array addition, nuke readlink, use arithmetic flag] Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-23 01:14:09 +08:00
c)
reverse default and set values for hostcache option
2012-07-14 21:33:46 +08:00
hostcache=1
pacstrap: store cache on target system by default However, add a '-c' switch to use the host cache instead. The default is useful for when installing a system from an install media (which has possibly constrained storage), but the '-c' switch is useful when e.g. creating build-chroots. I considered doing this the other way around ('-c' being the default). However, I think it makes sense to default to the expected behavior for install both because a new user is less likely to know that they need to add a switch, and because the errormessage they'd get when they run out of space/memory is nonsensical and would cause lots of annoying questions. [dave: use proper array addition, nuke readlink, use arithmetic flag] Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-23 01:14:09 +08:00
;;
properly error on options missing an optarg
2012-06-18 22:05:40 +08:00
:)
die '%s: option requires an argument -- '\''%s'\' "${0##*/}" "$OPTARG"
;;
initial commit
2012-06-18 03:17:10 +08:00
?)
die '%s: invalid option -- '\''%s'\' "${0##*/}" "$OPTARG"
;;
esac
done
shift $(( OPTIND - 1 ))
enforce user-specified root directory Remove the -r option, forcing the user to explicitly pass a root directory. This removes some confusion wherein we set defaults, but wouldn't allow all the defaults to be accepted. This also adds some mild documentation to the help output for genfstab and pacstrap.
2012-07-15 22:04:49 +08:00
(( $# )) || die "No root directory specified"
newroot=$1; shift
pacman_args=("${@:-base}")
pacstrap: store cache on target system by default However, add a '-c' switch to use the host cache instead. The default is useful for when installing a system from an install media (which has possibly constrained storage), but the '-c' switch is useful when e.g. creating build-chroots. I considered doing this the other way around ('-c' being the default). However, I think it makes sense to default to the expected behavior for install both because a new user is less likely to know that they need to add a switch, and because the errormessage they'd get when they run out of space/memory is nonsensical and would cause lots of annoying questions. [dave: use proper array addition, nuke readlink, use arithmetic flag] Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-23 01:14:09 +08:00
if (( ! hostcache )); then
pacman_args+=(--cachedir="$newroot/var/cache/pacman/pkg")
initial commit
2012-06-18 03:17:10 +08:00
fi
pacstrap: add -d option to allow install to non-mount
2012-06-18 11:45:46 +08:00
[[ -d $newroot ]] || die "%s is not a directory" "$newroot"
if ! mountpoint -q "$newroot" && (( ! directory )); then
die '%s is not a mountpoint!' "$newroot"
fi
initial commit
2012-06-18 03:17:10 +08:00
# create obligatory directories
msg 'Creating install root at %s' "$newroot"
pacstrap: create package cache along with DBPath pacman creates this for us, but seems to have problems writing to it. Hackily addresses FS#30807
2012-07-23 08:08:56 +08:00
mkdir -p "$newroot"/var/{cache/pacman/pkg,lib/pacman} "$newroot"/{dev,proc,sys,run,tmp,etc}
initial commit
2012-06-18 03:17:10 +08:00
pacstrap: set umount trap prior to calling api_mount the api_mount function could, for some bizzare reason, fail midway through, leaving the user with a half mounted chroot. set the trap before the function instead, but mask errors since we might see "foo not mounted" errors.
2012-06-19 04:51:38 +08:00
# always call umount on quit after this point
trap 'api_fs_umount "$newroot" 2>/dev/null' EXIT
initial commit
2012-06-18 03:17:10 +08:00
# mount API filesystems
call umount as a trap handler
2012-06-18 03:27:38 +08:00
api_fs_mount "$newroot" || die "failed to setup API filesystems in new root"
initial commit
2012-06-18 03:17:10 +08:00
msg 'Installing packages to %s' "$newroot"
pacstrap: store cache on target system by default However, add a '-c' switch to use the host cache instead. The default is useful for when installing a system from an install media (which has possibly constrained storage), but the '-c' switch is useful when e.g. creating build-chroots. I considered doing this the other way around ('-c' being the default). However, I think it makes sense to default to the expected behavior for install both because a new user is less likely to know that they need to add a switch, and because the errormessage they'd get when they run out of space/memory is nonsensical and would cause lots of annoying questions. [dave: use proper array addition, nuke readlink, use arithmetic flag] Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-23 01:14:09 +08:00
if ! pacman -r "$newroot" -Sy --noconfirm "${pacman_args[@]}"; then
pacstrap: copy the keyring into the new root
2012-06-19 20:11:07 +08:00
die 'Failed to install packages to new root'
fi
pacstrap: don't copy over keyring if it exist already We want to be able to call pacstrap with the target being an existing install (in case it has been severely broken), and hence we might want to preserve the existing keyring. Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-20 02:30:08 +08:00
# if there's a keyring on the host, copy it into the new root, unless it exists already
if [[ -d /etc/pacman.d/gnupg && ! -d $newroot/etc/pacman.d/gnupg ]]; then
cp -a /etc/pacman.d/gnupg "$newroot/etc/pacman.d/"
fi
initial commit
2012-06-18 03:17:10 +08:00
pacstrap: copy the mirrorlist from the host to the new root This would overwrite an existing mirrorlist, but the one at the host is known to be good at this point, so the loss is minimal. Signed-off-by: Tom Gundersen <teg@jklm.no>
2012-06-20 02:34:01 +08:00
# install the host's mirrorlist onto the new root
cp -a /etc/pacman.d/mirrorlist "$newroot/etc/pacman.d/"
fix typo in array name
2012-06-18 04:05:18 +08:00
# vim: et ts=2 sw=2 ft=sh:
Reference in New Issue Copy Permalink