Egregoros · Phoenix Framework

Timeline

Post

Remote status

Context

Dan Langille

@dvl@bsd.network remote

Let's see what happens if I reboot all my hosts at the same time...

#FreeBSD

Replying to @dvl@bsd.network

Dan Langille

@dvl@bsd.network remote

Two hosts came back with bad /etc/resolv.conf

I fixed it with 'resolvconf=NO` in /etc/resolvconf.conf and `mv /etc/resolvconf.conf.bak /etc/resolvconf.conf `

Replies

Replying to @dvl@bsd.network

feld

@feld@friedcheese.us remote

@dvl it really took me too much work to find that configuration to disable this behavior

Replying to @feld@friedcheese.us

dch

@dch@bsd.network remote

@feld @dvl I seriously hate resolvconf and it should be disabled by default. In the same way you don’t leave a running chainsaw on the floor with kids around.

Replying to @dch@bsd.network

Dan Langille

@dvl@bsd.network remote

@dch @feld

I don't like it, I can see it being useful for a laptop, not a server.

Replying to @dch@bsd.network

Tom

@pertho@mastodon.bsd.cafe remote

@dch @feld @dvl I'm still annoyed my network has priority=5 in /etc/wpa_supplicant.conf but it decides to connect to the free & open WiFi network instead that is priority=0 until I comment that thing out and restart netif.

Replying to @pertho@mastodon.bsd.cafe

Dan Langille

@dvl@bsd.network remote

@pertho @dch @feld

Oh.

One thing I rely on is my laptop always connecting to my hotspot if it sees it.

For example, when I'm at home, get on that hotspot when your laptop starts up. I use that for debugging / verifying some stuff so I'm not coming at the problem from within the homelab.