Differential D31926 Diff 95469 documentation/content/en/articles/linux-users/_index.adoc

Changeset View

Standalone View

documentation/content/en/articles/linux-users/_index.adoc

Context not available.
	:sectnumlevels: 6	:sectnumlevels: 6
	:source-highlighter: rouge	:source-highlighter: rouge
	:experimental:	:experimental:
		:images-path: articles/linux-users/
	ifeval::["{backend}" == "html5"]
	include::shared/en/urls.adoc[]	ifdef::env-beastie+backend-html5[]
	endif::[]	include::shared/authors.adoc[]
		include::shared/mirrors.adoc[]
	ifeval::["{backend}" == "pdf"]	include::shared/releases.adoc[]
	include::../../../../shared/en/urls.adoc[]	include::shared/{{% lang %}}/mailing-lists.adoc[]
		include::shared/{{% lang %}}/urls.adoc[]
		:imagesdir: ../../../images/{images-path}
	endif::[]	endif::[]

	ifeval::["{backend}" == "epub3"]	ifndef::env-beastie[]
	include::../../../../shared/en/urls.adoc[]	include::../../../../shared/asciidoctor.adoc[]
	endif::[]	endif::[]

	[.abstract-title]	[.abstract-title]
Context not available.
	This document highlights some of the technical differences between FreeBSD and Linux(R) so that intermediate to advanced Linux(R) users can quickly familiarize themselves with the basics of FreeBSD.	This document highlights some of the technical differences between FreeBSD and Linux(R) so that intermediate to advanced Linux(R) users can quickly familiarize themselves with the basics of FreeBSD.

	This document assumes that FreeBSD is already installed.	This document assumes that FreeBSD is already installed.
	Refer to the link:{handbook}#bsdinstall[Installing FreeBSD] chapter of the FreeBSD Handbook for help with the installation process.	Refer to the extref:{handbook}[Installing FreeBSD, bsdinstall] chapter of the FreeBSD Handbook for help with the installation process.

	[[shells]]	[[shells]]
	== Default Shell	== Default Shell
Context not available.
	man:sh[1] is very similar to Bash but with a much smaller feature-set.	man:sh[1] is very similar to Bash but with a much smaller feature-set.
	Generally shell scripts written for man:sh[1] will run in Bash, but the reverse is not always true.	Generally shell scripts written for man:sh[1] will run in Bash, but the reverse is not always true.

	However, Bash and other shells are available for installation using the FreeBSD link:{handbook}#ports[Packages and Ports Collection].	However, Bash and other shells are available for installation using the FreeBSD extref:{handbook}[Packages and Ports Collection, ports].

	After installing another shell, use man:chsh[1] to change a user's default shell.	After installing another shell, use man:chsh[1] to change a user's default shell.
	It is recommended that the `root` user's default shell remain unchanged since shells which are not included in the base distribution are installed to [.filename]#/usr/local/bin#.	It is recommended that the `root` user's default shell remain unchanged since shells which are not included in the base distribution are installed to [.filename]#/usr/local/bin#.
Context not available.
	# pkg install apache24	# pkg install apache24
	....	....

	For more information on packages refer to section 5.4 of the FreeBSD Handbook: link:{handbook}#pkgng-intro[Using pkgng for Binary Package Management].	For more information on packages refer to section 5.4 of the FreeBSD Handbook: extref:{handbook}[Using pkgng for Binary Package Management, pkgng-intro].

	[[ports]]	[[ports]]
	=== Ports	=== Ports
