Date: Sat, 24 Feb 2024 07:31:41 -0800 From: bob prohaska <fbsd@www.zefox.net> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-current@freebsd.org Subject: Re: Missing files on -current Message-ID: <ZdoL3Y/idexMVSMS@www.zefox.net> In-Reply-To: <ZdoE-__q6lrlr9Rg@albert.catwhisker.org> References: <ZdoC8Xqg9eA8%2BQ3R@www.zefox.net> <ZdoE-__q6lrlr9Rg@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 24, 2024 at 07:02:19AM -0800, David Wolfskill wrote: > > This is from an amd64 system at main-n268514-61b88a230bac, but > run_rc_scripts is a shell function defined in /etc/rc.subr. > > So the whine about not finding run_rc_scripts would indicate that at > least one of the following is true: > > * The script that should have sourced /etc/rc.subr failed to do so. > > * /etc/rc.csubr is corrupted, and fails to define run_rc_scripts(). > Indeed, it seems to be absent: root@:~ # more /etc/rc.csubr /etc/rc.csubr: No such file or directory root@:~ # However, the same is true of a Pi3 running 14-release p5. It boots reliably once it reaches loader. I wouldn't expect this part of the boot process to be platform dependent. Maybe -current and -release do things differently? > * /etc/rc.subr is missing. Present and accounted for: root@:~ # ls -l /etc/rc.subr -rw-r--r-- 1 root wheel 51911 Nov 18 21:46 /etc/rc.subr root@:~ # Thanks for writing! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZdoL3Y/idexMVSMS>