X-Git-Url: https://gitweb.dragonflybsd.org/ikiwiki.git/blobdiff_plain/370f7494b7da3eb83160918391254fa065915893..HEAD:/docs/faq/FAQ-English.mdwn diff --git a/docs/faq/FAQ-English.mdwn b/docs/faq/FAQ-English.mdwn index 4314fbe7..1618e5c6 100644 --- a/docs/faq/FAQ-English.mdwn +++ b/docs/faq/FAQ-English.mdwn @@ -1,80 +1,69 @@ -# About this FAQ +This is the official DragonFly FAQ. -You can find a copy of the FAQ on the official () DragonFly website. In addition, there is a copy maintained on the wiki which is periodically synchronized with the official FAQ. +[[!toc startlevel=3]] -You can also find translations to other languages at these locations: Dansk (Danish) - Deutsch (German) - Español (Spanish) - Français (French) - Italiano (Italian) - LietuviÅ¡kai (Lithuanian) - Magyar (Hungarian) - Nederlands - Norwegian - Polski (Polish - not completed) - [Română](http://www.dragonflybsd.org/docs/faq/FAQ-Romanian/) (Romanian - work in progress) - Русский (Russian) - Svenska (Swedish) - Ukrainian (not completed). +### Is DragonFly ready for production? +Yes. DragonFly is generally stable and speedy at this point. For third-party software, it uses [DPorts](https://www.dragonflybsd.org/docs/howtos/HowToDPorts/), which is based on the [FreeBSD ports collection](http://www.freebsd.org/ports/index.html) and contains more than 24,000 packages. We have an active community that are working on keeping things working. As in any open source project, if you find problems [reporting them](https://bugs.dragonflybsd.org/) increases the chance that someone can fix it. -# Is DragonFly ready for production? -Yes. A number of people are using it in production. DragonFly is generally stable and speedy at this point. As of 1.4, DragonFly uses the NetBSD Packages Collection pkgsrc () for third-party software. pkgsrc contains over 5500 packages and is supported on several different platforms from Linux to AIX. You are advised to keep a close eye on the forums. Check the forums page () to find out on how to get access. We have an active community that are working on keeping things working. As in any open source project, if you find problems reporting them increases the chance that someone can fix it. +### What are the potential goals for the next release? +For DragonFly news and events, keep an eye on the [DragonFly BSD Digest](https://www.dragonflydigest.com/), this Wiki, and the [DragonFly mailing lists/newsgroups](https://www.dragonflybsd.org/mailinglists/). -# What are the potential goals for the next release? -Multiprocessor-safe networking without the Big Giant Lock, a cache coherency management system, and the importation of Sun's ZFS (). See Matthew Dillon's post () for more details. +### Is there a branch oriented towards stability, like the FreeBSD's -STABLE? -For DragonFly news and events, keep an eye on the DragonFly BSD Log (), the DragonFly Wiki, and the DragonFly mailing lists/newsgroups (). +We have the `DragonFly_RELEASE_X_X` branches which are considered to be stable. -# Is there a branch oriented towards stability, like the FreeBSD's -STABLE? +### I get garbage on the screen when I boot or I can't seem to pause at the initial boot menu. -We have a -RELEASE tag which is considered to be fairly stable. +DragonFly, when booting, outputs to both video and serial ports. If the booting computer has a 'noisy' serial device connected, it may read data from it during the boot process. Serial console activation during boot can be disabled by creating the file `/boot.config` with this contents: `-V` -# I get garbage on the screen when I boot or I can't seem to pause at the initial boot menu. +### How can I speed up my build process? -DragonFly, when booting, outputs to both video and serial ports. If the booting computer has a 'noisy' serial device connected, it may read data from it during the boot process. Serial console activation during boot can be disabled by creating the file /boot.config with the contents: '-V' +You can use `make quickworld` instead of `make buildworld`. This reuses existing tools on disk and speeds this step up considerably. For the kernel there is a similar `quickkernel` target. -# How can I speed up my build process? +### But `make quickworld` / `make quickkernel` fails! -You can use make quickworld instead of make buildworld. This reuses existing tools on disk and speeds this step up considerably. For the kernel there is a similar quickkernel target. +Try `make buildworld` or `make buildkernel` instead. -# But make quickworld/quickkernel fails! +### What is used to handle third-party applications? (like ports, yum, apt-get, etc.) -Try make buildworld or buildkernel instead. +DragonFly uses [DPorts](https://www.dragonflybsd.org/docs/howtos/HowToDPorts/), a patched version of the [FreeBSD Ports Collection](http://www.freebsd.org/ports/index.html) that runs on DragonFly systems. You can build from the DPorts collection by going to the port of your choice and running `make config install clean`. Binary packages can be easily installed/managed using the [`pkg(8)`](https://www.dragonflybsd.org/cgi/web-man?command=pkg§ion=) package manager, and they are advised unless non-standard options are required. -# What is used to handle third-party applications? (like ports, RPM, apt-get, etc.) +### What architectures does DragonFly support? -As of 1.4, DragonFly uses the NetBSD Packages Collection pkgsrc () for third-party applications. pkgsrc is a packaging system much like FreeBSD ports, and there are many pre-built packages available. For a quick guide see the pkgsrc HOWTO. Eventually, DragonFly will have a homegrown port system, using the VFS mechanisms that are as of this writing not complete yet. For more information, check the specifications for the ideal package management system (). +DragonFly is currently targeted at the 64-bit x86 line of processors (x86_64); version 3.8 was the last release supporting 32-bit processors (i386). There are currently no plans for support of other processor types. However, support for Sparc or PowerPC or other systems is possible in the future. If you plan to submit code to the DragonFly project, please keep this in mind. -# What architectures does DragonFly support? +### How can I contribute? -DragonFly is currently targeted at the x86 line of processors; it should work on 386 and up, though a 386 is certainly not recommended. Work is also being done on support for the new 64-bit processors from AMD. There are currently no plans for support of other processor types. However, support for Sparc or PowerPC or other systems is possible in the future. If you plan to submit code to the DragonFly project, please keep this in mind. +Pick a topic that you enjoy and start working. Check the [team page](http://www.dragonflybsd.org/team/) to see if there are others interested in your topic, or ask around in the [appropriate forum](https://www.dragonflybsd.org/mailinglists/). You can [download the source](http://www.dragonflybsd.org/download/) to the operating system and to the official site, and send patches in unified diff format (`diff -uN`) to *submit at dragonflybsd.org* for review. Subscribe to that same submit [mailing list/newsgroup](https://www.dragonflybsd.org/mailinglists/) to see feedback on your patches, and to find if they have been accepted or rejected. In addition, you can update this DragonFly Wiki. +Note that you do not have to be a programmer in order to help. Evangelizing DragonFly and testing it on a variety of hardware, and reporting results can help a great deal. Try new features and report to the forums on your experiences. Cleaning up `/etc/rc.d` only requires shell script experience, for instance, and there's always a need for better documentation. -# How can I contribute? -Pick a topic that you enjoy and start working. Check the team page () to see if there are others interested in your topic, or ask around in the appropriate forum (). You can download the source () to the operating system and to the official site, and send patches in unified diff format (diff -uN) to 'submit at dragonflybsd.org' for review. Subscribe to that same submit mailing list/newsgroup () to see feedback on your patches, and to find if they have been accepted or rejected. In addition, you can update the DragonFly Wiki. +### Does DragonFly use a dynamic `/dev` filesystem, as in *devfs*? -Note that you do not have to be a programmer in order to help. Evangelizing DragonFly and testing it on a variety of hardware, and reporting results can help a great deal. Try new features and report to the forums on your experiences. Cleaning up /etc/rc.d only requires shell script experience, for instance, and there's always a need for better documentation. +DragonFly has a dynamic `/dev` file system, aka [devfs(5)](http://leaf.dragonflybsd.org/cgi/web-man?command=devfs§ion=ANY). -# Will DragonFly use a dynamic /dev filesystem, as in devfs? +### Will DragonFly use (insert name here) technology? -Since 2.3, DragonFly has a dynamic /dev file system, aka devfs(5). +Yes and no. Features must match the existing plan outlined on the site here, and there's plenty of existing problems to solve before 'non-essential' work can be done. However, if you are willing to work on it, it probably can be done. The [forums](http://www.dragonflybsd.org/mailinglists/) are an excellent place to get feedback and to find others that may be interested in your topic. The [team page](http://www.dragonflybsd.org/team/) is also a good place to check. -# What is the state of journaling fs / background fsck? We cannot wait... -Matt is working on journaling, but you may want to read this post: - -Or just go through the whole topic: - - -# Will DragonFly use (insert name here) technology? - -Yes and no. Features must match the existing plan outlined on the site here, and there's plenty of existing problems to solve before 'nonessential' work can be done. However, if you are willing to work on it, it probably can be done. The forums are an excellent place to get feedback and to find others that may be interested in your topic. The team page () is also a good place to check. - - -# What's the correct way to name this operating system? +### What's the correct way to name this operating system? It's a BSD variant, called DragonFly. Note the capitalization on the F, which isn't proper English. -# Should ldconfig_path be updated in /etc/defaults/rc.conf to include support for pkgsrc? +### Who is "Fred"? -No. pkgsrc links everything with -rpath so all binaries should carry the correct paths already. If it breaks it's broken. +**Fred** is the name of the [mascot](https://www.dragonflybsd.org/images/) of the DragonFly BSD, and owns the assets of the Project, as can be seen from the [repositories page](https://gitweb.dragonflybsd.org/).