FreeBSD - Revision history

Leo: Text replacement - "{\| " to "{| class="wikitable" "

2019-09-01T01:36:40Z

Text replacement - "{\| " to "{| class="wikitable" "

← Older revision		Revision as of 01:36, 1 September 2019
Line 40:		Line 40:
	=== Kernel Modules ===		=== Kernel Modules ===
	Kernel modules can be loaded/unloaded or listed like you would on linux.		Kernel modules can be loaded/unloaded or listed like you would on linux.
	{\|		{\| class="wikitable"
	! FreeBSD		! FreeBSD
	! Linux		! Linux
Line 102:		Line 102:

	Refer to the following table for a quick usage guide and its equivalent {{code\|yum}} or {{code\|dnf}} commands.		Refer to the following table for a quick usage guide and its equivalent {{code\|yum}} or {{code\|dnf}} commands.
	{\|		{\| class="wikitable"
	! RedHat / Fedora		! RedHat / Fedora
	! FreeBSD		! FreeBSD
Line 173:		Line 173:

	Portmaster usage in a nutshell:		Portmaster usage in a nutshell:
	{\|		{\| class="wikitable"
	! Command		! Command
	! Description		! Description
Line 214:		Line 214:
	Security updates can be applied to the FreeBSD system by using the {{code\|freebsd-update}} utility <ref>[https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html#freebsdupdate-security-patches Applying Security Patches]</ref>. This utility can also be used to upgrade a system to a newer major or minor release.		Security updates can be applied to the FreeBSD system by using the {{code\|freebsd-update}} utility <ref>[https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html#freebsdupdate-security-patches Applying Security Patches]</ref>. This utility can also be used to upgrade a system to a newer major or minor release.

	{\|		{\| class="wikitable"
	! Command		! Command
	! Description		! Description
Line 295:		Line 295:

	=== Linux Util Equivalents ===		=== Linux Util Equivalents ===
	{\|		{\| class="wikitable"
	! Description		! Description
	! Linux		! Linux

Leo: /* Portmaster */

2018-06-02T20:45:29Z

Portmaster

← Older revision		Revision as of 20:45, 2 June 2018
Line 201:		Line 201:

	Before updating any ports, it's a good idea to review any changes by viewing {{code\|/usr/ports/UPDATING}}.		Before updating any ports, it's a good idea to review any changes by viewing {{code\|/usr/ports/UPDATING}}.

			To clean up afterwards:

			{{highlight\|lang=terminal\|code=
			# portmaster --check-depends
			# portmaster --check-port-dbdir
			# portmaster -s
			# portmaster -y --clean-distfiles
			}}

	== System Update ==		== System Update ==

Leo at 20:43, 2 June 2018

2018-06-02T20:43:25Z

@@ Line 5: / Line 5: @@
 Default settings not specified in {{code|/etc/rc.conf}} are included from {{code|/etc/defaults/rc.conf}}. Additional settings can also be placed in separate files in {{code|/etc/rc.conf.d}}.
 === Network ===
@@ Line 38: / Line 37: @@
 # /etc/rc.d/routing restart
 }}
 === Kernel Modules ===
@@ Line 74: / Line 71: @@
 Most modules should have a startup script which gets triggered by an entry in {{code|/etc/rc.conf}}. Alternatively, it can also be loaded by adding a line to {{code|/etc/loader.conf}}.
 == Package Management ==

Leo: /* Package Management */

2018-06-02T18:33:05Z

Package Management

← Older revision		Revision as of 18:33, 2 June 2018
Line 76:		Line 76:

	== Package Management ==		== Package Management ==
	There are two ways to obtain software on your FreeBSD machine: Through precompiled packages, or using FreeBSD ~~Ports. Both will be covered in the sections below~~.		There are two ways to obtain software on your FreeBSD machine: Through precompiled packages or using FreeBSD's port collection.

	=== Pkg Package Management ===		=== Pkg Package Management ===
	{{code\|pkg}} is package management utility that downloads and installs packages from FreeBSD's pkg service at http://pkg.freebsd.org/ and is available on FreeBSD versions after 10.x.		{{code\|pkg}} is package management utility that downloads and installs packages from FreeBSD's pkg service at http://pkg.freebsd.org/ and is available on FreeBSD versions after 10.x.

	~~Bootstrap the system by running~~ {{code\|/usr/sbin/pkg}}~~, or install it through ports under {{code\|/usr/ports/ports-mgmt/pkg}}~~.		The {{code\|/usr/sbin/pkg}} should already be installed as part of the system.

	~~If you are familiar with~~ {{code\|yum}} or {{code\|dnf}}~~, this table may help:~~		Refer to the following table for a quick usage guide and its equivalent {{code\|yum}} or {{code\|dnf}} commands.
	{\|		{\|
	! RedHat / Fedora		! RedHat / Fedora
Line 119:		Line 119:

	=== FreeBSD Ports ===		=== FreeBSD Ports ===
	The ~~port system automates building~~ and ~~installing packages on~~ your system ~~from source~~. ~~Rather than trusting pre-compiled 3rd party packages, the~~ ports ~~system allows you~~ to ~~customize and compile a software package along with its dependencies~~.		The ports collection is a set of makefiles, patches, and description files stored in {{code\|/usr/ports}}. These files provide a way to bootstrap the build and install of applications to your system.

			The ports collection can be obtained by downloading and extracting it to {{code\|/usr/ports}} using {{code\|portsnap}}.

	~~To get started, updates the ports collection on your system:~~
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	## Download the ports collection to /var/db/portsnap		## Download the ports collection to /var/db/portsnap
Line 129:		Line 130:
	}}		}}

	~~You may want to update~~ the ~~ports~~ collection ~~to get~~ software updates ~~periodically in the future. To do so~~, ~~run~~:		Since the port collection will change periodically with new applications and software updates, an update can be pulled by running:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# portsnap fetch update		# portsnap fetch update
	}}		}}

	To compile and install a port, go to ~~the directory of the~~ port to ~~be installed~~ and ~~then~~ run {{code\|make install}}.		==== Using Ports ====
			To compile and install a port, go to {{code\|/usr/ports}} and navigate to a port you wish to install and run {{code\|make install}}.

	~~Most packages have configurations~~ that ~~can be customized. For larger packages with many~~ dependencies~~, this may become unwieldy~~. ~~There are two ways around this: One is to ask for~~ all the ~~customization options up front by running~~ {{code\|make config-recursive}} prior to {{code\|make install}}~~; the other is to use~~ the default ~~options~~ by ~~setting~~ the environment variable {{code\|1=BATCH=yes}}.		Depending on the application, you will be asked to configure build options that are available for the program as well as its dependencies as they're built. You can configure all build options before the compilation process using {{code\|make config-recursive}} prior to {{code\|make install}}. To accept the default configurations set by the package, define an environment variable {{code\|1=BATCH=yes}} when running {{code\|make install}}.

	After building a port, it is a good idea to clean the port's working directory to reduce wasted space by running {{code\|make clean}}.		After building a port, it is a good idea to clean the port's working directory to reduce wasted space by running {{code\|make clean}}.
Line 142:		Line 144:
	To remove an installed port, use either {{code\|pkg delete}} or run {{code\|make deinstall}} in the port's directory.		To remove an installed port, use either {{code\|pkg delete}} or run {{code\|make deinstall}} in the port's directory.

	~~There are utilities that make using ports more convenient.~~ {{code\|portmaster}} ~~works like~~ a ~~package manager by automating upgrades~~ and ~~installs~~ on the system. Eg:		==== Portmaster ====
			{{code\|portmaster}} is a shell script used for installing and updating installed ports on the system. It is capable of reading package information from {{code\|/var/db/pkg}} to determine which packages need to be updated.

			{{code\|portmaster}} can be installed via ports:
			{{highlight\|lang=terminal\|code=
			# portsnap fetch update
			# cd /usr/ports/ports-mgmt/portmaster
			# make install clean
			}}

			Portmaster usage in a nutshell:
	{\|		{\|
	! Command		! Command
Line 160:		Line 172:
	# portmaster shells/bash		# portmaster shells/bash
	}}		}}
	\| Automatically builds and installs the port package		\| Automatically builds and installs/upgrades the port package
			\|-
			\| {{highlight\|lang=terminal\|code=
			# portmaster -dw shells/bash
			}}
			\| Automatically builds and installs/upgrades the port package, but with:
			* {{code\|-d}} - clean up installation files in {{code\|/usr/ports/distfiles}}.
			* {{code\|-w}} - save old shared libraries (in {{code\|/usr/local/lib/compat/pkg/}}) before uninstalling the existing port, allowing those libraries to potentially be restored.
	\|}		\|}

	~~=== Checking for Updates ===~~		Before updating any ports, it's a good idea to review any changes by viewing {{code\|/usr/ports/UPDATING}}.
	~~Regardless of which method you used~~ to ~~install packages, you can check for newer versions of packages or ports~~ by ~~updating ports or the package cache and then running:~~

	{{~~highlight~~\|~~lang=terminal\|code=~~
	~~# pkg version -1 "<"~~
	}}

	== System Update ==		== System Update ==

