Re: mdnsd rcorder

[Greg Troxel <gdt%lexort.com@localhost>]

Martin Husemann <martin%duskware.de@localhost> writes:

> On Wed, May 21, 2025 at 05:30:11PM +0200, Edgar Fuß wrote:
>> > If you have /usr on a separate partition, you need to add it to
>> > 
>> > 	critical_filesystems_local
>> > 
>> > (see rc.conf(5)).
>> Where exactly does it say that?
>
> Not explecitily, I was more refering to the description of the variable:
>
> 	File systems mounted very early in the system
> 	boot before networking services are available.
>
> There are various things that may break in rc.d land if /usr is not available
> early (so I have it in critical_filesystems_local on all machines that have
> /usr separate, but I forgot what exactly triggered it - and I am not using
> mdnsd).

>> What if I had /usr on NFS?

If you are mounting /usr from NFS, then it belongs in
critical_filesystems_remote.

> Not sure you could make that work with mdnsd and the current rc.d scripts.

I suspect that it would be ok, assuming
critical_filesystems_remote=/usr, but also that using zeroconf hostnames
for NFS mounting would not work.

Basically, it was solid tradition long ago to NFS mount the system (80s
and early 90s), and my take is that it's now a niche thing for some lab
setups and test booting.

So if /usr and /var are on local disk, they belong in
critical_filesystems_local.  It would be cool to automate that.

And if you are NFS_mounting /usr and /var but not / well you will have
to figure it out because it's hard.