Date: Mon, 09 Dec 2024 21:36:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283110] freebsd-update IDS vs. installed permissions for kernels (444 vs 555) Message-ID: <bug-283110-227-eK4yNNBHpG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283110-227@https.bugs.freebsd.org/bugzilla/> References: <bug-283110-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283110 --- Comment #8 from wbe@psr.com --- (In reply to John Baldwin from comment #7) > ... you'd have to have some way to know what the distribution metadata is= ... My impression (possibly wrong, since I haven't read the code) is that freebsd-update pulls in copies of the distributions for both the old and new release, and that that's how UpdateIfUnmodified is able to determine whether the file has been modified. If distributions include permissions, then the= re's enough information for a permission comparison. Unfortunately, I now see that this won't work when KeepModifiedMetadata is = true and >1 release has been installed since the permission/metadata change, sin= ce the distribution-change will then look like a user-change from the previous distribution. > Possibly this could just be handled as a special case in freebsd-update > though as files rarely change metadata like permissions. That may well turn out to be easier, faster, and work in more situations. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283110-227-eK4yNNBHpG>