Difference between revisions of "/boot/loader.conf"
From GhostBSD Wiki
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Welcome}} | {{Welcome}} | ||
| − | + | ||
==Introduction== | ==Introduction== | ||
This is the place to make changes. | This is the place to make changes. | ||
| − | The file loader.conf contains descriptive information on bootstrapping the system. Through it you can specify the kernel to be booted, parameters to be passed to it, and additional modules to be loaded; and gener ally set all variables described in [https://www.freebsd.org/cgi/man.cgi?query=loader.conf&sektion=5&manpath=freebsd-release-ports loader(8)] | + | The file loader.conf contains descriptive information on bootstrapping the system. Through it you can specify the kernel to be booted, parameters to be passed to it, and additional modules to be loaded; and gener ally set all variables described in [https://www.freebsd.org/cgi/man.cgi?query=loader.conf&sektion=5&manpath=freebsd-release-ports loader.conf(8)] |
| + | Though loader.conf's format was defined explicitly to resemble [https://www.freebsd.org/cgi/man.cgi?query=rc.conf&sektion=5&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports rc.conf(5)], and can be sourced by [https://www.freebsd.org/cgi/man.cgi?query=sh&sektion=1&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports sh(1)], some settings are treated in a special fashion. Also, the behavior of some settings is defined by the setting's suffix; the prefix identifies which module the setting controls. | ||
You may also find more information on [[/boot/defaults/loader.conf]] | You may also find more information on [[/boot/defaults/loader.conf]] | ||
| Line 25: | Line 26: | ||
|- | |- | ||
|hw.psm.synaptics_support="1" | |hw.psm.synaptics_support="1" | ||
| − | | | + | |To enable [https://www.freebsd.org/cgi/man.cgi?query=psm&sektion=4&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports psm(4)] Synaptics support, add this line to /boot/loader.conf; [https://wiki.freebsd.org/SynapticsTouchpad Synaptics Touchpad] |
|- | |- | ||
|net.inet.ip.fw.default_to_accept="1" | |net.inet.ip.fw.default_to_accept="1" | ||
| − | | | + | |When first creating or testing a firewall ruleset, consider temporarily setting this tunable; This sets the default policy of [https://www.freebsd.org/cgi/man.cgi?query=ipfw&sektion=8&manpath=freebsd-release-ports ipfw(8)] to be more permissive than the default deny ip from any to any, making it slightly more difficult to get locked out of the system right after a reboot. [https://www.freebsd.org/doc/handbook/firewalls-ipfw.html#30.4.3. Example Ruleset 30.4.3. Example Ruleset] |
|- | |- | ||
|boot_mute="YES" | |boot_mute="YES" | ||
| − | | | + | |This option is intended to suppress all boot time messages following the timed delay message. Only the boot prob messages are being suppressed. All the starting services messages are NOT being suppressed. [https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228193] |
|- | |- | ||
|crypto_load="YES" | |crypto_load="YES" | ||
| − | | | + | |make sure crypto is loaded [https://antranigv.am/weblog_en/posts/freebsd-geli-encryption-usb-and-zvol/] |
|- | |- | ||
|aesni_load="YES" | |aesni_load="YES" | ||
| − | | | + | |driver for the AES and SHA accelerator on x86 CPUs [https://www.freebsd.org/cgi/man.cgi?query=aesni&sektion=4] |
| + | |||
|- | |- | ||
|geom_eli_load="YES" | |geom_eli_load="YES" | ||
| − | | | + | |make sure geom_eli is loaded [https://antranigv.am/weblog_en/posts/freebsd-geli-encryption-usb-and-zvol/] |
|- | |- | ||
|vfs.zfs.arc_max="512M" | |vfs.zfs.arc_max="512M" | ||
| − | | | + | |ZFS Tuning [https://wiki.freebsd.org/ZFSTuningGuide] |
|- | |- | ||
|zfs_load="YES" | |zfs_load="YES" | ||
| − | | | + | |Load ZFS |
| − | + | ||
| − | + | ||
| − | + | ||
|- | |- | ||
|vboxdrv_load="YES" | |vboxdrv_load="YES" | ||
| − | | | + | |To make shure, that the kernelmodul for VirtualBox will be loaded after start [https://www.freebsd.org/doc/de_DE.ISO8859-1/books/handbook/virtualization-host-virtualbox.html] |
|} | |} | ||
| Line 60: | Line 59: | ||
|} | |} | ||
| − | [[Category: | + | [[Category:Booting]] |
Latest revision as of 07:44, 6 February 2020
Welcome to  /boot/loader.conf.
|
Introduction[edit]
This is the place to make changes. The file loader.conf contains descriptive information on bootstrapping the system. Through it you can specify the kernel to be booted, parameters to be passed to it, and additional modules to be loaded; and gener ally set all variables described in loader.conf(8) Though loader.conf's format was defined explicitly to resemble rc.conf(5), and can be sourced by sh(1), some settings are treated in a special fashion. Also, the behavior of some settings is defined by the setting's suffix; the prefix identifies which module the setting controls. You may also find more information on /boot/defaults/loader.conf
Content[edit]
This is an examble:
| Directory | Description |
|---|---|
| loader_brand="ghostbsd" | |
| loader_logo="ghostbsd" | |
| loader_menu_title="Welcome to GhostBSD" | |
| hw.psm.synaptics_support="1" | To enable psm(4) Synaptics support, add this line to /boot/loader.conf; Synaptics Touchpad |
| net.inet.ip.fw.default_to_accept="1" | When first creating or testing a firewall ruleset, consider temporarily setting this tunable; This sets the default policy of ipfw(8) to be more permissive than the default deny ip from any to any, making it slightly more difficult to get locked out of the system right after a reboot. Example Ruleset 30.4.3. Example Ruleset |
| boot_mute="YES" | This option is intended to suppress all boot time messages following the timed delay message. Only the boot prob messages are being suppressed. All the starting services messages are NOT being suppressed. [1] |
| crypto_load="YES" | make sure crypto is loaded [2] |
| aesni_load="YES" | driver for the AES and SHA accelerator on x86 CPUs [3] |
| geom_eli_load="YES" | make sure geom_eli is loaded [4] |
| vfs.zfs.arc_max="512M" | ZFS Tuning [5] |
| zfs_load="YES" | Load ZFS |
| vboxdrv_load="YES" | To make shure, that the kernelmodul for VirtualBox will be loaded after start [6] |
Back to the  Directory Structure to .conf Files or to /boot/
|
|---|
