On 2011-05-08, at 1:54 PM, Chris Smith wrote: > After an update to -current yesterday Internet access was lost as > pf.conf could not be loaded. The error message was: > pfctl: DIOCADDRULE: Operation not supported by device > > This error occurred after upgrading the kernel and then rebooting. > After userland was brought up to date as well and the system rebooted > everything was fine. The system in question was local so outside of > being offline for the amount of time it took to build userland there > wasn't a lot to worry about. What I'm concerned with is this being an > issue on a remote system where not being able to get back in after > rebooting with just an updated kernel would (if it happened) be a > serious issue. > > Is there a good way to avoid this? Is it safe to skip rebooting > between the kernel build and userland build? Or would it work to > manually build and install pfctl before the reboot after the kernel > build? Or something else that hasn't occurred to me yet? > > Thanks, > > Chris >
Hi, Following the upgrade.html document may be the best approach. What I typically do is build the release on a system (build kernel as well as all binaries and do a make release) and then follow the upgrade.html approach for remote systems after I am sure nothing at the remote branch will break. In our case the remote branch in question is within driving distance and that makes it less risky for me but the procedure has not failed me for close to 10 years. Before 4.x I used to follow a slightly different approach (pax) but since 4.2 or so I have been following the update.html document verbatim. Vijay Vijay Sankar vsan...@foretell.ca
