You are not logged in.

#1 2023-08-18 12:32:37

grimor
Member
Registered: 2023-07-15
Posts: 5

Offline on installation from existing Linux

Hi again to Arch Linux 32 community!

# mount archlinux32-2023.03.02-i686.iso /mnt
# unsquashfs /mnt/arch/i686/airootfs.sfs

"airootfs.sfs" is extracted on new 'squashfs-root' directory

# umount /mnt
# mount --bind squashfs-root squashfs-root
# mount -t proc none squashfs-root/proc
# mount -t sysfs none squashfs-root/sys
# mount -o bind /dev squashfs-root/dev
# mount -o bind /dev/pts squashfs-root/dev/pts
# cp -L /etc/resolv.conf squashfs-root/etc
# chroot squashfs-root bash
[root@debian /]# pacman-key --init
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/CFD553EB136002AF3A24AC4FC7C9B0A2CFB40D95.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
[root@debian /]# pacman-key --populate archlinux
==> ERROR: The keyring file /usr/share/pacman/keyrings/archlinux.gpg does not exist.
[root@debian /]# exit
# mv squashfs-root/usr/share/pacman/keyrings/archlinux32.gpg squashfs-root/usr/share/pacman/keyrings/archlinux.gpg
# mv squashfs-root/usr/share/pacman/keyrings/archlinux32-revoked squashfs-root/usr/share/pacman/keyrings/archlinux-revoked
# mv squashfs-root/usr/share/pacman/keyrings/archlinux32-trusted squashfs-root/usr/share/pacman/keyrings/archlinux-trusted
# chroot squashfs-root bash
[root@debian /]# pacman-key --populate archlinux
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signed 5 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabled 3 keys.
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   5  signed:   2  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:   2  signed:   0  trust: 2-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-12-31
[root@debian /]# pacman -Syy archlinux32-keyring
:: Synchronizing package databases...
 core.db failed to download
error: failed retrieving file 'core.db' from mirror.datacenter.by : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.datacenter.by : The requested URL returned error: 404
error: failed retrieving file 'core.db' from archlinux32.agoctrl.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from archlinux32.agoctrl.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from de.mirror.archlinux32.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from de.mirror.archlinux32.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.archlinux32.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.archlinux32.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.archlinux32.oss : Could not resolve host: mirror.archlinux32.oss
warning: too many errors from mirror.archlinux32.oss, skipping for the remainder of this transaction
error: failed retrieving file 'core.db' from gr.mirror.archlinux32.org : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.juniorjpdj.pl : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.juniorjpdj.pl : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.yandex.ru : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.yandex.ru : The requested URL returned error: 404
error: failed retrieving file 'core.db' from archlinux32.andreasbaumann.cc : The requested URL returned error: 404
error: failed retrieving file 'core.db' from archlinux32.andreasbaumann.cc : The requested URL returned error: 404
error: failed retrieving file 'core.db' from 32.arlm.tyzoid.com : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.math.princeton.edu : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.math.princeton.edu : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.clarkson.edu : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.clarkson.edu : The requested URL returned error: 404
error: failed retrieving file 'core.db' from mirror.bradiceanu.net : The requested URL returned error: 404
error: failed to synchronize all databases (failed to retrieve some files)

Tutorial:
https://wiki.archlinux.org/title/Instal … ting_Linux

Offline

#2 2023-08-19 15:44:27

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 988
Website

Re: Offline on installation from existing Linux

From the error messages it looks like you have no network at all in the chroot, which is weird, as you should get it from the host where you are chrooting from.

Offline

Board footer

Powered by FluxBB