Minor changes and corrections

This commit is contained in:
joborun linux 2023-09-06 10:31:05 +00:00
parent 3e7cb05b51
commit 42d6d28f17
1 changed files with 9 additions and 8 deletions

View File

@ -22,11 +22,11 @@ For simplicity we will refer to this prepared and mounted partition as the "targ
- Network is functional
- Arguments passed to the script are valid pacman targets
- You are in a root shell
- arch-install-scripts is installed in your system (includes arch-chroot & genfstab which will be used here)
- arch-install-scripts is installed in your system (alternatively read up on the arch wiki on how to do the mounting of filesystems into the target before you use the common chroot - proc/ run/ sys/ dev/ )
One of the key differences with Arch is that joborun and Obarun have a few more repositories that are placed higher up in hierarchy within /etc/pacman.conf to give priority to joborun's packages over Obarun, and Obarun's packages over arch. (Obarun's packages other than s6/66 are generally rebuilds without systemd/libs running dependencies. Joborun's packages over Arch are rebuilds without systemd/libs makedependencies and presence).
###### Create pacman lib directory in /mnt ######
##### Create pacman lib directory in /mnt #####
<pre>
# mkdir -p /mnt/var/lib/pacman
@ -34,15 +34,14 @@ One of the key differences with Arch is that joborun and Obarun have a few more
This is necessary for installing pacman to the target in order to use the current and correct joborun pacman.conf.
###### install joborun's pacman to target ######
##### install joborun's pacman to target #####
<pre>
# pacman -Sy pacman --config /tmp/pac-inst.conf -r /mnt
# pacman -Sy jobbot -r /mnt
</pre>
** Sysusers should be used in lack of systemd to set systemd IDs for special 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).
** 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.
Select the closest mirrors to your location and remove the comment sign '#' from in front of them. Pacman hits the first uncommented server on the list and only if it fails goes to the next. You do this by editing:
/etc/pacman.d/mirrorlist and
@ -76,11 +75,11 @@ for US English ) and pass the choice into the system:
If you are working in chroot don't expect the change in locale to be automatic, you must either restart a shell, or exit and re-enter.
###### Your installation is complete ######
##### Your installation is complete #####
Use arch-chroot to get into the installation and do more configurations or pkg installations as you need.
## **Welcome to joborun build-environment** ##
### **Welcome to joborun build-environment** ###
What you will need now is a user, the standard user in the jobbot image is make and the home directory for this user is /home/make If you choose another keep in mind that for simplicity "make" will be referred to as the standard user in other documentation.
@ -89,10 +88,12 @@ useradd make (consult the arch wiki https://wiki.archlinux.org/title/users_and_g
In trying to keep jobbot as minimal as possible man-pages do not work without the man-db/man-pages pkgs. If you need to read them for the installed packages install those and remember to uninstall them when you are done. If not, when you run ckchroot command at the end or beggining of building it will show you that you have additional packages in the environment.
## ** Switch to /src/pkg and clone our repositories ** ##
### ** Switch to /src/pkg and clone our repositories ** ###
- Install git
- Use the commands listed in the README stored in /src/pkg to clone the repositories. If youjust want to refresh them use pull instead of clone
- Uninstall git
- Run /usr/local/bin/ckchroot to verify your environment ONLY has what is prescribed to be the minimal building environment, nothing more or less.
Go build some packages (read our wiki entries for building and building like joborun)