git: 02d9ae1165 - main - NanoBSD: add how to obtain the source code

Mitchell Horne <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
The branch main has been updated by mhorne:

URL: https://cgit.FreeBSD.org/doc/commit/?id=02d9ae11650e82b2129f80d3e19a826e7c731585

commit 02d9ae11650e82b2129f80d3e19a826e7c731585
Author:     Minsoo Choo <[email protected]>
AuthorDate: 2023-11-27 15:04:53 +0000
Commit:     Mitchell Horne <[email protected]>
CommitDate: 2023-11-27 15:05:00 +0000

    NanoBSD: add how to obtain the source code
    
    There is a request in the bugzilla report to introduce how to obtain the
    source code for building NanoBSD. I added more lines to the patch
    provided by the original reporter.
    
    PR:             274709
    Reviewed by:    mhorne
    Co-Authored-By: [email protected]
    Differential Revision: https://reviews.freebsd.org/D42743
---
 documentation/content/en/articles/nanobsd/_index.adoc | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/documentation/content/en/articles/nanobsd/_index.adoc b/documentation/content/en/articles/nanobsd/_index.adoc
index f8dadb9314..a8f3ba03d6 100644
--- a/documentation/content/en/articles/nanobsd/_index.adoc
+++ b/documentation/content/en/articles/nanobsd/_index.adoc
@@ -108,6 +108,16 @@ Keeping [.filename]#/cfg# mounted at all times is not a good idea, especially if
 
 === Building a NanoBSD Image
 
+The source code of FreeBSD is required to build NanoBSD.
+To obtain the source code:
+
+[source,shell]
+....
+# git clone https://git.FreeBSD.org/src.git /usr/src
+....
+
+For more details, follow the steps extref:{handbook}cutting-edge#updating-src-obtaining-src[here].
+
 A NanoBSD image is built using a simple [.filename]#nanobsd.sh# shell script, which can be found in the [.filename]#/usr/src/tools/tools/nanobsd# directory.
 This script creates an image, which can be copied on the storage medium using the man:dd[1] utility.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.