summaryrefslogtreecommitdiff
path: root/stand/defaults
Commit message (Collapse)AuthorAgeFilesLines
* Fix a few mandoc issuesGordon Bergling2020-10-091-1/+0
| | | | | | | | | | | | - whitespace at end of input line - skipping paragraph macro: Pp at the end of Sh - new sentence, new line - consider using OS macro: Fx - AUTHORS section without An macro - skipping paragraph macro: Pp before Ss Notes: svn path=/head/; revision=366575
* loader: zfs should support bootonce an nextbootToomas Soome2020-09-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bootonce feature is temporary, one time boot, activated by "bectl activate -t BE", "bectl activate -T BE" will reset the bootonce flag. By default, the bootonce setting is reset on attempt to boot and the next boot will use previously active BE. By setting zfs_bootonce_activate="YES" in rc.conf, the bootonce BE will be set permanently active. bootonce dataset name is recorded in boot pool labels, bootenv area. in case of nextboot, the nextboot_enable boolean variable is recorded in freebsd:nvstore nvlist, also stored in boot pool label bootenv area. On boot, the loader will process /boot/nextboot.conf if nextboot_enable is "YES", and will set nextboot_enable to "NO", preventing /boot/nextboot.conf processing on next boot. bootonce and nextboot features are usable in both UEFI and BIOS boot. To use bootonce/nextboot features, the boot loader needs to be updated on disk; if loader.efi is stored on ESP, then ESP needs to be updated and for BIOS boot, stage2 (zfsboot or gptzfsboot) needs to be updated (gpart or other tools). At this time, only lua loader is updated. Sponsored by: Netflix, Klara Inc. Differential Revision: https://reviews.freebsd.org/D25512 Notes: svn path=/head/; revision=365938
* Properly backout r362998Warner Losh2020-07-101-4/+4
| | | | | | | | | | Correct a small mistake in r363060's backaout of r362998 by reverse-applying r362998 by hand to loader.conf. Differential Revision: https://reviews.freebsd.org/D25606 Notes: svn path=/head/; revision=363063
* Revert r362998, r326999 while a better compatibility strategy is devised.Scott Long2020-07-091-1/+1
| | | | Notes: svn path=/head/; revision=363060
* Fix a example/docs typo from r362998, no functional change.Scott Long2020-07-071-1/+1
| | | | Notes: svn path=/head/; revision=362999
* Migrate the feature of excluding RAM pages to use "excludelist"Scott Long2020-07-071-4/+4
| | | | | | | | | as its nomenclature. MFC after: 1 week Notes: svn path=/head/; revision=362998
* loader.conf(5): document that loader_conf_files may be clobberedKyle Evans2020-04-301-1/+5
| | | | | | | | | | | | | | | | | | | | A future change in lualoader may take some liberties with the loader_conf_files in the name of efficiency; namely, it may start omitting it from the loader environment entirely so that it doesn't need to worry about maintaining any specific value. This variable has historically been incredibly volatile anyways, as it may get set to completely different values in any given configuration file to trigger a load of more files. Document now that we may not maintain it in the future, but perhaps we'll reserve the right to change our minds and eventually formally export all of the loader configuration files that were read using this variable. MFC after: 3 days Notes: svn path=/head/; revision=360486
* Preload hostuuid for early-boot useKyle Evans2020-04-161-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prison0's hostuuid will get set by the hostid rc script, either after generating it and saving it to /etc/hostid or by simply reading /etc/hostid. Some things (e.g. arbitrary MAC address generation) may use the hostuuid as a factor in early boot, so providing a way to read /etc/hostid (if it's available) and using it before userland starts up is desirable. The code is written such that the preload doesn't *have* to be /etc/hostid, thus not assuming that there will be newline at the end of the buffer or even the exact shape of the newline. White trailing whitespace/non-printables trimmed, the result will be validated as a valid uuid before it's used for early boot purposes. The preload can be turned off with hostuuid_load="NO" in /boot/loader.conf, just as other preloads; it's worth noting that this is a 37-byte file, the overhead is believed to be generally minimal. It doesn't seem necessary at this time to be concerned with kern.hostid. One does wonder if we should consider validating hostuuids coming in via jail_set(2); some bits seem to care about uuid form and we bother validating format of smbios-provided uuid and in-fact whatever uuid comes from /etc/hostid. Reviewed by: karels, delphij, jamie MFC after: 1 week (don't preload by default, probably) Differential Revision: https://reviews.freebsd.org/D24288 Notes: svn path=/head/; revision=359999
* Enable lualoader's kernel autodetection, disabled on install mediaKyle Evans2018-10-111-0/+1
| | | | | | | | | | | As documented in loader.conf(5), kernels_autodetect="YES" will cause the Lua scripts to effectively scan /boot for directories with a "kernel" file inside, to be listed in the loader menu. Approved by: re (kib) Notes: svn path=/head/; revision=339308
* Fix a minor typo in loader.conf(5).Glen Barber2018-10-101-1/+1
| | | | | | | | Approved by: re (kib) Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=339292
* lualoader: Create a module blacklist, add DRM modules to itKyle Evans2018-10-072-1/+11
| | | | | | | | | | | | | | | | | | This is a step in the process of easing migration into the new world order of DRM drivers. Strongly encourage users towards loading DRM modules via rc.conf(5) instead of loader.conf(5) by failing the load from loader(8). Users so inclined may wipe out the blacklist via module_blacklist="" in loader.conf(5), and it is expected that these modules will eventually be removed from the blacklist. They may still be loaded as dependencies of other modules or explicitly via the loader prompt, but this should not be a major problem. Approved by: re (rgrimes) Relnotes: yes Differential Revision: https://reviews.freebsd.org/D16914 Notes: svn path=/head/; revision=339218
* The kernel DTrace audit provider (dtaudit) relies on auditd(8) to loadRobert Watson2018-09-031-0/+5
| | | | | | | | | | | | | | | | | | | | /etc/security/audit_event to provide a list of audit event-number <-> name mappings. However, this occurs too late for anonymous tracing. With this change, adding 'audit_event_load="YES"' to /boot/loader.conf will cause the boot loader to preload the file, and then the kernel audit code will parse it to register an initial set of audit event-number <-> name mappings. Those mappings can later be updated by auditd(8) if the configuration file changes. Reviewed by: gnn, asomers, markj, allanjude Discussed with: jhb Approved by: re (kib) MFC after: 1 week Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D16589 Notes: svn path=/head/; revision=338443
* Document the cpu_microcode_* tunables.Mark Johnston2018-08-281-1/+25
| | | | | | | | | | Reviewed by: bcr (previous version), kib Approved by: re (gjb) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D16923 Notes: svn path=/head/; revision=338354
* Add microcode update configuration to the default loader.conf.Mark Johnston2018-08-131-0/+8
| | | | | | | | MFC after: 6 weeks Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=337716
* Default loader.conf: Drop efi_max_resolution to 1x1Kyle Evans2018-04-031-1/+1
| | | | | | | | | | | | | | | | | Effectively disabling the mode changing bits in the loader. No matter which way we go with it, it seems to be wrong- either the firmware doesn't change the resolution and reports the resolution we requested, or the firmware changes the resolution and doesn't report the resolution we requested. It some cases, it does the right thing, but the bad cases outweight those. Interested individuals can still set efi_max_resolution to 1080p or whatnot in loader.conf(5) to restore the new behavior, but the new behavior does not work out well for many cases. Discussed with: imp Notes: svn path=/head/; revision=331904
* loader.conf(5): Convert list of values to much better looking table formatKyle Evans2018-03-231-5/+11
| | | | | | | Discussed with: jhb, rpokala Notes: svn path=/head/; revision=331470
* loader.conf(5): Document efi_max_resolutionKyle Evans2018-03-231-1/+8
| | | | Notes: svn path=/head/; revision=331469
* efi loader: Respect efi_max_resolution in loader.conf(5)Kyle Evans2018-03-231-0/+3
| | | | | | | | | | | | | | | | | Default the max resolution to 1080p, we'll accept Width x Height specifications along with the following presets: - 480p - 720p - 1080p - 2160p or 4k - 5k PR: 224825 Differential Revision: https://reviews.freebsd.org/D14801 Notes: svn path=/head/; revision=331464
* Amend missed reference to /boot/overlays, moved to /boot/dtb/overlaysKyle Evans2018-03-191-1/+1
| | | | Notes: svn path=/head/; revision=331213
* Move /boot/overlays to /boot/dtb/overlaysKyle Evans2018-03-191-1/+1
| | | | | | | | | The former is fairly vague; these are FDT overlays to be applied to the running system, so /boot/dtb is a sensible location to put it without cluttering up /boot/dtb even further if desired. Notes: svn path=/head/; revision=331212
* loader.conf: remove obsolete non-x86 beastie menu statementEd Maste2018-03-191-2/+1
| | | | | | | | | As of r330005 the same loader.conf defaults are used on all platforms. Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=331207
* loader.conf(5): Document some other settingsKyle Evans2018-03-071-1/+18
| | | | | | | | | | These tend to have less coverage in other places and they don't have defaults as of yet, so mention them here: - fdt_overlays - kernels_autodetect (lualoader only) Notes: svn path=/head/; revision=330622
* Fix a typo: "now" -> "no".John Baldwin2018-02-261-1/+1
| | | | Notes: svn path=/head/; revision=330029
* These two directories build man pages, so it's incorrect to tag themWarner Losh2018-02-261-3/+1
| | | | | | | NO_OBJ. Also, make sure the loader.conf.5 man gets built and installed. Notes: svn path=/head/; revision=330021
* loader.conf is loader agnostic, so remove 4th references.Warner Losh2018-02-261-18/+0
| | | | Notes: svn path=/head/; revision=330007
* Take a meat cleaver to defaults/loader.confWarner Losh2018-02-261-428/+13
| | | | | | | | | | | | | | | | | Remove almost all of the _load=XXX options (kept only those relevant to splash screens, since there were other settings). Remove the excessively cutesy comment blocks. Remove excessive comments and replace with similar content Remove gratuitous blank lines (while leaving some) We have too many modules to list them all here. There's no purpose in doing so and it's a giant hassle to maintain. In addition the extra ~500 lines slow this down on small platforms. It slowed it down so much small platforms forked, which caused other issues... This is a compromise between those two extremes. Notes: svn path=/head/; revision=330006
* Go back to one loader.confWarner Losh2018-02-263-0/+910
We really only need one loader.conf. The other loader.conf was created because the current one took forever to parse in FORTH. That will be fixed in the next commit. Notes: svn path=/head/; revision=330005
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-22 10:17:52 +0000