On Thu, Jun 06, 2019 at 10:18:46PM +0300, cho...@jtan.com wrote: > Unrelated to my other syspatch email, I ran syspatch inside a chroot (same > server so ignore the identical hostname) and this happened: > > drogo# syspatch > Get/Verify syspatch65-002_srtp.tgz 100% |*************************| 4316 KB > 00:04 > Installing patch 002_srtp > Get/Verify syspatch65-003_mds.tgz 100% |**************************| 49488 KB > 01:03 > Installing patch 003_mds > Relinking to create unique kernel... failed! > drogo# syspatch -l > 002_srtp > 003_mds > drogo# ^D > > Failing to relink the kernel isn't a problem, obviously, because there isn't > one but why did it skip 001_rip6cksum without so much as a comment? > > The chroot was created by simply extracting all the sets (and *etc.tgz), > copying some /etc files and running MAKEDEV.
That is because 001 only includes kernel object files which you do not have since you run under a chroot and didn't extract /usr/share/relink/kernel.tgz So syspatch(8) considers you don't have that "set" installed. syspatch-003 on the other end includes a header change and that header *is* installed on your system. So syspatch installs it. But you are missing all the other pieces to actually relink your kernel and that's why it fails. You are running syspatch under a totally unsupported setup. -- Antoine
