null31
/
aab
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
23 Commits 1 Branch 0 Tags 68 KiB
Perl 92.1%
Makefile 5.6%
Shell 2.3%
Go to file
Stoiko Ivanov 01756eba20 refactor initial device creation for pacman 
`aab` installs `archlinux-keyring`, which in turn invokes `dirmngr` during
installation. `dirmngr` needs access (at least) to '/dev/null' (see [0]), which
`aab` only created afterwards (before populating the keyring). This lead to
`dirmngr` spinning (and filling the filesystem with a regular file
'${rootfs}/dev/null' containing error messages.

This patch changes the behavior of aab: it now creates the devices before
installing 'archlinux-keyring' and removes them after the keyring is populated.

In order to save one further `mkdir` call for the 'dev' directory, this was
appended to the `mkpath` invocation in ve_init.

[0] https://bbs.archlinux.org/viewtopic.php?id=222002

Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
 		2019-04-26 08:17:03 +00:00
PVE refactor initial device creation for pacman 2019-04-26 08:17:03 +00:00
scripts initial import 2015-08-21 09:08:11 +02:00
.gitignore initial import 2015-08-21 09:08:11 +02:00
COPYING added README and COPYING files 2015-08-24 08:01:14 +02:00
Makefile Use %m (month) not %M (minute) for today's date... 2017-12-14 09:03:01 +01:00
README added README and COPYING files 2015-08-24 08:01:14 +02:00
aab using a weak key for pacman-key --init 2015-08-31 10:37:42 +02:00

README 

Usage example:

1) Create an aab.conf file describing your template.

--- Example aab.conf:
Name: base
Version: 2015-08-21-1
Section: optional
Maintainer: Your Name
Headline: ArchLinux base image.
Architecture: x86_64
Source: http://archlinux.cu.be/$repo/os/$arch
--- End of example

2) Run as root:

  # ./aab init
  # ./aab bootstrap

3) Maybe install additional packages

  # ./aab install base-devel

4) Create the archive and clean up:

  # ./aab finalize
  # ./aab cleanup