Context not available.
	When installing a port, the system will fetch the source code, apply any required patches, compile the code, and install the application and any required dependencies.	When installing a port, the system will fetch the source code, apply any required patches, compile the code, and install the application and any required dependencies.

	The Ports Collection, sometimes referred to as the ports tree, can be installed to [.filename]#/usr/ports# using man:portsnap[8].	The Ports Collection, sometimes referred to as the ports tree, can be installed to [.filename]#/usr/ports# using man:portsnap[8].
	Detailed instructions for installing the Ports Collection can be found in link:{handbook}#ports-using[section 5.5] of the FreeBSD Handbook.	Detailed instructions for installing the Ports Collection can be found in extref:{handbook}[section 5.5, ports-using] of the FreeBSD Handbook.

	To compile a port, change to the port's directory and start the build process. The following example installs Apache 2.4 from the Ports Collection:	To compile a port, change to the port's directory and start the build process. The following example installs Apache 2.4 from the Ports Collection:

Context not available.
	# make WITH_LDAP="YES" install clean	# make WITH_LDAP="YES" install clean
	....	....

	Refer to link:{handbook}#ports-using[Using the Ports Collection] for more information.	Refer to extref:{handbook}[Using the Ports Collection, ports-using] for more information.

	[[startup]]	[[startup]]
	== System Startup	== System Startup
Context not available.
	The scripts in [.filename]#/usr/local/etc/rc.d/# are for user-installed applications such as Apache and Squid.	The scripts in [.filename]#/usr/local/etc/rc.d/# are for user-installed applications such as Apache and Squid.

	Since FreeBSD is developed as a complete operating system, user-installed applications are not considered to be part of the "base" system.	Since FreeBSD is developed as a complete operating system, user-installed applications are not considered to be part of the "base" system.
	User-installed applications are generally installed using link:{handbook}#ports-using[Packages or Ports].	User-installed applications are generally installed using extref:{handbook}[Packages or Ports, ports-using].
	In order to keep them separate from the base system, user-installed applications are installed under [.filename]#/usr/local/#.	In order to keep them separate from the base system, user-installed applications are installed under [.filename]#/usr/local/#.
	Therefore, user-installed binaries reside in [.filename]#/usr/local/bin/#, configuration files are in [.filename]#/usr/local/etc/#, and so on.	Therefore, user-installed binaries reside in [.filename]#/usr/local/bin/#, configuration files are in [.filename]#/usr/local/etc/#, and so on.

Context not available.
	FreeBSD does not use Linux(R) IPTABLES for its firewall.	FreeBSD does not use Linux(R) IPTABLES for its firewall.
	Instead, FreeBSD offers a choice of three kernel level firewalls:	Instead, FreeBSD offers a choice of three kernel level firewalls:

	* link:{handbook}#firewalls-pf[PF]	* extref:{handbook}[PF, firewalls-pf]
	* link:{handbook}#firewalls-ipf[IPFILTER]	* extref:{handbook}[IPFILTER, firewalls-ipf]
	* link:{handbook}#firewalls-ipfw[IPFW]	* extref:{handbook}[IPFW, firewalls-ipfw]

	PF is developed by the OpenBSD project and ported to FreeBSD.	PF is developed by the OpenBSD project and ported to FreeBSD.
	PF was created as a replacement for IPFILTER and its syntax is similar to that of IPFILTER.	PF was created as a replacement for IPFILTER and its syntax is similar to that of IPFILTER.
Context not available.

	====	====

	For more information on source and binary updates, refer to link:{handbook}#updating-upgrading[the chapter on updating] in the FreeBSD Handbook.	For more information on source and binary updates, refer to extref:{handbook}[the chapter on updating, updating-upgrading] in the FreeBSD Handbook.

	[[procfs]]	[[procfs]]
	== procfs: Gone But Not Forgotten	== procfs: Gone But Not Forgotten
Context not available.
	== Conclusion	== Conclusion

	This document has provided an overview of FreeBSD.	This document has provided an overview of FreeBSD.
	Refer to the link:{handbook}[FreeBSD Handbook] for more in-depth coverage of these topics as well as the many topics not covered by this document.	Refer to the extref:{handbook}[FreeBSD Handbook] for more in-depth coverage of these topics as well as the many topics not covered by this document.
Context not available.