Leo at 17:56, 2 June 2018

2018-06-02T17:56:14Z

← Older revision		Revision as of 17:56, 2 June 2018
Line 252:		Line 252:

	== Miscellaneous ==		== Miscellaneous ==
	~~=== Encrypted swap ===~~
	* [[Hardening/FreeBSD#Encrypted_swap\|Hardening/FreeBSD]]

	=== Linux Util Equivalents ===		=== Linux Util Equivalents ===
Line 335:		Line 333:
	* Buffers: Disk cache		* Buffers: Disk cache
	* Free: Memory that is completely free and ready to use.		* Free: Memory that is completely free and ready to use.

			== Questions ==
			What are the equivalents for:
			* cat /proc/cpuinfo, lscpu



	== Links ==		== Links ==

Leo: /* Miscellaneous */

2017-09-02T21:59:52Z

Miscellaneous

@@ Line 254: / Line 254: @@
 === Encrypted swap ===
 * [[Hardening/FreeBSD#Encrypted_swap|Hardening/FreeBSD]]
 === Linux Binary Emulation ===

Leo at 18:34, 6 August 2017

2017-08-06T18:34:42Z

Show changes

Leo: /* Linux compatibility */

2017-08-05T00:21:30Z

Linux compatibility

← Older revision		Revision as of 00:21, 5 August 2017
Line 308:		Line 308:
	}}		}}

	Set {{code\|linux_enable="YES"}} in {{code\|/etc/rc.conf}}.		Set {{code\|1=linux_enable="YES"}} in {{code\|/etc/rc.conf}}.


	=== Screensaver ===		=== Screensaver ===

