From 680c4bc00afb82f78c36b23a7ce39ce492e68056 Mon Sep 17 00:00:00 2001 From: "mazocomp@125cb8d34e6d7cae380bf8564194dad8935888ba" Date: Fri, 5 Jan 2018 13:17:38 +0000 Subject: [PATCH] Update Handbook's Introduction --- docs/handbook/introduction/index.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/handbook/introduction/index.mdwn b/docs/handbook/introduction/index.mdwn index be3a6744..95ab82ba 100644 --- a/docs/handbook/introduction/index.mdwn +++ b/docs/handbook/introduction/index.mdwn @@ -22,7 +22,7 @@ After reading this chapter, you will know: ## Welcome to DragonFly! -DragonFly is a [[4.4BSD-Lite|http://en.wikipedia.org/wiki/Berkeley_Software_Distribution]] Unix operating system for the Intel x86 (until version 4) and AMD64 (x86_64) architectures. +DragonFly is a [[4.4BSD-Lite-based|http://en.wikipedia.org/wiki/Berkeley_Software_Distribution]] Unix operating system for the AMD64 (x86_64) architecture. ### What Can DragonFly Do? @@ -54,7 +54,7 @@ The robust TCP/IP networking built into DragonFly renders it an ideal platform f * And more... -With DragonFly, you can install on almost any PC, from older 32 bit computers running 386 or Pentium chips, to modern 64 bit Intel Core or AMD X64 desktop CPUs, and even up to and including high end Xeon CPUs. All of these CPUs share a common ancestry and instruction set, going back to the original Intel 80386 CPU, the first fully 32-bit desktop CPU for "IBM PC compatible" computers. +With DragonFly, you can install on almost any PC, from Pentium chips, to modern 64 bit Intel Core or AMD X64 desktop CPUs, and even up to and including high end Xeon CPUs. All of these CPUs share a common ancestry and instruction set, going back to the original Intel 80386 CPU, the first fully 32-bit desktop CPU for "IBM PC compatible" computers. Here are some of the fields where people are using Dragonfly BSD, and the reasons that they find that DragonFly BSD fits their needs: @@ -68,7 +68,7 @@ Here are some of the fields where people are using Dragonfly BSD, and the reason * ***Software Development:*** The basic DragonFly system comes with a full complement of development tools including the renowned GNU C/C++ compiler and debugger. -DragonFly is available via anonymous FTP or GIT. Please see [Appendix A](mirrors.html) for more information about obtaining DragonFly. +DragonFly is available via anonymous FTP or GIT. Please see [Mirrors](/mirrors/) for more information about obtaining DragonFly. For more help on installing, see the appropriate sections of this handbook. @@ -90,7 +90,7 @@ DragonFly is an effort to maintain the traditional BSD format -- lean, stable co ***Written by Justin Sherrill. *** -DragonFly is developed by many people around the world. There is no qualification process; anyone may submit his or her code, documentation, or designs, for use in the Project. Here is a general description of the Project's organizational structure. +DragonFly is developed by many people around the world. There is no qualification process; anyone may submit own code, documentation, or designs, for use in the Project. Here is a general description of the Project's organizational structure. Source for DragonFly is kept in [git](http://www.git.org/), available with each DragonFly install. The primary [git repository](http://gitweb.dragonflybsd.org/?p=dragonfly.git;a=summary) resides on a machine in California, USA. Documentation on obtaining the DragonFly source is available elsewhere in this book. The best way of getting changes made to the DragonFly source is to mail the [submit](http://www.dragonflybsd.org/mailinglists/) mailing list. Including desired source code changes (unified diff format is best) is the most useful format. A certain number of developers have access to commit changes to the DragonFly source, and can do so after review on that list. The DragonFly development model is loose; changes to the code are generally peer-reviewed and added when any objections have been corrected. There is no formal entry/rejection process, though final say on all code submissions goes to Matt Dillon, as originator of this project. -- 2.32.0