Differences

This shows you the differences between two versions of the page.

--- documentation:technical_docs [2021/01/15 21:22] – [Prerequisite] olivier
+++ documentation:technical_docs [2024/11/12 15:23] (current) – [Current problems with make] olivier
@@ Line 3: / Line 3: @@
-====== NanoBSD ======
+====== poudriere-image ======
+Note that work-in-progess to migrate from the old NanoBSD to the [[Documentation:Technical docs:poudriere|new poudriere image framework]].
-The first step was to understand [[Documentation:Technical docs:NanoBSD|what is NanoBSD ?]]
 ====== How to build BSDRP images ======
@@ Line 16: / Line 19: @@
 ===== Prerequisite =====
-You need 21G of free space (1G for FreeBSD installation, 2G for FreeBSD sources, 10G for ports sources, and 8G for the working dir).
+You need 21G of free space (1G for FreeBSD installation, 3G for FreeBSD sources, 3G for ports sources and 8G for the working dir).
 ==== Getting BSDRP source code ====
-You can download the source code of BSDRP with svnlite (included in FreeBSD):
+git clone:
 <code>
-pkg install ca_root_nss
+pkg install git sudo poudriere-devel
-svnlite co https://github.com/ocochard/BSDRP/trunk BSDRP
-cd BSDRP
-</code>
-or using git if you had installed it:
-<code>
-pkg install ca_root_nss
 git clone https://github.com/ocochard/BSDRP.git BSDRP
 </code>
-Once you download the code, you can kept your BSDRP sources up-to-date with these commands:
-<code>
-svnlite update | git pull
-./make -u
-</code>
-===== make.sh flowshart =====
-Here is the big picture regarding BSDRP image build process:
-{{BSDRP.framework.flowshart.png| BSDRP build framework flowshart}}
 ===== Running the build script =====
@@ Line 50: / Line 36: @@
 <code>
-./make.sh -h
+make
 </code>
 The FreeBSD code include all architecture and limited cross-compiling tools: You can generate an i386 BSDRP image from a FreeBSD amd64, but you can't generate a sparc64 image from an i386/amd64 host.
-===== Current problems with make =====
-==== Disk image creation can fail ====
-On FreeBSD dektop, sometimes NanoBSD can't umount the md during image creation.
-"fstat | grep BSDRP" display the name of the process locking the temporary mount point. It can be:
-    * gam_server
-    * gvfsd-trash
-here is the log of a failed build:
+Once you download the code, you can kept your BSDRP sources up-to-date with these commands:
 <code>
-### log : /usr/obj/BSDRP.amd64/_.di
+make upstream-sync
-Error encountered. Check errors in last log file.
-Running exit trap code
-root@dev # tail -n 4 /usr/obj/BSDRP.amd64/_.di
-unmount: unmount of /usr/obj/BSDRP.amd64/_.mnt failed: Device busy
 </code>
-==== gam_server ====
-For preventing gamin to lock the working mount point, create this configuration file and force a restart of gamin:
-<code>
-mkdir /usr/local/etc/gamin
-echo "fsset ufs poll 10" > /usr/local/etc/gamin/gaminrc
-killall -9 gam_server
-</code>
-==== gvfsd-trash ====
-I don't know how to fix this gvfs bug.
 ====== How to generate customized BSDRP images ======