This has been exhausting so far, so please read if you're going to reply. That's not an insult to you personally, yadayada, but simply me trying to avoid more frustration based on past experiences.
I have never built a custom kernel (and never will), never touched anything for any reason in any non-standard way. I have only ever used freebsd-update the binary, as instructed, very carefully. I've found many others with similar problems for all kinds of FreeBSD versions, but the solutions are always non-existent or involve ugly hacks where you force the text to not be shown, not solving any actual problem, clogging up your system with non-standard garbage and potentially putting you at risk as future updates might not be applied correctly.
If I could, I would simply reinstall the OS. However, I only own one machine and cannot afford the downtime.
The problem:
Whenever I run
I've run
Is there a real way to solve this? A proper way? Why does it happen to begin with? Is the only choice to swallow the hours of downtime (at best) and reinstall the entire damn machine?
The only "reason" I can think of is that I did a non-minor upgrade a few months back, from 9.0 to 9.1. Again, though, all through freebsd-update, with no fancy special commands or tricks. Something is clearly out of sync somewhere, for some reason.
Please note that it's not an option to rebuild the kernel from sources or anything like that.
I wish there were a
I have never built a custom kernel (and never will), never touched anything for any reason in any non-standard way. I have only ever used freebsd-update the binary, as instructed, very carefully. I've found many others with similar problems for all kinds of FreeBSD versions, but the solutions are always non-existent or involve ugly hacks where you force the text to not be shown, not solving any actual problem, clogging up your system with non-standard garbage and potentially putting you at risk as future updates might not be applied correctly.
If I could, I would simply reinstall the OS. However, I only own one machine and cannot afford the downtime.
The problem:
Whenever I run
freebsd-update fetch, it says this:
Code:
# freebsd-update fetch ;
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 9.1-RELEASE from update3.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files are affected by updates, but no changes have
been downloaded because the files have been modified locally:
/var/db/mergemaster.mtree
The following files will be updated as part of updating to 9.1-RELEASE-p4:
/boot/kernel/linker.hintsI've run
freebsd-update install 100 times, rebooted, etc. Nothing helps. It keeps outputting this nonsense. uname -a says I have 9.1-RELEASE-p4 installed. I have no idea what's going on, and again, I have not been doing anything "exotic" or "weird" or "non-standard" or "broken" my box in any way. I also very much doubt it's been compromised.Is there a real way to solve this? A proper way? Why does it happen to begin with? Is the only choice to swallow the hours of downtime (at best) and reinstall the entire damn machine?
The only "reason" I can think of is that I did a non-minor upgrade a few months back, from 9.0 to 9.1. Again, though, all through freebsd-update, with no fancy special commands or tricks. Something is clearly out of sync somewhere, for some reason.
Please note that it's not an option to rebuild the kernel from sources or anything like that.
I wish there were a
freebsd-update fixit command... x(
