src/etc/rc, branch releng/11.3FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F11.32018-04-04T16:59:10ZMFC r307826,r328949: Firstboot fs mount changes2018-04-04T16:59:10ZKyle Evanskevans@FreeBSD.org2018-04-04T16:59:10Zurn:sha1:6ad9aa79b92555bfd6223bd1d1bcd4fc5664a1af
MFC r307826: Use checkyesno instead of rolling my own..
MFC r328949: Fix firstboot fs mount logic
The firstboot logic has an error which causes the filesystem to be
mounted readonly even though root_rw_mount=YES. This fixes the error to
ensure that the root filesystem is mounted rw as expected after the run
of the firstboot scripts.
MFC r307469 (imp):2017-05-22T16:07:17ZGlen Barbergjb@FreeBSD.org2017-05-22T16:07:17Zurn:sha1:be52f88bd37bb13ee162eb5b682448516eec2d90
Allow root_rw_mount to be both lower and upper case. Before, if it was
upper case, you'd wind up with a read-only filesystem when you should
sometimes.
PR: 213549
Sponsored by: The FreeBSD Foundation
Try a little harder to remove firstboot and firstboot-reboot files in2016-01-06T17:13:40ZWarner Loshimp@FreeBSD.org2016-01-06T17:13:40Zurn:sha1:3e972f44093c9fa5f585388920bb1caccbe6ff15
case they accidentally get created as directories or with flags that
prevent their removal. While I wouldn't normally go the extra mile
here and let the normal unix rules prevail, the effects of failure are
large enough that extra care is warranted.
Use the more proper -f. Leave /bin/rm in place since that's what2016-01-05T21:20:47ZWarner Loshimp@FreeBSD.org2016-01-05T21:20:47Zurn:sha1:71b902050d159268fdc5e15c4fc9d143bf72bcaf
other rc scripts have, though it isn't strictly necessary.
Use /bin/rm to remove /firstboot*. Otherwise rm -i alias is picked2016-01-03T19:18:48ZWarner Loshimp@FreeBSD.org2016-01-03T19:18:48Zurn:sha1:d3e4bc1271f6d0df1dc6e728826c4c6423fbd2e5
up and can cause issues on boot with the prompts. Fix the read-only
root case with horrible kludge of mounting rw removing the files, then
mounting ro. But since that's no more horrible than the kludge of
using marker files in /. With this change, NanoBSD configs can safely
use /firstboot + growfs to produce minimal images that grow to the
size of the card.
The early-late divider was originally set to mountcritlocal. Since that2014-12-01T12:29:59ZDag-Erling Smørgravdes@FreeBSD.org2014-12-01T12:29:59Zurn:sha1:cd06771f0c1b1ab57a433c594426b61f124e7ca6
service does not run in jails, it was necessary to change it to something
else when jailed, and NETWORKING was arbitrarily chosen. The divider was
later moved to FILESYSTEMS when it was introduced, but the logic to change
it to NETWORKING when jailed remained. Remove it, as it no longer serves
any purpose.
PR: 194975
MFC after: 1 week
The rc system aggressively caches the contents of /etc/rc.conf in order to2013-12-03T21:55:57ZColin Percivalcperciva@FreeBSD.org2013-12-03T21:55:57Zurn:sha1:b6ae696fc9d8b84913d50c73ec94c926f5238725
improve boot performance; this produces arguably astonishing (non-)results
if /etc/rc.conf is modified during the boot process.
Since performance considerations make it infeasible to automatically detect
if the cached /etc/rc.conf parameters should be invalidated, provide a
mechanism for explicitly requesting that /etc/rc.conf be reloaded: Catch
SIGALRM and reload /etc/rc.conf if it is received.
Discussed on: freebsd-rc
MFC after: 3 days
Add support for "first boot" rc.d scripts. [1]2013-10-19T21:37:06ZColin Percivalcperciva@FreeBSD.org2013-10-19T21:37:06Zurn:sha1:cabad2645377fe097fc53e7403d2c5b3ed95ff9a
These scripts, containing
# KEYWORD: firstboot
will only be run if a sentinel file (default: /firstboot, configurable
via the rc.conf ${firstboot_sentinel} variable) exists; this sentinel
file will be deleted at the end of the boot process.
Scripts can request that the system reboot after the first boot by
creating the file ${firstboot_sentinel}-reboot.
This functionality is expected to be useful for embedded systems and
virtual machine images, where it may be desirable to
(a) download and install updates which became available between when
the image was created and when it was "turned on";
(b) download and install packages which may be newer than those
which were available when the image was created;
(c) install packages which run binaries during their install process,
bypassing the problem of cross-architecture installs;
(d) resize filesystems to match the disk onto which a VM image was
installed;
(e) perform initialization tasks relevant to cloud systems (e.g.,
Amazon's Elastic Compute Cloud);
and likely to perform many other one-time initialization functions.
Document this new functionality in rc.conf(5) and rc(8). [2]
Reviewed by: freebsd-current, freebsd-rc [1]
Reviewed by: Warren Block [2]
MFC after: 3 days
Refine the "nojail" rc keyword, adding "nojailvnet" for files that don't2013-05-19T04:10:34ZJamie Grittonjamie@FreeBSD.org2013-05-19T04:10:34Zurn:sha1:761d2bb5b9e70cf30f9c2dac62a47a2d2593e83f
apply to most jails but do apply to vnet jails. This includes adding
a new sysctl "security.jail.vnet" to identify vnet jails.
PR: conf/149050
Submitted by: mdodd
MFC after: 3 days
Hide stty(1) errors.2012-03-14T16:10:39ZEd Schoutened@FreeBSD.org2012-03-14T16:10:39Zurn:sha1:93bd0cdedd5ef285de4a7540281a0382d759e4fc
If rc(8) is executed without using a TTY, this error appears at the
beginning:
stty: stdin isn't a terminal
Because this is to be expected and of course not harmful, it is better
to simply hide the error message.
MFC after: 1 week