Hi,
I just tried to upgrade my 10.2 install to 10.3. I made sure 10.2 was up to date and as a side note,
The patch list from 10.2 to 10.3 was quite lengthy, but no matter, the
However, I ended up rolling back, I didn't quite have the time to look at the issues, but I saw that files like rc.conf and usb.conf had significant merge conflicts, that after the merge setting like ifconfig_xx had been set to "" ... this seemed a bit strange. I wasn't expecting a point upgrade to cause quite so many merge conflicts.
The rc.conf file had grown a huge amount and it wasn't practical for me to step through every change given the amount of time I had.
Just wondering is it possible to just keep the existing rc.conf/usb.conf files somehow (maybe just cut and paste the old .conf file in) ? I'd hope there would be nothing breaking in a point release and if there is new functionality, I'd rather add it when I need it (to something fundamental like rc.conf)?
I just tried to upgrade my 10.2 install to 10.3. I made sure 10.2 was up to date and as a side note,
pkg upgrade
showed that I had no packages that needed upgrading (I spent some time recently getting everything updated).The patch list from 10.2 to 10.3 was quite lengthy, but no matter, the
freebsd-update
worked.However, I ended up rolling back, I didn't quite have the time to look at the issues, but I saw that files like rc.conf and usb.conf had significant merge conflicts, that after the merge setting like ifconfig_xx had been set to "" ... this seemed a bit strange. I wasn't expecting a point upgrade to cause quite so many merge conflicts.
The rc.conf file had grown a huge amount and it wasn't practical for me to step through every change given the amount of time I had.
Just wondering is it possible to just keep the existing rc.conf/usb.conf files somehow (maybe just cut and paste the old .conf file in) ? I'd hope there would be nothing breaking in a point release and if there is new functionality, I'd rather add it when I need it (to something fundamental like rc.conf)?