Date: Sat, 20 Feb 2016 20:39:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207377] [10.3-BETA2] freebsd-update relying on kern.bootfile copies around entire filesystem Message-ID: <bug-207377-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207377 Bug ID: 207377 Summary: [10.3-BETA2] freebsd-update relying on kern.bootfile copies around entire filesystem Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: h2+fbsdports@fsfe.org I am just updating to 10.3-BETA2 with freebsd-update and it starting copyin= g my entire filesystem into /boot/kernel.old/ After some debugging I found out that this is due to a mechanism where it detects the kernel dir from kern.bootfile. Since I have a slightly more sophisticated setup where I use grub, this variable ends up being /kernel =3D> freebsd-update assumes that / is the kerneldir and copies *everything*= into the backup dir as mentioned above. I think this is bad behaviour, a smart thing would be to check if the direc= tory pointed to by kern.bootfile actually contains a kernel file, and if not ask= the user to specify the directory or skip the backup process entirely. Most use= rs rely on snapshots nowadays so this step is not really crucial. And / should never be accepted as KERNELDIR IMHO. Thank you! --=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-207377-8>