joborun
/
web
2
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

correct --conf chroot pacman.conf 

added a --conf flag to 2nd step of the installation of jobbot after pacman is already installed.
This commit is contained in:
joborun linux 2023-09-18 09:44:48 +00:00
parent 42d6d28f17
commit 18ac4d4bc3
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
install3.md
View File

@ -38,7 +38,7 @@ This is necessary for installing pacman to the target in order to use the curren
<pre>
# pacman -Sy pacman --config /tmp/pac-inst.conf -r /mnt
# pacman -Sy jobbot -r /mnt
# pacman -Sy jobbot --config /mnt/etc/pacman.conf -r /mnt
</pre>
** Sysusers should be used in lack of systemd to set user/group IDs for special system users like systemd does. With the use of s6 and 66 obsysusers is a dependency and replaces opensysusers. Basically it is the same script and runs through a pacman hook reading a sysusers.d directory for users settings by any software that require to execute something as a special system user (neither a regular user or root). On the buildbot we have neither runit or s6 nor 66, nothing points to a bootable system, but some software still need sysusers to install properly.
@ -98,3 +98,9 @@ In trying to keep jobbot as minimal as possible man-pages do not work without th
Go build some packages (read our wiki entries for building and building like joborun)
#Note:#
Thanks to [[u/unix21311 | https://www.reddit.com/user/unix21311/]] a detail that escaped us not actually using a different distro to do the installation, till pacman and mirrorlists are installed in the chroot the flag --conf /mnt/etc/pacman.conf must be used for your local pacman to be reading a different configuration and repositories than what is native. So the 2nd step of installation was modified. In the first step you use the pacman.conf that is temporary to install joborun's pacman, the 2nd step is using the chroot's own new pacman.conf.