Differential D35345 Diff 106714 documentation/content/en/books/faq/_index.adoc

Changeset View

Standalone View

documentation/content/en/books/faq/_index.adoc

	---			---
	title: Frequently Asked Questions for FreeBSD 12.X and 13.X			title: Frequently Asked Questions for FreeBSD 12.X and 13.X
				grahamperrinUnsubmitted Done Inline Actions Is it necessary to be specific? Consider removing the tail of this line. (Some of the answers relate to 14.0-CURRENT.) grahamperrin: Is it necessary to be specific? Consider removing the tail of this line. (Some of the…
				pauamma_gundo.comAuthorUnsubmitted Done Inline Actions Not sure about necessary, and I agree some of it is about -CURRENT or applicable to it, but 12 and 13 are the intended primary focus, so it's at the very least useful. pauamma_gundo.com: Not sure about necessary, and I agree some of it is about -CURRENT or applicable to it, but 12…
	authors:			authors:
	- author: The FreeBSD Documentation Project			- author: The FreeBSD Documentation Project
	copyright: 1995-2021 The FreeBSD Documentation Project			copyright: 1995-2022 The FreeBSD Documentation Project
	description: Frequently Asked Questions, and answers, covering all aspects of FreeBSD			description: Frequently Asked Questions, and answers, covering all aspects of FreeBSD
	trademarks: ["freebsd", "ibm", "ieee", "adobe", "intel", "linux", "microsoft", "opengroup", "sun", "netbsd", "general"]			trademarks: ["freebsd", "ibm", "ieee", "adobe", "intel", "linux", "microsoft", "opengroup", "sun", "netbsd", "general"]
	bookOrder: 5			bookOrder: 5
	tags: ["FAQ", "FreeBSD FAQ"]			tags: ["FAQ", "FreeBSD FAQ"]
	---			---

	= Frequently Asked Questions for FreeBSD {rel2-relx} and {rel-relx}			= Frequently Asked Questions for FreeBSD {rel2-relx} and {rel-relx}
	:doctype: book			:doctype: book
	▲ Show 20 Lines • Show All 172 Lines • ▼ Show 20 Lines
	However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use,			However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use,
	as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT.			as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT.
	Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD.			Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD.
	_FreeBSD-CURRENT_, on the other hand, has been one unbroken line since 2.0 was released.			_FreeBSD-CURRENT_, on the other hand, has been one unbroken line since 2.0 was released.

	For more detailed information on branches see "extref:{releng}[FreeBSD Release Engineering: Creating the Release Branch, rel-branch]",			For more detailed information on branches see "extref:{releng}[FreeBSD Release Engineering: Creating the Release Branch, rel-branch]",
	the status of the branches and the upcoming release schedule can be found on the https://www.FreeBSD.org/releng[Release Engineering Information] page.			the status of the branches and the upcoming release schedule can be found on the https://www.FreeBSD.org/releng[Release Engineering Information] page.

	Version https://download.FreeBSD.org/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}] is the latest release from the {rel-stable} branch; it was released in {rel121-current-date}.			Version {u-rel123-announce}[{rel123-current}] is the latest release from the {rel2-stable} branch; it was released on {rel123-current-date}.
	Version https://download.FreeBSD.org/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}] is the latest release from the {rel2-stable} branch; it was released in {rel113-current-date}.			Version {u-rel131-announce}[{rel131-current}] is the latest release from the {rel-stable} branch; it was released on {rel131-current-date}.

	[[release-freq]]			[[release-freq]]
	=== When are FreeBSD releases made?			=== When are FreeBSD releases made?

	The {re} releases a new major version of FreeBSD about every 18 months and a new minor version about every 8 months, on average.			The {re} releases a new major version of FreeBSD about every 18 months and a new minor version about every 8 months, on average.
	Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested.			Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested.
	A testing period precedes each release, to ensure that the addition of new features does not compromise the stability of the release.			A testing period precedes each release, to ensure that the addition of new features does not compromise the stability of the release.
	Many users regard this caution as one of the best things about FreeBSD, even though waiting for all the latest goodies to reach _-STABLE_ can be a little frustrating.			Many users regard this caution as one of the best things about FreeBSD, even though waiting for all the latest goodies to reach _-STABLE_ can be a little frustrating.
	Show All 28 Lines
	There is a much larger team of more than 350 extref:{contributors}[committers, staff-committers] who are authorized to make changes directly to the FreeBSD source tree.			There is a much larger team of more than 350 extref:{contributors}[committers, staff-committers] who are authorized to make changes directly to the FreeBSD source tree.

	However, most non-trivial changes are discussed in advance in the <<mailing,mailing lists>>,			However, most non-trivial changes are discussed in advance in the <<mailing,mailing lists>>,
	and there are no restrictions on who may take part in the discussion.			and there are no restrictions on who may take part in the discussion.

	[[where-get]]			[[where-get]]
	=== Where can I get FreeBSD?			=== Where can I get FreeBSD?

	Every significant release of FreeBSD is available via anonymous FTP from the https://download.FreeBSD.org/releases/[FreeBSD FTP site]:			Every supported release of FreeBSD is available from the https://www.freebsd.org/where/[FreeBSD release locator page]:
				grahamperrinUnsubmitted Done Inline Actions Recent versions are grahamperrin: Recent versions are
				pauamma_gundo.comAuthorUnsubmitted Done Inline Actions Went for "supported" pauamma_gundo.com: Went for "supported"

	* The latest {rel-stable} release, {rel121-current}-RELEASE can be found in the https://download.FreeBSD.org/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}-RELEASE directory].			* For the latest {rel-stable} release, {rel131-current}-RELEASE, follow the link for link:https://www.freebsd.org/where/#download-rel131[the appropriate architecture and installation mode for {rel131-current}-RELEASE].
	* link:https://www.FreeBSD.org/snapshots/[Snapshot] releases are made monthly for the <<current,-CURRENT>> and <<stable,-STABLE>> branch, these being of service purely to bleeding-edge testers and developers.			* For the latest {rel2-stable} release, {rel123-current}-RELEASE, follow the link for link:https://www.freebsd.org/where/#download-rel123[the appropriate architecture and installation mode for {rel123-current}-RELEASE].
	* The latest {rel2-stable} release, {rel113-current}-RELEASE can be found in the https://download.FreeBSD.org/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}-RELEASE directory].			* link:https://www.FreeBSD.org/snapshots/[Snapshot] releases are made monthly for the <<current,-CURRENT>> and <<stable,-STABLE>> branches, these being of service purely to bleeding-edge testers and developers.
				grahamperrinUnsubmitted Not Done Inline Actions branches grahamperrin: branches
				grahamperrinUnsubmitted Not Done Inline Actions I'm more familiar with snapshots appearing approximately weekly, although I understand that frequencies will vary across branches and platforms. For example, at the time of writing: `20220512`, `20220519` and `20220527` at https://download.freebsd.org/snapshots/ISO-IMAGES/14.0/. https://www.freebsd.org/snapshots/ seems to make no promise about frequency. Instead, there's acknowledgement that things may be somewhat outdated. I suggest removing the word monthly. grahamperrin: I'm more familiar with snapshots appearing approximately //weekly,// although I understand that…
				pauamma_gundo.comAuthorUnsubmitted Done Inline Actions No idea; perhaps someone who knows what happens and what's meant to happen can say. Leaving all undone, and focusing on versions and the extra easy change I snuck in, as I have other changes I need to make anyway. pauamma_gundo.com: No idea; perhaps someone who knows what happens and what's meant to happen can say. Leaving all…
				grahamperrinUnsubmitted Not Done Inline Actions Consider removing this phrase. At least: I should not describe `STABLE` as bleeding edge. Readers can learn about the nature of snapshots at https://www.freebsd.org/snapshots/. grahamperrin: Consider removing this phrase. At least: I should not describe `STABLE` as //bleeding edge//.
				grahamperrinUnsubmitted Not Done Inline Actions It's potentially confusing to describe snapshots (of branches that are not `RELEASE`) as snapshot releases. Some overlap with use of the phrase FreeBSD Snapshot Releases at https://www.freebsd.org/snapshots/. grahamperrin: It's potentially confusing to describe snapshots (of branches that are not `RELEASE`) as…

	Information about obtaining FreeBSD on CD, DVD, and other media can be found in extref:{handbook}[the Handbook, mirrors].			Information about obtaining FreeBSD on CD, DVD, and other media can be found in extref:{handbook}[the Handbook, mirrors].

	[[access-pr]]			[[access-pr]]
	=== How do I access the Problem Report database?			=== How do I access the Problem Report database?

	The Problem Report database of all user change requests may be queried by using our web-based PR https://bugs.FreeBSD.org/search/[query] interface.			The Problem Report database of all user change requests may be queried by using our web-based PR https://bugs.FreeBSD.org/search/[query] interface.

	▲ Show 20 Lines • Show All 316 Lines • ▼ Show 20 Lines

	[[compatibility-general]]			[[compatibility-general]]
	=== General			=== General

	[[which-hardware-to-get]]			[[which-hardware-to-get]]
	==== I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best?			==== I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best?

	This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly.			This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly.
	Read through the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}] and search the mailing list https://www.FreeBSD.org/search/#mailinglists[archives] before asking about the latest and greatest hardware.			Read through the Hardware Notes for FreeBSD link:{u-rel123-hardware}[{rel123-current}] or link:{u-rel131-hardware}[{rel131-current}] and search the https://www.FreeBSD.org/search/#mailinglists[mailing list archives] before asking about the latest and greatest hardware.
				grahamperrinUnsubmitted Done Inline Actions Outdated links. grahamperrin: Outdated links.
	Chances are a discussion about that type of hardware took place just last week.			Chances are a discussion about that type of hardware took place just last week.

	Before purchasing a laptop, check the archives for {freebsd-questions},			Before purchasing a laptop, check the archives for {freebsd-questions},
	or possibly a specific mailing list for a particular hardware type.			or possibly a specific mailing list for a particular hardware type.

	[[memory-upper-limitation]]			[[memory-upper-limitation]]
	==== What are the limits for memory?			==== What are the limits for memory?

	▲ Show 20 Lines • Show All 72 Lines • ▼ Show 20 Lines
	to [.filename]#/etc/rc.conf#			to [.filename]#/etc/rc.conf#

	[[compatibility-peripherals]]			[[compatibility-peripherals]]
	=== Peripherals			=== Peripherals

	[[supported-peripherals]]			[[supported-peripherals]]
	==== What kind of peripherals does FreeBSD support?			==== What kind of peripherals does FreeBSD support?

	See the complete list in the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}].			See a list of hardware known to work and any applicable restrictions in the Hardware Notes for FreeBSD link:{u-rel123-hardware}[{rel123-current}] or link:{u-rel131-hardware}[{rel131-current}].
				grahamperrinUnsubmitted Done Inline Actions Outdated links. For a future review, re: https://forums.freebsd.org/posts/554130 (discussion with Joseph Mingrone) IMHO we should make clear that hardware notes are not intended to be comprehensive. Frankness about their scope should not lessen the value of the notes. FAQ might be an ideal place for this frankness. grahamperrin: Outdated links. ---- For a future review, re: <https://forums.freebsd.org/posts/554130>…
				pauamma_gundo.comAuthorUnsubmitted Done Inline Actions Tweaked that a bit while here. pauamma_gundo.com: Tweaked that a bit while here.

	[[compatibility-kbd-mice]]			[[compatibility-kbd-mice]]
	=== Keyboards and Mice			=== Keyboards and Mice

	[[moused]]			[[moused]]
	==== Is it possible to use a mouse outside the X Window system?			==== Is it possible to use a mouse outside the X Window system?

	The default console driver, man:vt[4], provides the ability to use a mouse pointer in text consoles to cut & paste text.			The default console driver, man:vt[4], provides the ability to use a mouse pointer in text consoles to cut & paste text.
	▲ Show 20 Lines • Show All 1,225 Lines • ▼ Show 20 Lines
	The security level cannot be lowered in multi-user mode.			The security level cannot be lowered in multi-user mode.
	Either boot to single-user mode to change the date or change the security level in [.filename]#/etc/rc.conf# and reboot.			Either boot to single-user mode to change the date or change the security level in [.filename]#/etc/rc.conf# and reboot.
	See the man:init[8] manual page for details on `securelevel`, and see [.filename]#/etc/defaults/rc.conf# and the man:rc.conf[5] manual page for more information on [.filename]#rc.conf#.			See the man:init[8] manual page for details on `securelevel`, and see [.filename]#/etc/defaults/rc.conf# and the man:rc.conf[5] manual page for more information on [.filename]#rc.conf#.

	[[statd-mem-leak]]			[[statd-mem-leak]]
	=== Why is rpc.statd using 256 MB of memory?			=== Why is rpc.statd using 256 MB of memory?

	No, there is no memory leak, and it is not using 256 MB of memory.			No, there is no memory leak, and it is not using 256 MB of memory.
	For convenience, `rpc.statd` maps an obscene amount of memory into its address space.			For convenience, `rpc.statd` maps a large amount of memory into its address space.
	There is nothing terribly wrong with this from a technical standpoint; it just throws off things like man:top[1] and man:ps[1].			There is nothing terribly wrong with this from a technical standpoint; it just throws off things like man:top[1] and man:ps[1].

	man:rpc.statd[8] maps its status file (resident on [.filename]#/var#) into its address space;			man:rpc.statd[8] maps its status file ([.filename]#/var/db/statd.status#) into its address space;
	to save worrying about remapping the status file later when it needs to grow, it maps the status file with a generous size.			to save worrying about remapping the status file later when it needs to grow, it maps the status file with a generous size.
	This is very evident from the source code, where one can see that the length argument to man:mmap[2] is `0x10000000`,
	or one sixteenth of the address space on an IA32, or exactly 256 MB.

	[[unsetting-schg]]			[[unsetting-schg]]
	=== Why can I not unset the schg file flag?			=== Why can I not unset the schg file flag?

	The system is running at securelevel greater than 0.			The system is running at securelevel greater than 0.
	Lower the securelevel and try again.			Lower the securelevel and try again.
	For more information, see <<securelevel,the FAQ entry on securelevel>> and the man:init[8] manual page.			For more information, see <<securelevel,the FAQ entry on securelevel>> and the man:init[8] manual page.

	▲ Show 20 Lines • Show All 1,293 Lines • Show Last 20 Lines