Leo: /* Memory */ pipe

2017-08-05T00:21:05Z

Memory: pipe

← Older revision		Revision as of 00:21, 5 August 2017
Line 349:		Line 349:
	FreeBSD memory notation is quite different <ref>[http://unix.stackexchange.com/questions/134862/what-do-the-different-memory-counters-in-freebsd-mean What do the different memory counters in FreeBSD mean?]</ref>. Running top shows various numbers:		FreeBSD memory notation is quite different <ref>[http://unix.stackexchange.com/questions/134862/what-do-the-different-memory-counters-in-freebsd-mean What do the different memory counters in FreeBSD mean?]</ref>. Running top shows various numbers:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	$ top -b -d 1 \| grep -A1 ^Mem		$ top -b -d 1 {{!}} grep -A1 ^Mem
	Mem: 112M Active, 687M Inact, 158M Wired, 8268K Cache, 87M Buf, 12M Free		Mem: 112M Active, 687M Inact, 158M Wired, 8268K Cache, 87M Buf, 12M Free
	Swap: 1024M Total, 41M Used, 983M Free, 3% Inuse		Swap: 1024M Total, 41M Used, 983M Free, 3% Inuse

Leo: /* Configuration */

2017-08-05T00:20:31Z

Configuration

← Older revision		Revision as of 00:20, 5 August 2017
Line 295:		Line 295:

	=== Linux compatibility ===		=== Linux compatibility ===
			Mount {{code\|linuxprocfs}} and install {{code\|linux-f10-procps}}<ref>[https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/linuxemu.html Linux® Binary Compatibility]</ref>:

	~~Mount <tt>linuxprocfs</tt> and install <tt>linux-f10-procps</tt><ref>[https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/linuxemu.html Linux® Binary Compatibility]</ref>:~~		{{highlight\|lang=terminal\|code=
			$ grep ^lin /etc/fstab
	$ grep ^lin /etc/fstab		linprocfs /compat/linux/proc linprocfs rw 0 0
	linprocfs /compat/linux/proc linprocfs rw 0 0		linsys /compat/linux/sys linsysfs rw 0 0
	linsys /compat/linux/sys linsysfs rw 0 0

	~~$ sudo mkdir -p /compat/linux/{proc,sys}~~
	~~$ sudo mount /compat/linux/proc && sudo mount /compat/linux/sys~~

	$ sudo ~~pkg install~~ linux~~-f10-procps~~		$ sudo mkdir -p /compat/linux/{proc,sys}
			$ sudo mount /compat/linux/proc && sudo mount /compat/linux/sys

	~~Set <tt>linux_enable="YES"</tt> in <tt>/etc/rc.conf</tt>.~~		$ sudo pkg install linux-f10-procps
			}}

	=~~== Screensaver ===~~		Set {{code\|linux_enable="YES"}} in {{code\|/etc/rc.conf}}.

	On this laptop I wanted to have the LCD shut off when the (text) console was idle<ref>[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=114928 green_saver does not switch DVI monitor power off]</ref><ref>[http://lists.freebsd.org/pipermail/freebsd-current/2010-November/021589.html Should green_saver.ko shut off a laptop's backlight?]</ref>

	$ cat /etc/rc.conf		=== Screensaver ===
	[...]		To have the LCD shut off when the text console is idle<ref>[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=114928 green_saver does not switch DVI monitor power off]</ref><ref>[http://lists.freebsd.org/pipermail/freebsd-current/2010-November/021589.html Should green_saver.ko shut off a laptop's backlight?]</ref>
	apm_enable="YES"		{{highlight\|lang=terminal\|code=
	blanktime="60"		$ cat /etc/rc.conf
	saver="blank"		[...]
			apm_enable="YES"
			blanktime="60"
			saver="blank"
			}}

	Enable APM<ref>[https://www.freebsd.org/doc/en/articles/laptop/article.html#power-management FreeBSD on Laptops: APM]</ref> in ~~<tt>~~device.hints~~</tt>~~<ref>[https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/device-hints.html 13.4. Device Hints]</ref>		Enable Advanced Power Management (APM) <ref>[https://www.freebsd.org/doc/en/articles/laptop/article.html#power-management FreeBSD on Laptops: APM]</ref> in {{code\|device.hints}} <ref>[https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/device-hints.html 13.4. Device Hints]</ref>

	$ grep apm.0.disabled /boot/device.hints		{{highlight\|lang=terminal\|code=
	hint.apm.0.disabled="0"		$ grep apm.0.disabled /boot/device.hints
			hint.apm.0.disabled="0"
			}}

	=== SMART ===		=== SMART ===

	To enable {{WP\|~~S.M.A.R.T.\|S.M.A.R.T.~~}}~~, use <tt>smartmontools</tt>~~:<ref>[http://www.smartmontools.org/ smartmontools]</ref><ref>[http://www.freebsddiary.org/smart.php Monitoring your HDD using SMART and Nagios]</ref>		To enable SMART, install {{code\|smartmontools}}: <ref>[http://www.smartmontools.org/ smartmontools]</ref><ref>[http://www.freebsddiary.org/smart.php Monitoring your HDD using SMART and Nagios]</ref>

	~~pkg install smartmontools~~
	~~echo 'smartd_enable="YES"' >> /etc/rc.conf~~
	~~cp -i /usr/local/etc/smartd.conf.sample /usr/local/etc/smartd.conf~~

	~~Start <tt~~>smartd</~~tt> and~~		{{highlight\|lang=terminal\|code=
			# pkg install smartmontools
			# echo 'smartd_enable="YES"' >> /etc/rc.conf
			# cp -i /usr/local/etc/smartd.conf.sample /usr/local/etc/smartd.conf
			}}

	/usr/local/etc/rc.d/smartd start		Start {{code\|smartd}} manually:
			{{highlight\|lang=terminal\|code=
			# /usr/local/etc/rc.d/smartd start
			}}

	The installation package should have created ~~<tt>~~/usr/local/etc/periodic/daily/smart~~</tt>~~ to check on monitored devices periodically.		The installation package should have created {{code\|/usr/local/etc/periodic/daily/smart}} to check on monitored devices periodically.

	=== Memory ===		=== Memory ===

	FreeBSD memory notation is quite different~~, let's explain it in short:~~<ref>[http://unix.stackexchange.com/questions/134862/what-do-the-different-memory-counters-in-freebsd-mean What do the different memory counters in FreeBSD mean?]</ref>		FreeBSD memory notation is quite different <ref>[http://unix.stackexchange.com/questions/134862/what-do-the-different-memory-counters-in-freebsd-mean What do the different memory counters in FreeBSD mean?]</ref>. Running top shows various numbers:
			{{highlight\|lang=terminal\|code=
	$ top -b -d 1 \| grep -A1 ^Mem		$ top -b -d 1 \| grep -A1 ^Mem
	Mem: 112M Active, 687M Inact, 158M Wired, 8268K Cache, 87M Buf, 12M Free		Mem: 112M Active, 687M Inact, 158M Wired, 8268K Cache, 87M Buf, 12M Free
	Swap: 1024M Total, 41M Used, 983M Free, 3% Inuse		Swap: 1024M Total, 41M Used, 983M Free, 3% Inuse
			}}

			These values are:
	* Active: Memory currently being used by a process		* Active: Memory currently being used by a process
	* Inactive: Memory that has been freed but is still cached since it may be used again.		* Inactive: Memory that has been freed but is still cached since it may be used again.
Line 352:		Line 361:
	* Buffers: Disk cache		* Buffers: Disk cache
	* Free: Memory that is completely free and ready to use.		* Free: Memory that is completely free and ready to use.


	== Links ==		== Links ==