If all goes well, tomorrow's build will have a new "C" library. That won't mean much to most end users, but the result is that most, if not all, packages have been rebuilt, and will be upgraded. This will result in something like 300 packages being upgraded if you chose to do that.
Since one of the components being upgraded will be the networking system itself, the upgrade is likely to fail halfway through because it cannot download things while the network was being reset (a problem in the package manager that may have been fixed now). Don't worry, just wait for the reboot and re-run the upgrade. You might even need to repeat this.
I guess at this point, it'd be faster to just re-flash the box, than to run the online upgrade. But hey, that's for you to decide.
PS: Running the upgrade from a telnet or ssh session will fail horriby, since telnet and ssh will be upgraded too, causing the upgrade process to be killed rather suddenly. Running it from the GUI is likely to restore that.
Since one of the components being upgraded will be the networking system itself, the upgrade is likely to fail halfway through because it cannot download things while the network was being reset (a problem in the package manager that may have been fixed now). Don't worry, just wait for the reboot and re-run the upgrade. You might even need to repeat this.
I guess at this point, it'd be faster to just re-flash the box, than to run the online upgrade. But hey, that's for you to decide.
PS: Running the upgrade from a telnet or ssh session will fail horriby, since telnet and ssh will be upgraded too, causing the upgrade process to be killed rather suddenly. Running it from the GUI is likely to restore that.